Elevated privilege needs a time limit
Aliases: temporary elevation · permission lease · just-in-time privilege
What it is
Time-bounded privilege elevation grants extra capability for an explicit task, session, or short lease and restores least privilege when the task ends, the session idles, the device locks, or time expires. One confirmation should not leave authority active after the user forgets, the application moves to background, or the device changes hands.
Why it happens
Permanent grants reduce prompts but enlarge the window available to malware, mistakes, and later account takeover. People rarely remember or revoke historical authorization. Binding lifetime to task events reduces exposure, but a lease that is too short creates repeated elevation and fatigue. Duration must fit real work and reauthentication cost.
Studying it
Estimate legitimate task duration and gaps from approved telemetry, then compare permanent, fixed, idle-expiring, and task-ending policies. Measure elevated window, reprompts, interruption, bypass, and unauthorized background action. Fault-test sleep, lock, crash, disconnect, and clock changes to verify authority ends in the authorization state, not merely in displayed time.
Where it stops holding
Long-running services, assistive tools, device management, and server jobs may need persistent capability, controlled through minimal scope, managed policy, and continuous visibility. Time limits do not replace scope limits; one minute of excessive authority can cause severe harm. Emergency extension can be allowed with ownership and later audit.
Applying it
- Default to leases such as this task, this session, or a suitable period; make permanent authority require a higher threshold.
- Bind expiry to task completion, idle, lock, and account switch and enforce it in the authorization layer.
- Continuously show remaining authority, holder, and early termination instead of mentioning duration only at approval.
- After expiry, verify background processes, children, tokens, and cached handles lose capability; renewal must restate scope.
Related
Cards in the same group
- O3.08.1Privilege elevation requires explicit confirmation
- O3.08.2Confirmation must explain what capability will be gained
- O3.08.4Frequent elevation prompts produce unthinking consecutive approval
- O3.08.5One approval is often expanded to cover all later related operations
- O3.08.6Ambiguous elevation wording makes users underestimate granted authority
- O3.08.7Batch or silent elevation needs stricter limits than one interactive request