Step-up authentication
Requiring a stronger or fresher authentication only when a user attempts a sensitive action or the session looks risky.
Step-up authentication lets most of a session run at a lower assurance level, then demands more (a passkey, a recent re-authentication) before high-risk actions: changing payout details, exporting data, adding an MFA device. A risk engine can also trigger it from signals such as new device or impossible travel.
In OAuth and OIDC it is expressed with acr_values and max_age in the request and acr, amr and auth_time in the ID token. RFC 9470 defines how an API signals insufficient_user_authentication so the client can go back and step up.
Bugs: checking the step-up in the UI but not the API, accepting a step-up that happened hours ago, and letting an attacker downgrade to a weaker factor such as SMS.
Learn it properly
Also used in
- What happens when you log inSecEng · Foundations of Security EngineeringFree
- API securitySecEng · Application Security & DevSecOpsFree
- Design a zero-trust access gatewayHLD · Design problems: Access & identityFree
- Design an SSO identity providerHLD · Design problems: Access & identityFree
- Design a payment fraud scoring serviceHLD · Design problems: fraud & abuseFree
- Rate limiting and quotasHLD · Security design building blocksFree
- SSO at scale: SAML, OIDC and SCIMSecEng · Identity & Access EngineeringPro
- Zero trust reference architectureSecEng · Advanced: Security Architecture at ScalePro