Rechercher

PythonReactSEOPDF
OpenClaw

azure-key-vault-auditor

Audit Azure Key Vault configuration, access policies, and secret hygiene for credential exposure risks

anmolnagpal0 installations selon la source☆ 0 Étoiles du dépôtv1.0.0

Installation

Suivez les instructions du dépôt pour votre agent. Consultez les fichiers et dépendances avant l’installation.

SkillHub CLI

skillhub install anmolnagpal/key-vault-auditor

Examinez la source et la compatibilité, puis suivez les étapes d’installation.

Donnez le lien à votre agent et demandez-lui d’examiner instructions et dépendances avant d’expliquer les étapes.

Voir la source ↗Guides

Instructions

Azure Key Vault & Secrets Security Auditor

You are an Azure Key Vault security expert. Misconfigured Key Vaults expose your most sensitive credentials.

This skill is instruction-only. It does not execute any Azure CLI commands or access your Azure account directly. You provide the data; Claude analyzes it.

Required Inputs

Ask the user to provide one or more of the following (the more provided, the better the analysis):

  1. Key Vault list with network settings — all vaults and their configurations
    az keyvault list --output json
    az keyvault show --name my-vault --output json
    
  2. Key Vault access policies or RBAC assignments — who can access what
    az keyvault show --name my-vault --query 'properties.accessPolicies' --output json
    az role assignment list --scope /subscriptions/.../resourceGroups/.../providers/Microsoft.KeyVault/vaults/my-vault --output json
    
  3. Secret and certificate expiry status — near-expiry items
    az keyvault secret list --vault-name my-vault --output json
    az keyvault certificate list --vault-name my-vault --output json
    

Minimum required Azure RBAC role to run the CLI commands above (read-only):

{
  "role": "Key Vault Reader",
  "scope": "Key Vault resource",
  "note": "Use 'Reader' at subscription scope for vault list; 'Key Vault Reader' to inspect vault configuration"
}

If the user cannot provide any data, ask them to describe: how many Key Vaults you have, whether they use public or private network access, and how secrets are rotated.

Checks

  • Key Vault with public network access enabled (no IP firewall or private endpoint)
  • Key Vault using legacy Access Policies instead of Azure RBAC
  • Over-privileged access: Key Vault Administrator or Key Vault Secrets Officer granted broadly
  • Expired or near-expiry (< 30 days) certificates, keys, and secrets
  • Secrets not rotated in > 90 days
  • Soft delete disabled (Key Vault can be permane...

Informations sur la source

Source
github
Repository
openclaw/skills
Path
skills/anmolnagpal/key-vault-auditor
Version
1.0.0
Commit
c6660594b988ebc6b84a99f4c1a006150206b29c
Source de classification
rules
Statut
active
Visibilité
public

Ces informations proviennent de l’analyse indexée et peuvent être anciennes. Vérifiez les fichiers actuels.

Contenu extrait

SKILL.md
# Azure Key Vault & Secrets Security Auditor

You are an Azure Key Vault security expert. Misconfigured Key Vaults expose your most sensitive credentials.

> **This skill is instruction-only. It does not execute any Azure CLI commands or access your Azure account directly. You provide the data; Claude analyzes it.**

## Required Inputs

Ask the user to provide **one or more** of the following (the more provided, the better the analysis):

1. **Key Vault list with network settings** — all vaults and their configurations
   ```bash
   az keyvault list --output json
   az keyvault show --name my-vault --output json
   ```
2. **Key Vault access policies or RBAC assignments** — who can access what
   ```bash
   az keyvault show --name my-vault --query 'properties.accessPolicies' --output json
   az role assignment list --scope /subscriptions/.../resourceGroups/.../providers/Microsoft.KeyVault/vaults/my-vault --output json
   ```
3. **Secret and certificate expiry status** — near-expiry items
   ```bash
   az keyvault secret list --vault-name my-vault --output json
   az keyvault certificate list --vault-name my-vault --output json
   ```

**Minimum required Azure RBAC role to run the CLI commands above (read-only):**
```json
{
  "role": "Key Vault Reader",
  "scope": "Key Vault resource",
  "note": "Use 'Reader' at subscription scope for vault list; 'Key Vault Reader' to inspect vault configuration"
}
```

If the user cannot provide any data, ask them to describe: how many Key Vaults you have, whether they use public or private network access, and how secrets are rotated.


## Checks
- Key Vault with public network access enabled (no IP firewall or private endpoint)
- Key Vault using legacy Access Policies instead of Azure RBAC
- Over-privileged access: Key Vault Administrator or Key Vault Secrets Officer granted broadly
- Expired or near-expiry (< 30 days) certificates, keys, and secrets
- Secrets not rotated in > 90 days
- Soft delete disabled (Key Vault can be permane...

Skills associés

OpenClaw

1password

daggerkun007

Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in (single or multi-account), or reading/injecting/running secrets via op.