Study guide
4.2 Defender for Cloud Compliance & Security Standards
Microsoft Certified: Cloud and AI Security Engineer Associate SC-500
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
1.1 Current Exam Facts 1.2 Skills Measured & Weightings 1.3 Study Path, Prerequisites & Exam Strategy
2 Microsoft Entra ID Secure Access
2.1 Privileged Identity Management (PIM) 2.2 Conditional Access Policies 2.3 MFA and Passwordless Authentication 2.4 Application Identities, OAuth Consent & Managed Identities
3 Azure Key Vault Secrets and Keys
3.1 Deploy and Configure Key Vault 3.2 Access Control and Firewall for Key Vault 3.3 Keys, Secrets, Certificates & Defender for Key Vault
4 Governance, Policy & RBAC
4.1 Azure Policy for Security Controls 4.2 Defender for Cloud Compliance & Security Standards 4.3 Resource Locks and Azure RBAC 4.4 Custom Roles, Overprivileged Access, Backup & IaC Security
5 Secure Storage Accounts
5.1 Storage Account Security Fundamentals 5.2 Storage Firewalls and Access Policies 5.3 Defender for Storage
6 Secure Databases
6.1 Azure SQL Platform Security 6.2 Database Auditing 6.3 Defender for Databases
7 Network Security Groups & Virtual Network Manager
7.1 Network Security Groups and Application Security Groups 7.2 Azure Virtual Network Manager Security Admin Rules 7.3 Virtual WAN and VPN Security
8 Private Access, Private Link & Azure Firewall
8.1 Microsoft Entra Private Access 8.2 Private Endpoints and Private Link 8.3 Azure Firewall 8.4 Network Watcher Diagnostics and Effective Rules
9 Security for AI Workloads
9.1 Purview DSPM for AI and Data Overexposure 9.2 Copilot Studio Protection and Agent Management 9.3 Microsoft Entra Agent ID Security 9.4 Defender for AI, Foundry Guardrails & AI Gateway
10 Secure Servers and Virtual Machines
10.1 Disk Encryption 10.2 Azure Bastion and JIT VM Access 10.3 Azure Arc and Defender for Servers 10.4 Trusted Launch, VM Security Features & Machine Configuration
11 Application Platform Security
11.1 Containers: AKS, ACR, ACI, Container Apps & Defender for Containers 11.2 Azure Functions and Logic Apps Security 11.3 Azure App Service Security 11.4 Web Application Firewall and API Management Protection
12 Defender for Cloud Security Posture
12.1 Defender CSPM and Secure Score 12.2 Workload Protection Plans and Multicloud Connectors 12.3 Vulnerability Management and Defender EASM
13 Microsoft Sentinel Activity and Event Collection
13.1 Workspaces, Roles & Content Hub 13.2 Data Connectors, Syslog/CEF & Windows Event Collection 13.3 Custom Tables, Retention & Purview Audit 13.4 Automation Rules and Playbooks
14 Microsoft Security Copilot & Final Review
14.1 Microsoft Security Copilot Workspaces and Roles 14.2 Plugins and Security Agents 14.3 Final Review and Exam-Day Strategy
4.2 Defender for Cloud Compliance & Security Standards
Key Takeaways Explain This Topic AI
Defender for Cloud’s regulatory compliance dashboard maps security assessments to controls in standards such as the Microsoft cloud security benchmark (MCSB), CIS, NIST, PCI, and others.
MCSB is enabled by default when Defender for Cloud is on; additional non-default standards generally require at least one paid Defender plan.
Recommendations (assessments) drive both Secure Score improvement and compliance control status; remediating recommendations improves both posture views.
Controls include automated assessments and manual attestation with evidence for items Azure cannot fully auto-verify.
Assessments refresh on a delayed cycle (on the order of ~12 hours for many compliance impacts)—do not expect instant dashboard changes after every fix.
Last updated: July 2026
4.2 Defender for Cloud Compliance & Security Standards
Quick Answer: Use Microsoft Defender for Cloud’s regulatory compliance experience to evaluate subscriptions (and connected AWS/GCP accounts) against security standards —especially the Microsoft cloud security benchmark (MCSB) plus frameworks such as CIS , NIST , and industry standards. Fix recommendations that map to failed controls; that work also improves Secure Score . Enable extra standards when a paid Defender plan is active; attest manual controls with evidence when automation cannot prove compliance alone.
SC-500 asks you to evaluate regulatory compliance with Defender for Cloud and to implement security controls including security standards and recommendations . This section is the compliance and standards lens; deeper CSPM/Secure Score mechanics also appear later in the posture chapters—here you need enough to design and operate standards-based enforcement and reporting.
Where compliance sits in Defender for Cloud
Defender for Cloud continuously runs security assessments (recommendations) against resources. Those assessments are the common engine behind:
Recommendations lists and unhealthy resource counts.
Secure Score (weighted progress toward recommended best practices).
Regulatory compliance (mapping assessments to framework controls).
When a recommendation fails, a mapped control in MCSB or CIS may show as noncompliant. When you remediate the recommendation, both Secure Score and the compliance control can improve after the next assessment cycle.
Surface Primary question it answers
Recommendations What should I fix on which resources?
Secure Score How healthy is my overall security posture (0–100 style score)?
Regulatory compliance How do I map to CIS / MCSB / NIST / PCI control language for auditors?
Regulatory compliance dashboard
In the Defender for Cloud portal, open Regulatory compliance . You will typically:
Select a standard (for example MCSB or Azure CIS).
See subscriptions/accounts where the standard applies.
Expand controls to view associated assessments .
Open Control details for overview, Your Actions , and Microsoft Actions (shared responsibility clarity).
Drill into failing automated assessments to remediate resources.
Complete manual attestation where required and attach evidence.
Automated vs manual assessments
Type What happens Operator action
Automated Defender evaluates resource configuration via platform signals/policies Follow remediation steps; fix resources; wait for reassessment
Manual Control cannot be fully proven by Azure telemetry alone Attest compliance, attach evidence, save for auditors
Scenario: For a CIS control requiring a documented incident-response plan, automation may not see a Word doc in SharePoint. The dashboard expects manual attestation and evidence links. For “disk encryption should be enabled on VMs,” the assessment is automated —encrypt disks, then watch the control improve.
Security standards you will see on the exam
Standard / package Role for SC-500 thinking
Microsoft cloud security benchmark (MCSB) Default Microsoft-centric baseline for Azure (and multicloud guidance); enabled by default when Defender for Cloud is enabled
- CIS Azure Foundations Industry hardening benchmark; common in enterprise audits
- NIST SP 800-53 / other NIST mappings Government and regulated-industry mapping
- PCI DSS, ISO, SOC-related views Industry frameworks; some via standards onboarding and audit report downloads
- Custom initiatives / standards Org-specific packages built on Policy assessments
Exact catalog names evolve; the exam cares about the workflow : enable standard → review failed controls → remediate recommendations → re-evaluate → report.
Enabling standards
MCSB is on by default when Defender for Cloud is enabled for a subscription/account.
Additional non-default standards generally require that at least one paid Defender plan is enabled on the environment.
Multicloud connectors (AWS/GCP) bring those accounts into the same compliance storytelling when connected.
Permissions note (practical): Reading policy compliance data needs more than casual curiosity. Subscription Reader can access policy compliance data in many setups, while Security Reader alone may not see all policy compliance data. Roles such as combinations involving Security Admin and policy-related rights are often needed to manage standards. On the exam, if someone “cannot see compliance data,” think missing permissions on policy compliance , not a broken MCSB.
Recommendations and remediation
Recommendations are the actionable unit:
Open a failing assessment from a control or from the recommendations page.
Review unhealthy resources and the remediation steps .
Use Quick Fix / Fix when offered (often a DeployIfNotExists-style remediation under the hood), or remediate manually in the resource blade.
Optionally exempt a resource with justification when risk is accepted (exemptions should be time-bound and reviewed).
Wait for the assessment cycle—Microsoft documentation notes roughly ~12 hours for many compliance impacts to refresh after changes.
Relationship to Secure Score (high level)
Secure Score aggregates the impact of recommendations into a single posture number. You do not need the full scoring formula for SC-500 governance items, but you must know:
Fixing recommendations that are unhealthy generally raises Secure Score .
The same fixes often improve regulatory control status when those recommendations map into an enabled standard.
Secure Score is a prioritization and progress tool; regulatory compliance is the framework mapping tool. They share assessment DNA but answer different stakeholder questions (CISO dashboard vs auditor control matrix).
Reporting and continuous export
Defender for Cloud supports:
Download report (PDF/summary status for a standard) for stakeholders.
Audit reports for Microsoft’s own certifications (ISO, SOC, PCI packages) to show platform compliance vs your customer configuration compliance—do not confuse Azure’s SOC report with your subscription’s CIS score.
Continuous export of regulatory compliance data to Log Analytics or Event Hubs for SIEM, long-term trending, or Microsoft Sentinel analytics.
Workflow automation (Logic Apps) when assessment state changes—for example, email Security Ops when a PCI control fails.
Integration with Microsoft Purview Compliance Manager can surface Defender for Cloud compliance data alongside broader organizational compliance work—useful context, less likely as a deep configuration question.
Shared responsibility in control details
Opening Microsoft Actions vs Your Actions reinforces cloud shared responsibility: Microsoft hardens the cloud fabric; you harden configuration, identity, encryption choices, network exposure, and operational processes. SC-500 is almost entirely about Your Actions .
Exam traps
Expecting compliance % to update instantly after remediation.
Confusing Microsoft audit certificates with your resource compliance against CIS/MCSB.
Thinking enabling a standard alone remediates resources—it only measures and guides; you still fix recommendations.
Believing Secure Score and regulatory compliance are unrelated products—they share assessments.
Enabling dozens of standards without a paid plan or without operational capacity to act on noise.
Practical playbook for SC-500 scenarios
Confirm Defender for Cloud is enabled on in-scope subscriptions.
Verify MCSB is present; add CIS/NIST/PCI standards required by the business (with plan prerequisites).
Sort controls by failed automated assessments with high unhealthy resource counts.
Remediate “quick wins” that also move Secure Score (exposed management ports, missing encryption, public storage, weak Key Vault network rules).
Attest manual controls with evidence stored in a controlled repository.
Export compliance weekly to Log Analytics for leadership reporting.
Feed chronic failures into Azure Policy Deny initiatives so new resources cannot recreate the gap.
That last step closes the loop with section 4.1: Defender tells you what is wrong; Policy keeps it from coming back.