Software Security Frameworks
Download as PPT, PDF5 likes3,310 views
This document discusses building security into the software development life cycle (SDLC) through a business case approach. It outlines the costs of application security versus software security. Adopting a formal secure SDLC process using security enhancing models can reduce costs by finding and fixing defects earlier. Making an initial business case by assessing return on security investment and integrating software security with overall risk management is recommended. Regularly reviewing the business case ensures commitment to security throughout the SDLC.
![Building Security Into The Software Life Cycle A Business Case Marco M. Morana Senior Consultant Foundstone Professional Services a Division of McAfee Email: [email_address]](https://image.slidesharecdn.com/turbotalkblackhat-2006-marco-morana-building-security-into-slc-1227743787068099-8/85/Software-Security-Frameworks-1-320.jpg)
Software Security Frameworks
- 1. Building Security Into The Software Life Cycle A Business Case Marco M. Morana Senior Consultant Foundstone Professional Services a Division of McAfee Email: [email_address]
- 2. Outline Glossary Application Security Risks Software Security and Application Security Costs and Return Of Security Investment (ROSI) Software Security Development Life Cycle (S-SDLC) Process Models and Frameworks Business Risks, Technical Risks and Strategies Summary Resources
- 3. Glossary Information Security Risks : the probability that a particular threat-source will exercise a particular information system vulnerability and the resulting impact if this should occur (NIST publication 800-27) Software Security: a way to defend against software exploits by building software to be secure (McGraw Exploiting Software) Application Security : a way to defend against software exploits in a post-facto way after deployment is complete (McGraw Exploiting Software) Return Of Security Investment in Security (ROSI) : The total amount of money that an organization is expected to save in a year by implementing a security control (Microsoft Security Risk Management Guide)
- 4. What is at risk?
- 5. How we approach risk? Application Security Issue-based, short-term approach * Penetrate and Patch * Threat Modeling * Code Reviews Software Security Holistic, long-term approach * Root Cause Analysis * Organizational Change
- 6. What are the costs? Application Security Costs: Defect Management: 5 defects/KLOC, $ 30,000/KLOC (Business week) Patch Management: 1000 servers, $ 300,000 to test and deploy a patch (Gartner) Loss of productivity due of loss of service: $ 500 ML lost from DoS attack (Microsoft) Software Security Costs: Unbudgeted time to fix security problems:1000 man-hours (Microsoft) Cost of training software developers in security: $100 Million (Microsoft) Inadequate software testing costs: $3.3 billion (NIST)
- 7. When we do address the problem? Today most people test after software is built!
- 8. When is more cost effective to build security in? Assume the following data from a study (IBM) : - Secure Software Engineering Expense Per Phase - Number of Security Defects found Per Phase - Percentage of Vulnerabilities Fixed The Return Of Security Investment (ROSI) in dollar savings for every $ 100,000 spent is: - $ 21,000 when defects are fixed and identified during design - $ 15,000 when defects are fixed during implementation - $ 12,000 when defects are fixed during tests
- 9. Software Risk Management and Secure Software Development Life Cycles (S-SDLC)
- 10. How do we get there? Adopt an activity driven approach Document security activities derived by best practices Define dependencies and prerequisites Define entry scenarios for the activities Define strategic and tactical tracks for the activities Define the roadmaps for software security Position the activities with respect to different SDLC methodologies
- 11. Enhance security through a repeatable and measurable process Provide guidance on secure software activities Provide secure software development reviews Include tactical resources Provision the use of automation tools Suggest roles for conducting the activities Integrate with foundational software development activities Security-Enhancing Lifecycle Process Models
- 12. Security Enhancing Process Models Microsoft’s Trustworthy Computing Security Development Lifecycle
- 13. Security Enhancing Process Models Comprehensive Lightweight Application Security Process (CLASP)
- 14. Security Enhancing Process Models Gary McGraw Touch-Point Model
- 15. Security Enhancing Process Models SEI Team Software Process for Secure Software Development
- 17. Business Risks, Technical Risks and Strategies Business Risk Factors: - Business impact - Value of the assets - Information risk management Technical Risks Factors: - Technical impacts - Value of data - Software risks associated to threats and vulnerabilities Risk Remediation Strategies: - Cost to fix vulnerabilities vs. cost of exploitation - Translate technical risks to business risks - Assess, evaluate and prioritize by business impact
- 18. In Summary Make the initial business case - Costs - Return Of Security Investment (ROSI) Adopt a formal process to build security into the SDLC - Security Enhancing Process Models - Software Security Frameworks Have a plan for the implementation - Tactical and strategic plans - Roadmaps: short term and long term Integrate Software Security with Information Security Risks - Assess business impacts - Factor technical and business impacts in overall risks Review the business case and commit to it - Measure overall risk and decide strategies - Commit people, process and technology
- 19. Questions?
- 20. Thank you for listening! Foundstone Links Foundstone Software Application Security Services (SASS) www.foundstone.com /sass Foundstone Resources www.foundstone.com/resources.overview.htm