Difference between revisions of "Loss of availability"

From OWASP
Jump to: navigation, search
(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 13:56, 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.

  1. Start with a one-sentence description of the technical impact
  2. Describe the technical damage done to the system
  3. Note the security interest that is damaged - confidentiality, integrity, availability, accountability
  4. 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


References