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 "Loss of integrity"
From OWASP
(New page: Every '''Technical Impact''' should follow this template. {{Template:Technical Impact}} Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}''' ==Descripti...) |
|||
| Line 1: | Line 1: | ||
| + | {{Template:Stub}} | ||
Every '''[[Technical Impact]]''' should follow this template. | Every '''[[Technical Impact]]''' should follow this template. | ||
Latest revision as of 18:55, 23 October 2008
This article is a stub. You can help OWASP by expanding it or discussing it on its Talk page.
Every Technical Impact should follow this template.
This is a Technical Impact. To view all business impact, please see the Technical Impact page.
Last revision (mm/dd/yy): 10/23/2008
Description
A technical impact is the system damage that results from a successful security breach. This is just the effect on the technology, not the business.
- Start with a one-sentence description of the technical impact
- Describe the technical damage done to the system
- Note the security interest that is damaged - confidentiality, integrity, availability, accountability
- Is the damage immediate or spread over a time period?
Risk Factors
- Talk about the factors that govern this technical 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 Vulnerabilities
Related Controls
Related Business Impacts
