This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org

OWASP Software Security Assurance Process

From OWASP
Revision as of 16:44, 5 February 2014 by Mateo Martínez (talk | contribs)

Jump to: navigation, search

Main

The OWASP Software Security Assurance Process (OSSAP) main intent is to embed security in the software development lifecycle (SDLC). OSSAP reduces the possibility of requirement oversights, design flaws, implementation bugs and deployment configuration mistakes during the SDLC. This project outlines mandatory and recommended processes and practices to manage risks associated with applications. What is exactly Software Assurance? Software assurance is defined as the level of confidence that software is free from vulnerabilities, either intentionally designed into the software or accidentally inserted at any time during its life cycle, and that the software functions in the intended manner. Reference: mitre.org

  • Project Roadmap
  • OSSAP Sub-Processess
  • Mapping OSSAP to OpenSAMM

OWASP Software Security Assurance Processess

  • Software Security Integration in the SDLC Process
  • Security Requirements Identification Process
  • Design Security Review Process
  • Architecture Security Review Process
  • Security Code Review Process
  • Security Testing Process
  • Deployment Security Review Process
  • Release Security Review Process

Project About

PROJECT INFO
What does this OWASP project offer you?
RELEASE(S) INFO
What releases are available for this project?
what is this project?
Name: OWASP Software Security Assurance Process (home page)
Purpose: To outlines mandatory and recommended processes and practices to manage risks associated with applications. Software Security is equally dependent on people, processes and technology. The effectiveness of the OWASP Software Security Process is continuously measured and is improved through feedback, threat landscape changes, availability of new concepts and tools. Should be the framework to map Requirements, Dev and Testing guidelines for example.
License: Creative Commons Attribution ShareAlike 3.0 license
who is working on this project?
Project Leader(s):
Project Contributor(s):
how can you learn more?
Project Pamphlet: Not Yet Created
Project Presentation:
Mailing list: Mailing List Archives
Project Roadmap: View
Key Contacts
current release
Not Yet Published
last reviewed release
Not Yet Reviewed


other releases