liveBook · Manning

Security continuum

As explained in Microsoft Azure in Action

A security continuum is a scale representing progressively stronger levels of protection rather than a binary secure-or-insecure state.

Security is not a switch labeled secure. It is a sliding scale from less secure to more secure, constrained by budget, time, technology, and knowledge. The practical goal is to become as secure as possible within those limits. section 6.1

Apply the continuum when making protection decisions:

  • Treat security as an ongoing improvement target rather than a finished status. section 6.1
  • Use layered defenses instead of relying on one control or feature; defense in depth provides backup and redundancy. section 6.1.1
  • Balance stronger protection against available budget, time, technology, and knowledge. section 6.1

A castle for your data

A castle protects its king with a gatehouse, moat, drawbridge, walls, towers, and guards rather than one heroic lock. Defense in depth uses the same idea for data: multiple layers can protect it when one layer fails. section 6.1.1

Figure 6.1 The security continuum

Use the security-continuum diagram to visualize protection as a progression from less secure to more secure. section 6.1

How Microsoft Azure in Action covers it

How deep it goes
Defines a protection scale and illustrates layered defense through a castle analogy and Azure’s seven defensive layers.
Examples
Uses an Azure virtual machine and a medieval castle to demonstrate progressive and layered protection.
What you can do after
Evaluate security decisions as trade-offs and understand why resilient infrastructure requires multiple protective layers.
How it connects
Connects security continuum with defense in depth, role-based access control, Azure Policy, encryption, and Microsoft Defender for Cloud.

Related concepts

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.