Authorization decisions need context beyond identity and requested action. A three-dimensional choice space organizes that context by the signals that matter, how they arrive, and how fresh they must be. section 12.0
Design each authorization context along three dimensions:
- Signal type: employment status, device trust, multifactor authentication, geolocation, risk score, or account balance. section 12.0
- Delivery method: embed signals in tokens, fetch them through APIs, receive them from event streams, or gather them with local agents. section 12.0
- Freshness requirement: query live data, cache it briefly, or accept values until token expiry. section 12.0
Contrasting authorization contexts
A low-risk collaboration feature may use token-based context lasting an hour. A production deployment decision may require live operational data and short-lived device-posture signals. The choice reflects risk, latency, and assurance requirements. section 12.0
