defensive-depth is a human-made security architecture that layers multiple independent controls so the failure of any single one does not compromise the protected asset. It is carved by: (1) heterogeneous barriers (different mechanisms, not redundant copies of the same), (2) independence (failure of one layer does not impair others), (3) progression resistance (an attacker must defeat each layer sequentially, increasing detection probability and effort), and (4) coverage gaps (deliberately overlapping zones of control to eliminate blind spots). It persists through design standards, security policies, and implementation practices that mandate layered protection in system architecture. [formal: defensiopluralis | substrate: behavior | horizon: a life | explicit: yes | epoch: 0.42]
Accepted ontology entry
defensive-depth
defensive-depth is a human-made security architecture that layers multiple independent controls so the failure of any single one does not compromise the protected asset. It is carved by: (1) heterogeneous barriers (different mechanisms, no…
Definition
Why it is in scope
A human-made security architecture principle that layers multiple independent controls so that the failure of any single control does not compromise the whole system. Built to persist through design standards, architectural reviews, and compliance frameworks that mandate layered protection.
Names and aliases
- defensive-depthen · CANONICAL
Relations from this entry
- cmrhnc65902098aehuxnv9f0wSERVES →
defensive-depth is designed and maintained for the sake of security: layering defenses exists specifically to further security's operation. SERVES direction correct — servant (defensive-depth) points at master (security).
- cms9293jz002i7skq3m4d9hr1SERVES →
Defensive depth (layered protection) is designed and maintained for the sake of safety management — its purpose is to provide multiple independent layers of defense so that safety management can ensure no single failure compromises the system.
Relations to this entry
No accepted relations in this direction.
Record identity
- Created
- Jul 31, 2026, 1:51 AM UTC
- Content hash
- e8f3fbae8872776a5ffa0f8ec647249270dad981a67861a068aef9075bdd0131