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
Difference between revisions of "OWASP Application Security Program Quick Start Guide Project"
From OWASP
KateHartmann (talk | contribs) (Created page with "=Main= <!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --> <div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">link=</...") |
Gabrielgumbs (talk | contribs) (→Main) |
||
Line 16: | Line 16: | ||
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--> | <!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--> | ||
<span style="color:#ff0000"> | <span style="color:#ff0000"> | ||
− | This is | + | This guide is intended to be a short, straightforward introductory guide to standing-up or improving an Application Security Program . The intended goal of the AppSec program is to implement measures throughout the code's life-cycle to prevent gaps in the application security policy or the underlying system through flaws in the design, development, deployment, upgrade, or maintenance of the application. |
+ | The application security program should effectively manage the security of its application systems, protecting information from unauthorized access, use, disclosure, disruption, modification, or destruction in order to provide integrity, confidentiality and availability. | ||
+ | A fundamental component of this improved application security management is the ability to demonstrate acceptable levels of risk based on defined KPIs, including but limited to: | ||
+ | • The number of vulnerabilities present in an application | ||
+ | • The time to fix vulnerabilities | ||
+ | • The remediation rate of vulnerabilities | ||
+ | • The time vulnerabilities remain open. | ||
+ | The application security program deliverables include a holistic view of the state of security for each application, identifying the risks associated with the application and the countermeasures implemented to mitigate those risks, explaining how security is implemented, planning for system downtimes and emergencies, and providing a formal plan to improve the security in one or more of these areas. | ||
+ | |||
</span> | </span> | ||
Revision as of 15:20, 1 December 2014