# In the cloud, least privilege is a standing requirement on every identity, human or machine

Guide, 10 Nov 2026, read 10 Nov 2026

**The short answer.** The principle of least privilege gives each entity only the access its function needs. NIST SP 800-53 control AC-6 requires it, and AWS and Google Cloud each publish guidance for applying it. The cloud case differs in scale: identities are created in code, and most of them belong to workloads.

## What the principle says

NIST's glossary defines least privilege, citing NIST SP 800-53 Rev. 5, as the principle that a security architecture is designed so that each entity is granted the minimum system resources and authorizations that the entity needs to perform its function. The older CNSSI definition applies the same idea to users and to processes acting on their behalf. The wording is deliberately general: it covers people, services and processes alike, which matters in the cloud, where most principals are not people.

The control that turns the principle into a requirement is AC-6 in NIST SP 800-53 Rev. 5. Its statement reads: employ the principle of least privilege, allowing only authorized accesses for users, or processes acting on behalf of users, that are necessary to accomplish assigned organizational tasks. The statement is short on purpose, and the guidance paragraph that follows it does the explaining.

## What AC-6 adds beyond the sentence

The control's guidance says least privilege is applied to specific duties and systems, and to system processes, so that processes operate at privilege levels no higher than necessary. It also says organizations consider creating additional processes, roles and accounts as necessary to achieve it. In cloud terms that is the case for narrow roles per workload. An assessment against the control examines documents, configuration and records, so a policy statement alone does not satisfy AC-6.

The enhancements name practices that map directly to cloud work, including AC-6(1) authorize access to security functions, AC-6(5) privileged accounts, AC-6(7) review of user privileges and AC-6(9) log use of privileged functions. AWS lists NIST 800-53 AC-6 among the related requirements for several of its Security Hub IAM controls. Assessors also test the mechanisms that implement least privilege, so the proof is in configuration and not only in documents.

## What AWS and Google advise

AWS's IAM best practices tell customers to grant only the permissions required to perform a task, by defining the actions allowed on specific resources under specific conditions. They add that starting with AWS managed policies may not give least privilege for your use case, that Access Analyzer can generate a policy from CloudTrail activity, and that you should regularly review and remove unused users, roles, permissions, policies and credentials. The advice is consistent across both providers: begin with the narrowest role that works, then measure and tighten.

Google Cloud's guidance on using IAM securely makes the same point about roles: basic roles include thousands of permissions across all services, so in production you should grant the most limited predefined or custom roles that meet your needs. Google's role recommendations then check granted roles against 90 days of use. Google adds that to replace a basic role you can use role recommendations to decide which roles to grant instead, and Policy Simulator to confirm that the change will not affect the principal's access.

## How the cloud case differs

In a data center, a privileged account was a person with a ticket. In the cloud, most principals are workloads: roles, service accounts and managed identities created by pipelines, often with broad permissions granted while a developer was exploring. AWS says as much in its own advice, that you might start broad and reduce as the use case matures. Pipelines, containers and functions each carry an identity, and each identity needs its own boundary.

Creation is fast and removal is slow, so the gap grows by default. The principle is unchanged, and the work is different: continuous measurement of use against grants, changes tested before they ship, and boundaries that remove whole classes of access. This is the territory of the CIEM tools ranked on this index. Tracking both the grants and the use of each identity over time is the job of the tools ranked here.

## Turning the principle into evidence

An auditor reading AC-6 asks for the access control policy, procedures for least privilege, the list of assigned authorizations and system configuration settings and audit records. The assessment objects in the NIST catalog name these items. A program that keeps policies as code, simulation results and approvals produces them as a by-product. Assessors may also ask who reviewed the access and when.

The index scores "Evidence for auditors" at 5 percent in the main view and 15 percent in the regulated situation. [The method](/method/) lists the weights. For a program-level plan, see [the first 90 days](/guides/the-first-90-days/). A single audit request is easier to meet when the evidence is collected as the work is done. Regulated buyers should read the regulated situation page, which weights evidence at 15 percent.

## Sources

- NIST CSRC glossary, least privilege: https://csrc.nist.gov/glossary/term/least_privilege (read 10 Nov 2026)
- NIST SP 800-53 Rev. 5 catalog, control AC-6: https://raw.githubusercontent.com/usnistgov/oscal-content/main/nist.gov/SP800-53/rev5/json/NIST_SP-800-53_rev5_catalog.json (read 10 Nov 2026)
- AWS IAM best practices: https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html (read 10 Nov 2026)
- Google Cloud, using IAM securely: https://cloud.google.com/iam/docs/using-iam-securely (read 10 Nov 2026)
- Google Cloud, overview of role recommendations: https://cloud.google.com/policy-intelligence/docs/role-recommendations-overview (read 10 Nov 2026)
- AWS Security Hub, IAM controls: https://docs.aws.amazon.com/securityhub/latest/userguide/iam-controls.html (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://cloudleastprivilege.com/guides/principle-of-least-privilege-in-the-cloud/
