Primary sources
References.
Evidence and interpretation
Technical claims link to their supporting sources. Hypothetical examples and proposed operating approaches remain distinct from documented incidents and external requirements.
An incident establishes a particular failure path. It does not establish how often that path occurs elsewhere or the loss every organization should expect. Limitations that affect a conclusion remain beside it.
The capability profile and 90 day planning sequence are proposed aids for assessment and delivery. They are not universal maturity standards or regulatory requirements.
Review before implementation
The sources were checked on 21 September 2026. Product behavior can change, so implementation needs to be checked against current documentation.
Regulatory claims need an assessment of the requirements applicable to the particular entity and service. Detailed cryptographic recovery and supplier limitations also need their own assessment.
Corrections and proposed changes can be raised in the repository, together with supporting evidence. Live credentials do not belong in those records.
- OWASP Secrets Management Cheat Sheet ↗
Secret management spans creation, use, and retirement as well as discovery.
- GitHub secret scanning detection scope ↗
Documented coverage distinguishes push protection from background detection.
- GitHub OpenID Connect ↗
This explains the exchange of workflow identity for temporary provider access and the trust conditions behind it.
- AWS security best practices in IAM ↗
Provider guidance covers temporary workload credentials and permissions appropriate to the task.
- Kubernetes good practices for Secrets ↗
Storage, retrieval, and runtime protection have distinct boundaries. Base64 encoding does not provide confidentiality.
- GitHub guidance on remediating a leaked secret ↗
Replacement and revocation need sequencing that accounts for both exposure and availability.
- GitHub guidance on removing sensitive data ↗
Revocation takes priority over cleanup. Removing repository history also has operational and coverage limits.
- GitHub advisory for CVE-2025-30066 ↗
The March 2025 compromise exposed secrets through workflow logs. Use of the action does not establish confirmed credential loss.
- CircleCI January 2023 incident report ↗
The provider report documents response extending to credentials and connected systems.
- NIST Cybersecurity Framework 2.0 ↗
The framework organizes risk outcomes. It does not prescribe the capability profile or planning sequence used here.