detect-cicd-secret-exposurelisted
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