[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71CE4AGVNKXCY4ASR3KJSSZ":3,"skill-same:01M71CE4AGVNKXCY4ASR3KJSSZ":96},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":69,"commitSha":70,"skillDirectory":71,"forksCount":14,"repositoryHtmlUrl":72,"repositoryHomepageUrl":6,"ownerHtmlUrl":73,"ownerBlogUrl":6,"ownerDescription":74,"updatedAt":75,"install":76,"resources":89},"01M71CE4AGVNKXCY4ASR3KJSSZ","azure-defender-audit",null,"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.","DCx7C5\u002Fai-marketplace","DCx7C5","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F42419559?v=4","01M71C01G2AZV3NTNGWAWSHJPP","DC","01M71C01GQW6G50S2BYMS7PP3E",0,"MIT","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fazure\u002Fdefender\u002Faudit\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"defender","azure defender audit","audit","azure","aml","cybersecurity","implementing","across","map","configure security","databases","cm","up","configure","Bash","cwpp","defender-for-cloud","cspm","t1078","SET","2026-11-10 10:12:30",false,"---\nname: azure-defender-audit\ndescription: 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.\ndomain: cybersecurity\nsubdomain: cloud-security\ntags:\n- cloud-security\n- azure\n- defender-for-cloud\n- cspm\n- cwpp\n- security-recommendations\nnist_ai_rmf:\n- MEASURE-2.7\n- MAP-5.1\n- MANAGE-2.4\natlas_techniques:\n- AML.T0070\n- AML.T0066\n- AML.T0082\nnist_csf:\n- PR.IR-01\n- ID.AM-08\n- GV.SC-06\n- DE.CM-01\nmodel: sonnet\nmaxTurns: 20\ntools: [Read, Bash, Glob, Grep]\nmitre_attack:\n- T1078.004\ncapec: []\n---\n\n# Implementing Azure Defender for Cloud\n\n## When to Use\n\n- When enabling comprehensive security monitoring across Azure subscriptions\n- When implementing cloud workload protection for VMs, containers, SQL, storage, and Key Vault\n- When compliance requirements demand continuous assessment against regulatory frameworks\n- When building adaptive security controls that respond to detected threats\n- When centralizing security findings from Azure-native and hybrid workloads\n\n**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\u002FSAST), or for identity-specific protection (use Microsoft Defender for Identity).\n\n## Prerequisites\n\n- Azure subscription with Contributor or Security Admin role\n- Azure Policy enabled for compliance assessment\n- Log Analytics workspace for diagnostic data collection\n- Azure Arc connected machines for hybrid server protection\n- Pricing tier set to Standard for Defender plans (free tier provides CSPM only)\n\n## Workflow\n\n### Step 1: Enable Defender for Cloud Plans\n\nEnable the appropriate Defender plans for each workload type requiring protection.\n\n```bash\n# Enable Defender for Cloud CSPM (foundational posture management)\naz security pricing create --name CloudPosture --tier standard\n\n# Enable Defender for Servers\naz security pricing create --name VirtualMachines --tier standard \\\n  --subplan P2\n\n# Enable Defender for Containers\naz security pricing create --name Containers --tier standard\n\n# Enable Defender for Storage\naz security pricing create --name StorageAccounts --tier standard \\\n  --subplan PerStorageAccount\n\n# Enable Defender for SQL\naz security pricing create --name SqlServers --tier standard\n\n# Enable Defender for Key Vault\naz security pricing create --name KeyVaults --tier standard\n\n# Enable Defender for App Service\naz security pricing create --name AppServices --tier standard\n\n# Verify all enabled plans\naz security pricing list \\\n  --query \"[].{Plan:name, Tier:pricingTier, SubPlan:subPlan}\" -o table\n```\n\n### Step 2: Configure Auto-Provisioning of Security Agents\n\nEnable automatic deployment of monitoring agents to VMs and containers.\n\n```bash\n# Enable auto-provisioning of Log Analytics agent\naz security auto-provisioning-setting update \\\n  --name default --auto-provision on\n\n# Configure Log Analytics workspace for data collection\naz security workspace-setting create \\\n  --name default \\\n  --target-workspace \"\u002Fsubscriptions\u002FSUB_ID\u002FresourceGroups\u002FRG\u002Fproviders\u002FMicrosoft.OperationalInsights\u002Fworkspaces\u002FSecurityWorkspace\"\n\n# Enable Defender for Containers auto-provisioning components\naz security setting update \\\n  --name Sentinel \\\n  --setting-kind DataExportSettings\n\n# Verify auto-provisioning status\naz security auto-provisioning-setting list -o table\n```\n\n### Step 3: Review and Prioritize Security Recommendations\n\nRetrieve security recommendations and prioritize remediation based on secure score impact.\n\n```bash\n# Get the current secure score\naz security secure-score list \\\n  --query \"[].{Name:displayName, Current:current, Max:max, Percentage:percentage}\" -o table\n\n# List all active security recommendations\naz security assessment list \\\n  --query \"[?status.code=='Unhealthy'].{Name:displayName, Severity:metadata.severity, Category:metadata.category, ResourceCount:status.cause}\" \\\n  -o table\n\n# Get recommendations sorted by severity\naz security assessment list \\\n  --query \"[?status.code=='Unhealthy'] | sort_by(@, &metadata.severity)\" \\\n  -o table\n\n# Get detailed recommendation with remediation steps\naz security assessment show \\\n  --name ASSESSMENT_ID \\\n  --query \"{Name:displayName, Description:metadata.description, Severity:metadata.severity, Remediation:metadata.remediationDescription}\"\n\n# List recommendations by control\naz security secure-score-controls list \\\n  --query \"[].{Control:displayName, CurrentScore:current, MaxScore:max, NotHealthy:notHealthyResourceCount}\" \\\n  -o table\n```\n\n### Step 4: Configure Regulatory Compliance Dashboard\n\nEnable compliance standards and monitor adherence across subscriptions.\n\n```bash\n# List available regulatory compliance standards\naz security regulatory-compliance-standards list \\\n  --query \"[].{Standard:name, State:state}\" -o table\n\n# Enable specific compliance standards\naz security regulatory-compliance-standards update \\\n  --name \"CIS-Azure-2.0\" --state \"Enabled\"\n\naz security regulatory-compliance-standards update \\\n  --name \"PCI-DSS-4.0\" --state \"Enabled\"\n\naz security regulatory-compliance-standards update \\\n  --name \"NIST-SP-800-53-R5\" --state \"Enabled\"\n\n# Get compliance status for a specific standard\naz security regulatory-compliance-controls list \\\n  --standard-name \"CIS-Azure-2.0\" \\\n  --query \"[].{Control:id, Description:displayName, State:state, PassedResources:passedResources, FailedResources:failedResources}\" \\\n  -o table\n\n# Get failing assessments for a control\naz security regulatory-compliance-assessments list \\\n  --standard-name \"CIS-Azure-2.0\" \\\n  --control-name \"2.1\" \\\n  --query \"[?state=='Failed'].{Assessment:id, State:state}\" -o table\n```\n\n### Step 5: Set Up Security Alerts and Automation\n\nConfigure alert notifications and automated response workflows.\n\n```bash\n# Create security contact for alert notifications\naz security contact create \\\n  --name \"SecurityTeam\" \\\n  --email \"security-ops@company.com\" \\\n  --phone \"+1-555-0199\" \\\n  --alert-notifications on \\\n  --alerts-to-admins on\n\n# List active security alerts\naz security alert list \\\n  --query \"[?status=='Active'].{Name:alertDisplayName, Severity:severity, Time:timeGeneratedUtc, Status:status}\" \\\n  -o table\n\n# Create workflow automation for high-severity alerts (Logic App trigger)\naz security automation create \\\n  --name \"high-severity-alert-response\" \\\n  --resource-group \"security-rg\" \\\n  --scopes \"[{\\\"description\\\":\\\"Full subscription\\\",\\\"scopePath\\\":\\\"\u002Fsubscriptions\u002FSUB_ID\\\"}]\" \\\n  --sources \"[{\n    \\\"eventSource\\\":\\\"Alerts\\\",\n    \\\"ruleSets\\\":[{\n      \\\"rules\\\":[{\n        \\\"propertyJPath\\\":\\\"Severity\\\",\n        \\\"propertyType\\\":\\\"String\\\",\n        \\\"expectedValue\\\":\\\"High\\\",\n        \\\"operator\\\":\\\"Equals\\\"\n      }]\n    }]\n  }]\" \\\n  --actions \"[{\n    \\\"logicAppResourceId\\\":\\\"\u002Fsubscriptions\u002FSUB_ID\u002FresourceGroups\u002Fsecurity-rg\u002Fproviders\u002FMicrosoft.Logic\u002Fworkflows\u002Falert-response\\\",\n    \\\"actionType\\\":\\\"LogicApp\\\"\n  }]\"\n```\n\n### Step 6: Implement Adaptive Application Controls and JIT VM Access\n\nConfigure advanced workload protection features for runtime security.\n\n```bash\n# Enable Just-In-Time VM access\naz security jit-policy create \\\n  --resource-group \"production-rg\" \\\n  --name \"jit-policy\" \\\n  --virtual-machines \"[{\n    \\\"id\\\":\\\"\u002Fsubscriptions\u002FSUB_ID\u002FresourceGroups\u002Fproduction-rg\u002Fproviders\u002FMicrosoft.Compute\u002FvirtualMachines\u002Fweb-server-01\\\",\n    \\\"ports\\\":[\n      {\\\"number\\\":22,\\\"protocol\\\":\\\"TCP\\\",\\\"allowedSourceAddressPrefix\\\":\\\"*\\\",\\\"maxRequestAccessDuration\\\":\\\"PT3H\\\"},\n      {\\\"number\\\":3389,\\\"protocol\\\":\\\"TCP\\\",\\\"allowedSourceAddressPrefix\\\":\\\"*\\\",\\\"maxRequestAccessDuration\\\":\\\"PT3H\\\"}\n    ]\n  }]\"\n\n# Request JIT access when needed\naz security jit-policy initiate \\\n  --resource-group \"production-rg\" \\\n  --name \"jit-policy\" \\\n  --virtual-machines \"[{\n    \\\"id\\\":\\\"VM_ID\\\",\n    \\\"ports\\\":[{\\\"number\\\":22,\\\"endTimeUtc\\\":\\\"2026-02-23T15:00:00Z\\\",\\\"allowedSourceAddressPrefix\\\":\\\"10.0.1.50\\\"}]\n  }]\"\n\n# Review adaptive application control recommendations\naz security adaptive-application-controls list \\\n  --query \"[].{Group:displayName, Recommendation:recommendationAction, VMCount:vmRecommendations|length(@)}\" \\\n  -o table\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|------------|\n| Microsoft Defender for Cloud | Azure-native security platform providing CSPM and cloud workload protection (CWP) across Azure, hybrid, and multi-cloud environments |\n| Secure Score | Numerical measure of an organization's security posture based on the percentage of security recommendations that have been implemented |\n| Security Recommendation | Actionable guidance from Defender for Cloud to improve security posture, prioritized by severity and secure score impact |\n| Defender Plan | Workload-specific protection tier (Servers, Containers, SQL, Storage, etc.) that enables advanced threat detection for specific resource types |\n| Just-In-Time VM Access | Feature that reduces attack surface by blocking management ports (SSH\u002FRDP) by default and granting time-limited access on request |\n| Adaptive Application Controls | Machine-learning-based allowlisting that recommends which applications should be allowed to run on VMs |\n\n## Tools & Systems\n\n- **Microsoft Defender for Cloud**: Central security platform with CSPM, CWP, and regulatory compliance capabilities\n- **Azure Policy**: Governance service used by Defender for Cloud to evaluate and enforce security configurations\n- **Log Analytics Workspace**: Backend data store for security telemetry collected by Defender agents\n- **Azure Logic Apps**: Workflow automation for incident response triggered by Defender alerts\n- **Azure Arc**: Extends Defender for Cloud protection to hybrid and multi-cloud servers and Kubernetes clusters\n\n## Common Scenarios\n\n### Scenario: Rolling Out Defender for Cloud Across a Multi-Subscription Enterprise\n\n**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.\n\n**Approach**:\n1. Enable the CSPM plan (CloudPosture) across all subscriptions using Azure Policy initiative\n2. Enable Defender for Servers P2, Containers, and SQL on production subscriptions\n3. Configure auto-provisioning to deploy Log Analytics agents to all VMs\n4. Enable CIS Azure 2.0 and PCI DSS 4.0 compliance standards\n5. Create security contacts and configure alert notifications to the SOC team\n6. Set up workflow automation for High severity alerts via Logic Apps\n7. Enable JIT VM access for all production servers to eliminate persistent SSH\u002FRDP exposure\n8. Create a weekly Secure Score report for executive stakeholders\n\n**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.\n\n## Output Format\n\n```\nMicrosoft Defender for Cloud Deployment Report\n=================================================\nOrganization: Acme Corp\nSubscriptions: 20 (12 production, 8 non-production)\nDeployment Date: 2026-02-23\n\nDEFENDER PLANS ENABLED:\n  CloudPosture (CSPM):     20 \u002F 20 subscriptions\n  Servers P2:              12 \u002F 20 (production only)\n  Containers:              12 \u002F 20 (production only)\n  SQL:                     12 \u002F 20 (production only)\n  Storage:                 20 \u002F 20 all subscriptions\n  Key Vault:               20 \u002F 20 all subscriptions\n\nSECURE SCORE:\n  Current: 62% (baseline)\n  Target: 80% within 90 days\n\nCOMPLIANCE STATUS (CIS Azure 2.0):\n  Compliant controls:        78 \u002F 142 (55%)\n  Non-compliant controls:    52 \u002F 142\n  Not applicable:            12 \u002F 142\n\nRECOMMENDATIONS:\n  Critical:    8 recommendations affecting 34 resources\n  High:       24 recommendations affecting 89 resources\n  Medium:     56 recommendations affecting 234 resources\n  Low:        34 recommendations affecting 112 resources\n\nSECURITY ALERTS (Last 7 Days):\n  High severity:    3\n  Medium severity:  12\n  Low severity:     28\n```\n","# Implementing Azure Defender for Cloud\n\n## When to Use\n\n- When enabling comprehensive security monitoring across Azure subscriptions\n- When implementing cloud workload protection for VMs, containers, SQL, storage, and Key Vault\n- When compliance requirements demand continuous assessment against regulatory frameworks\n- When building adaptive security controls that respond to detected threats\n- When centralizing security findings from Azure-native and hybrid workloads\n\n**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\u002FSAST), or for identity-specific protection (use Microsoft Defender for Identity).\n\n## Prerequisites\n\n- Azure subscription with Contributor or Security Admin role\n- Azure Policy enabled for compliance assessment\n- Log Analytics workspace for diagnostic data collection\n- Azure Arc connected machines for hybrid server protection\n- Pricing tier set to Standard for Defender plans (free tier provides CSPM only)\n\n## Workflow\n\n### Step 1: Enable Defender for Cloud Plans\n\nEnable the appropriate Defender plans for each workload type requiring protection.\n\n```bash\n# Enable Defender for Cloud CSPM (foundational posture management)\naz security pricing create --name CloudPosture --tier standard\n\n# Enable Defender for Servers\naz security pricing create --name VirtualMachines --tier standard \\\n  --subplan P2\n\n# Enable Defender for Containers\naz security pricing create --name Containers --tier standard\n\n# Enable Defender for Storage\naz security pricing create --name StorageAccounts --tier standard \\\n  --subplan PerStorageAccount\n\n# Enable Defender for SQL\naz security pricing create --name SqlServers --tier standard\n\n# Enable Defender for Key Vault\naz security pricing create --name KeyVaults --tier standard\n\n# Enable Defender for App Service\naz security pricing create --name AppServices --tier standard\n\n# Verify all enabled plans\naz security pricing list \\\n  --query \"[].{Plan:name, Tier:pricingTier, SubPlan:subPlan}\" -o table\n```\n\n### Step 2: Configure Auto-Provisioning of Security Agents\n\nEnable automatic deployment of monitoring agents to VMs and containers.\n\n```bash\n# Enable auto-provisioning of Log Analytics agent\naz security auto-provisioning-setting update \\\n  --name default --auto-provision on\n\n# Configure Log Analytics workspace for data collection\naz security workspace-setting create \\\n  --name default \\\n  --target-workspace \"\u002Fsubscriptions\u002FSUB_ID\u002FresourceGroups\u002FRG\u002Fproviders\u002FMicrosoft.OperationalInsights\u002Fworkspaces\u002FSecurityWorkspace\"\n\n# Enable Defender for Containers auto-provisioning components\naz security setting update \\\n  --name Sentinel \\\n  --setting-kind DataExportSettings\n\n# Verify auto-provisioning status\naz security auto-provisioning-setting list -o table\n```\n\n### Step 3: Review and Prioritize Security Recommendations\n\nRetrieve security recommendations and prioritize remediation based on secure score impact.\n\n```bash\n# Get the current secure score\naz security secure-score list \\\n  --query \"[].{Name:displayName, Current:current, Max:max, Percentage:percentage}\" -o table\n\n# List all active security recommendations\naz security assessment list \\\n  --query \"[?status.code=='Unhealthy'].{Name:displayName, Severity:metadata.severity, Category:metadata.category, ResourceCount:status.cause}\" \\\n  -o table\n\n# Get recommendations sorted by severity\naz security assessment list \\\n  --query \"[?status.code=='Unhealthy'] | sort_by(@, &metadata.severity)\" \\\n  -o table\n\n# Get detailed recommendation with remediation steps\naz security assessment show \\\n  --name ASSESSMENT_ID \\\n  --query \"{Name:displayName, Description:metadata.description, Severity:metadata.severity, Remediation:metadata.remediationDescription}\"\n\n# List recommendations by control\naz security secure-score-controls list \\\n  --query \"[].{Control:displayName, CurrentScore:current, MaxScore:max, NotHealthy:notHealthyResourceCount}\" \\\n  -o table\n```\n\n### Step 4: Configure Regulatory Compliance Dashboard\n\nEnable compliance standards and monitor adherence across subscriptions.\n\n```bash\n# List available regulatory compliance standards\naz security regulatory-compliance-standards list \\\n  --query \"[].{Standard:name, State:state}\" -o table\n\n# Enable specific compliance standards\naz security regulatory-compliance-standards update \\\n  --name \"CIS-Azure-2.0\" --state \"Enabled\"\n\naz security regulatory-compliance-standards update \\\n  --name \"PCI-DSS-4.0\" --state \"Enabled\"\n\naz security regulatory-compliance-standards update \\\n  --name \"NIST-SP-800-53-R5\" --state \"Enabled\"\n\n# Get compliance status for a specific standard\naz security regulatory-compliance-controls list \\\n  --standard-name \"CIS-Azure-2.0\" \\\n  --query \"[].{Control:id, Description:displayName, State:state, PassedResources:passedResources, FailedResources:failedResources}\" \\\n  -o table\n\n# Get failing assessments for a control\naz security regulatory-compliance-assessments list \\\n  --standard-name \"CIS-Azure-2.0\" \\\n  --control-name \"2.1\" \\\n  --query \"[?state=='Failed'].{Assessment:id, State:state}\" -o table\n```\n\n### Step 5: Set Up Security Alerts and Automation\n\nConfigure alert notifications and automated response workflows.\n\n```bash\n# Create security contact for alert notifications\naz security contact create \\\n  --name \"SecurityTeam\" \\\n  --email \"security-ops@company.com\" \\\n  --phone \"+1-555-0199\" \\\n  --alert-notifications on \\\n  --alerts-to-admins on\n\n# List active security alerts\naz security alert list \\\n  --query \"[?status=='Active'].{Name:alertDisplayName, Severity:severity, Time:timeGeneratedUtc, Status:status}\" \\\n  -o table\n\n# Create workflow automation for high-severity alerts (Logic App trigger)\naz security automation create \\\n  --name \"high-severity-alert-response\" \\\n  --resource-group \"security-rg\" \\\n  --scopes \"[{\\\"description\\\":\\\"Full subscription\\\",\\\"scopePath\\\":\\\"\u002Fsubscriptions\u002FSUB_ID\\\"}]\" \\\n  --sources \"[{\n    \\\"eventSource\\\":\\\"Alerts\\\",\n    \\\"ruleSets\\\":[{\n      \\\"rules\\\":[{\n        \\\"propertyJPath\\\":\\\"Severity\\\",\n        \\\"propertyType\\\":\\\"String\\\",\n        \\\"expectedValue\\\":\\\"High\\\",\n        \\\"operator\\\":\\\"Equals\\\"\n      }]\n    }]\n  }]\" \\\n  --actions \"[{\n    \\\"logicAppResourceId\\\":\\\"\u002Fsubscriptions\u002FSUB_ID\u002FresourceGroups\u002Fsecurity-rg\u002Fproviders\u002FMicrosoft.Logic\u002Fworkflows\u002Falert-response\\\",\n    \\\"actionType\\\":\\\"LogicApp\\\"\n  }]\"\n```\n\n### Step 6: Implement Adaptive Application Controls and JIT VM Access\n\nConfigure advanced workload protection features for runtime security.\n\n```bash\n# Enable Just-In-Time VM access\naz security jit-policy create \\\n  --resource-group \"production-rg\" \\\n  --name \"jit-policy\" \\\n  --virtual-machines \"[{\n    \\\"id\\\":\\\"\u002Fsubscriptions\u002FSUB_ID\u002FresourceGroups\u002Fproduction-rg\u002Fproviders\u002FMicrosoft.Compute\u002FvirtualMachines\u002Fweb-server-01\\\",\n    \\\"ports\\\":[\n      {\\\"number\\\":22,\\\"protocol\\\":\\\"TCP\\\",\\\"allowedSourceAddressPrefix\\\":\\\"*\\\",\\\"maxRequestAccessDuration\\\":\\\"PT3H\\\"},\n      {\\\"number\\\":3389,\\\"protocol\\\":\\\"TCP\\\",\\\"allowedSourceAddressPrefix\\\":\\\"*\\\",\\\"maxRequestAccessDuration\\\":\\\"PT3H\\\"}\n    ]\n  }]\"\n\n# Request JIT access when needed\naz security jit-policy initiate \\\n  --resource-group \"production-rg\" \\\n  --name \"jit-policy\" \\\n  --virtual-machines \"[{\n    \\\"id\\\":\\\"VM_ID\\\",\n    \\\"ports\\\":[{\\\"number\\\":22,\\\"endTimeUtc\\\":\\\"2026-02-23T15:00:00Z\\\",\\\"allowedSourceAddressPrefix\\\":\\\"10.0.1.50\\\"}]\n  }]\"\n\n# Review adaptive application control recommendations\naz security adaptive-application-controls list \\\n  --query \"[].{Group:displayName, Recommendation:recommendationAction, VMCount:vmRecommendations|length(@)}\" \\\n  -o table\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|------------|\n| Microsoft Defender for Cloud | Azure-native security platform providing CSPM and cloud workload protection (CWP) across Azure, hybrid, and multi-cloud environments |\n| Secure Score | Numerical measure of an organization's security posture based on the percentage of security recommendations that have been implemented |\n| Security Recommendation | Actionable guidance from Defender for Cloud to improve security posture, prioritized by severity and secure score impact |\n| Defender Plan | Workload-specific protection tier (Servers, Containers, SQL, Storage, etc.) that enables advanced threat detection for specific resource types |\n| Just-In-Time VM Access | Feature that reduces attack surface by blocking management ports (SSH\u002FRDP) by default and granting time-limited access on request |\n| Adaptive Application Controls | Machine-learning-based allowlisting that recommends which applications should be allowed to run on VMs |\n\n## Tools & Systems\n\n- **Microsoft Defender for Cloud**: Central security platform with CSPM, CWP, and regulatory compliance capabilities\n- **Azure Policy**: Governance service used by Defender for Cloud to evaluate and enforce security configurations\n- **Log Analytics Workspace**: Backend data store for security telemetry collected by Defender agents\n- **Azure Logic Apps**: Workflow automation for incident response triggered by Defender alerts\n- **Azure Arc**: Extends Defender for Cloud protection to hybrid and multi-cloud servers and Kubernetes clusters\n\n## Common Scenarios\n\n### Scenario: Rolling Out Defender for Cloud Across a Multi-Subscription Enterprise\n\n**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.\n\n**Approach**:\n1. Enable the CSPM plan (CloudPosture) across all subscriptions using Azure Policy initiative\n2. Enable Defender for Servers P2, Containers, and SQL on production subscriptions\n3. Configure auto-provisioning to deploy Log Analytics agents to all VMs\n4. Enable CIS Azure 2.0 and PCI DSS 4.0 compliance standards\n5. Create security contacts and configure alert notifications to the SOC team\n6. Set up workflow automation for High severity alerts via Logic Apps\n7. Enable JIT VM access for all production servers to eliminate persistent SSH\u002FRDP exposure\n8. Create a weekly Secure Score report for executive stakeholders\n\n**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.\n\n## Output Format\n\n```\nMicrosoft Defender for Cloud Deployment Report\n=================================================\nOrganization: Acme Corp\nSubscriptions: 20 (12 production, 8 non-production)\nDeployment Date: 2026-02-23\n\nDEFENDER PLANS ENABLED:\n  CloudPosture (CSPM):     20 \u002F 20 subscriptions\n  Servers P2:              12 \u002F 20 (production only)\n  Containers:              12 \u002F 20 (production only)\n  SQL:                     12 \u002F 20 (production only)\n  Storage:                 20 \u002F 20 all subscriptions\n  Key Vault:               20 \u002F 20 all subscriptions\n\nSECURE SCORE:\n  Current: 62% (baseline)\n  Target: 80% within 90 days\n\nCOMPLIANCE STATUS (CIS Azure 2.0):\n  Compliant controls:        78 \u002F 142 (55%)\n  Non-compliant controls:    52 \u002F 142\n  Not applicable:            12 \u002F 142\n\nRECOMMENDATIONS:\n  Critical:    8 recommendations affecting 34 resources\n  High:       24 recommendations affecting 89 resources\n  Medium:     56 recommendations affecting 234 resources\n  Low:        34 recommendations affecting 112 resources\n\nSECURITY ALERTS (Last 7 Days):\n  High severity:    3\n  Medium severity:  12\n  Low severity:     28\n```\n",{"name":5,"tags":44,"capec":47,"model":48,"tools":49,"domain":24,"maxTurns":53,"nist_csf":54,"subdomain":45,"description":7,"nist_ai_rmf":59,"mitre_attack":63,"atlas_techniques":65},[45,22,35,36,34,46],"cloud-security","security-recommendations",[],"sonnet",[50,33,51,52],"Read","Glob","Grep",20,[55,56,57,58],"PR.IR-01","ID.AM-08","GV.SC-06","DE.CM-01",[60,61,62],"MEASURE-2.7","MAP-5.1","MANAGE-2.4",[64],"T1078.004",[66,67,68],"AML.T0070","AML.T0066","AML.T0082","main","a91f1293287ffa9f4f1b8f486cd6e835a1568c84","skills\u002Fcloud\u002Fazure\u002Fdefender\u002Faudit","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace","https:\u002F\u002Fgithub.com\u002FDCx7C5","#Python","2026-09-01 11:21:00",{"source":8,"skillName":5,"commands":77,"prompt":87,"zipAvailable":88},[78,81,84],{"tool":79,"command":80},"npx","npx skills add DCx7C5\u002Fai-marketplace --skill azure-defender-audit",{"tool":82,"command":83},"bunx","bunx skills add DCx7C5\u002Fai-marketplace --skill azure-defender-audit",{"tool":85,"command":86},"pnpm","pnpm dlx skills add DCx7C5\u002Fai-marketplace --skill azure-defender-audit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fazure\u002Fdefender\u002Faudit\u002FSKILL.md",true,[90],{"path":91,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":94,"sourceHtmlUrl":95},"index.json","REFERENCE","参考文档",671,"https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fazure\u002Fdefender\u002Faudit\u002Findex.json",[97,121,142,163,185,201],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":39},"01M71HAPZ01KQ30RKTB0FFSQ05","services-wmi-persistence-detect","Detect WMI event subscription persistence by enumerating ActiveScriptEventConsumer, CommandLineEventConsumer, and permanent subscriptions in the WMI repository.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fservices\u002Fwmi\u002Fpersistence\u002Fdetect\u002FSKILL.md",[],[104,105,106,107,108,109,30,110,111,112,113,114,115,116,117,118,119,24,120],"services","detect","services wmi persistence detect","wmi","persistence","de","process","activescript","event","subscriptions","commandline-consumer","repository","subscription","event-subscription","t1546.003","forensics","process-forensics",{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":39},"01M71HAK6JTTTS229T17WJMMCG","services-wmi-exec-exploit","Perform lateral movement across Windows networks using WMI-based remote execution techniques including Impacket wmiexec.py, CrackMapExec, and native WMI commands for stealthy post-exploitation during red team engagements.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fservices\u002Fwmi\u002Fexec\u002Fexploit\u002FSKILL.md",[],[128,104,129,107,130,131,132,24,33,133,134,26,135,136,109,137,138,139,140,141],"exploit","services wmi exec exploit","exec","remote","traffic","analysis","team","crackmapexec","native","command","lateral movement","read","lateral-movement","Impacket",{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":148,"publishedAt":39},"01M71HAG6MHKNQV8KDZKMT4886","registry-artifact-extract","Extract and analyze Windows Registry hives to uncover user activity, installed software, autostart entries, and evidence of system compromise.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fregistry\u002Fartifact\u002Fextract\u002FSKILL.md",[],[149,150,151,152,153,154,24,33,155,133,156,157,109,139,158,159,160,161,162,48],"artifact","registry","registry artifact extract","extract","evidence-collection","artifact-analysis","collection","analyze","uncover","software","activity","digital-forensics","windows-registry","regripper",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":169,"publishedAt":39},"01M71HACR4A8XTWTTSXK4124AA","processes-token-impersonate-detect","Detect Windows token impersonation and privilege abuse including SeImpersonatePrivilege exploitation via Potato attacks and token stealing techniques.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fprocesses\u002Ftoken\u002Fimpersonate\u002Fdetect\u002FSKILL.md",[],[105,170,171,172,173,174,175,30,176,24,120,177,178,179,180,181,182,183,184,109],"processes token impersonate detect","token","processes","attacks","windows","escalation","techniques","privilege-escalation","seimpersonate","token-impersonation","printspoofer","exploitation","potato","impersonation","via",{"skillNo":186,"name":187,"nameZh":6,"description":188,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":189,"categories":190,"keywords":191,"publishedAt":39},"01M71HAABSB4Z6QFSXEG00R4RK","processes-thread-injection-detect","Detect Windows thread injection techniques including CreateRemoteThread, QueueUserAPC, NtCreateThreadEx, and thread hijacking via process memory analysis.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fprocesses\u002Fthread\u002Finjection\u002Fdetect\u002FSKILL.md",[],[192,193,105,194,172,174,195,30,196,176,24,120,133,197,198,199,200,184,109,110],"thread","processes thread injection detect","injection","memory","process-injection","api","apc-injection","thread-injection","nt-api",{"skillNo":202,"name":203,"nameZh":6,"description":204,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":205,"categories":206,"keywords":207,"publishedAt":39},"01M71HA7H311V5G14WMX58HQSS","processes-hollow-technique-detect","Detect process hollowing (RunPE) by identifying processes with mismatched image paths between PEB and VAD tree, or unmapped PE headers in memory.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fprocesses\u002Fhollow\u002Ftechnique\u002Fdetect\u002FSKILL.md",[],[208,105,172,209,195,30,210,211,24,120,212,213,214,215,216,217,109,110,218,219],"processes hollow technique detect","tree","memory-forensics","process-hollow","peb","runpe","image","pe-header","in memory","with","mismatched","headers"]