agentleFS
ricmmartinsricmmartins/azure-sre-agent-skills/skills/02-compliance-governance/SKILL.md

compliance-governance-audit

Skill70 starsChanged 4 months agoMITView on GitHub

Audit Azure environment for compliance and governance posture. Checks Azure Policy, RBAC, tagging, resource locks, naming conventions, and regulatory alignment. Use when asked about compliance, governance, audit readiness, or policy violations.

The file

Show its rules and text

We split this skill into the rules it gives an agent

21 rules. About 0 are common, 18 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈18

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use Unicode emoji characters directly (🟢 🟡 🔴) in ALL output — headers, tables, findings, bullet points, everywhere.

    line 15
  2. Distinctive:

    Check overall policy compliance state.

    line 32
  3. Distinctive:

    Check for orphaned policy assignments (assigned but no effect)

    line 40
  4. Distinctive:

    Verify initiative assignments for regulatory frameworks (CIS, NIST, etc.)

    line 41
  5. Distinctive:

    Classic admins: Check for legacy co-administrators

    line 57
  6. Distinctive:

    Check mandatory tags across all resources.

    line 66
  7. Distinctive:

    Check critical resources for delete/read-only locks.

    line 84
  8. Distinctive:

    Verify production databases have delete locks

    line 90
  9. Distinctive:

    Verify production storage accounts have delete locks

    line 91
  10. Distinctive:

    Verify networking resources (VNets, ExpressRoute) have locks

    line 92
  11. Very specific:

    Check against Azure naming conventions (e.g., rg-, vnet-, vm-, st, kv-)

    line 99
  12. Distinctive:

    Check for resources with public endpoints that should be private

    line 104
  13. Distinctive:

    Verify NSG flow logs are enabled

    line 105
  14. Distinctive:

    Check for Network Watcher in all active regions

    line 106
  15. Distinctive:

    Verify DDoS protection on VNets with public-facing resources

    line 107
  16. Distinctive:

    Check that all critical resources have diagnostic settings enabled

    line 110
  17. Distinctive:

    Verify logs flow to a central Log Analytics workspace

    line 111
  18. Distinctive:

    Check Activity Log export at subscription level

    line 112
  19. Distinctive:

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

    line 130
  20. Distinctive:

    When exceptions are provided:

    line 140
  21. Very specific:

    Use GetAzCliHelp to validate the command syntax before suggesting

    line 178

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

Compliance & Governance Audit

Purpose

Assess the governance posture of Azure subscriptions by auditing policies, RBAC assignments, tagging standards, resource locks, and regulatory alignment. Produce a compliance scorecard with remediation steps.

CRITICAL formatting rule

Use Unicode emoji characters directly (🟢 🟡 🔴) in ALL output — headers, tables, findings, bullet points, everywhere. NEVER use emoji shortcodes like :red_circle:, :yellow_circle:, :green_circle:, or any :name: syntax. This applies to every section of the report without exception.

When to use this skill

  • User asks "are we compliant?"
  • User asks about governance, policy violations, or audit readiness
  • Pre-audit preparation (SOC2, ISO 27001, HIPAA, etc.)
  • Monthly governance review

Pre-check

Confirm with the user:

  • Scope: which subscriptions/management groups
  • Compliance framework (if any): SOC2, ISO 27001, HIPAA, PCI-DSS, CIS Benchmarks, or general best practices
  • Any known exceptions or waivers

Audit procedure

Step 1: Azure Policy compliance

Check overall policy compliance state.

az policy state summarize --query "value[].{policy:policyDefinitionName, nonCompliant:nonCompliantResources}" -o table
  1. List all non-compliant resources grouped by policy
  2. Identify policies in "audit" mode that should be "deny"
  3. Check for orphaned policy assignments (assigned but no effect)
  4. Verify initiative assignments for regulatory frameworks (CIS, NIST, etc.)

Report:

  • Total policies assigned
  • % compliant
  • Top 5 violated policies with resource count

Step 2: RBAC review

Audit role assignments for least-privilege violations.

az role assignment list --all --query "[].{principal:principalName, role:roleDefinitionName, scope:scope}" -o table
  1. Owner count: Flag if > 3 Owners at subscription level
  2. Contributor sprawl: List all Contributor assignments — flag service principals with Contributor when a custom role would suffice
  3. Classic admins: Check for legacy co-administrators
    az role assignment list --include-classic-administrators -o table
  4. Guest users with privileged roles: Flag external identities with Owner/Contributor
  5. Stale assignments: Cross-reference with sign-in logs — flag principals that haven't signed in for 90+ days
  6. Custom roles: Review custom role definitions for overly broad permissions (e.g., * actions)

Step 3: Tagging compliance

Check mandatory tags across all resources.

Define expected mandatory tags (confirm with user or use defaults):

  • environment (prod/staging/dev/test)
  • owner (team or individual)
  • cost-center (billing code)
  • application (workload name)
az resource list --query "[?tags.environment==null || tags.owner==null].{name:name, type:type, rg:resourceGroup, tags:tags}" -o table

Report:

  • % of resources with all mandatory tags
  • Top offending resource groups
  • Resources with no tags at all

Step 4: Resource locks

Check critical resources for delete/read-only locks.

az lock list --query "[].{name:name, level:level, resource:resourceId}" -o table
  1. Verify production databases have delete locks
  2. Verify production storage accounts have delete locks
  3. Verify networking resources (VNets, ExpressRoute) have locks
  4. Flag production resources without any lock

Step 5: Naming conventions

Analyze resource naming patterns.

  1. Extract all resource names and types
  2. Check against Azure naming conventions (e.g., rg-, vnet-, vm-, st, kv-)
  3. Flag resources that don't follow a consistent pattern
  4. Report % compliance with naming standards

Step 6: Network governance

  1. Check for resources with public endpoints that should be private
  2. Verify NSG flow logs are enabled
  3. Check for Network Watcher in all active regions
  4. Verify DDoS protection on VNets with public-facing resources

Step 7: Diagnostic settings

  1. Check that all critical resources have diagnostic settings enabled
  2. Verify logs flow to a central Log Analytics workspace
  3. Check Activity Log export at subscription level
az monitor diagnostic-settings subscription list --subscription <id> -o table

Scoring model

RatingMeaning
🟢 CompliantMeets standard, no action needed
🟡 PartialPartially implemented, needs improvement
🔴 Non-compliantMissing or misconfigured, action required

Reminder: use the actual Unicode characters 🟢 🟡 🔴 above, never shortcodes.

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
2.1 Owner countFounding engineers require Owner for break-glass access
3.1 Tagging complianceLegacy resource groups exempt until Q3 migration
4.2 Production locksTerraform-managed resources use state locking instead

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)

Compliance & Governance Audit Report

FieldValue
Subscription(name + ID)
Assessment DateYYYY-MM-DD
Overall ScoreXX%

Governance scorecard

AreaStatusCompliantPartialNon-compliantScore
Azure Policy🟡XYZ%
RBAC🔴.........%
Tagging🟡.........%
Resource Locks🔴.........%
Naming🟢.........%
Network Gov.🟡.........%
Diagnostics🟡.........%
Overall%

Critical findings (act now)

Items that represent immediate risk or audit failure.

Remediation plan

For each finding:

  • What's wrong
  • Why it matters
  • How to fix it (with az cli command or portal steps)
  • Use GetAzCliHelp to validate the command syntax before suggesting
  • Include the official Microsoft Learn documentation link
  • Estimated effort
  • Priority (Critical/High/Medium/Low)

References

Regulatory mapping (if framework specified)

Map findings to specific controls (e.g., SOC2 CC6.1, ISO 27001 A.9.2.3).

Sample output

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

Compliance & Governance Audit Report

FieldValue
Subscriptioncontoso-prod-001 (a1b2c3d4-e5f6-7890-abcd-ef1234567890)
Assessment Date2026-07-15
Overall Score61%

Governance scorecard

AreaStatusCompliantPartialNon-compliantScore
Azure Policy🟡185369%
RBAC🔴21333%
Tagging🟡4512869%
Resource Locks🔴10325%
Naming🟢526287%
Network Gov.🟡31160%
Diagnostics🟡42157%
Overall61%

Critical findings (sample)

#FindingAreaSeverity
16 subscription-level Owners detected (limit: 3)RBAC🔴 Critical
22 guest users with Contributor role on productionRBAC🔴 Critical
3SQL Server sql-contoso-prod has no delete lockResource Locks🔴 High
48 resources in rg-app-prod missing cost-center tagTagging🟡 Medium

Remediation guidance (sample)

# Remove excess Owner assignments
az role assignment delete --assignee user@external.com --role Owner --scope /subscriptions/a1b2c3d4-...

# Add delete lock to production SQL Server
az lock create --name CanNotDelete --resource-group rg-data-prod --resource sql-contoso-prod --resource-type Microsoft.Sql/servers --lock-type CanNotDelete

# Tag resources with missing cost-center
az resource tag --ids /subscriptions/.../resourceGroups/rg-app-prod/providers/Microsoft.Web/sites/app-api-prod --tags cost-center=CC-1234 environment=prod owner=platform-team

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.