Least privilege access is granted narrow, in time, and checked against use
Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.
Least privilege access means an identity can reach only the resources and actions its work needs, for only as long as it needs them. In cloud accounts that takes four steps: grant a narrow role, scope it to resources, set an end date, and compare it with usage records. Provider guidance read on 16 Nov 2026.
Open the calculator ยท The field guide
Access is least privilege when it is narrow on four axes
An access grant has four properties that can be too wide: the actions allowed, the resources they apply to, the conditions under which they apply, and the time they last. Least privilege access narrows all four. Narrowing only the actions while leaving the resource as a wildcard removes less than it appears to.
AWS words the first three as defining the actions allowed on specific resources under specific conditions (AWS IAM best practices, read 16 Nov 2026). The fourth is covered by time-bound assignment, which Microsoft documents for Privileged Identity Management. The mechanisms behind each are on least privilege access control.
Start from the narrowest role that works
AWS says starting with AWS managed policies might not give least privilege for your use case, and it provides managed policies for job functions that align to common roles in an organization. Google Cloud says basic roles include thousands of permissions across all services and should not be granted in production unless there is no alternative.
Microsoft advises avoiding broader roles at broader scopes, and says that when a privileged administrator role must be assigned, a narrow scope such as a resource group or resource is better than a management group or subscription. The common shape is the same: the role is the first limit and the scope is the second. Neither limit helps if the grant is then given to a shared group that dozens of people can join, so check group membership as part of the same review.
Set an end date where the task has one
Microsoft documents Privileged Identity Management as a model in which users receive temporary permissions to perform privileged tasks, so that access is granted only when users need it. Assignments can be given start and end dates, and an eligible assignment must be activated before it takes effect.
A grant with an end date removes itself. A grant without one depends on a person remembering to review it, which is the pattern behind privilege creep. For tasks with no natural end, such as a service account for a running workload, the review cycle takes the place of the end date.
Compare the grant with use, then remove the difference
Usage records show which part of a grant is dormant. AWS Access Analyzer can generate a policy from CloudTrail activity, with a look-back of up to 90 days, and its unused access findings list unused roles, unused access keys and passwords, and unused permissions. Google's role recommendations compare a principal's permissions with those used in the last 90 days.
Neither provider applies the change for you. Google states that the IAM recommender does not apply recommendations automatically, and that you apply or dismiss each one. The removal step is therefore a decision with an owner, which is where projects usually slow down. The first 90 days gives that step a place in a schedule.
Workloads need the same treatment as people
Workload identities are most of the principals in a cloud account. Google recommends dedicated service accounts for each application, and AWS says workloads on its compute services should use the temporary credentials of an IAM role. Microsoft's managed identities remove the need to manage credentials for a workload on Azure.
The per-cloud detail is in the identity guides, for example AWS human identities and Azure workload identities. A short checklist for the whole path is the written policy template.
A practical test for any single grant is to ask four questions: which actions does it allow, on which resources, under which conditions, and until when. A grant that answers all four in specific terms is least privilege access. A grant that answers "any", "any", "always" and "never expires" is not, however clean the role name looks. Run the test on the five most powerful roles in each account first, since the reduction there is the largest, and write down the answers so the next reviewer can see what was decided and why.
Related pages
Sources
- AWS, security best practices in IAM, read 16 Nov 2026
- AWS, managed policies for job functions, read 16 Nov 2026
- Google Cloud, using IAM securely, read 16 Nov 2026
- Microsoft, best practices for Azure RBAC, read 16 Nov 2026
- Microsoft, what is Privileged Identity Management, read 16 Nov 2026
- AWS, generate policies based on access activity, read 16 Nov 2026
- AWS, IAM Access Analyzer findings, read 16 Nov 2026
- Google Cloud, role recommendations overview, read 16 Nov 2026
- Google Cloud, best practices for service accounts, read 16 Nov 2026
- Microsoft, managed identities for Azure resources, read 16 Nov 2026
Last reviewed 16 Nov 2026.