Study guide

2.2 Defense in Depth and the CIA Triad

Azure SC-900 Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Orientation: SC-900 Audience, Format, Scoring, Retakes, and Study Map

1.1 Credential Purpose and Audience 1.2 Exam Duration, Seat Duration, and Experience 1.3 Scoring, Scaled Score, and Pass-Rate Myths 1.4 Retake Policy and Certification Lifecycle 1.5 Scheduling, Price, and Delivery Options 1.6 Skills Measured and Study Map

2 Security, Compliance, and Identity Concepts: Zero Trust, Shared Responsibility, and GRC

2.1 Shared Responsibility Model 2.2 Defense in Depth and the CIA Triad 2.3 Zero Trust Model 2.4 Encryption, Hashing, and Data States 2.5 Governance, Risk, and Compliance 2.6 Identity Perimeter, Authentication, Authorization, and Federation

3 Microsoft Entra ID: Identities, Hybrid Identity, and Authentication

3.1 Microsoft Entra ID Foundations 3.2 Identity Types and Directory Objects 3.3 Hybrid Identity and Entra Connect Concepts 3.4 Authentication Methods and Sign-in Assurance 3.5 Multifactor Authentication 3.6 Password Protection, Self-Service Password Reset, and External Identities

4 Microsoft Entra Access Management, Governance, PIM, and Identity Protection

4.1 Conditional Access Purpose 4.2 Signals and Controls 4.3 Microsoft Entra Roles and Role-Based Access Control 4.4 Identity Governance, Entitlement Management, and Lifecycle Governance 4.5 Access Reviews and Privileged Identity Management 4.6 Microsoft Entra ID Protection and Risk

5 Azure Infrastructure Security: DDoS, Firewall, WAF, NSGs, Bastion, and Key Vault

5.1 Choose the Right Infrastructure Security Control 5.2 Azure DDoS Protection for Availability 5.3 Azure Firewall for Centralized Network Policy 5.4 Web Application Firewall for HTTP Workloads 5.5 Virtual Networks, Subnets, and Network Security Groups 5.6 Bastion and Key Vault for Administration and Secrets

6 Defender for Cloud: CSPM, Cloud Workload Protection, and Secure Score

6.1 Defender for Cloud Purpose and Exam Role 6.2 CSPM, Foundational Posture, and Defender CSPM 6.3 Policies, Standards, and Security Recommendations 6.4 Secure Score and Remediation Priority 6.5 Regulatory Compliance and Multicloud Posture 6.6 Cloud Workload Protection and Defender Plans

7 Microsoft Sentinel: SIEM, SOAR, Analytics, Hunting, Workbooks, and Playbooks

7.1 Sentinel as SIEM and SOAR 7.2 Data Connectors and Security Signals 7.3 Analytics Rules, Incidents, and Detection 7.4 Workbooks for Visual Review 7.5 Hunting, KQL Awareness, and Notebooks 7.6 Automation Rules and Logic Apps Playbooks

8 Microsoft Defender XDR: Office, Endpoint, Cloud Apps, Identity, Vulnerability, and Threat Intelligence

8.1 Defender XDR Suite and Microsoft Defender Portal 8.2 Defender for Office 365 8.3 Defender for Endpoint 8.4 Defender for Cloud Apps 8.5 Defender for Identity 8.6 Vulnerability Management and Threat Intelligence

9 Microsoft Purview, Service Trust, Privacy, Compliance Manager, and Compliance Score

9.1 Service Trust Portal and Assurance Resources 9.2 Privacy Principles and Microsoft Priva 9.3 Microsoft Purview Portal 9.4 Compliance Manager Assessments 9.5 Compliance Score and Improvement Actions 9.6 Scenario Selection for Trust, Privacy, and Compliance Manager

10 Microsoft Purview Data Classification, Labels, DLP, Retention, eDiscovery, and Audit

10.1 Data Classification Foundations 10.2 Content Explorer and Activity Explorer 10.3 Sensitivity Labels and Label Policies 10.4 Data Loss Prevention 10.5 Retention, Records Management, and Label Policies 10.6 eDiscovery, Audit, and Insider Risk Management

11 SC-900 Product Selection Playbooks and Common Microsoft Rebrand Traps

11.1 Read the Scenario Before Picking a Product 11.2 Entra Playbook for Identity, Access, and Governance 11.3 Defender Playbook for Protection, Detection, and Posture 11.4 Sentinel Playbook for SIEM, SOAR, and Hunting 11.5 Purview Playbook for Compliance, Data, and Risk 11.6 Renamed Products and Similar-Name Traps 11.7 Microsoft Learn Practice Assessment Review Loop

12 Final SC-900 Review, Timed Practice, Exam Day, and Next Certification Path

12.1 Domain-Weighted Final Review Plan 12.2 Timed Practice and Pacing 12.3 Exam Sandbox and Question Experience 12.4 Exam-Day Logistics and Boundaries 12.5 Scoring, Retakes, and After-Exam Decisions 12.6 Final Memory Check and Scenario Drills 12.7 Next Certification Path After SC-900

2.2 Defense in Depth and the CIA Triad

Key Takeaways Explain This Topic AI

Defense in depth uses multiple overlapping layers of controls so that if one layer fails, another limits the damage — it does not rely on a single perimeter.

Microsoft's seven layers, outer to inner, are physical, identity and access, perimeter, network, compute, application, and data.

The CIA triad defines the three security goals: confidentiality (only authorized parties read), integrity (data is accurate and unaltered), and availability (systems are reachable when needed).

A single control can serve multiple CIA goals, but SC-900 scenarios usually have one primary cue — encryption -> confidentiality, hashing -> integrity, redundancy/DDoS protection -> availability.

Defense in depth and Zero Trust complement each other: layers protect resources while Zero Trust verifies every request.

Last updated: June 2026

Layered security: assume any control can fail

Defense in depth is a security strategy that uses multiple overlapping layers of controls rather than depending on one perfect wall. The premise is that any single control can fail — through misconfiguration, an unpatched vulnerability, stolen credentials, or a deliberate business exception — so the design must ensure another layer limits the damage. If an attacker defeats one layer, the next layer should slow, detect, contain, or reduce the impact of the attack.

Microsoft describes the strategy as a set of concentric layers that move from the outside (physical) inward toward the most valuable asset (data). Importantly, defense in depth is not synonymous with firewalls. A firewall is one control in one layer; the broader strategy combines identity controls, segmentation, endpoint hardening, application security, encryption, monitoring, and recovery planning.

The seven Microsoft layers

  • Layer (outer -> inner) What it does Example control
  • Physical security Restricts physical access to facilities and hardware Badge access, guards at datacenters
  • Identity and access Authenticates and authorizes users Multifactor authentication, least privilege
  • Perimeter Protects the external boundary from bulk attacks DDoS protection, perimeter firewalls
  • Network Segments and controls internal traffic Network segmentation, deny-by-default rules
  • Compute Hardens VMs, containers, and hosts Patching, restricting admin access, endpoint protection
  • Application Reduces software vulnerabilities Input validation, secure development, vulnerability testing
  • Data Protects the information itself Classification, access control, encryption

Know the order — physical is outermost, data is innermost — because the exam may ask which layer a control belongs to or which layer sits closest to the data.

The CIA triad

The CIA triad frames the three fundamental goals of information security. Spell each one out precisely, because SC-900 distractors swap the definitions:

Confidentiality — sensitive information is accessible only to authorized parties. Breached by data leaks, eavesdropping, or over-broad permissions.

Integrity — data stays accurate, complete, and is changed only through authorized processes. Breached by tampering, corruption, or unauthorized modification.

Availability — systems and data are accessible to authorized users when needed . Breached by outages, ransomware, or denial-of-service attacks.

Attackers, by contrast, pursue the opposite trio sometimes called the DAD triad : Disclosure (against confidentiality), Alteration (against integrity), and Denial/Destruction (against availability).

Mapping controls to CIA goals

A control can support more than one goal, but each exam scenario has a primary cue:

  • Control Primary CIA goal Why
  • Encryption Confidentiality Makes data unreadable without the key
  • Hashing / digital signatures Integrity Detects whether data was altered
  • Access control / least privilege Confidentiality + integrity Limits who can read or modify
  • Backups, redundancy, failover, DDoS protection Availability Keeps services reachable through failure or attack

When you read a scenario, work in three steps: (1) identify the asset (facility, identity, network, compute, application, or data); (2) identify the failure being reduced (exposure, tampering, outage, or unauthorized access); (3) map the proposed control to the nearest layer and CIA goal . This turns vague questions into a quick lookup.

How defense in depth and Zero Trust fit together

Defense in depth and Zero Trust are distinct but complementary. Defense in depth says use layers . Zero Trust says trust nothing by default — verify explicitly, grant least privilege, and assume breach . A strong modern design uses both: layered controls around resources, and identity-centered verification for every individual access request. Neither replaces the other. For example, network segmentation (a defense-in-depth layer) supports Zero Trust's 'assume breach' principle by limiting lateral movement, but segmentation alone does not satisfy the requirement to verify every request explicitly.

Common exam traps

Treating one product as the whole strategy. Buying a firewall or enabling MFA strengthens one layer; it is not defense in depth by itself.

Confusing the goals. Availability is not about secrecy. If a question describes keeping a service reachable during a DDoS attack, the answer is availability, not confidentiality.

Assuming hashing hides data. Hashing supports integrity , not confidentiality — it does not keep data secret, it detects change.

Forgetting the layer order. Identity and access sits near the outside (right after physical), while data is the innermost layer being protected.

For SC-900, you should be able to (1) recite the seven layers in order, (2) define each CIA goal in one accurate sentence, and (3) match a described control to both its layer and its primary CIA goal. That combination answers the majority of Domain 1 'concepts' questions on this topic.

Worked example

Consider a scenario: 'A company encrypts its customer database, requires MFA for administrators, segments its production network, and keeps geo-redundant backups. ' Database encryption is the data layer, supporting confidentiality . MFA for admins is the identity and access layer, supporting confidentiality and integrity by limiting who can sign in and change things. Network segmentation is the network layer, supporting the assume-breach idea and limiting exposure (confidentiality/integrity). Geo-redundant backups are about availability — they keep data recoverable after an outage or ransomware event.

One scenario, four controls, four clean mappings — exactly the reasoning the exam tests.

Keep in mind that non-repudiation and authenticity are sometimes mentioned alongside CIA, but the triad the exam asks about is strictly confidentiality, integrity, and availability . If an option lists 'non-repudiation' or 'federation' as a CIA goal, it is a distractor.