Layered security control

As explained in Microsoft Azure in Action

A layered approach is a security strategy that combines multiple protective controls at successive points in an environment.

Layered security control protects important assets with multiple defenses placed one after another. Rather than trusting a single switch, service, or guard, it creates backup and redundancy across the environment. section 6.1.1

A castle with very good security instincts

Imagine a castle protected by a gatehouse, moat, drawbridge, outer wall, inner wall, keep, and guards. If one defense fails, others still stand between an attacker and the treasure. Azure applies the same defense-in-depth idea to protect data, beginning with physical facilities and identity controls. section 6.1.1

Figure 6.2 The seven layers of castle defense

Use the castle diagram to see how successive controls combine into defense in depth. section 6.1.1

Figure 6.3 Azure layers of defense in depth

Use the Azure diagram to connect the castle analogy with layered protection for cloud data. section 6.1.1

How Microsoft Azure in Action covers it

How deep it goes

Explains redundancy through a castle analogy and identifies physical and identity layers before stopping short of detailing all seven.

Examples

Uses a seven-layer medieval castle and Azure’s corresponding defense-in-depth diagram to illustrate successive protection.

What you can do after

Evaluate security designs by looking for multiple defensive layers, backup controls, and redundancy.

How it connects

Connects defense in depth with the security continuum, physical security, identity, and data protection.

liveBookmanning.com

Read Microsoft Azure in Action on liveBook Get the book at manning.com

Related concepts

• defense in depthincludes · Defense in depth is a security strategy that combines multiple protective controls so that the failure or compromise of one does not eliminate all protection.
• multi-tier applicationcontrasts with · A multi-tier application is an application organized into distinct tiers that separate responsibilities and interact through defined dependencies or interfaces.

This explainer was generated by Manning's knowledge graph from the text of Microsoft Azure in Action. The section links point to the parts of the book it draws on.