Least Privilege Calculator
Score how close an identity is to least privilege by comparing permissions granted against permissions actually used.
Inputs
Least Privilege Score
33/ 100
Rating
F — Critical
Unused Permissions
86
Excess Permission Rate
71.7%
Granted ÷ Used
3.53×
Permissions Safe to Revoke
86
Step by step
Values used
Permissions granted = 120 permissions; Permissions actually used = 34 permissions; Of those granted, administrative ones = 8 permissions; Usage observation window = 90 days
Least Privilege
excess rate = (granted − used) ÷ granted, and the score is 100 minus 0.8 × the excess rate minus an administrative-permission penalty, scaled by how long you observed usage.
Least Privilege Score
= 33 / 100
Rating
= F — Critical
Unused Permissions
= 86
Excess Permission Rate
= 71.7
Granted ÷ Used
= 3.53 ×
Permissions Safe to Revoke
= 86
How it works
Cloud access analysers give you both numbers: what a principal could do and what it did. The gap is the unused privilege you can remove, weighted upward for administrative actions because those carry the largest blast radius, and discounted when a short observation window may simply have missed seasonal work. Unused permissions are the raw material of every privilege-escalation path and lateral-movement step, and they cost nothing to remove compared with the incident they enable.
Formula
Least Privilege
excess rate = (granted − used) ÷ granted, and the score is 100 minus 0.8 × the excess rate minus an administrative-permission penalty, scaled by how long you observed usage.
- granted
- Permissions the identity holds through every policy and role
- used
- Permissions exercised at least once in the observation window
- windowFactor
- Confidence discount when the window is shorter than 90 days
Frequently Asked Questions
How is Least Privilege calculated?
excess rate = (granted − used) ÷ granted, and the score is 100 minus 0.8 × the excess rate minus an administrative-permission penalty, scaled by how long you observed usage. Cloud access analysers give you both numbers: what a principal could do and what it did. The gap is the unused privilege you can remove, weighted upward for administrative actions because those carry the largest blast radius, and discounted when a short observation window may simply have missed seasonal work.
Why does Least Privilege matter?
Unused permissions are the raw material of every privilege-escalation path and lateral-movement step, and they cost nothing to remove compared with the incident they enable.
What values do I need to enter?
This calculator takes 4 inputs: Permissions granted, Permissions actually used, Of those granted, administrative ones, Usage observation window. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.
How long should I observe usage before revoking?
Ninety days is the common default because it covers a quarter-end and most monthly batch jobs. Shorter windows over-report excess — a permission used once a year looks unused in 30 days — which is why the score here is discounted for windows under 90 days rather than treated as equally trustworthy.
Should I revoke everything unused?
Revoke in tranches and keep a rollback path. Start with administrative and data-destructive actions that were never used, move the identity to a scoped-down policy behind a permissions boundary, and keep the old policy detached but intact for a cycle so a break-fix restore is one attach away.
You might also need
- IAM Health Score CalculatorCommonly used together
- RBAC Role Count CalculatorCommonly used together
- Permission Coverage CalculatorCommonly used together
- Privilege Escalation Risk CalculatorCommonly used together
- JWT Payload Size CalculatorAlso in Identity & Access Management
- Federation Trust CalculatorAlso in Identity & Access Management