← ClaudeAtlas

detect-cicd-secret-exposurelisted

Detection, hunting, and hardening methodology for secrets exposed in CI/CD pipelines: deployment keys, cloud tokens, API secrets, and registry passwords leaked through build logs, caches, artifacts, credential stores, and OIDC federation trust. Maps to MITRE ATT&CK T1552 Unsecured Credentials and its sub-techniques T1552.001 Credentials In Files, T1552.004 Private Keys, and T1552.007 Container API. Keys off GitHub and GitLab audit logs, CI job logs, AWS CloudTrail, Azure Key Vault diagnostic logs, GCP Cloud Audit Logs, and HashiCorp Vault audit devices. Gives the defender's method for spotting a leaked or abused pipeline secret, a hypothesis-driven hunt, and least-privilege hardening, and points to public rule sources. Use when investigating a possible CI/CD secret leak, a secret-scanning alert, an unexpected GetSecretValue or AccessSecretVersion, an AssumeRoleWithWebIdentity from a pipeline, a push-protection bypass, or when hardening GitHub Actions, GitLab CI, Jenkins, or Azure DevOps secret handling.
umbrasec-labs/umbra-blue · ★ 0 · DevOps & Infrastructure · score 62
Install: claude install-skill umbrasec-labs/umbra-blue
# CI/CD Secret Exposure - Defensive Methodology > **Tier 2 - methodology skill.** No bespoke UMBRASEC detection rule ships with this skill yet. It gives the defender's method, the log sources and signals, and the hardening, and points to public rule sources. Promotion to Tier 1 (a sourced, tuned UMBRASEC rule) is tracked in [COVERAGE.md](https://github.com/umbrasec-labs/umbra-blue/blob/main/COVERAGE.md). Do not treat the content below as citing a UMBRASEC rule; there is none for this threat yet. ## TL;DR Pipeline secrets leak two ways: they are written somewhere a reader can reach (a build log, a cache, an artifact, a fork's pull-request run), or they are read and used by an identity that should never have touched them. You catch the first with secret scanning plus push protection on every repository, and the second by watching the credential store and cloud audit trail for reads and federation events that do not line up with a legitimate deployment. The highest-value single control is replacing long-lived static secrets with short-lived OIDC federation, because it shrinks what a leaked value is worth. A leaked secret that is scoped tight and rotated on exposure is a near-miss; a broad, long-lived one is an incident. ## What it looks like, defender view In telemetry a leaked pipeline secret shows up as a mismatch, not as a single malicious event. A secret-scanning alert fires on a commit, or a cloud read of a secret arrives from an identity or an IP range that has never