Definition
Defense in depth is the deliberate use of multiple, independent safeguards around important systems, identities, data, and operations. The layers should not all fail for the same reason.
Why it matters
Every control can be bypassed, misconfigured, unavailable, or used incorrectly. Layering gives defenders more opportunities to prevent, detect, contain, and recover from a problem.
Common layers
- Identity controls such as multifactor authentication and least privilege
- Endpoint prevention, hardening, detection, and response
- Network segmentation and controlled pathways
- Application security and data protection
- Monitoring, alerting, incident response, and tested recovery
Common mistake
Adding many tools is not automatically defense in depth. The controls must address meaningful failure modes, exchange useful context, and be operated consistently.
BMC v0.2.2 cornerstone expansion
Start analysis of Defense in Depth with the mission or business outcome, then identify assets, identities, data, trust boundaries, dependencies, expected behavior, and credible failure or abuse cases.
Translate those observations into preventive, detective, responsive, and recovery controls. A mature explanation states not only what the concept is, but also how a practitioner demonstrates that it is working under normal, abnormal, and recovery conditions.
Evidence of effective implementation
- Documented ownership, scope, decision criteria, and permitted exceptions.
- Configuration or architectural evidence tied to a clear control objective.
- Operational telemetry showing expected and unexpected behavior.
- Testing that covers normal use, abuse cases, failure, rollback, and recovery.
- Exceptions that are approved, time bounded, monitored, and revisited.
- Lessons learned that result in updated designs, procedures, detections, or training.
Questions for learners
- Which security properties and business outcomes does Defense in Depth support?
- What assumptions must remain true for the control or process to work safely?
- What could an attacker, insider, failure, or design error do at each trust boundary?
- Which evidence would prove that controls work continuously rather than only on paper?
- How would the organization respond, restore service, and re-establish trust after failure?
Certification relevance
This subject appears in or supports the following certification bodies of knowledge: