Implementing Microsoft Defender for Cloud to enable cloud security posture management, workload protection across VMs, containers, databases, and storage, configure security recommendations, and set up adaptive security controls with automated remediation.
Instrucciones de origen · Vista previa de solo lectura
name
azure-defender-cloud
description
Implementing Microsoft Defender for Cloud to enable cloud security posture management, workload protection across VMs, containers, databases, and storage, configure security recommendations, and set up adaptive security controls with automated remediation.
When enabling comprehensive security monitoring across Azure subscriptions
When implementing cloud workload protection for VMs, containers, SQL, storage, and Key Vault
When compliance requirements demand continuous assessment against regulatory frameworks
When building adaptive security controls that respond to detected threats
When centralizing security findings from Azure-native and hybrid workloads
Do not use for non-Azure workload protection exclusively (use AWS Security Hub or GCP SCC), for application-level security testing (use Azure DevOps DAST/SAST), or for identity-specific protection (use Microsoft Defender for Identity).
Prerequisites
Azure subscription with Contributor or Security Admin role
Azure Policy enabled for compliance assessment
Log Analytics workspace for diagnostic data collection
Azure Arc connected machines for hybrid server protection
Pricing tier set to Standard for Defender plans (free tier provides CSPM only)
Workflow
Step 1: Enable Defender for Cloud Plans
Enable the appropriate Defender plans for each workload type requiring protection.
# Enable Defender for Cloud CSPM (foundational posture management)
az security pricing create --name CloudPosture --tier standard
# Enable Defender for Servers
az security pricing create --name VirtualMachines --tier standard \
--subplan P2
# Enable Defender for Containers
az security pricing create --name Containers --tier standard
# Enable Defender for Storage
az security pricing create --name StorageAccounts --tier standard \
--subplan PerStorageAccount
# Enable Defender for SQL
az security pricing create --name SqlServers --tier standard
# Enable Defender for Key Vault
az security pricing create --name KeyVaults --tier standard
# Enable Defender for App Service
az security pricing create --name AppServices --tier standard
# Verify all enabled plans
az security pricing list \
--query "[].{Plan:name, Tier:pricingTier, SubPlan:subPlan}" -o table
Step 2: Configure Auto-Provisioning of Security Agents
Enable automatic deployment of monitoring agents to VMs and containers.
# Enable auto-provisioning of Log Analytics agent
az security auto-provisioning-setting update \
--name default --auto-provision on
az security workspace-setting create \
--name default \
--target-workspace
az security setting update \
--name Sentinel \
--setting-kind DataExportSettings
az security auto-provisioning-setting list -o table
# Configure Log Analytics workspace for data collection
# Enable Defender for Containers auto-provisioning components
# Verify auto-provisioning status
Step 3: Review and Prioritize Security Recommendations
Retrieve security recommendations and prioritize remediation based on secure score impact.
# Get the current secure score
az security secure-score list \
--query "[].{Name:displayName, Current:current, Max:max, Percentage:percentage}" -o table
# List all active security recommendations
az security assessment list \
--query "[?status.code=='Unhealthy'].{Name:displayName, Severity:metadata.severity, Category:metadata.category, ResourceCount:status.cause}" \
-o table
# Get recommendations sorted by severity
az security assessment list \
--query "[?status.code=='Unhealthy'] | sort_by(@, &metadata.severity)" \
-o table
# Get detailed recommendation with remediation steps
az security assessment show \
--name ASSESSMENT_ID \
--query "{Name:displayName, Description:metadata.description, Severity:metadata.severity, Remediation:metadata.remediationDescription}"# List recommendations by control
az security secure-score-controls list \
--query "[].{Control:displayName, CurrentScore:current, MaxScore:max, NotHealthy:notHealthyResourceCount}" \
-o table
Step 4: Configure Regulatory Compliance Dashboard
Enable compliance standards and monitor adherence across subscriptions.
# List available regulatory compliance standards
az security regulatory-compliance-standards list \
--query "[].{Standard:name, State:state}" -o table
# Enable specific compliance standards
az security regulatory-compliance-standards update \
--name "CIS-Azure-2.0" --state "Enabled"
az security regulatory-compliance-standards update \
--name "PCI-DSS-4.0" --state "Enabled"
az security regulatory-compliance-standards update \
--name "NIST-SP-800-53-R5" --state "Enabled"# Get compliance status for a specific standard
az security regulatory-compliance-controls list \
--standard-name "CIS-Azure-2.0" \
--query "[].{Control:id, Description:displayName, State:state, PassedResources:passedResources, FailedResources:failedResources}" \
-o table
# Get failing assessments for a control
az security regulatory-compliance-assessments list \
--standard-name "CIS-Azure-2.0" \
--control-name "2.1" \
--query "[?state=='Failed'].{Assessment:id, State:state}" -o table
Step 5: Set Up Security Alerts and Automation
Configure alert notifications and automated response workflows.
# Create security contact for alert notifications
az security contact create \
--name "SecurityTeam" \
--email "security-ops@company.com" \
--phone "+1-555-0199" \
--alert-notifications on \
--alerts-to-admins on
# List active security alerts
az security alert list \
--query "[?status=='Active'].{Name:alertDisplayName, Severity:severity, Time:timeGeneratedUtc, Status:status}" \
-o table
# Create workflow automation for high-severity alerts (Logic App trigger)
az security automation create \
--name "high-severity-alert-response" \
--resource-group "security-rg" \
--scopes "[{\"description\":\"Full subscription\",\"scopePath\":\"/subscriptions/SUB_ID\"}]" \
--sources "[{
\"eventSource\":\"Alerts\",
\"ruleSets\":[{
\"rules\":[{
\"propertyJPath\":\"Severity\",
\"propertyType\":\"String\",
\"expectedValue\":\"High\",
\"operator\":\"Equals\"
}]
}]
}]" \
--actions "[{
\"logicAppResourceId\":\"/subscriptions/SUB_ID/resourceGroups/security-rg/providers/Microsoft.Logic/workflows/alert-response\",
\"actionType\":\"LogicApp\"
}]"
Step 6: Implement Adaptive Application Controls and JIT VM Access
Configure advanced workload protection features for runtime security.
# Enable Just-In-Time VM access
az security jit-policy create \
--resource-group "production-rg" \
--name "jit-policy" \
--virtual-machines "[{
\"id\":\"/subscriptions/SUB_ID/resourceGroups/production-rg/providers/Microsoft.Compute/virtualMachines/web-server-01\",
\"ports\":[
{\"number\":22,\"protocol\":\"TCP\",\"allowedSourceAddressPrefix\":\"*\",\"maxRequestAccessDuration\":\"PT3H\"},
{\"number\":3389,\"protocol\":\"TCP\",\"allowedSourceAddressPrefix\":\"*\",\"maxRequestAccessDuration\":\"PT3H\"}
]
}]"# Request JIT access when needed
az security jit-policy initiate \
--resource-group "production-rg" \
--name "jit-policy" \
--virtual-machines "[{
\"id\":\"VM_ID\",
\"ports\":[{\"number\":22,\"endTimeUtc\":\"2026-02-23T15:00:00Z\",\"allowedSourceAddressPrefix\":\"10.0.1.50\"}]
}]"# Review adaptive application control recommendations
az security adaptive-application-controls list \
--query "[].{Group:displayName, Recommendation:recommendationAction, VMCount:vmRecommendations|length(@)}" \
-o table
Key Concepts
Term
Definition
Microsoft Defender for Cloud
Azure-native security platform providing CSPM and cloud workload protection (CWP) across Azure, hybrid, and multi-cloud environments
Secure Score
Numerical measure of an organization's security posture based on the percentage of security recommendations that have been implemented
Security Recommendation
Actionable guidance from Defender for Cloud to improve security posture, prioritized by severity and secure score impact
Defender Plan
Workload-specific protection tier (Servers, Containers, SQL, Storage, etc.) that enables advanced threat detection for specific resource types
Just-In-Time VM Access
Feature that reduces attack surface by blocking management ports (SSH/RDP) by default and granting time-limited access on request
Adaptive Application Controls
Machine-learning-based allowlisting that recommends which applications should be allowed to run on VMs
Tools & Systems
Microsoft Defender for Cloud: Central security platform with CSPM, CWP, and regulatory compliance capabilities
Azure Policy: Governance service used by Defender for Cloud to evaluate and enforce security configurations
Log Analytics Workspace: Backend data store for security telemetry collected by Defender agents
Azure Logic Apps: Workflow automation for incident response triggered by Defender alerts
Azure Arc: Extends Defender for Cloud protection to hybrid and multi-cloud servers and Kubernetes clusters
Common Scenarios
Scenario: Rolling Out Defender for Cloud Across a Multi-Subscription Enterprise
Context: An enterprise with 20 Azure subscriptions needs to enable Defender for Cloud with server, container, and SQL protection while establishing a compliance baseline against CIS Azure 2.0.
Approach:
Enable the CSPM plan (CloudPosture) across all subscriptions using Azure Policy initiative
Enable Defender for Servers P2, Containers, and SQL on production subscriptions
Configure auto-provisioning to deploy Log Analytics agents to all VMs
Enable CIS Azure 2.0 and PCI DSS 4.0 compliance standards
Create security contacts and configure alert notifications to the SOC team
Set up workflow automation for High severity alerts via Logic Apps
Enable JIT VM access for all production servers to eliminate persistent SSH/RDP exposure
Create a weekly Secure Score report for executive stakeholders
Pitfalls: Defender for Servers P2 costs per server per hour. For environments with many VMs, costs can escalate quickly. Use Defender for Servers P1 for development subscriptions and P2 only for production. Auto-provisioning of agents may conflict with existing agent deployments managed by SCCM or other tools.
