Microsoft Defender for Cloud and Microsoft Sentinel: Secure Score, Threat Protection, SIEM and Automated Response
Two Complementary Services
| Service | Role |
|---|---|
| Defender for Cloud | Posture management (CSPM) and workload protection (CWPP) for Azure, AWS, GCP and on-premises |
| Microsoft Sentinel | Cloud SIEM and SOAR: collect logs, detect threats, investigate and automate response |
Defender for Cloud Basics
- Foundational CSPM is free: secure score, recommendations and asset inventory
- Defender CSPM (paid) adds attack path analysis, governance and agentless scanning
- Defender plans protect workloads: Servers, Containers, Storage, SQL, App Service, Key Vault, Databases, APIs and more
- Regulatory compliance dashboard maps controls to standards such as ISO 27001, PCI DSS, NIST and the Microsoft cloud security benchmark
Secure Score
Each recommendation, such as enable MFA, close management ports, encrypt with CMK or apply system updates, adds to your score when fixed. Use it to prioritize.
bash
az security pricing create -n VirtualMachines --tier Standard
az security pricing create -n StorageAccounts --tier Standard
az security pricing list -o table
az security assessment list --query "[?status.code=='Unhealthy'].{name:displayName}" -o table
Just-in-Time VM Access
- Management ports (SSH 22, RDP 3389) stay closed. A user requests access for a few hours from their IP and Defender adds a temporary NSG rule
- Needs Defender for Servers Plan 2 on the VM. Combine with Bastion for better security
Other Protection Features
- Adaptive application controls and file integrity monitoring for servers
- Vulnerability assessment with integrated scanners
- Container image scanning in registries and runtime protection in AKS
- Security alerts and incidents with MITRE ATT&CK mapping, with continuous export to workspaces and Event Hubs
Microsoft Sentinel
- Collect: data connectors for Microsoft Entra ID, Microsoft 365, Defender products, Azure activity, firewalls, AWS CloudTrail, syslog and many more
- Detect: analytics rules (scheduled KQL queries, near-real-time rules, Microsoft security rules, machine learning anomalies and threat intelligence matching)
- Investigate: incidents, entity pages, investigation graph, hunting queries and notebooks
- Respond: automation rules and playbooks built with Logic Apps
kql
// Analytics rule idea: many failed sign-ins followed by a success
let failures = SigninLogs
| where TimeGenerated > ago(1h) and ResultType != 0
| summarize failCount = count() by UserPrincipalName, IPAddress
| where failCount > 10;
SigninLogs
| where TimeGenerated > ago(1h) and ResultType == 0
| join kind=inner failures on UserPrincipalName, IPAddress
| project TimeGenerated, UserPrincipalName, IPAddress, failCount
| Sentinel concept | Meaning |
|---|---|
| Workspace | Log Analytics workspace with Sentinel enabled |
| Connector | Brings data in |
| Analytics rule | Creates alerts and incidents |
| Playbook | Logic App that responds, for example block a user, isolate a VM, post to Teams |
| Workbook | Dashboards |
| Watchlist | Reference lists such as VIP users |
Product direction Microsoft is merging Sentinel into the Defender portal experience. Check current guidance for portal and licensing changes.
Practice
- Enable Defender for Cloud and note the secure score
- Fix three recommendations and watch the score change
- Enable JIT access on a test VM
- Connect Entra ID logs to Sentinel and run a hunting query
Conclusion
Defender for Cloud improves posture with secure score and protects workloads, while Sentinel collects logs, detects threats and automates response. Use both for continuous cloud security.
Quick Summary: two services; Defender; secure score; JIT; Sentinel flow; practice.

