CI credentials are secrets or identity materials that continuous integration systems use to access services while building, testing, or deploying software. They can include API tokens, repository keys, cloud credentials, and short-lived identity tokens. CI jobs may need them to fetch dependencies, publish packages, or deploy applications.
These credentials are attractive targets because automated jobs can hold broad permissions and run code from repositories or dependencies. Malicious code in a build environment may attempt to read available secrets and send them outside the organization. Defenses include limiting each token’s permissions and lifetime, avoiding secrets in untrusted jobs, monitoring CI audit logs, and rotating credentials if exposure is suspected.


