Loading…
Open-Policy Exchange
~5 min to deploy
Claude Code Secrets & Credentials Guard
Stops an agent reading, printing, or committing credential files, and escalates any command that would rotate a secret.
For: Platform and security engineers letting agents work in credentialed repos
SOC 2 CC6.1ISO 27001 A.8.24Secret-handling evidence
What it enforces
Credential file read block
Blocks reads of .env, key material, and cloud credential files.
Secret echo guard
Blocks shell commands that would print an environment secret to stdout or a log.
Rotation escalation
Escalates any command that would rotate or revoke a secret so two approvers sign off.
claude-code-secrets-guard.yaml
# Claude Code Secrets & Credentials Guard
# Fork: extend the protected path list with your own credential locations.
apiVersion: decionis.dev/v1
kind: PolicyPack
metadata:
name: claude-code-secrets-guard
surface: claude_code
standards: [SOC2-CC6.1, ISO27001-A.8.24]
defaults:
mode: shadow
emit_dossier: true
fail_closed: true
protected_paths:
- ".env"
- ".env.*"
- "**/*.pem"
- "**/*.key"
- "~/.aws/credentials"
- "~/.ssh/**"
rules:
- name: credential_file_read_block
when: "tool in ['Read', 'Bash']"
decision: |
BLOCK IF path matches any protected_paths
ALLOW OTHERWISE
reason_code: credential_file_access_blocked
- name: secret_echo_guard
when: "tool == 'Bash'"
decision: |
BLOCK IF command matches '(echo|printenv|env)\b.*(SECRET|TOKEN|PASSWORD|API_KEY)'
ALLOW OTHERWISE
reason_code: secret_would_be_printed
- name: rotation_escalation
when: "tool == 'Bash'"
decision: |
ESCALATE IF command matches '(rotate|revoke).*(key|secret|token)'
ALLOW OTHERWISE
reason_code: secret_rotation_requires_two_approvers
Fork it, change the thresholds to match your environment, and deploy in shadow mode first — it defaults to listen-only so nothing in your live pipeline changes.
How to install it
Follow the install path for this surface, then paste the forked YAML as your policy config.
What to do next
This recipe is one step in a path. The same five steps apply to every recipe in the exchange.
- Simulate this recipe
Run the policy against a realistic action in the browser. Push it past what the rules allow and watch the verdict come back. No account.
- View the signed Decision Dossier
See exactly what was decided and why: the rule that fired, the evidence it read, the policy version in force, and an Ed25519 signature you can verify yourself.
- Deploy in shadow mode
Measure what the policy would have caught on your own traffic without touching the live path. Every recipe defaults to shadow, so the first deployment carries no execution risk.
- Connect a real workflow
Point the same policy at the system where the action actually originates — a checkout, an ERP posting, a Zap, an agent's tool call.
- Share the verified result
Publish the proof: a public verification link, an embeddable badge, a PR comment, or an anonymized shadow-mode finding. This is how the next person discovers Decionis.