Overview
Microsoft Defender for Resource Manager scans incoming administrative requests to change your infrastructure from both CLI and the Azure portal.
Rationale
Scanning resource requests lets you be alerted every time there is suspicious activity in order to prevent a security threat from being introduced.
Impact
Enabling Microsoft Defender for Resource Manager requires enabling Microsoft Defender for your subscription. Both will incur additional charges.
Remediation guidance
From Azure Console
- Open Microsoft Defender for Cloud | Environment settings
- Select a subscription
- Under
Settings, selectDefender plans - For
Resource Manager, selectOnforStatus - Select Save
Using Azure Command Line Interface
az security pricing create -n 'Arm' --tier 'Standard'
Using Azure PowerShell
Set-AzSecurityPricing -Name 'Arm' -PricingTier 'Standard'
Default Value
By default, Microsoft Defender for Resource Manager is not enabled.
References
- https://azure.microsoft.com/en-us/pricing/details/defender-for-cloud/
- https://learn.microsoft.com/en-us/azure/defender-for-cloud/defender-for-resource-manager-introduction
- https://azure.microsoft.com/en-us/pricing/details/defender-for-cloud/
- https://learn.microsoft.com/en-us/azure/defender-for-cloud/alerts-overview
- https://learn.microsoft.com/en-us/security/benchmark/azure/security-controls-v3-logging-threat-detection#lt-1-enable-threat-detection-capabilities
Service-wide remediation
Recommended when many resources are affected: fix the platform baseline first so new resources inherit the secure setting, then remediate the existing flagged resources in batches.
Azure
Use management group or subscription Azure Policy assignments, remediation tasks where supported, landing-zone standards, and IaC modules so drift is prevented at scale.
Operational rollout
- Fix the baseline first at the account, subscription, project, cluster, or tenant scope that owns this control.
- Remediate the currently affected resources in batches, starting with internet-exposed and production assets.
- Re-scan and track approved exceptions with an owner and expiry date.
Query logic
These are the stored checks tied to this control.
Azure Subscriptions without Microsoft Defender for Resource Manager
Connectors
Covered asset types
Expected check: eq []
{
connectors(
where: { pricing_SOME: { name: "Arm", pricingTier: "Free" } }
) {
...AssetFragment
}
}
Microsoft Azure