
azure-inspector
GRC connector for Azure: Entra ID, Storage, Key Vault, Monitor, and Defender for Cloud to v1 finding contract
- version
- 0.1.0
- GitHub stars
- 436
Install
/plugin install azure-inspector@grc-engineering-suiteRun it inside Claude Code after adding the marketplace with /plugin marketplace add GRCEngClub/claude-grc-engineering.
Contents
Discovered from sourceSkills 1
azure-inspector expert
Use this skill when interpreting azure-inspector findings or explaining Azure control gaps.
Checks This Connector Runs
Entra ID
| SCF | Check | Typical outcome |
|---|---|---|
| IAC-01.1 | MFA posture needs Graph/authentication-method verification | inconclusive when Azure CLI cannot prove coverage |
| IAC-04 | Enabled Conditional Access policies exist | high fail if none found |
Storage accounts
| SCF | Check | Severity |
|---|---|---|
| CRY-05 | Blob/file encryption enabled | high if disabled |
| DCH-01.2 | Blob public access disabled | critical if allowed |
| CRY-06 | Minimum TLS version is TLS 1.2 or later | medium |
Key Vault
| SCF | Check | Severity |
|---|---|---|
| BCD-11 | Soft delete and purge protection | high/medium |
| IAC-07.2 | Azure RBAC authorization preferred over access policies | medium |
Monitor + Defender for Cloud
| SCF | Check | Severity |
|---|---|---|
| MON-02 | Subscription Activity Log diagnostic export configured | high |
| MON-01.2 | Defender for Cloud Standard plan enabled | high |
Interpretation Rules
- Prefer SCF control IDs already emitted by the connector. Do not remap to Azure-native benchmark IDs unless the user asks for a CIS Azure Benchmark view.
- Treat
inconclusiveas an evidence gap, not a pass. Entra MFA coverage often needs Microsoft Graph permissions beyond basic Azure Reader. - Treat a subscription-level
not_applicabledocument as a scope signal, not a security defect. Example: no Key Vaults found. - For Key Vault, soft delete and purge protection are recovery controls. They do not prove key rotation.
- For Storage,
allowBlobPublicAccess=trueis a high-risk configuration even when no container is currently public because it permits future public ACLs.
Common Failure Modes
az loginis valid but the principal lacks subscription Reader.- Conditional Access queries require Microsoft Graph permissions such as
Policy.Read.All. - Defender pricing reads require Security Reader or equivalent permissions in some tenants.
- Diagnostic settings can exist at resource scope even if subscription Activity Log export is missing. The connector checks subscription-level export for v0.1.0.
Remediation Guidance
- Entra ID: baseline Conditional Access for admins, all users MFA, risky sign-ins, and legacy authentication blocking.
- Storage: set
allowBlobPublicAccess=false, enforce TLS 1.2+, and keep service encryption enabled. - Key Vault: enable soft delete, enable purge protection for production vaults, and migrate broad access policies to Azure RBAC.
- Monitor: export Activity Logs to Log Analytics, Event Hub, or Storage with retention aligned to the compliance program.
- Defender: enable Standard plans for regulated resource types and verify alert routing into the incident workflow.
Roadmap Boundaries
v0.1.0 does not inspect network security groups, Azure Policy assignments, VM disk encryption, AKS, SQL, Sentinel analytics, or Defender recommendations. Mark those as future connector coverage unless separate evidence is supplied.
Commands 3
/azure-inspector:collect
Scans an Azure subscription for compliance-relevant resources and configurations.
How to run
node plugins/connectors/azure-inspector/scripts/collect.js [options]
Arguments
--subscription=<id>- override the configured subscription--tenant=<id>- override the configured tenant--services=<csv>- subset ofentra,storage,keyvault,monitor,defender(default: all)--output=<fmt>-silent|summary(default) |json--quiet- no stderr progress
What it evaluates
Entra ID:
| SCF | Check | Severity |
|---|---|---|
| IAC-01.1 | MFA posture requires Graph/authentication-method verification | inconclusive if CLI cannot determine |
| IAC-04 | Conditional Access policies enabled | high if absent |
Storage accounts:
| SCF | Check | Severity |
|---|---|---|
| CRY-05 | Blob/file service encryption enabled | high if disabled |
| DCH-01.2 | Blob public access disabled | critical if allowed |
| CRY-06 | Minimum TLS version is TLS 1.2 or later | medium |
Key Vault:
| SCF | Check | Severity |
|---|---|---|
| BCD-11 | Soft delete and purge protection | high/medium if disabled |
| IAC-07.2 | Azure RBAC authorization preferred over access policies | medium |
Monitor + Defender for Cloud:
| SCF | Check | Severity |
|---|---|---|
| MON-02 | Subscription Activity Log diagnostic export configured | high |
| MON-01.2 | Defender for Cloud Standard plan enabled | high |
Output
-
~/.cache/claude-grc/findings/azure-inspector/<run_id>.json- array of Findings -
~/.cache/claude-grc/runs.log- run manifest appended -
stdout summary unless
--output=silent:azure-inspector: 18 resources, 64 evaluations, 7 failing (1 critical, 3 high, 3 medium).
Exit codes
0success2credentials invalid or subscription inaccessible3rate-limited (Azure quota exhausted)4partial (some services inaccessible; report still written)5config missing - run setup
Minimum Azure role/API access
Reader on the subscription
Security Reader for Defender for Cloud posture
Microsoft Graph Policy.Read.All for Conditional Access reads
Managed identity works when the identity has equivalent role assignments.
Examples
# Current subscription, all services
/azure-inspector:collect
# Multiple subscriptions
for s in sub-prod sub-stage; do
/azure-inspector:collect --subscription=$s
done
# Storage only
/azure-inspector:collect --services=storage
CI/CD usage
az login --identity
node plugins/connectors/azure-inspector/scripts/collect.js --quiet
node plugins/grc-engineer/scripts/gap-assessment.js FedRAMP-Moderate --sources=azure-inspector --output=sarif --quiet > azure-gap.sarif
/azure-inspector:setup
Prepares the azure-inspector connector. Confirms az CLI is installed and authenticated, writes ~/.config/claude-grc/connectors/azure-inspector.yaml, and runs a read-only subscription health check.
How to run
bash plugins/connectors/azure-inspector/scripts/setup.sh [--subscription=<id>] [--tenant=<id>]
Exits 0 on success, 2 on missing/invalid credentials, 5 on missing az binary.
Credential precedence
Honors the standard Azure CLI credential chain:
--subscription/--tenantflagsAZURE_SUBSCRIPTION_IDenvironment variable for collection- Active
az account showcontext - Managed identity after
az login --identity
The setup script verifies az account show --subscription <id> before writing config.
Config written
version: 1
source: azure-inspector
source_version: "0.1.0"
subscription_id: "<subscription-id>"
subscription_name: "<name>"
tenant_id: "<tenant-id>"
caller: "<user-or-service-principal>"
defaults:
services: ["entra", "storage", "keyvault", "monitor", "defender"]
Failure modes
- az not installed: exit 5. Install Azure CLI.
- No active account: exit 2. Run
az loginoraz login --identity. - Subscription inaccessible: exit 2. Grant Reader on the subscription; add Security Reader and Microsoft Graph Policy.Read.All for fuller coverage.
Safe to re-run
Yes. Re-running verifies the current account and overwrites config without deleting cached findings.
/azure-inspector:status
Non-destructive health check. Shows whether the connector is configured, whether Azure credentials still work, and when it last produced findings.
How to run
bash plugins/connectors/azure-inspector/scripts/status.sh
Output
azure-inspector
status: ready
az: 2.72.0
subscription: Prod (00000000-0000-0000-0000-000000000000)
tenant: 11111111-1111-1111-1111-111111111111
caller: scanner@example.com
config: ~/.config/claude-grc/connectors/azure-inspector.yaml
cache: ready
last run: 4h ago (20260430121212-a1b2c3d4)
cached: 18 resources, 64 evaluations
Status values
ready- config exists, Azure CLI can read the subscription, and cached findings are absent or recentnot-configured- setup has not runcredentials-expired-or-subscription-inaccessible-az account showfailed for the configured subscriptionstale- last run is older than 7 days
Sponsors
Details
- Marketplace
- GRCEngClub/claude-grc-engineering
- Source
- plugins/connectors/azure-inspector
- Category
- Community
More from GRCEngClub/claude-grc-engineering
All 70- ch-fadpv0.1.0
- cis-controlsv0.1.0
- cmmcv0.1.0
- compliance-posture-dashboardv0.1.0
- crowdstrike-inspectorv0.1.0
- csa-ccmv0.1.0
- cyber-essentials-plusv0.1.0
- datadog-inspectorv0.1.0
- dorav0.1.0
- drata-inspectorv0.1.0
- essential8v0.1.0
- eu-nis2v0.1.0
- fedramp-20xv0.1.0
- fedramp-rev5v0.1.0
- fedramp-sspv0.1.0
- gcp-docsv0.1.0
- gcp-inspectorv0.1.0
- gcp-secret-metadatav0.1.0
- gdprv0.1.0
- github-inspectorv0.1.0
- glbav0.1.0
- grc-auditorv0.1.0
- grc-diagramsv0.1.0
- grc-engineerv0.1.0