config-encryption-auditor
Scans OpenClaw config directories for plaintext API keys, tokens, and secrets in unencrypted files — flags exposure risks and suggests encryption or environment variable migration.
Works with
--- name: config-encryption-auditor description: Scans OpenClaw config directories for plaintext API keys, tokens, and secrets in unencrypted files — flags exposure risks and suggests encryption or environment variable migration. license: MIT --- # Config Encryption Auditor ## What it does OpenClaw stores configuration in `~/.openclaw/` — API keys, channel tokens, provider credentials. By default, these are plaintext YAML or JSON files readable by any process on your machine. OpenLobster solved this with AES-GCM encrypted config files. We can't change OpenClaw's config format, but we can audit it — scanning for exposed secrets, flagging unencrypted credential files, and suggesting migrations to environment variables or encrypted vaults. ## When to invoke - Automatically, every Sunday at 9am (cron) - After initial OpenClaw setup - Before deploying to shared infrastructure - After any config change that adds new API keys ## Checks performed | Check | Severity | What it detects | |---|---|---| | PLAINTEXT_API_KEY | CRITICAL | API key patterns in config files (sk-, AKIA, ghp_, etc.) | | PLAINTEXT_TOKEN | HIGH | OAuth tokens, bearer tokens, passwords in config | | WORLD_READABLE | HIGH | Config files with 644/755 permissions (readable by all users) | | NO_GITIGNORE | MEDIUM | Config directory not gitignored (risk of committing secrets) | | ENV_AVAILABLE | INFO | Secret could be migrated to environment variable | ## How to use ```bash python3 audit.py --scan # Full audit python3 audit.py --scan --critical-only # CRITICAL findings only python3 audit.py --fix-permissions # chmod 600 on config files python3 audit.py --suggest-env # Print env var migration guide python3 audit.py --status # Last audit summary python3 audit.py --format json ``` ## Procedure **Step 1 — Run the audit** ```bash python3 audit.py --scan ``` **Step 2 — Fix CRITICAL issues first** For each PLAINTEXT_API_KEY finding, migrate the key to an environment variable: ```bash # Instead of storing in config.yaml: # api_key: sk-abc123... # Use: export OPENCLAW_API_KEY="sk-abc123..." ``` **Step 3 — Fix file permissions** ```bash python3 audit.py --fix-permissions ``` This sets `chmod 600` on all config files (owner read/write only). **Step 4 — Verify gitignore coverage** Ensure `~/.openclaw/` or at minimum the config files are in your global `.gitignore`. ## State Audit results and history stored in `~/.openclaw/skill-state/config-encryption-auditor/state.yaml`. Fields: `last_audit_at`, `findings`, `files_scanned`, `audit_history`.
More Security skills
entra-app-registration
microsoft/azure-skills
Guides Microsoft Entra ID app registration, OAuth 2.0 authentication, and MSAL integration. USE FOR: create app registration, register Azure AD app, configure OAuth, set up authentication, add API permissions, generate service principal, MSAL example, console app auth, Entra ID setup, Azure AD authentication. DO NOT USE FOR: Key Vault secrets (use azure-keyvault-expiration-audit), general Azure resource security guidance.
azure-messaging
microsoft/azure-skills
Troubleshoot and resolve issues with Azure Messaging SDKs for Event Hubs and Service Bus. Covers connection failures, authentication errors, message processing issues, and SDK configuration problems. WHEN: event hub SDK error, service bus SDK issue, messaging connection failure, AMQP error, event processor host issue, message lock lost, message lock expired, lock renewal, lock renewal batch, send timeout, receiver disconnected, SDK troubleshooting, azure messaging SDK, event hub consumer, service bus queue issue, topic subscription error, enable logging event hub, service bus logging, eventhub python, servicebus java, eventhub javascript, servicebus dotnet, event hub checkpoint, event hub not receiving messages, service bus dead letter, batch processing lock, session lock expired, idle timeout, connection inactive, link detach, slow reconnect, session error, duplicate events, offset reset, receive batch.
azure-compliance
microsoft/azure-skills
Run Azure compliance and security audits with azqr plus Key Vault expiration checks. Covers best-practice assessment, resource review, policy/compliance validation, and security posture checks. WHEN: compliance scan, security audit, BEFORE running azqr (compliance cli tool), Azure best practices, Key Vault expiration check, expired certificates, expiring secrets, orphaned resources, compliance assessment.

