Search

PythonReactSEOPDF
OpenClaw

azure-key-vault-auditor

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

anmolnagpal0 source installs☆ 0 Repository starsv1.0.0

Installation

Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.

SkillHub CLI

skillhub install anmolnagpal/key-vault-auditor

Inspect the source and compatibility requirements, then follow its installation steps.

Give your agent the source link and ask it to inspect instructions and dependencies before explaining the installation steps.

View source ↗Guides

Skill 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...

Source information

Source
github
Repository
openclaw/skills
Path
skills/anmolnagpal/key-vault-auditor
Version
1.0.0
Commit
c6660594b988ebc6b84a99f4c1a006150206b29c
Classification source
rules
Status
active
Visibility
public

These signals come from indexed source analysis and may lag behind changes. Check the current source files.

Extracted content

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...

Related skills

OpenClaw

captchas-openclaw

captchasco

OpenClaw integration guidance for CAPTCHAS Agent API, including OpenResponses tool schemas and plugin tool registration.

OpenClaw

Modelready

carol-gutianle

name: modelready description: Start using a local or Hugging Face model instantly, directly from chat. metadata: {"openclaw":{"requires":{"bins": "bash", "curl" }, "env": "URL" }}

OpenClaw

Ethereum History

cartoonitunes

Read-only factual data about historical Ethereum mainnet contracts. Use when the user asks about a specific contract address, early Ethereum contracts, deployment era, deployer, bytecode, decompiled code, or do...