SlideShare utilise les cookies pour améliorer les fonctionnalités et les performances, et également pour vous montrer des publicités pertinentes. Si vous continuez à naviguer sur ce site, vous acceptez l’utilisation de cookies. Consultez nos Conditions d’utilisation et notre Politique de confidentialité.
SlideShare utilise les cookies pour améliorer les fonctionnalités et les performances, et également pour vous montrer des publicités pertinentes. Si vous continuez à naviguer sur ce site, vous acceptez l’utilisation de cookies. Consultez notre Politique de confidentialité et nos Conditions d’utilisation pour en savoir plus.
Forcing muscle growth is a long process which requires high intensity weight training and high mental concentration. While the ultimate goal is often clear, one of the greatest mistakes bodybuilders consistently make is to overlook the importance of tracking their weight lifting progress. Like a successful bodybuilding workout, a security development lifecycle program must consistently log simple to obtain, yet meaningful metrics throughout the entire process. Good metrics must lack subjectivity and clearly aid decision makers to determine areas that need improvement. In this pragmatic presentation we’ll discuss metrics used at Symantec, the world’s largest security ISV, to classify and appropriately compare security vulnerabilities found in different phases of the SDL by different teams working in different locations and in different products. We’ll also discuss how to easily provide decision makers different views of the same data and verify whether the process is indeed catching critical vulnerabilities internally and how the numbers compare with the competition.
Cassio Goldschmidt is senior manager of the product security team under the Office of the CTO at Symantec Corporation. In this role he leads efforts across the company to ensure the secure development of software products. His responsibilities include managing Symantec’s internal secure software development process, training, threat modeling and penetration testing. Cassio’s background includes over 13 years of technical and managerial experience in the software industry. During the seven years he has been with Symantec, he has helped to architect, design and develop several top selling product releases, conducted numerous security classes, and coordinated various penetration tests. Cassio is also internationally known for leading the OWASP chapter in Los Angeles.Cassio represents Symantec on the SAFECode technical committee and (ISC)2 in the development of the CSSLP certification. He holds a bachelor degree in computer science from PontificiaUniversidadeCatolica do Rio Grande Do Sul, a masters degree in software engineering from Santa Clara University, and a masters of business administration from the University of Southern California.
Tracking the Progress of an SDL Program: Lessons from the Gym
Tracking the Progress of an SDL ProgramLessons from the Gym<br />Cassio Goldschmidt<br />June 29th, 2009<br />
Common Weakness EnumerationWhat is it?<br />A common language for describing software security weaknesses<br />Maintained by the MITRE Corporation with support from the National Cyber Security Division (DHS). <br />Hierarchical<br />Each individual CWE represents a single vulnerability type<br />Deeper levels of the tree provide a finer granularity<br />Higher levels provide a broad overview of a vulnerability<br />11<br />
Common Weakness EnumerationPortion of CWE structure<br />12<br />
Common Weakness EnumerationWhat data is available for each CWE?<br />Weakness description<br />Applicable platforms and programming languages<br />Common Consequences<br />Likelihood of Exploit<br />Coding Examples<br />Potential Mitigations<br />Related Attacks<br />Time of Introduction<br />Taxonomy Mapping<br />13<br />Link to CWE Page on XSS<br />
Common Weakness Enumeration How useful is this information?<br />14<br />Pie Chart showing the frequency of CWEs<br />found in penetration tests<br />
Objective (and “perfect enough”) metric<br />A universal way to convey vulnerability severity<br />Can be used for competitive analysis<br />CVSS score ranges between 0.0 and 10.0<br />Can be expressed as high, medium, low as well<br />Composed of 3 vectors<br />Base<br />Represents general vulnerability severity: Intrinsic and immutable<br />Temporal<br />Time-dependent qualities of a vulnerability<br />Environmental<br />Qualities of a vulnerability specific to a particular IT environment<br />16<br />Common Vulnerability Scoring System (CVSS)What is it?<br />
17<br />Common Vulnerability Scoring System (CVSS)BASE Vector<br />Exploitability<br />Impact<br />Sample Score: 7.5<br />Sample Vector: (AV:N/AC:L/Au:N/C:P/I:P/A:P)<br />Every CVSS score should be accompanied by the corresponding vector<br />
18<br />Common Vulnerability Scoring System (CVSS)The Calculator<br />
Managers: Secure Development Lifecycle (also known as Symmunize)</li></li></ul><li>Training and Metrics Security Learning Process<br />24<br />Quality Assurance - Capture the flag<br /><ul><li> Use Beta software
Top 3 finders receive prizes and are invited to explain what techniques and tools they used to find the vulnerabilities to the rest of the group</li></li></ul><li>Training and Metrics Security Learning Process<br />25<br />Pos Class Survey<br /><ul><li> Anonymous