Skip to content
Least Privilege Principle

Privilege creep is access that outlives the task it was granted for

Privilege creep is the build-up of access an identity no longer needs, because grants are added for each new task and rarely removed. In the cloud it shows up as old roles, temporary grants left in place and unused keys. AWS, Google Cloud and Microsoft each publish a way to measure it, read on 16 Nov 2026.

Open the calculator ยท The field guide

Privilege creep is the gap between what an identity holds and what it uses

The term comes from people who change jobs and keep the access of every earlier job. In the cloud the same pattern applies to people, service accounts, roles and managed identities. Each task adds a grant. Nothing in the normal workflow removes one, so the total only rises.

NIST control AC-6(7), Review of User Privileges, names the counter-measure: review the privileges assigned to defined roles or classes of users to validate the need for such privileges (NIST SP 800-53 Rev. 5 catalog, read 16 Nov 2026). Privilege creep is what that review exists to find. The parent requirement is on the principle of least privilege page.

Four cloud habits produce most of it

Role changes come first. A person moves from one team to another and keeps the group memberships of the old team, because the new team's request is the only ticket anyone files. Project ends are second: the contractor group, the migration role and the test account stay after the work is done.

Temporary grants left in place are third. An engineer receives administrator access for an incident, and the expiry is a reminder in someone's calendar. Broad starting grants are fourth. AWS says in its IAM guidance that you might start with AWS managed policies, which may not give least privilege for your use case, and then work toward it. The second half of that sequence is the one that gets skipped.

  • Role change: old group memberships kept after a move
  • Project end: roles and accounts left after the work stops
  • Temporary access: a grant with no expiry or no one tracking it
  • Broad start: a wide managed policy that is never narrowed

Provider tools measure it from usage records

Each provider reports what was granted against what was used. The reports differ in window and in what they cover, so a clean result from one is not a clean result from another.

Provider toolWhat it reportsWindow stated in the documentation
AWS last accessed informationServices and management actions last used by an IAM identity, and by an Organizations entityTracking period for service information of at least 400 days
AWS IAM Access Analyzer, unused accessUnused roles, unused IAM user access keys and passwords, unused permissionsSet when the analyzer is created
Google Cloud role recommendationsRoles to remove or replace, based on permissions usedLast 90 days by default
Microsoft Defender for Cloud permissions managementExcessive, unused or misconfigured permissions for users, service principals, managed identities and service accountsNot stated on the page read

Read the window before you act on a finding

The AWS page on last accessed information says the tracking period for service information is at least 400 days, and that action information started on different dates by service: April 2020 for Amazon S3 actions, April 2021 for Amazon EC2, IAM and Lambda actions, and May 2023 for all other services. An action that shows no activity may simply predate the tracking.

Google documents that the IAM recommender looks at permissions used in the last 90 days and, by default, needs 90 days of data. For project-level recommendations the minimum can be set to 30 or 60 days, and Google says accuracy might be affected. A role used once a year, for example for failover, can sit outside both windows. List such identities by hand before any removal.

Measure creep as a count that falls over time

Four counts are enough to track it and any team can produce them without a purchased product: identities with a last-used date older than your window, access keys unused for the whole window, role assignments past their expiry, and exceptions open past their expiry date.

Record the counts each quarter. Creep is a rate as much as a stock, so the useful figure is how many grants were added and how many were removed in the period. If additions outpace removals, a one-time clean-up will not hold. The Access Debt Calculator sizes the clean-up from the counts, and why least privilege stalls explains what usually interrupts it.

Microsoft's Entra access reviews are the scheduled counter-measure: they review group memberships, application access and role assignments on a recurring basis so that only the right people keep access (Microsoft Learn, read 16 Nov 2026). The first 90 days places that review in the plan.

Sources

  1. NIST SP 800-53 Rev. 5 catalog (OSCAL JSON), control AC-6, read 16 Nov 2026
  2. AWS, security best practices in IAM, read 16 Nov 2026
  3. AWS, refine permissions using last accessed information, read 16 Nov 2026
  4. AWS, IAM Access Analyzer findings, read 16 Nov 2026
  5. Google Cloud, role recommendations overview, read 16 Nov 2026
  6. Microsoft, permissions management in Defender for Cloud, read 16 Nov 2026
  7. Microsoft, access reviews in Microsoft Entra ID, read 16 Nov 2026

Last reviewed 16 Nov 2026.