Azure (Microsoft) logo

Skill

defender_secure_score_monitor

monitor and improve Microsoft Defender Secure Score

Covers Security Azure Microsoft Defender Monitoring

Description

Monitor and improve Microsoft Defender for Cloud Secure Score. Tracks score trends, identifies quick wins, checks Defender plan coverage, and highlights critical security recommendations. Use when asked about secure score, security posture, or Defender status.

SKILL.md

Defender Secure Score Monitor

Purpose

Track and improve your Microsoft Defender for Cloud Secure Score through focused monitoring, trend analysis, and actionable remediation guidance.

Procedure

Step 1: Current Secure Score

az rest --method get --url "https://management.azure.com/subscriptions/<sub-id>/providers/Microsoft.Security/secureScores/ascScore?api-version=2020-01-01"
az rest --method get --url "https://management.azure.com/subscriptions/<sub-id>/providers/Microsoft.Security/secureScores/ascScore/secureScoreControls?api-version=2020-01-01"

Report current score (X/Y points, Z%), top 5 controls with most room for improvement.

Step 2: Unhealthy assessments

az rest --method get --url "https://management.azure.com/subscriptions/<sub-id>/providers/Microsoft.Security/assessments?api-version=2021-06-01" \
  --query "value[?properties.status.code=='Unhealthy'].{displayName:properties.displayName, severity:properties.metadata.severity}"

Group by severity: 🔴 High, 🟡 Medium, 🟢 Low.

Step 3: Quick wins

Identify recommendations that affect the most resources, have the highest point value, and can be fixed with a single command or policy (HTTPS-only, secure transfer, enable Defender plans, restrict public access).

Step 4: Defender plan coverage

az security pricing list --query "[].{plan:name, tier:pricingTier, subPlan:subPlan}" -o table

Check: Servers (P2), App Service, SQL, Storage, Containers, Key Vault, Resource Manager, DNS. Flag disabled plans with estimated score impact.

Step 5: Attack surface indicators

  1. Public management ports (SSH/RDP open to internet)
  2. Storage accounts with public blob access
  3. SQL servers with public endpoint
  4. Key Vaults accessible from public network

Step 6: Credential hygiene

Check Key Vault secrets and certificates expiring within 30 days, and app registrations with expiring credentials.

Scoring

LevelCriteria
🔴 CriticalActive exposure, immediate risk
🟠 HighSignificant gap, low-effort exploit
🟡 MediumGap exists, specific conditions needed
🟢 LowBest practice deviation, minimal risk

Sample output

FieldValue
Subscriptioncontoso-prod-001
Secure Score38.50 / 56 (69%)
PriorityActionPointsEffort
1Enable HTTPS-only on 3 App Services+45 min
2Enable Defender for Storage+32 min
3Restrict SQL public access+330 min
Total achievable+10~40 min

References

More from Azure (Microsoft)

View publisher

© 2026 YourAI.tools. Every skill from an identity-verified publisher.

Independent catalog. Not affiliated with, endorsed by, or sponsored by Anthropic or any listed publisher. All trademarks belong to their respective owners.