Step-Up authentication
Last updated
Last updated
This document defines how Step-Up Authentication is applied for Business Accounts when a login attempt is identified as risky.
Step-Up Authentication requires users to complete additional verification steps beyond their primary login method.
Step-Up Authentication is designed to:
Reduce account takeover risk
Apply stronger authentication only when risk is detected
Protect sensitive business data and operations
Maintain a smooth user experience for low-risk logins
Step-Up Authentication is enforced when:
One or more Risk Detection Signals exceed configured thresholds
Organization security policies require additional verification
Users attempt to access sensitive resources or elevated privileges
Trigger Conditions ├── Medium risk login attempt ├── High risk login attempt ├── Access to sensitive resources ├── Policy-based enforcement └── Compliance requirements
The system may require one or more of the following:
Available methods depend on organization policy configuration.
Authentication Levels ├── Level 1: Primary authentication only ├── Level 2: Primary + one MFA factor └── Level 3: Strong MFA (phishing-resistant)
…Step-Up Authentication Flow
If step-up authentication fails:
After successful step-up authentication:
The following events are recorded:
Logs are available for security review and compliance audits.
MFA via Authenticator App (TOTP)
Email verification codes
Passkeys (FIDO2 / WebAuthn)
Backup recovery codes (limited use)
Risk Level
Required Authentication
Low
Level 1
Medium
Level 2
High
Level 3
User submits primary credentials
System evaluates risk signals
Risk score is calculated
Step-up requirement is determined
User is prompted for additional verification
Access is granted or denied
User logs in from a new device
System detects medium risk
User is prompted for MFA
User completes verification
Session continues normally
User logs in from suspicious location
System detects high risk
Strong MFA is enforced
Access is granted only after successful verification
User is denied access
Retry limits are enforced
Security event is logged
Admins may be notified based on policy
Session is marked as verified
Trust may be temporarily cached
Re-authentication may be required if risk context changes
Step-up challenges are time-bound
MFA attempts are rate-limited
Strong MFA is required for elevated access
Authentication methods are validated per policy
Step-up triggered
Method requested
Verification success or failure
Policy decision applied