Skip to content
Least Privilege Principle

The Access Debt Calculator: how big your least privilege clean-up is

The methodology page shows how the Access Debt Calculator works: its six inputs, the two plans it sizes, the assumptions it makes and the arithmetic in each step. A reader can reproduce any result by hand, change any assumption, and see where the calculator stops being a reliable guide.

Open the calculator ยท Download the assumptions (CSV)

The calculator takes seven inputs: the number of identities, the number of identities with unused permissions, the permissions granted per identity, the permissions used per identity, the number of accounts, the changes your team ships per week, and the number of risk classes a boundary plan should cover. Most of them can be read from the provider reports described on the privilege creep page, such as unused access findings. It outputs the size of two plans.

The permission-by-permission plan assumes one reviewed change per identity with unused permissions, since each identity has its own policy, owner and test, and divides that by your weekly rate. The boundary plan assumes one boundary per risk class, attached high in the hierarchy and rolled out in stages over your accounts. The stage count is an assumption stated under the calculator, and you can change every input.

Read the result as a ratio. If the permission plan is a hundred times the boundary plan, hand edits will not finish before the estate changes again. The calculator does not account for how long a change takes to test, how many owners must approve, or whether a boundary breaks a rare dependency. Those costs are real, and the pages on boundaries and on the first 90 days explain how to test for them.

Every assumption, with the default example

Default example as on the home page; edition 16 Nov 2026.
StepRuleDefault example
GrantedIdentities times the mean permissions granted per identity2,400 times 120 = 288,000
UsedIdentities times the mean permissions used in the last 90 days2,400 times 9 = 21,600
Unused share(granted minus used) divided by granted, per identity93%
Permission-by-permission planOne reviewed change per identity with unused permissions1,500 changes
Weeks, permission planChanges divided by changes shipped per week, rounded up60 weeks at 25 a week
Rollout stages1 plus the base-4 logarithm of the accounts, rounded up5 stages for 120 accounts
Boundary planRisk classes times rollout stages6 times 5 = 30 changes
Weeks, boundary planBoundary changes divided by changes shipped per week, rounded up2 weeks

Twenty known cases

The calculator is checked against twenty cases written before it was built, kept in the site's tests folder; the build fails if one gives a different answer. The table shows the first five.

CaseInputsPermission planBoundary plan
default exampleidentities 2400, unused 1500, granted 120, used 9, accounts 120, rate 25, classes 61500 changes, 60 weeks30 changes, 2 weeks
one accountidentities 50, unused 10, granted 40, used 4, accounts 1, rate 5, classes 310 changes, 2 weeks3 changes, 1 week
four accountsidentities 200, unused 100, granted 60, used 6, accounts 4, rate 10, classes 4100 changes, 10 weeks8 changes, 1 week
five accountsidentities 200, unused 100, granted 60, used 6, accounts 5, rate 10, classes 4100 changes, 10 weeks12 changes, 2 weeks
sixteen accountsidentities 300, unused 150, granted 80, used 10, accounts 16, rate 20, classes 5150 changes, 8 weeks15 changes, 1 week

Cite this

Cite this line: 'Least Privilege Principle, The Access Debt Calculator, edition 16 Nov 2026, https://leastprivilegeprinciple.com/methodology/'

Sources

  1. AWS Organizations: service control policies, read 16 Nov 2026

Last reviewed 16 Nov 2026.