Ivan Medvedev - Security Development Lifecycle Tools
4 likes1,450 views
Microsoft is continually improving its Security Development Lifecycle (SDL) process and tools to help developers build more secure software. Key takeaways from the presentation include that Microsoft is investing in SDL support and customers should use the available tools to enhance security. The presentation provided overviews of SDL tools for requirements and design, implementation, verification, and response. Microsoft is also announcing a new BlueHat Prize to encourage innovation in mitigating memory safety vulnerabilities.
Ivan Medvedev - Security Development Lifecycle Tools
- 1. Ivan Medvedev Principal Security Development Lead Microsoft Corporation
- 2. Session Objectives and Takeaways Session Objective(s): β’ Give an overview of the Security Development Lifecycle β’ Discuss the externally available tools that support the SDL β’ Provide guidance on using the tools to build more secure software Key takeaways: β’ Microsoft is investing into supporting the SDL β’ Customers should use the tools to build more secure software
- 3. Security Timeline at Microsoftβ¦ Now β’ Optimize the process 2005-2007 through feedback, analysis and automation β’ SDL is enhanced β’ Evangelize 2004 β’ βFuzzβ testing the SDL to the software β’ Microsoft Senior β’ Code analysis development community: 2002-2003 Leadership Team agrees β’ Crypto design β’ SDL Process Guidance requirements SDL Optimization Model to require SDL for all β’ β’ Bill Gates writes β’ Privacy SDL Pro Network products that: β’ βTrustworthy Computingβ β’ Are exposed to β’ Banned APIs β’ SDL Threat Modeling Tool memo early 2002 meaningful risk and/or β’ and moreβ¦ β’ SDL Process Templates β’ βWindows security pushβ β’ Process sensitive data β’ Windows Vista is the for Windows Server 2003 first OS to go through full SDL cycle β’ Security push and FSR extended to other products
- 4. SDL β Continual Improvement Microsoftβs secure development processes have come a long way since the SDL was first introduced β the SDL is constantly evolving
- 5. SDL for Spiral/Waterfall Development Education Process Accountability Ongoing Process Improvements
- 6. SDL for Agile Development Simple: Major differentiators of Agile: No distinct phases Short release cycles Comprehensive: Customizable:
- 7. What About the Cloud? Native code requirements address implementation of cloud services SDL has applied to web properties since v3.2 β’ Requirements address issues such as cross site scripting and SQL injection Cloud services and web properties often use agile development models β’ βProduct cycleβ might be 2 weeks, not three years Multiple iterations of SDL for agile development since 2006
- 8. Motivation for Action The application space is under attack things are bad, and getting worse β’ Users now expect security *without* having to pay for it Software security and holistic development practices are becoming a competitive differentiator β’ Procurement Showing up in government regulations β’ DISA STIG β’ NIST Smart Grid Requirements Failure to show forward momentum will lead to unintended consequences and loss of consumer trust
- 9. Tools for SDL: Requirements and Release SDL Process Template MSF-Agile + SDL Process Template
- 10. SDL Template for VSTS (Spiral) Incorporates β’ SDL requirements as work items β’ SDL-based check-in policies β’ Generates Final Security Review report β’ Third-party security tools β’ Security bugs and custom queries β’ A library of SDL how-to guidance Integrates with previously released free SDL tools β’ SDL Threat Modeling Tool The SDL Process Template integrates SDL 4.1 directly β’ Binscope Binary Analyzer into the VSTS software development environment. β’ Minifuzz File Fuzzer
- 11. MSF Agile + SDL Template for VSTS Automatically creates new security workflow items for SDL requirements whenever users check in code or create new sprints Ensures important security processes are not accidentally skipped or forgotten Integrates with previously released free SDL tools β’ SDL Threat Modeling Tool β’ Binscope Binary Analyzer Incorporates SDL-Agile secure development practices β’ Minifuzz File Fuzzer directly into the Visual Studio IDE - now available as beta (planned release at the end of Q2CY10) Will be updated for VS2010
- 12. Tools for SDL: Design SDL Threat Modeling Tool
- 13. SDL Threat Modeling Tool Transforms threat modeling from an expert-led Provides: process into a process that any software β’ Guidance in drawing threat diagrams architect can perform effectively β’ Guided analysis of threats and mitigations β’ Integration with bug tracking systems β’ Robust reporting capabilities
- 15. Tools for SDL: Implementation Banned.h Code Analysis for C/C++ β’ Visual Studio Premium and Ultimate Microsoft Code Analysis Tool .NET (CAT.NET) 1.0 CTP β’ Detects common web app vulnerabilities, like XSS FxCop 10.0 β’ Standalone or integrated into VS Premium and Ultimate Anti-Cross Site Scripting (Anti-XSS) Library 4.0 SiteLock ATL Template
- 18. Tools for SDL: Verification BinScope Binary Analyzer β’ Ensures the build process followed the SDL MiniFuzz File Fuzzer β’ !exploitable RegexFuzer Attack Surface Analyzer Beta β’ Snapshot based analysis AppVerifier β’ Dynamic analysis
- 19. Binscope Binary Analyzer Provides an extensive analysis of an application binary Checks done by Binscope β’ /GS - to prevent buffer overflows β’ /SafeSEH - to ensure safe exception handling β’ /NXCOMPAT - to prevent data execution β’ /DYNAMICBASE - to enable ASLR β’ Strong-Named Assemblies - to ensure unique key pairs and strong integrity checks β’ Known good ATL headers are being used Use either standalone or integrated with Visual Studio (VS) and Team Foundation Server (TFS)
- 21. MiniFuzz File Fuzzer MiniFuzz is a basic testing tool designed to help detect code flaws that may expose security vulnerabilities in file-handling code. β’ Creates corrupted variations of valid input files β’ Exercises the code in an attempt to expose unexpected application behaviors. β’ Lightweight, for beginner or advanced security testing β’ Use either standalone or integrated with Visual Studio (VS) and Team Foundation Server (TFS)
- 22. !exploitable Creates hashes to determine the uniqueness of a crash Assigns an exploitability rating to the crash: Exploitable, Probably Exploitable, Probably Not Exploitable, or Unknown. An extension of Microsoft debuggers β’ windbg badapp.exe usersmikedesktopminifuzzcrashesfoobar8776.bad β’ !load winextmsec.dll β’ Run the process and have it parse the file: g β’ Finally, run !exploitable to take a first pass analysis of the failure: !exploitable Open source http://msecdbg.codeplex.com/
- 24. Attack Surface Analyzer Takes system attack surface snapshots One before and one after installing the product Compares the snapshots and generates a report
- 27. EMET: Simplifying mitigation deployment GUI and command line interface Configure system-wide mitigations Enable mitigations for specific applications Verify mitigation settings
- 28. EMET: Protecting applications Protect at-risk or known vulnerable applications Protect against active 0day attacks in the wild Granular control over which mitigations are enabled
- 29. Important Resources Microsoft SDL Portal http://microsoft.com/sdl SDL Tools (with download links and training/videos) http://www.microsoft.com/security/sdl/adopt/tools.aspx Visual Studio 2010 http://msdn.microsoft.com/en-us/vstudio/aa718325 FxCop documentation http://msdn.microsoft.com/en-us/library/dd264939(v=VS.100).aspx !exploitable http://msecdbg.codeplex.com/ MSEC http://www.microsoft.com/security/msec.aspx
- 30. BlueHat Prize Announcement First BlueHat Prize Challenge: β’ Design a novel runtime mitigation technology that is capable of preventing the exploitation of memory safety vulnerabilities Entry Period: Aug 3, 2011 β Apr 1, 2012 Winners announced: BlackHat USA August 2012 IP remains the property of the inventor, with a license for Microsoft to use the technology Grand Prize: β’ $200,000 in cash Second Prize: β’ $50,000 in cash Third Prize: β’ MSDN subscription ($10,000 value)
- 31. Examples of Mitigation Technology Data Execution Prevention (DEP) β’ Sets non executable memory pages Address Space Layout Randomization (ASLR) β’ Randomizes memory in which apps load Structured Exception Handler Overwrite Protection (SEHOP) β’ Verifies exception handler lists have not been corrupted Mitigation tools from Microsoft: Download EMET
- 32. BlueHat Prize Judging Criteria Practicality β 30% β’ Can the solution be implemented and deployed at a large scale on Windows? β’ Overhead must be low (e.g. CPU and memory cost no more than 5%). β’ No application compatibility regressions should occur. β’ No usability regressions should occur. β’ Reasonable to develop, test, and deploy. Robustness β 30% β’ How easy would it be to bypass the proposed solution? Impact β 40% β’ Does the solution strongly address key open problems or significantly refine an existing approach? β’ Would the solution strongly mitigate modern exploits above and beyond our current arsenal?
- 33. For More Information⦠BlueHat Prize Web site: www.bluehatprize.com ⒠Questions? bluehatprize.@microsoft.com MSRC Blog: http://blogs.technet.com/msrc EcoStrat Blog: http://blogs.technet.com/ecostrat/ Help Defend the Planet: http://careers.microsoft.com Follow us on Twitter: @k8em0 and @MSFTSecResponse
- 34. In Review: Session Objectives and Takeaways Session Objective(s): β’ Give an overview of the Secure Development lifecycle β’ Discuss the externally available tools that support the SDL β’ Provide guidance on using the tools to build more secure software Key takeaways: β’ Microsoft is investing into supporting the SDL β’ Our customers should use the tools to build more secure software
- 35. We are hiring