Short-Lived Credentials
A workload exchanges its identity for a temporary credential that expires, reducing the useful lifetime of theft and eliminating manual rotation.
Frame the problem
Security starts with a concrete asset, attacker capability and trust crossing.
Why the system fails
Permanent keys spread across machines and repositories and remain valid long after their purpose ends.
The important question is not “what is Short-Lived Credentials?” but “which assumption let untrusted data or an over-scoped identity cross workload identity → temporary delegated capability?” Trace the decision at the boundary, then constrain what can happen after the first control fails.
Design the control in layers
Start with the control closest to the interpretation or privilege boundary: Use workload federation and temporary credentials Then add a control that reduces blast radius and telemetry that proves the decision was enforced.
The resulting design is not labelled secure. Record the identified controls, the known failure paths, the remaining exposure, and the evidence you would need during an incident.
| Prevent | Detect | Recover |
|---|---|---|
| Use workload federation and temporary credentials · Minimize lifetime and scope · Avoid exporting credentials into broad process environments | Credential use after workload termination or from another environment | Contain the affected identity or component, scope impact from audit evidence, and preserve a regression test. |
Key points
- Asset: Cloud and service credentials.
- Boundary: Workload identity → temporary delegated capability
- Primary control: Use workload federation and temporary credentials
- Detection signal: Credential use after workload termination or from another environment
- Always ask what limits damage when the primary control fails.
Boundary control exercise
This lesson uses the shared boundary-control exercise.
Follow the attack
Safe conceptual simulation: capability → missing control → crossed boundary → asset impact.
- 1Attacker starts with: Someone who reads environment variables, files, logs or build output.
- 2Permanent keys spread across machines and repositories and remain valid long after their purpose ends.
- 3The weak or missing boundary control is crossed: Workload identity → temporary delegated capability
- 4Impact: Persistent access until discovery and manual revocation.
- Persistent access until discovery and manual revocation.
Defend, detect, recover
One prevention is a single point of security failure. Layer it and make failure observable.
- • Use workload federation and temporary credentials
- • Minimize lifetime and scope
- • Avoid exporting credentials into broad process environments
- • Credential use after workload termination or from another environment
- • Contain the affected identity or component.
- • Scope access from audit evidence.
- • Fix the boundary and add a regression test.
- • Misconfiguration and new access paths can bypass the intended control.
- • A privileged insider or compromised control plane may still reach the asset.