Skip to content
Cloud Least Privilege

Guide, 10 Nov 2026, read 10 Nov 2026

The first 90 days should end with one boundary enforced, not a longer list of findings

See the rankingAll guides

Plan around the 90-day window

The tools that generate removals from usage want about 90 days of history. Google documents a default minimum observation period of 90 days for role recommendations, adjustable to 30 or 60 days for project-level ones. AWS lets Access Analyzer read up to 90 days of CloudTrail events. If logging is not on today, the first job in month one is turning it on, because every later step depends on the data it produces.

That makes a 90-day program natural. Month one collects and assigns. Month two chooses and tests. Month three enforces and sets the review that keeps it. A program that tries to enforce in month one is guessing, and one that has no enforcement by month three has produced a report. Both of those are decisions about data, and the platforms on this index differ in how they help with them.

Month one: inventory, logs and owners

Confirm that audit logging covers every account, subscription and project, and that it is retained for at least the window you plan to use. Turn on the provider analyzers in report mode: Access Analyzer unused access, the Google IAM recommender, and Defender for Cloud CIEM if you run Azure. Produce a first list of unused roles, access keys and dormant identities.

Assign an owner to each account or project. Removal fails when the person who can approve it cannot be found. NIST SP 800-53 control AC-6 requires organizations to employ the principle of least privilege, and its enhancement AC-6(7) calls for a review of user privileges. Record who performs that review, how often, and where the result is kept. Keep the list short enough to act on, since a first list of two thousand items teaches nothing.

Month two: choose one class and simulate it

Pick one class of access to remove, using the data from month one. Good first candidates are the ones with few legitimate users: unused regions, unused services, access keys unused for the whole window, and roles that trust accounts outside the organization. Choose the one where you can name every principal that currently uses it. Starting small is a choice made on purpose: the first change builds trust in the process before a larger one needs it.

Write the change as code. Replay recent access under it using Google Policy Simulator or the AWS policy simulator, or the simulation your vendor provides. How to simulate a permission change lists the steps. Review each changed outcome with its owner. A change nobody can explain stays in the branch. Keep a record of the principals that used the access during the window, so you can contact each owner before enforcement.

Month three: audit mode, enforcement and the review

Release the change in audit or log-only mode where the cloud offers one, and watch blocked attempts across a full business cycle. Fix or exempt each hit with a recorded reason. Then enforce, and keep the previous version ready to restore. Write the date and the evidence into the change record; an auditor will ask for exactly those two things. Keep the evidence beside the change, so the record survives staff changes.

Close the quarter by setting a recurring review. Microsoft documents access reviews in Entra ID as a way to review group memberships, application access and role assignments regularly so that only the right people keep access. Add the new boundary to that cycle, and add a pipeline check so the removed access is not granted again. The check is what keeps a quarter's work from being undone the following week.

What to measure at day 90

Report four numbers: the share of accounts with logging verified, the count of unused roles and keys removed, the number of principals whose outcome changed under the enforced boundary, and the number of exceptions open past their expiry date. A fifth, if you have a reachability model, is the count of paths removed. These are plain counts that any team can produce without a vendor, and they make a quarter's progress readable by someone outside the team.

If you are choosing a platform during the quarter, rank candidates on the situation closest to yours on the index. The method shows the five situations and their published weights. A small team that cannot clear findings should weigh removal and class-level change most heavily. Choose the platform after the first change has shipped, because shipping it shows which of the seven criteria matters most to your team.

Sources

  1. Google Cloud, overview of role recommendations, read 10 Nov 2026
  2. AWS IAM Access Analyzer policy generation, read 10 Nov 2026
  3. NIST SP 800-53 Rev. 5 catalog, control AC-6, read 10 Nov 2026
  4. Microsoft Learn, access reviews in Entra ID, read 10 Nov 2026
  5. Google Cloud, Policy Simulator for allow policies, read 10 Nov 2026
  6. AWS, IAM policy testing with the policy simulator, read 10 Nov 2026

Last reviewed 10 Nov 2026.