Microsoft Defender for Cloud Plans Not Enabled
The subscription relies only on Defender for Cloud's free posture features, so threat detection for servers, storage, databases, key vaults and other workloads is not running.
| Severity | Low |
| CVSS 3.1 | 3.1 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N Open in the calculator |
| CVSS 4.0 | 2.3 CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N Open in the calculator |
| CWE | CWE-778: Insufficient Logging |
| OWASP Top 10 | A09:2025 Security Logging and Alerting Failures |
| Category | Insufficient Logging |
Description
Microsoft Defender for Cloud provides free foundational posture management, which assesses configuration against its recommendations, and paid Defender plans that add threat detection and protection for specific kinds of workload. These include Defender for Servers, Storage, Databases, Containers, App Service, Key Vault, Resource Manager and APIs. Each plan is enabled per subscription, and while a plan is off, Defender for Cloud raises no security alerts for that kind of resource.
The finding applies where the plans relevant to a subscription's resources are switched off, for example Defender for Servers on a subscription with virtual machines, or Defender for Storage where sensitive data is held. This does not in itself let an attacker into the environment, but it removes a layer of detection that would otherwise alert the organisation to attacks in progress against its Azure workloads.
Activity such as brute-force attempts against SQL logins, malware uploaded to storage, unusual access to key vault secrets and suspicious management operations then goes undetected unless another tool covers it, so attackers can remain in the environment for longer, and the organisation may learn of a compromise only from its consequences. The impact is lower where equivalent detection comes from other tools, such as endpoint detection and response on servers and a monitored SIEM that receives the relevant logs.
The weakness is identified in Defender for Cloud's environment settings, which list each subscription's plans and their status, or with az security pricing list, where plans that are off show the Free tier.
Remediation
- Enable the Defender plans that match the resources in each subscription, prioritising production and internet-facing workloads: typically Servers, Storage, Databases, Key Vault, Resource Manager, App Service and Containers.
- Apply the plans consistently through Azure Policy at management group level, so that new subscriptions are covered automatically.
- Configure email notifications to the security contacts for alerts of an appropriate severity, and stream alerts to the organisation's SIEM, for example through the Microsoft Sentinel connector or continuous export.
- Define who triages Defender for Cloud alerts and how quickly, so that alerts lead to action.
- Review the foundational posture recommendations, which remain available without paid plans, and remediate the high-severity ones.
Where cost prevents enabling every plan, start with the subscriptions that hold the most sensitive data or the most exposed workloads, and record the compensating detection for the rest. Confirm the fix with az security pricing list showing the Standard tier for the required plans, and by generating sample alerts in Defender for Cloud to check that notifications reach the right people.
References
Add This Finding to Your Library
In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.
Free trialYour trial starts when your portal goes live, not when you sign up, so the time you spend setting up does not count. · No card required
Only need the reporting? Our reporting tool is free and open source, with the same library.