Microsoft Defender for Cloud
Security alerts, recommendations, and regulatory-compliance state across your Azure subscriptions.
What CMDash reads
- Incidents & alerts
- Vulnerabilities
- Maturity telemetry
Syncs only read from Microsoft Defender for Cloud. Some integrations also support write-back actions on Command and Enterprise plans, such as opening a ticket or deactivating a user.
How you connect
OAuth 2.0 through a CMDash-hosted app.
Once connected, CMDash syncs it every 4 hours by default. What it finds maps to your controls through rules you install or write.
Where this fits in your frameworks
- SOC 2 Type II — Incidents & alerts feeds Monitoring Activities
- HITRUST CSF v11 — Vulnerabilities feeds Risk Management
This is where Microsoft Defender for Cloud’s data is documented as relevant on our framework pages — not a pre-built, automatic control mapping. You configure which controls it maps to inside CMDash.
Also in Cloud Security
Ready to see your posture?
Start a 30-day free trial of any paid plan — a card is required, and it converts unless you cancel — or sign up for Free with no card at all.