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 "Censure by regulating agency"
From OWASP
(New page: Every '''Business Impact''' should follow this template. {{Template:Business Impact}} Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}''' ==Descriptio...) |
|||
(One intermediate revision by the same user not shown) | |||
Line 1: | Line 1: | ||
+ | {{Template:Stub}} | ||
+ | |||
Every '''[[Business Impact]]''' should follow this template. | Every '''[[Business Impact]]''' should follow this template. | ||
Line 39: | Line 41: | ||
* [http://www.link2.com Title for the link2] | * [http://www.link2.com Title for the link2] | ||
− | [Category:Non-compliance]] | + | [[Category:Non-compliance]] |
Latest revision as of 18:49, 23 October 2008
This article is a stub. You can help OWASP by expanding it or discussing it on its Talk page.
Every Business Impact should follow this template.
This is a Business Impact. To view all business impact, please see the Business Impact page.
Last revision (mm/dd/yy): 10/23/2008
Description
A business impact is the damage that results from a successful security breach. This should be the highest level impact to the business, not a glorified technical impact.
- Start with a one-sentence description of the business impact
- Describe the damage done to the business - money, loss of life, reputation, loss of customers, compliance, legal exposure
- Is the damage immediate or spread over a time period?
Risk Factors
- Talk about the factors that govern this business impact
- Try to be clear about the factors that make this impact serious
Examples
Short example name
- A short example description, small picture, or sample code with links
Short example name
- A short example description, small picture, or sample code with links
Related Technical Impacts