agentleFS
ricmmartinsricmmartins/azure-sre-agent-skills/skills/06-defender-secure-score/SKILL.md

defender-secure-score-monitor

Skill70 starsChanged 4 months agoMITView on GitHub

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

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before a security audit or customer questionnaire

    line 18
  2. Distinctive:

    After deploying new resources (to check score impact)

    line 19
  3. Distinctive:

    Check which Defender plans are enabled.

    line 69
  4. Distinctive:

    Check the most exploitable security gaps.

    line 88
  5. Distinctive:

    Check for expiring secrets that could cause outages or security drift.

    line 111
  6. Distinctive:

    If the user provides a list of accepted exceptions, do not flag those items.

    line 141
  7. Distinctive:

    When exceptions are provided:

    line 151
  8. Very specific:

    Use GetAzCliHelp to validate the command syntax before suggesting.

    line 187

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
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. Answers "what's our security score and how do we improve it?"

When to use this skill

  • User asks "what's our secure score?"
  • User asks how to improve security posture
  • Weekly security posture check
  • Before a security audit or customer questionnaire
  • After deploying new resources (to check score impact)

Difference from Compliance/Governance Audit

The Compliance skill does a broad governance audit (policy, RBAC, tagging, locks, naming). This skill is laser-focused on Defender for Cloud Secure Score — the single most important security KPI — and provides targeted actions to improve it.

Assessment procedure

Step 1: Current Secure Score

Get the overall score and per-control breakdown.

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"

Note: The az security secure-scores list CLI command may fail in some environments. The REST API approach above is more reliable. Replace <sub-id> with the target subscription ID.

Report:

  • Current Secure Score: X% (X/Y points)
  • Trend (if memory available): improved/declined vs. last check
  • Top 5 controls with the most room for improvement (highest max - current)

Step 2: Unhealthy assessments (recommendations)

Get the list of active security recommendations.

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, category:properties.metadata.categories[0], resourceId:properties.resourceDetails.id}"

Group by severity:

  • 🔴 High: Must fix — significant risk
  • 🟡 Medium: Should fix — moderate risk
  • 🟢 Low: Nice to have — minimal risk

Step 3: Quick wins (most points for least effort)

Identify recommendations that:

  1. Affect the most resources (batch fix possible)
  2. Have the highest point value per control
  3. Can be fixed with a single CLI command or policy

Examples of quick wins:

  • Enable HTTPS-only on App Services
  • Enable secure transfer on storage accounts
  • Enable Defender plans that are off
  • Restrict public network access

Step 4: Defender plan coverage

Check which Defender plans are enabled.

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

Expected plans to be enabled for full coverage:

  • Servers (P2 recommended)
  • App Service
  • SQL (databases)
  • Storage
  • Containers (with vulnerability assessment)
  • Key Vault
  • Resource Manager (ARM)
  • DNS

Flag disabled plans and estimate score impact of enabling them.

Step 5: Attack surface indicators

Check the most exploitable security gaps.

  1. Public management ports (SSH/RDP open to internet):
    az graph query -q "resources | where type == 'microsoft.network/networksecuritygroups' | mvexpand rules = properties.securityRules | where rules.properties.access == 'Allow' and rules.properties.direction == 'Inbound' and (rules.properties.destinationPortRange == '22' or rules.properties.destinationPortRange == '3389' or rules.properties.destinationPortRange == '*') and rules.properties.sourceAddressPrefix in ('*', '0.0.0.0/0', 'Internet')" -o table
  2. Storage accounts with public blob access:
    az storage account list --query "[?allowBlobPublicAccess==true].{name:name, rg:resourceGroup}" -o table
  3. SQL servers with public endpoint:
    az sql server list --query "[?properties.publicNetworkAccess=='Enabled'].{name:name, rg:resourceGroup}" -o table
  4. Key Vaults accessible from public network:
    az keyvault list --query "[?properties.publicNetworkAccess=='Enabled'].{name:name, rg:resourceGroup}" -o table

Step 6: Credential and certificate hygiene

Check for expiring secrets that could cause outages or security drift.

  1. Key Vault secrets expiring within 30 days (per vault):
    az keyvault secret list --vault-name <vault> --query "[?attributes.expires!=null && attributes.expires<'$(date -u -d '30 days' +%Y-%m-%dT%H:%M:%SZ)']" -o table
  2. Key Vault certificates expiring within 30 days (per vault):
    az keyvault certificate list --vault-name <vault> --query "[?attributes.expires!=null && attributes.expires<'$(date -u -d '30 days' +%Y-%m-%dT%H:%M:%SZ)']" -o table
  3. App registrations with expiring secrets:
    az ad app list --query "[].{name:displayName, creds:passwordCredentials[?endDateTime<'$(date -u -d '30 days' +%Y-%m-%dT%H:%M:%SZ)']}" --all -o table

Note on date handling: The SRE Agent sandbox runs Linux. Use $(date -u -d '30 days' +%Y-%m-%dT%H:%M:%SZ) for date calculations.

Risk scoring

LevelCriteriaColor
CriticalActive exposure, immediate risk of breach🔴
HighSignificant gap, exploit requires minimal effort🟠
MediumGap exists but requires specific conditions to exploit🟡
LowBest practice deviation, minimal immediate risk🟢

Accepted exceptions (optional)

If the user provides a list of accepted exceptions, do not flag those items. Instead, note them in the report as Accepted Exception with the reason provided.

Example format the user may provide:

CheckReason
3.1 Defender for DNSDNS plan deprecated by Microsoft, not applicable
5.2 Public blob access on storagePublic read access required for CDN-served static assets
5.4 Key Vault public accessKey Vault is accessed from hybrid on-prem workloads

When exceptions are provided:

  • Skip the flagged checks in scoring
  • List them in a separate "Accepted Exceptions" section at the end of the report
  • Recalculate the overall score excluding excepted checks

Expected output

Report header (mandatory — use this exact format)

Defender Secure Score Report

FieldValue
Subscription(name + ID)
Assessment DateYYYY-MM-DD
Overall ScoreXX.XX / YY (ZZ%)

Then present the gap summary:

The subscription is earning only ZZ% of its maximum Secure Score. There is a N-point gap to close.

Score improvement plan

PriorityActionPointsEffortResources affected
1Enable HTTPS-only on 4 App Services+45 minapp-web-, app-api-
2Enable Defender for Storage+32 minsubscription-level
3Restrict SQL public access on 2 servers+330 minsql-prod-, sql-staging-
4Add NSG to 2 subnets without rules+215 minsubnet-data-, subnet-mgmt-
Total achievable+12~1 hour

Critical findings (fix now)

Items that represent immediate exploitable risk.

Remediation commands

Pre-formatted az cli commands for each quick win, ready to approve and execute. Use GetAzCliHelp to validate the command syntax before suggesting.

# Enable HTTPS-only on App Service
az webapp update --name <app> --resource-group <rg> --set httpsOnly=true

# Enable Defender for Storage
az security pricing create --name StorageAccounts --tier Standard

References

Recommended cadence

Schedule this skill as a weekly task via SRE Agent scheduled tasks for continuous score improvement tracking.

Sample output

The following is a redacted example of what the report looks like when run against a subscription.

Defender Secure Score Report

FieldValue
Subscriptioncontoso-prod-001 (a1b2c3d4-e5f6-7890-abcd-ef1234567890)
Assessment Date2026-07-15
Overall Score38.50 / 56 (69%)

The subscription is earning only 69% of its maximum Secure Score. There is a 17.5-point gap to close.

Score improvement plan

PriorityActionPointsEffortResources affected
1Enable HTTPS-only on 3 App Services+45 minapp-web-prod, app-api-prod, app-admin-prod
2Enable Defender for Storage+32 minsubscription-level
3Restrict SQL public access on 2 servers+330 minsql-contoso-prod, sql-contoso-staging
4Add NSG to 2 subnets without rules+215 minsubnet-data-prod, subnet-mgmt-prod
5Rotate 3 expiring Key Vault secrets+1.520 minkv-contoso-prod
Total achievable+13.5~1.5 hours

Critical findings (sample)

#FindingSeverityResources
1SSH port 22 open to internet on NSG nsg-mgmt-prod🔴 Critical2 VMs exposed
2Storage account stcontosoprod allows public blob access🔴 Critical1 account
3Defender for Containers disabled🟠 HighAKS cluster aks-app-prod

Defender plan coverage

PlanStatusImpact
Cloud Posture (CSPM)✅ Standard—
Servers✅ P2—
Storage❌ Free+3 points if enabled
Containers❌ Free+2 points if enabled
Key Vault✅ Standard—
App Service✅ Standard—

Remediation commands (sample)

# Enable HTTPS-only on App Service
az webapp update --name app-web-prod --resource-group rg-app-prod --set httpsOnly=true

# Enable Defender for Storage
az security pricing create --name StorageAccounts --tier Standard

# Restrict SQL Server public access
az sql server update --name sql-contoso-prod --resource-group rg-data-prod --set publicNetworkAccess="Disabled"

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.