Difference between revisions of "Defense in depth"

From OWASP
Jump to: navigation, search
(Began the conforming the article to the Principles Template)
Line 3: Line 3:
 
{{Template:Stub}}
 
{{Template:Stub}}
  
==Overview==
+
==Description==
  
 
The principle of defense in depth suggests that where one control would be reasonable, more controls that approach risks in different fashions are better. Controls, when used in depth, can make severe vulnerabilities extraordinarily difficult to exploit and thus unlikely to occur.  
 
The principle of defense in depth suggests that where one control would be reasonable, more controls that approach risks in different fashions are better. Controls, when used in depth, can make severe vulnerabilities extraordinarily difficult to exploit and thus unlikely to occur.  
Line 9: Line 9:
 
With secure coding, this may take the form of tier-based validation, centralized auditing controls, and requiring users to be logged on all pages.  
 
With secure coding, this may take the form of tier-based validation, centralized auditing controls, and requiring users to be logged on all pages.  
  
For example, a flawed administrative interface is unlikely to be vulnerable to anonymous attack if it correctly gates access to production management networks, checks for administrative user authorization, and logs all access.  
+
==Examples==
 +
 
 +
===Vulnerable Administrative Interface===
 +
:A flawed administrative interface is unlikely to be vulnerable to anonymous attack if it correctly gates access to production management networks, checks for administrative user authorization, and logs all access.  
  
 
[[Category:Principle]]
 
[[Category:Principle]]

Revision as of 16:31, 23 May 2008

This is a principle or a set of principles. To view all principles, please see the Principle Category page.

This article is a stub. You can help OWASP by expanding it or discussing it on its Talk page.


Description

The principle of defense in depth suggests that where one control would be reasonable, more controls that approach risks in different fashions are better. Controls, when used in depth, can make severe vulnerabilities extraordinarily difficult to exploit and thus unlikely to occur.

With secure coding, this may take the form of tier-based validation, centralized auditing controls, and requiring users to be logged on all pages.

Examples

Vulnerable Administrative Interface

A flawed administrative interface is unlikely to be vulnerable to anonymous attack if it correctly gates access to production management networks, checks for administrative user authorization, and logs all access.