Security protects systems, data, applications, and infrastructure from unauthorized access, misuse, disruption, and damage. It is not a switch labeled secure; it is a continuum from less secure to more secure, shaped by budget, time, technology, and knowledge. section 6.1
Azure builds security into its infrastructure and services, but responsibility still includes choosing controls that fit the workload. A virtual machine may use encrypted storage, SSL or SSH connections, role-based access control, passwordless access, Azure Policies, and Microsoft Defender for Cloud. section 6.1
A practical security plan combines several protections:
- Protect stored data with transparent 256-bit AES encryption, provided for Azure Storage data at no extra cost. section 9.3
- Protect access with authentication, authorization, encrypted connections, and policies that restrict approved features, applications, and functions. section 6.1
- Match database security, performance, cost, and recovery capabilities to the application rather than assuming every database offers the same safeguards. section 10.3.4 section 10.6
Banning Books protects its inventory
A digital publisher must protect customer details, purchase history, book content, and transaction records. Azure Storage encryption protects data at rest, while database selection requires weighing threat protection, performance, cost, and disaster-recovery features. Security therefore supports both confidentiality and business continuity—not merely keeping cybercriminals out. section 9.3 section 10.3.4 section 10.6
Figure 6.1 The security continuum
Use the security continuum to compare protection choices and recognize that stronger security involves constraints and trade-offs rather than a final completion state. section 6.1
