Defense in depth (computing): Difference between revisions

Revision as of 19:56, 9 October 2024

Latest revision as of 12:45, 22 July 2025

(17 intermediate revisions by 7 users not shown)

Line 1:

{{Short description|Concept in information security}}

{{more citations needed|date=April 2012}}

'''Defense in depth''' is a concept used in [[information security]] in which multiple layers of security controls (defense) are placed throughout an [[information technology]] (IT) system. Its intent is to provide [[Redundancy (engineering)|redundancy]] in the event a [[Security controls|security control]] fails or a vulnerability is exploited that can cover aspects of ''personnel'', ''procedural'', ''technical'' and ''physical'' security for the duration of the system's life cycle.

== Background ==

The idea behind the defense in depth approach is to defend a system against any particular attack using several independent methods.<ref name=schneier2006>[https://www.schneier.com/blog/archives/2006/02/security_in_the.html Schneier on Security: Security in the Cloud]</ref> It is a layering tactic, conceived<ref>{{Cite web|title=Some principles of secure design. Designing Secure Systems module Autumn PDF Free Download|url=https://docplayer.net/17241198-Some-principles-of-secure-design-designing-secure-systems-module-autumn-2015.html|access-date=2020-12-12|website=docplayer.net |archiveurl=https://web.archive.org/web/20240511022456/https://docplayer.net/17241198-Some-principles-of-secure-design-designing-secure-systems-module-autumn-2015.html | archivedate=11 May 2024}}</ref> by the [[National Security Agency]] (NSA) as a comprehensive approach to information and electronic security.<ref name=nsa1>[https://web.archive.org/web/20121002051613/https://www.nsa.gov/ia/_files/support/defenseindepth.pdf Defense in Depth: A practical strategy for achieving Information Assurance in today’s highly networked environments.]</ref><ref name=owasp1>[https://cheatsheetseries.owasp.org/cheatsheets/Secure_Product_Design_Cheat_Sheet.html#2-the-principle-of-defense-in-depth OWASP CheatSheet: Defense in depth]</ref> The term defense in depth in computing is inspired by a military [[strategy]] of [[Defence in depth|the same name]], but is quite different in concept. The military strategy revolves around having a weaker perimeter defense and intentionally yielding space to buy time, envelop, and ultimately counter-attack an opponent, whereas the information security strategy simply involves multiple layers of controls, but not intentionally ceding ground (''cf.'' [[Honeypot (computing)|honeypot.]])

[[File:Defense In Depth - Onion Model.svg|thumb|right|The [[onion model]] of defense in depth]]An insight into defense in depth can be gained by thinking of it as forming the layers of an onion, with data at the core of the onion, people the next outer layer of the onion, and [[network security]], host-based security, and [[application security]] forming the outermost layers of the onion.<ref>{{Cite book|chapter=Security Onion Control Scripts|date=2014|chapter-url=http://dx.doi.org/10.1016/b978-0-12-417208-1.09986-4|title=Applied Network Security Monitoring|pages=451–456|publisher=Elsevier|doi=10.1016/b978-0-12-417208-1.09986-4|isbn=978-0-12-417208-1|access-date=2021-05-29}}</ref> Both perspectives are equally valid, and each provides valuable insight into the implementation of a good defense in depth strategy.{{cn|date=July 2025}}

== Controls ==

Line 10 ⟶ 11:

=== Physical ===

Physical controls<ref name="nsa1" /> are anything that physically limits or prevents access to IT systems. FencesExamples of physical defensive security are: fences, guards, dogs, and [[Closed-circuit television|CCTV]] systems and the like.

=== Technical ===

Technical controls are hardware or software whose purpose is to protect systems and resources. Examples of technical controls would be disk encryption, Filefile integrity software, and authentication. Hardware technical controls differ from physical controls in that they prevent access to the contents of a system, but not the physical systems themselves.

=== Administrative ===

Administrative controls are the organization's policies and procedures. Their purpose is to ensure that there is proper guidance available in regard to security and that regulations are met. They include things such as hiring practices, data handling procedures, and security requirements.

== Methods ==

Using more than one of the following layers constitutes an example of defense in depth.

=== System and application ===

* [[Antivirus software]]

* [[Authentication]] and [[password]] security

Line 30 ⟶ 27:

* [[Multi-factor authentication]]

* [[Vulnerability scanner]]s

* [[Timed access control]]

* [[Internet Security Awareness Training]]

* [[Sandbox (computer security)|Sandbox]]ing

* [[Intrusion detection system]]s (IDS)

=== Network ===

* [[Firewall (computing)|Firewall]]s (hardware or software)

* [[DMZ (computing)|Demilitarized zones]] (DMZ)

* [[Virtual private network]] (VPN)

=== Physical ===

* [[Biometrics]]

* [[Data-centric security]]

* [[Physical security]] (e.g. [[deadbolt]] locks)

=== Example ===

In the following scenario a web browser is developed using defense in depth -

* the browser developers receive security training

* the codebase is checked automatically using security analysis tools

* the browser is regularly audited by an internal security team

* ... is occasionally audited by an external security team

* ... is executed inside a sandbox

==See also==

*[[Defence-in-depth (Roman military)]]

*[[Defense strategy (computing)]]