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 "Category:OWASP Application Security Metrics Project"
From OWASP
Deleted user (talk | contribs) |
(Reverting to last version not containing links to s1.shard.jp) |
||
| Line 1: | Line 1: | ||
| − | |||
== Welcome to the Application Security Metrics Security Project == | == Welcome to the Application Security Metrics Security Project == | ||
| Line 7: | Line 6: | ||
== Project Guiding Principles: == | == Project Guiding Principles: == | ||
| − | The Application Security Metrics Security Project | + | The Application Security Metrics Security Project Project’s Guiding Principles were created in order to express the intentions of its contributors when designing application security metrics. |
* Effective security metrics have proven to be challenging to develop. As such, provide a means for the OWASP community to initially leverage what others have developed and find useful (i.e., provide the OWASP community useful metrics in use today). | * Effective security metrics have proven to be challenging to develop. As such, provide a means for the OWASP community to initially leverage what others have developed and find useful (i.e., provide the OWASP community useful metrics in use today). | ||
| − | * Where practical, attempt to | + | * Where practical, attempt to “standardize” nomenclature with other security metrics initiatives such as securitymetrics.org, Systems Security Engineering Capability Maturity Model (SSE-CMM), etc. |
| − | * In selecting best practice metrics, make use of high-level filters. For example, use Dr. Dan | + | * In selecting best practice metrics, make use of high-level filters. For example, use Dr. Dan Geer’s decision support mantra regarding security metrics: “How would that proposed measure advance appropriate decision making?" |
| − | * Link each metric to the business driver for the metric (e.g., Metric | + | * Link each metric to the business driver for the metric (e.g., Metric “X” helps support regulatory compliance and risk management objectives.” |
Comments to the editor or endorsements are welcome. | Comments to the editor or endorsements are welcome. | ||
| Line 21: | Line 20: | ||
== Project Scope: == | == Project Scope: == | ||
| − | In keeping with | + | In keeping with OWASP’s mission, this project will focus primarily on application security metrics. Below are some resources with information on application security metrics. |
* [http://www.attrition.org/pipermail/vim/attachments/20060914/42b97c1d/attachment-0001.obj Metrics on reported flaws from Mitre] | * [http://www.attrition.org/pipermail/vim/attachments/20060914/42b97c1d/attachment-0001.obj Metrics on reported flaws from Mitre] | ||
Revision as of 18:00, 29 May 2009
Welcome to the Application Security Metrics Security Project
This OWASP Project will first identify and provide the OWASP community a set of application security metrics that have been found by contributors to be effective in measuring application security. This will be followed by the development of new metrics that build on the initial metrics foundation to fulfill unmet metrics requirements. The goals of this Project are to make a baseline set of application security metrics available to the OWASP community and subsequently to provide a forum for the community to contribute metrics back into the baseline.
Project Guiding Principles:
The Application Security Metrics Security Project Project’s Guiding Principles were created in order to express the intentions of its contributors when designing application security metrics.
- Effective security metrics have proven to be challenging to develop. As such, provide a means for the OWASP community to initially leverage what others have developed and find useful (i.e., provide the OWASP community useful metrics in use today).
- Where practical, attempt to “standardize” nomenclature with other security metrics initiatives such as securitymetrics.org, Systems Security Engineering Capability Maturity Model (SSE-CMM), etc.
- In selecting best practice metrics, make use of high-level filters. For example, use Dr. Dan Geer’s decision support mantra regarding security metrics: “How would that proposed measure advance appropriate decision making?"
- Link each metric to the business driver for the metric (e.g., Metric “X” helps support regulatory compliance and risk management objectives.”
Comments to the editor or endorsements are welcome.
Project Scope:
In keeping with OWASP’s mission, this project will focus primarily on application security metrics. Below are some resources with information on application security metrics.
Feedback and Participation:
We hope you find the OWASP Application Security Metrics Project useful. Please contribute to the Project by volunteering for one of the Tasks, sending your comments, questions, and suggestions to [email protected]. To join the OWASP Application Security Metrics Project mailing list or view the archives, please visit the subscription page.
Project Contributors:
If you contribute to this Project, please add your name here Project Lead:
- Bob Austin of KoreLogic Security. He can be reached at [email protected].
Contributors:
- Cliff Barlow, KoreLogic Security
- James McGovern, The Hartford
Subcategories
This category has only the following subcategory.
O
Pages in category "OWASP Application Security Metrics Project"
The following 2 pages are in this category, out of 2 total.
