digital-native-governance-check
Assess Azure governance maturity for Digital Natives and startups. Detects the most common anti-patterns from the "Digital Natives on Azure" series: incomplete Service Health alerts, flat subscription topology without Management Groups, excessive RBAC (everyone is Owner), missing budget alerts, no Managed Identity usage, unprotected web apps without WAF/DDoS, and missing environment separation. Produces a scored maturity report (Foundation → Developing → Established → Optimized). Use when asked about startup readiness, governance maturity, "are we production-ready?", or before a customer security questionnaire.
ricmmartins · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add ricmmartins/azure-sre-agent-skills --skill digital-native-governance-check技能说明
name: digital-native-governance-check description: > Assess Azure governance maturity for Digital Natives and startups. Detects the most common anti-patterns from the "Digital Natives on Azure" series: incomplete Service Health alerts, flat subscription topology without Management Groups, excessive RBAC (everyone is Owner), missing budget alerts, no Managed Identity usage, unprotected web apps without WAF/DDoS, and missing environment separation. Produces a scored maturity report (Foundation → Developing → Established → Optimized). Use when asked about startup readiness, governance maturity, "are we production-ready?", or before a customer security questionnaire. tools:
- RunAzCliReadCommands
Digital Native Governance Check
Purpose
Evaluate whether a startup's Azure environment has the foundational governance that enterprise customers, investors, and auditors expect. Produces a maturity score (0–100) with clear next steps.
This is NOT a deep compliance audit (use the Compliance & Governance skill for that). This is a focused "did you get the basics right?" diagnostic for teams of 5–50 engineers who set up Azure fast and moved on.
When to use this skill
- Startup preparing for first enterprise customer security review
- CTO asks "are we production-ready?"
- Pre-Series A infrastructure maturity check
- After first incident: "what basics did we miss?"
- Quarterly governance health check for Digital Natives
Maturity levels
| Score | Level | Meaning |
|---|---|---|
| 0–39 | 🔴 Foundation | Governance basics missing — will fail any security questionnaire |
| 40–69 | 🟡 Developing | Some controls exist but significant gaps remain |
| 70–89 | 🟢 Established | Solid posture — can pass most security reviews |
| 90–100 | 🏆 Optimized | Enterprise-grade governance on Azure |
Assessment procedure
Run all checks in parallel where possible. Score each and sum for total.
🏥 CATEGORY 1 — Alerting & Observability (20 points)
Detects: "Azure VM went down and nobody knew" + "you configured one alert type out of four"
Check 1.1 — Service Health alerts exist (8 pts)
az monitor activity-log alert list \
--subscription <sub-id> \
--query "[?contains(to_string(condition.allOf), 'ServiceHealth')].{name:name, enabled:enabled}" \
-o json
Scoring:
- 8 pts: Alert exists covering all 4 event types (Service Issues, Health Advisories, Planned Maintenance, Security Advisories)
- 4 pts: Alert exists but covers only 1–2 types
- 0 pts: No Service Health alerts at all
Check 1.2 — Resource Health alerts for compute (6 pts)
az monitor activity-log alert list \
--subscription <sub-id> \
--query "[?contains(to_string(condition.allOf), 'ResourceHealth')].{name:name, enabled:enabled}" \
-o json
Scoring:
- 6 pts: Resource Health alerts exist and are enabled
- 0 pts: No Resource Health alerts — VMs can go Unavailable silently
📖 https://learn.microsoft.com/en-us/azure/service-health/resource-health-alert-monitor-guide
Check 1.3 — Action Groups with valid receivers (6 pts)
az monitor action-group list \
--subscription <sub-id> \
--query "[].{name:name, emails:length(emailReceivers), webhooks:length(webhookReceivers)}" \
-o table
Scoring:
- 6 pts: Action group with email + at least one other channel (webhook, SMS)
- 3 pts: Action group with email only
- 0 pts: No action groups configured
📖 https://learn.microsoft.com/en-us/azure/azure-monitor/alerts/action-groups
🏗️ CATEGORY 2 — Subscription Topology (20 points)
Detects: "the flat subscription problem" + "dev/test/prod in the same subscription"
Check 2.1 — Management Groups beyond Tenant Root (8 pts)
az account management-group list \
--query "[].{name:name, displayName:displayName}" \
-o table
Scoring:
- 8 pts: Custom MG hierarchy exists (nonprod/prod/platform pattern)
- 4 pts: At least one custom MG beyond Tenant Root Group
- 0 pts: Only Tenant Root Group — completely flat
📖 https://learn.microsoft.com/en-us/azure/governance/management-groups/overview
Check 2.2 — Environment separation (8 pts)
az account list --all \
--query "[?state=='Enabled'].{name:name, id:id}" \
-o table
Look for prod/nonprod/dev/staging patterns in subscription names.
Scoring:
- 8 pts: Clear separation (prod ≠ nonprod in distinct subscriptions)
- 4 pts: Multiple subscriptions but unclear separation
- 0 pts: Single subscription for everything
Check 2.3 — Resource Locks on critical infrastructure (4 pts)
az lock list --subscription <sub-id> \
--query "[].{name:name, level:level, notes:notes}" \
-o table
Scoring:
- 4 pts: CanNotDelete locks on infra resources (Log Analytics, Key Vault, Terraform state)
- 2 pts: Locks exist but only on non-critical resources
- 0 pts: Zero locks — anything can be accidentally deleted
📖 https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/lock-resources
💰 CATEGORY 3 — Cost Controls (15 points)
Detects: "surprise bill" + "VMs running in dev all weekend"
Check 3.1 — Budget alerts configured (8 pts)
az rest --method get \
--url "https://management.azure.com/subscriptions/<sub-id>/providers/Microsoft.Consumption/budgets?api-version=2023-11-01"
Scoring:
- 8 pts: Budget exists with notifications at 80% and 100%
- 4 pts: Budget exists but missing thresholds or notifications
- 0 pts: No budgets — first warning is the invoice
📖 https://learn.microsoft.com/en-us/azure/cost-management-billing/costs/tutorial-acm-create-budgets
Check 3.2 — Azure Advisor cost recommendations addressed (4 pts)
az advisor recommendation list --c
阅读完整来源 ↗