Defender for Cloud Is Only Effective When Properly Configured

Microsoft Defender for Cloud provides security posture management (CSPM) and workload protection (CWP) across your Azure, AWS, and GCP environments. However, enabling it is just the first step — you need to enable the right plans, configure governance, remediate recommendations, and integrate with your security operations center. This guide covers the complete hardening workflow.

Threat Landscape and Attack Surface

Hardening Azure Defender for Cloud requires understanding the threat landscape specific to this service. Azure services are attractive targets because they often store, process, or transmit sensitive data and provide control-plane access to cloud infrastructure. Attackers probe for misconfigured services using automated scanners that continuously sweep Azure IP ranges for exposed endpoints, weak authentication, and default configurations.

The attack surface for Azure Defender for Cloud includes several dimensions. The network perimeter determines who can reach the service endpoints. The identity and access layer controls what authenticated principals can do. The data plane governs how data is protected at rest and in transit. The management plane controls who can modify the service configuration itself. A comprehensive hardening strategy addresses all four dimensions because a weakness in any single layer can be exploited to bypass the controls in other layers.

Microsoft’s shared responsibility model means that while Azure secures the physical infrastructure, network fabric, and hypervisor, you are responsible for configuring the service securely. Default configurations prioritize ease of setup over security. Every Azure service ships with settings that must be tightened for production use, and this guide walks through the critical configurations that should be changed from their defaults.

The MITRE ATT&CK framework for cloud environments provides a structured taxonomy of attack techniques that adversaries use against Azure services. Common techniques relevant to Azure Defender for Cloud include initial access through exposed credentials or misconfigured endpoints, lateral movement through overly permissive RBAC assignments, and data exfiltration through unmonitored data plane operations. Each hardening control in this guide maps to one or more of these attack techniques.

Compliance and Regulatory Context

Security hardening is not just a technical exercise. It is a compliance requirement for virtually every regulatory framework that applies to cloud workloads. SOC 2 Type II requires evidence of security controls for cloud services. PCI DSS mandates network segmentation and encryption for payment data. HIPAA requires access controls and audit logging for health information. ISO 27001 demands a systematic approach to information security management. FedRAMP requires specific configurations for government workloads.

Azure Policy and Microsoft Defender for Cloud provide built-in compliance assessments against these frameworks. After applying the hardening configurations in this guide, run a compliance scan to verify your security posture against your applicable regulatory standards. Address any remaining findings to achieve and maintain compliance. Export compliance reports on a scheduled basis to satisfy audit requirements and demonstrate continuous adherence.

The Microsoft cloud security benchmark provides a comprehensive set of security controls mapped to common regulatory frameworks. Use this benchmark as a checklist to verify that your hardening effort covers all required areas. Each control includes Azure-specific implementation guidance and links to the relevant Azure service documentation.

Step 1: Enable All Relevant Defender Plans

# Enable Defender CSPM (attack path analysis, security explorer)
az security pricing create --name CloudPosture --tier Standard

# Enable workload protection plans
az security pricing create --name VirtualMachines --tier Standard --subplan P2
az security pricing create --name Containers --tier Standard
az security pricing create --name StorageAccounts --tier Standard
az security pricing create --name SqlServers --tier Standard
az security pricing create --name AppServices --tier Standard
az security pricing create --name KeyVaults --tier Standard
az security pricing create --name Dns --tier Standard
az security pricing create --name Arm --tier Standard
az security pricing create --name CosmosDbs --tier Standard
az security pricing create --name Api --tier Standard

# Verify all plans
az security pricing list -o table

Step 2: Review and Improve Secure Score

# Get current secure score
az security secure-score-controls list --query "[].{Control:displayName, Score:current, Max:max}" -o table

# List unhealthy resources for a specific control
az security assessments list --query "[?status.code=='Unhealthy'].{Resource:resourceDetails.id, Recommendation:displayName}" -o table

Focus on controls with the highest impact first. Common quick wins:

• Enable MFA for subscription owners
• Remove deprecated accounts with owner permissions
• Enable encryption at rest for storage accounts
• Remove public access from storage containers
• Enable TLS 1.2 on all web applications

Step 3: Configure Governance Rules

Governance rules automatically assign recommendations to resource owners with due dates:

• Navigate to Defender for Cloud > Environment settings > Governance rules
• Create rules that assign high-severity recommendations to owners
• Set SLA: Critical (3 days), High (7 days), Medium (30 days), Low (90 days)
• Enable email notifications to owners and their managers

Step 4: Apply Microsoft Cloud Security Benchmark (MCSB)

# MCSB is applied by default as the primary compliance standard
# Verify it is assigned
az security regulatory-compliance-standards list \
  --query "[?name=='Azure Security Benchmark'].{Name:name, State:state}" -o table

# Add additional standards (e.g., CIS, NIST)
az security regulatory-compliance-standards show --name "CIS Microsoft Azure Foundations Benchmark v1.4.0"

Step 5: Configure Security Alerts and Notifications

# Set notification email for security alerts
az security contact create \
  --name default --email security-team@contoso.com \
  --alert-notifications "on" --alerts-admins "on"

# Configure alert severity filter
az security auto-provisioning-setting update --name default --auto-provision on

Identity and Access Management Deep Dive

Identity is the primary security perimeter in cloud environments. For Azure Defender for Cloud, implement a robust identity and access management strategy that follows the principle of least privilege.

Managed Identities: Use system-assigned or user-assigned managed identities for service-to-service authentication. Managed identities eliminate the need for stored credentials (connection strings, API keys, or service principal secrets) that can be leaked, stolen, or forgotten in configuration files. Azure automatically rotates the underlying certificates, removing the operational burden of credential rotation.

Custom RBAC Roles: When built-in roles grant more permissions than required, create custom roles that include only the specific actions needed. For example, if a monitoring service only needs to read metrics and logs from Azure Defender for Cloud, create a custom role with only the Microsoft.Insights/metrics/read and Microsoft.Insights/logs/read actions rather than assigning the broader Reader or Contributor roles.

Conditional Access: For human administrators accessing Azure Defender for Cloud through the portal or CLI, enforce Conditional Access policies that require multi-factor authentication, compliant devices, and approved locations. Set session lifetime limits so that administrative sessions expire after a reasonable period, forcing re-authentication.

Just-In-Time Access: Use Azure AD Privileged Identity Management (PIM) to provide time-limited, approval-required elevation for administrative actions. Instead of permanently assigning Contributor or Owner roles, require administrators to activate their role assignment for a specific duration with a business justification. This reduces the window of exposure if an administrator’s account is compromised.

Service Principal Hygiene: If managed identities cannot be used (for example, for external services or CI/CD pipelines), use certificate-based authentication for service principals rather than client secrets. Certificates are harder to accidentally expose than text secrets, and Azure Key Vault can automate their rotation. Set short expiration periods for any client secrets and monitor for secrets that are approaching expiration.

Step 6: Enable Attack Path Analysis (Defender CSPM)

Attack path analysis identifies exploitable paths from the internet to your sensitive resources. It visualizes how an attacker could chain vulnerabilities, misconfigurations, and excessive permissions to reach critical data.

• Navigate to Defender for Cloud > Attack path analysis
• Review paths sorted by risk — prioritize those reaching sensitive data
• Remediate the weakest link in each path (often a single misconfiguration)
• Use Cloud Security Explorer to query your security graph

Step 7: Configure Continuous Export to SIEM

# Export alerts and recommendations to Log Analytics
az security automation create \
  --name export-to-law --resource-group rg-security \
  --scopes "/subscriptions/{sub}" \
  --actions '[{"actionType":"LogAnalytics","workspaceResourceId":"/subscriptions/{sub}/resourceGroups/rg-monitor/providers/Microsoft.OperationalInsights/workspaces/law-prod"}]' \
  --sources '[{"eventSource":"Alerts"},{"eventSource":"Assessments"}]'

For Microsoft Sentinel integration, use the built-in Defender for Cloud data connector.

Step 8: Enable Agentless Scanning

Defender CSPM and Defender for Servers P2 support agentless scanning:

• Agentless vulnerability assessment — scans VMs without installing agents
• Agentless secret scanning — detects exposed credentials in VM disk snapshots
• Container vulnerability assessment — scans images in registries and running containers

Enable through Environment settings > Defender plans > Settings > Agentless scanning.

Step 9: Configure Just-In-Time VM Access

# Enable JIT on a VM
az security jit-policy create \
  --resource-group rg-prod --location eastus \
  --name "default" \
  --virtual-machines '[{
    "id": "/subscriptions/{sub}/resourceGroups/rg-prod/providers/Microsoft.Compute/virtualMachines/vm-web",
    "ports": [{"number": 22, "maxRequestAccessDuration": "PT3H", "allowedSourceAddressPrefix": "*", "protocol": "TCP"},
              {"number": 3389, "maxRequestAccessDuration": "PT3H", "allowedSourceAddressPrefix": "*", "protocol": "TCP"}]
  }]'

JIT VM access reduces the attack surface by keeping management ports closed until needed. Users request access for a limited time from specific IPs.

Step 10: Implement Workflow Automation

# Auto-remediate specific recommendations via Logic Apps
az security automation create \
  --name auto-fix-storage --resource-group rg-security \
  --scopes "/subscriptions/{sub}" \
  --actions '[{"actionType":"LogicApp","logicAppResourceId":"/subscriptions/{sub}/resourceGroups/rg-security/providers/Microsoft.Logic/workflows/fix-storage-public-access"}]' \
  --sources '[{"eventSource":"Assessments","ruleSets":[{"rules":[{"propertyJPath":"properties.metadata.assessmentKey","expectedValue":"storage-public-access-key","operator":"Equals"}]}]}]'

Defense in Depth Strategy

No single security control is sufficient. Apply a defense-in-depth strategy that layers multiple controls so that the failure of any single layer does not expose the service to attack. For Azure Defender for Cloud, this means combining network isolation, identity verification, encryption, monitoring, and incident response capabilities.

At the network layer, restrict access to only the networks that legitimately need to reach the service. Use Private Endpoints to eliminate public internet exposure entirely. Where public access is required, use IP allowlists, service tags, and Web Application Firewall (WAF) rules to limit the attack surface. Configure network security groups (NSGs) with deny-by-default rules and explicit allow rules only for required traffic flows.

At the identity layer, enforce least-privilege access using Azure RBAC with custom roles when built-in roles are too broad. Use Managed Identities for service-to-service authentication to eliminate stored credentials. Enable Conditional Access policies to require multi-factor authentication and compliant devices for administrative access.

At the data layer, enable encryption at rest using customer-managed keys (CMK) in Azure Key Vault when the default Microsoft-managed keys do not meet your compliance requirements. Enforce TLS 1.2 or higher for data in transit. Enable purge protection on any service that supports soft delete to prevent malicious or accidental data destruction.

At the monitoring layer, enable diagnostic logging and route logs to a centralized Log Analytics workspace. Configure Microsoft Sentinel analytics rules to detect suspicious access patterns, privilege escalation attempts, and data exfiltration indicators. Set up automated response playbooks that can isolate compromised resources without human intervention during off-hours.

Continuous Security Assessment

Security hardening is not a one-time activity. Azure services evolve continuously, introducing new features, deprecating old configurations, and changing default behaviors. Schedule quarterly security reviews to reassess your hardening posture against the latest Microsoft security baselines.

Use Microsoft Defender for Cloud’s Secure Score as a quantitative measure of your security posture. Track your score over time and investigate any score decreases, which may indicate configuration drift or new recommendations from updated security baselines. Set a target Secure Score and hold teams accountable for maintaining it.

Subscribe to Azure update announcements and security advisories to stay informed about changes that affect your security controls. When Microsoft introduces a new security feature or changes a default behavior, assess the impact on your environment and update your hardening configuration accordingly. Automate this assessment where possible using Azure Policy to continuously evaluate your resources against your security standards.

Conduct periodic penetration testing against your Azure environment. Azure’s penetration testing rules of engagement allow testing without prior notification to Microsoft for most services. Engage a qualified security testing firm to assess your Azure Defender for Cloud deployment using the same techniques that real attackers would employ. The findings from these tests often reveal gaps that automated compliance scans miss.

Hardening Checklist

1. All relevant Defender plans enabled
2. Secure score reviewed and quick wins remediated
3. Governance rules with SLAs and owner assignment
4. MCSB applied plus industry-specific standards
5. Security contacts and alert notifications configured
6. Attack path analysis reviewed regularly
7. Continuous export to SIEM (Sentinel/Log Analytics)
8. Agentless scanning enabled
9. Just-In-Time VM access configured
10. Workflow automation for common remediations

For more details, refer to the official documentation: What is Microsoft Defender for Cloud?, Security policies in Defender for Cloud.