Study guide

13.3 Defender for Cloud Inventory, Compliance Standards & Custom Standards

Microsoft Azure Security Technologies AZ-500

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Exam Overview & Azure Security Architecture Foundation

1.1 Azure Security Engineer Role & Exam Logistics 1.2 Microsoft Cybersecurity Reference Architecture & Zero Trust Principles

2 Chapter 2: Secure Identity and Access - Authentication, MFA & PIM

2.1 Microsoft Entra ID Security, Users, and Groups 2.2 Authentication Methods, MFA, and Conditional Access Policy Design 2.3 Microsoft Entra Privileged Identity Management (PIM)

3 Chapter 3: Secure Identity and Access - RBAC & Workload Identity

3.1 Azure RBAC, Custom Roles, and Governance 3.2 Workload Identities and Managed Identities 3.3 External Identities and Cross-Tenant Collaboration

4 Chapter 4: Microsoft Entra Application Access & Consent Governance

4.1 Enterprise Applications, OAuth Permission Grants & Consent Governance 4.2 App Registrations, Permission Scopes & Service Principal Credentials

5 Chapter 5: Secure Azure Networking - Boundary & Perimeter Protection

5.1 Virtual Network Security & Micro-segmentation 5.2 Azure Firewall and Firewall Manager 5.3 Web Application Firewall (WAF) & Azure Front Door

6 Chapter 6: Secure Azure Networking - Private Access & Monitoring

6.1 Private Connectivity with Private Endpoints & Private Link 6.2 Azure Bastion & Remote Management Security 6.3 Network Perimeter Protection & Flow Monitoring

7 Chapter 7: Network Architecture, Routing & Hybrid Connectivity

7.1 Azure Virtual Network Manager, Network Groups & User-Defined Routes 7.2 VPN Gateway, ExpressRoute Encryption & Virtual WAN Secured Hub 7.3 Network Integration for App Service, Functions, App Service Environment & SQL Managed Instance

8 Chapter 8: Public and Edge Access Protection

8.1 Azure Application Gateway Security, TLS Policy & Mutual Authentication 8.2 Azure Front Door, CDN Caching & TLS for App Service and API Management

9 Chapter 9: Compute, Container & Registry Security

9.1 Azure Virtual Machine Hardening & Host Security 9.2 Azure Key Vault Deep Dive & Secrets Lifecycle 9.3 Container & Azure Kubernetes Service (AKS) Security 9.4 Azure Container Instances, Container Apps & Registry Access Control

10 Chapter 10: Storage Security, Access Methods & Data Protection

10.1 Storage Account Security & Access Controls 10.2 Selecting and Configuring Access to Azure Files 10.3 Selecting and Configuring Access to Azure Blob Storage 10.4 Storage Data Protection: Soft Delete, Versioning, Point-in-Time Restore & Backup

11 Chapter 11: Data Platform & Database Security

11.1 Azure SQL Database Security & Always Encrypted 11.2 Database Auditing & Vulnerability Assessment 11.3 Data Discovery, Classification, & Microsoft Purview Integration

12 Chapter 12: Cloud Governance, Key Lifecycle & Asset Protection

12.1 Azure Policy for Security Governance: Definitions, Initiatives, Effects & Remediation 12.2 Key Vault Backup, Recovery & Automated Key Rotation 12.3 Implementing Security Controls to Protect Backups 12.4 Security Controls for Asset Management: Locks, Tags, Resource Graph & Azure Arc

13 Chapter 13: Microsoft Defender for Cloud - Posture & Workload Protection

13.1 Microsoft Defender for Cloud & Secure Score 13.2 Defender Cloud Workload Protection (CWP) Plans 13.3 Defender for Cloud Inventory, Compliance Standards & Custom Standards 13.4 Connecting AWS and GCP Environments to Microsoft Defender for Cloud

14 Chapter 14: External Attack Surface & Vulnerability Management

14.1 Microsoft Defender External Attack Surface Management (EASM) 14.2 Agentless Scanning & Microsoft Defender Vulnerability Management for Azure VMs 14.3 Defender for Cloud DevOps Security: GitHub, Azure DevOps & GitLab

15 Chapter 15: Security Monitoring, Microsoft Sentinel & Automation

15.1 Azure Monitor Data Collection Rules & Network Security Event Monitoring 15.2 Microsoft Sentinel Data Connectors, Content Hub & Normalization 15.3 Microsoft Sentinel Workspace & KQL Threat Hunting 15.4 Sentinel Incident Management & SOAR Automation

13.3 Defender for Cloud Inventory, Compliance Standards & Custom Standards

Key Takeaways Explain This Topic AI

Only recommendations in the default Microsoft Cloud Security Benchmark affect Secure Score; other assigned standards change compliance reporting, not the score.

Asset inventory is powered by Azure Resource Graph and filters on plan coverage, agent status, resource type, tags, and outstanding recommendations.

Software inventory requires Defender for Servers Plan 2 with Defender Vulnerability Management integration.

Custom standards are created by grouping recommendations, and custom Azure recommendations are backed by Azure Policy definitions.

Governance rules assign an owner and a due date to recommendations so remediation has accountability rather than a static list.

Last updated: August 2026

Inventory: The Question "What Do We Actually Have?"

Defender for Cloud's Inventory page is a security-flavoured view over Azure Resource Graph , covering Azure, AWS, GCP, and Azure Arc–connected resources in one list.

Filters that matter operationally:

  • Filter Answers
  • Defender for Cloud plan coverage Which resources are unprotected because a plan is off
  • Agent / extension monitoring status Machines missing the Azure Monitor Agent or Defender for Endpoint
  • Recommendations Every resource failing a specific recommendation
  • Security findings Resources with open vulnerability findings
  • Resource type, subscription, tag, cloud Ownership and scoping questions

Two derived views are worth naming:

Software inventory lists the applications and versions installed on protected machines. It requires Defender for Servers Plan 2 with Microsoft Defender Vulnerability Management integration, and answers "which machines run the vulnerable library announced this morning" in seconds.

Attack path analysis and the cloud security graph (Defender CSPM) turn the inventory into exploitability chains — "internet-exposed VM → managed identity → Key Vault with production secrets" — so you triage by real reachability rather than by CVSS score alone.

Inventory also supports exporting a filtered set to CSV and opening the equivalent Resource Graph query, which is how inventory questions become repeatable automation.

Security Standards and the Compliance Dashboard

Defender for Cloud evaluates your environment against security standards , each of which is a set of recommendations (in Azure, backed by Azure Policy initiatives).

Microsoft Cloud Security Benchmark (MCSB) is assigned by default to every subscription. It is Microsoft's canonical baseline, mapped to CIS, NIST, and PCI controls.

Built-in regulatory standards you can add per subscription, management group, or cloud connector include PCI DSS, ISO/IEC 27001, SOC 2, NIST SP 800-53, CIS benchmarks, HIPAA HITRUST, FedRAMP, and country-specific standards. AWS and GCP connectors have their own CIS and PCI equivalents.

The Regulatory compliance dashboard shows passed and failed controls per standard, with drill-down to the failing resources and, for controls Azure cannot evaluate automatically, manual attestation where you upload evidence.

The Secure Score nuance candidates miss

Assigning a regulatory standard does not change your Secure Score. Secure Score is calculated only from the recommendations in the default MCSB standard . Adding PCI DSS gives you a compliance view of PCI controls; it does not add or remove score points. Conversely, remediating an MCSB recommendation improves both the score and any compliance control mapped to it.

If a scenario says "management wants the Secure Score to reflect our internal baseline", the answer is not "assign a regulatory standard" — it is to author policy-backed recommendations and understand that custom standards report compliance separately from the score.

Building a Custom Standard

Custom standards exist for the very common case where an organization's baseline is not any published framework.

The workflow:

In Environment settings → Security policies , create a custom security standard at the subscription, management group, or connector scope.

Add recommendations to it — any combination of built-in recommendations and your own custom recommendations.

Publish it; it then appears alongside MCSB and the regulatory standards on the compliance dashboard.

Custom recommendations are how you assess something Microsoft does not check:

For Azure , a custom recommendation is backed by an Azure Policy definition (typically an audit or auditIfNotExists definition placed in a custom initiative). Write the policy, add it to the custom standard, and its compliance state becomes a recommendation.

For AWS and GCP , custom recommendations are authored as KQL queries over the cloud security graph , and require Defender CSPM to be enabled on the connector.

Custom recommendations carry their own severity, remediation steps, and description, so the operations team receives the same experience as for built-in findings.

Making Remediation Accountable: Governance Rules

A list of recommendations with no owner never gets fixed. Governance rules (a Defender CSPM capability) let you:

Assign an owner automatically, by resource tag or by resource group owner.

Set a remediation due date (for example, 14 days for high severity).

Apply a grace period during which an overdue item does not damage the Secure Score.

Send automatic email notifications to owners and their managers on a schedule.

Overdue items are flagged, so the compliance conversation shifts from "here are 4,000 findings" to "here are the 12 items your team owns that are past due".

Exemptions and Their Score Effect

When a recommendation genuinely does not apply, create an exemption with a justification and category ( Waiver for accepted risk, Mitigated for a compensating control). The exempted resource is removed from the score calculation entirely — from both the numerator and the denominator — so it neither helps nor hurts. Exemptions require Defender CSPM or Defender for Servers Plan 2, and they should carry an expiry so accepted risk is re-reviewed rather than forgotten.

Continuous export sends recommendations, alerts, secure score, and compliance data to a Log Analytics workspace or Event Hub , which is the supported path into Microsoft Sentinel or a third-party SIEM for long-term reporting.