Skip to content
Cloud Least Privilege

Calculator, read 10 Nov 2026

The Access Debt Calculator: how big your hardening plan is

Read the assumptionsSee the index

The calculator takes six inputs: the number of identities, the number of identities with unused permissions, the number of reachable paths to sensitive resources, the number of accounts, the policy changes your team can review and ship in a week, and the number of risk classes a boundary plan should cover. You can read most of them from a CIEM report or an attack path view. 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 why the safe to enforce criterion is weighted 20.

Permission-by-permission plan

1,500 changes, 60 weeks

Boundary plan

6 boundaries, 6 rollout stages

The arithmetic, stated

  • Permission-by-permission plan: one reviewed policy change per identity that has unused permissions, because each identity has its own policy to edit. Weeks equal those changes divided by the changes your team ships per week.
  • Boundary plan: one boundary per risk class (for example, deny leaving the organization, deny disabling logs, deny public sharing), attached once high in the hierarchy so it applies to every account below it. AWS documents that an SCP attached to an organizational unit applies to every account in it.
  • Each boundary is rolled out in stages: a test unit first, then wider groups. The calculator assumes each stage covers four times as many accounts as the one before, so the number of stages is one plus the base-4 logarithm of your account count, rounded up.
  • Reachable paths are shown for scale only. A boundary removes every path in its risk class at once; a permission edit removes the paths that run through one identity. The calculator does not claim a number of paths removed, because that depends on your environment.
  • Nothing here estimates cost or time to write a boundary. Every number is an input you supply or a count derived from it.

Where the inputs come from

Identities with unused permissions: AWS IAM Access Analyzer unused access findings, the Google Cloud IAM recommender, or your platform's report. Reachable paths: your attack path or reachability tool. Accounts: AWS Organizations, Azure management groups or Google Cloud folders.

Where Act is behind

Act is not a CNAPP: it does not scan workloads or vulnerabilities (none found on 2026-11-10), and it publishes no pricing. It also does not make the change itself: it has read-only access to your cloud and delivers each change as a pull request to your Terraform or CloudFormation, or as a ticket, for your team to apply, and handling of violations and time-bound waivers after a change ships was described as roadmap.

Sources

  1. AWS Organizations: service control policies, read 10 Nov 2026
  2. aws.amazon.com/iam/access-analyzer, read 10 Nov 2026
  3. docs.aws.amazon.com/IAM/latest/UserGuide/what-is-access-analyzer.html, read 10 Nov 2026
  4. cloud.google.com/policy-intelligence/docs/role-recommendations-overview, read 10 Nov 2026
  5. cloud.google.com/policy-intelligence/docs/organization-policy-recommendations-ov, read 10 Nov 2026

Last reviewed 10 Nov 2026.