Modeling Software VulnerabilitiesWith Vulnerability Cause Graphs

Byers, David; Ardi, Shanai; Shahmehri, Nahid; Duma, Claudiu

doi:10.1109/icsm.2006.40

Cited by 32 publications

(19 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…As future work, we are investigating several approaches to improve the passive testing algorithms in order to perform online monitoring, possibly by including vulnerability cause graphs [4] of the implementation under test. We are also studying the different reactions that the network has to perform following a property violation detection.…”

Section: Discussionmentioning

confidence: 99%

Distributed Monitoring in Ad Hoc Networks: Conformance and Security Checking

Mallouli

Wehbi

Cavalli

2008

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. Ad hoc networks are exposed more than traditional networks to security threats due to their mobility and open architecture aspects. In addition, any dysfunction due to badly configured nodes can severely affect the network as all nodes participate in the routing task. For these reasons, it is important to check the validity of ad hoc protocols, to verify whether the running implementation is conform to its specification and to detect security flows in the network. In this paper, we propose a formal methodology to collect and analyze the network traffic trace. Observers running on a set of nodes collect local traces and send them later to a global observer that correlates them into a global trace thanks to an adapted time synchronization mechanism running in the network. The global trace is then analyzed to study the conformance and the security of the running routing protocol. This analysis is performed using dedicated algorithms that check the collected trace against a set of functional and security properties specified in an adapted formal language.

show abstract

Section: Discussionmentioning

confidence: 99%

Distributed Monitoring in Ad Hoc Networks: Conformance and Security Checking

Mallouli

Wehbi

Cavalli

2008

Lecture Notes in Computer Science

View full text Add to dashboard Cite

show abstract

“…Vulnerability modeling [5] is a process similar to root cause analysis, and results in a structure called a vulnerability cause graph (VCG), that models how causes (conditions or events that may contribute to the presence of a vulnerability; e.g. "Use of strcat") may contribute to the presence of software vulnerabilities.…”

Section: Process Stepsmentioning

confidence: 99%

“…Our process [2] consists of three major steps: vulnerability modeling [5], vulnerability cause mitigation [1], and process component definition. The process is described in section 2.…”

Section: Introductionmentioning

confidence: 99%

Design of a Process for Software Security

Byers

Shahmehri

2007

The Second International Conference on Availability, Reliability and Security (ARES'07)

Self Cite

View full text Add to dashboard Cite

Security is often an afterthought when developing software, and is often bolted on late in development or even during deployment or maintenance, through activities such as penetration testing, add-on security software and penetrate-and-patch maintenance. We believe that security needs to be built in to the software from the beginning, and that security activities need to take place throughout the software lifecycle. Accomplishing this effectively and efficiently requires structured approach combining a detailed understanding on what causes vulnerabilities, and how to prevent them.In this paper we present a process for software security that is based on vulnerability cause graphs, a formalism we have developed for modeling the causes of software vulnerabilities. The purpose of the software security process is to evolve the software development process so that vulnerabilities are prevented. The process we present differs from most current approaches to software security in its high degree of adaptability and in its ability to evolve in step with changing threats and risks. This paper focuses on how to apply the process and the criteria that have influenced the process design.

show abstract

“…structured way [3,6,8]. S 3 P is designed to be process agnostic and is a software development improvement process that runs in parallel to the software life cycle and interacts with it to enhance security.…”

Section: Introductionmentioning

confidence: 99%

Integrating a Security Plug-in with the OpenUP/Basic Development Process

Ardi

Shahmehri

2008

2008 Third International Conference on Availability, Reliability and Security

Self Cite

View full text Add to dashboard Cite

In this paper we present a security plug-in for the OpenUP/Basic development process. Our security plug-in is based on a structured unified process for secure software development, named S 3 P (Sustainable Software Security Process). This process provides the formalism required to identify the causes of vulnerabilities and the mitigation techniques that prevent these vulnerabilities. We also present the results of an expert evaluation of the security plug-in. The lessons learned from development of the plug-in and the results of the evaluation will be used when adapting S 3 P to other software development processes.

show abstract

Modeling Software VulnerabilitiesWith Vulnerability Cause Graphs

Cited by 32 publications

References 6 publications

Distributed Monitoring in Ad Hoc Networks: Conformance and Security Checking

Distributed Monitoring in Ad Hoc Networks: Conformance and Security Checking

Design of a Process for Software Security

Integrating a Security Plug-in with the OpenUP/Basic Development Process

Contact Info

Product

Resources

About