Temporary Credentials
Also called Short-lived credentials, STS tokens.
Time-limited, automatically expiring credentials issued for a session or role.
What it is
Access credentials that carry a built-in expiry, typically minutes to hours, issued when an identity assumes a role or starts a session. They reduce the value of stolen secrets because they stop working once they lapse.
Why it matters
Their short life shapes investigations, since a stolen token narrows the attack window, but it also means responders must capture logs quickly before the relevant session context ages out.
In practice
An analyst notes the attacker's stolen token was valid for only one hour, which neatly bounds the window of malicious API calls to investigate.
What to look for
- Session tokens used long after the work that requested them ended.
- Temporary credentials used from new IP ranges or user agents.
- Repeated requests for new sessions from the same stolen token.
Common mistake
Assuming short-lived means safe. A token is fully usable until it expires, so revoke the session when it is stolen.
Use it in CyberKit
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
Amazon GuardDuty Cloud service
AWS threat detection that analyzes CloudTrail, VPC flow logs and DNS logs.
-
Microsoft Defender for Cloud Commercial
Posture and threat protection for Azure, AWS and Google Cloud.
-
Wiz Commercial
Maps cloud resources, identities and exposures into one graph of risk.
-
Prowler Open source
An open source tool that checks cloud accounts against benchmarks such as CIS.
Read next
- Role Assumption: Temporarily taking on a role's permissions to act as a different identity.
- Instance Metadata Service: A link-local endpoint that hands instance credentials and config to a VM.
- Access Keys: Static, long-lived credential pairs used to authenticate to cloud APIs.