revocation
Cancelling a credential, session or key before its natural expiry so it stops working.
In more detail
Sessions are easy to revoke because the server holds them; self-contained tokens are harder, which is one reason to keep their lifetimes short. A compromised signing key needs a planned revocation and replacement.
Related terms
- session — A record the server keeps about a logged-in caller, found on each request through a handle the client presents, usually in a cookie.
- key rotation — Replacing a password or key with a new one on a schedule or after a suspected leak, and re-encrypting what it protected.
- token expiry — The time after which a token must no longer be accepted, carried in a JSON Web Token as the exp claim.
- temporary security credentials — Cloud credentials that expire on their own after minutes or hours, issued when a role is assumed.
- zero trust — A security approach where no user, device or network location is trusted by default, and every request is checked on its own merits.
- signing key — The secret key used to sign tokens or messages, together with the key used to verify them, which may be the same secret or the public half of a pair.
Taught in
- Basic Auth, Tokens And Sessions — Modern API Architecture: REST, GraphQL & gRPC
- OAuth Two And OpenID Connect — Modern API Architecture: REST, GraphQL & gRPC
- Scopes And Key Rotation — Modern API Architecture: REST, GraphQL & gRPC
- Cloud IAM Architecture & Permission Boundaries — Cloud Security & DevSecOps Engineering
- Cross-Account AssumeRole Chains & Temporary STS — Cloud Security & DevSecOps Engineering
- Zero-Trust Network Access & IdP Federation — Cloud Security & DevSecOps Engineering
- Pre-Commit Secret Scanning with Gitleaks & Entropy — Cloud Security & DevSecOps Engineering
- Provenance And Signing — Application Security & Threat Modeling for Engineers
- Secret Scanning — Application Security & Threat Modeling for Engineers