Individual skill
cloud-secrets-data-access
Cloud secrets and data access — AWS Secrets Manager, SSM Parameter Store, Azure Key Vault, GCP Secret Manager, environment/CI-CD/deployment credentials, distinguishing visible names from retrievable values and test placeholders from live credentials
internal/tools/skills/data/cloud-security/cloud-secrets-data-access/SKILL.md
Source commit d42f381ad34843e71a42658e5c57290c713e85af
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Instructions only
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,329
- Repository last updated
- Nov 9, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- cybersecurity Repository topic
- security Repository topic
- bug-bounty Repository topic
- automation Repository topic
- autonomous-pentesting Repository topic
- ai-agent Repository topic
- ai-security Repository topic
- ethical-hacking Repository topic
- golang Repository topic
- penetration-testing Repository topic
- data Derived category
- devops Derived category
- testing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
Read excerpt
# Cloud Secrets & Data Access
## Purpose
Enumerate and retrieve cloud-held secrets once any cloud context exists (credentials, metadata chain, or public exposure), then separate four very different states: name visible, value retrievable, placeholder, live credential.
## Entry Conditions
- A cloud identity (from `cloud-credential-abuse`) or a public exposure path (JS, config files, git, storage)
- Scope for secret retrieval governed by runtime policy — reading a secret value is an audit-visible, sometimes-irreversible action
## Discovery Signals
- Credentialed: Secrets Manager names, SSM parameter names, Key Vault certificate/secret/key lists, Secret Manager entries
- Black-box: `.env`/config in deployment bundles, source maps, git history, serverless packages, CI/CD variables exposed via public API metadata, storage bucket contents
- Token/audience: Key Vault requires its own audience (`https://<vault>.vault.azure.net`)
