Skip to content
Least Privilege Principle

A least privilege policy template you can adopt and edit

A written least privilege policy for cloud environments, with [bracketed placeholders] for your organization's names, periods and owners. It covers purpose, scope, roles, rules, reviews, exceptions with an expiry date, and enforcement, and maps to NIST SP 800-53 Rev. 5 control AC-6. Template edition 16 Nov 2026.

Open the calculator ยท The field guide

1. Purpose

This policy sets how [Organization] grants, reviews and removes access to its cloud environments so that every identity holds only the access its function needs. It implements the least privilege requirement of [framework, for example NIST SP 800-53 Rev. 5 control AC-6] and supports [other obligations, for example the access control requirements in your contracts].

The policy owner is [Role, for example Head of Cloud Security]. It was approved by [Approver] on [Date] and is reviewed at least every [12] months.

2. Scope

This policy applies to every cloud account, subscription and project that [Organization] owns or operates, including [AWS accounts], [Azure subscriptions] and [Google Cloud projects]. It covers every identity: employees, contractors, partners, service accounts, roles, managed identities, pipelines and automation.

It applies to production and to non-production environments that hold [production data or credentials that reach production]. Systems outside the scope are listed in [Register name], each with a named owner and a reason.

3. Roles and responsibilities

The access owner for each account, subscription or project is named in [Register name]. The access owner approves grants, performs the reviews in section 6, and signs exceptions. The security team maintains this policy, the boundaries in section 5 and the evidence described in section 8.

Engineering teams request access through [Ticketing or pull request process] and do not grant access to themselves. The internal audit function, [Function], tests this policy at least [annually] and reports to [Governance body].

4. Rules for granting access

Access is granted for a stated task, to a named identity, at the narrowest scope that works. Each grant records the requester, the approver, the reason and the date. These rules apply to all identities:

  • No identity receives a basic or administrator role in a production environment unless the access owner approves it in writing for a stated task.
  • People use federated sign-in with temporary credentials. Long-lived access keys are issued only under an exception in section 7.
  • Each workload has its own identity. Identities are not shared between workloads or between environments.
  • Roles are assigned to groups, not to individuals, except for [named break-glass accounts].
  • Privileged roles are assigned as time-bound or on-request access with a maximum duration of [8 hours].
  • Wildcards in actions or resources require a recorded reason and are reviewed in section 6.
  • Access is defined in code and changed by pull request, so each change has an author, a reviewer and a date.

5. Boundaries

The security team maintains organization-level limits that hold whatever roles are granted: [the cloud regions in use], [the services in use], a block on leaving the organization with data, and protection of logging and of the boundaries themselves.

A new boundary is tested against [30 days] of recent access, released first in audit or log-only mode where the cloud offers it, and enforced after the affected owners have confirmed. The previous version is kept for rollback. Changes to boundaries need approval from [Role].

6. Reviews

Access owners review every human and workload identity every [90 days] for privileged roles and every [180 days] for all others. A review compares what is granted with what was used in the last [90] days and records the decision to keep, narrow or remove each grant.

Dormant identities with no use for [90] days are disabled and removed after [30] more days unless the access owner records a reason. The security team reports each quarter: reviews completed on time, grants removed, exceptions open, and exceptions past expiry.

7. Exceptions

An exception is a written, approved departure from section 4. It names the identity, the access, the reason, the compensating control, the approver and an expiry date no later than [90] days after approval.

Expired exceptions are removed automatically or by the access owner within [5] working days. An exception can be renewed once by the same approver and then needs approval from [Senior role]. The register of exceptions is part of the evidence in section 8.

8. Evidence and enforcement

The security team keeps for [7] years: this policy and its versions, the list of identities and their grants, review results, approvals, exception records, boundary changes and audit logs of privileged actions. Evidence is stored in [System] with access limited to [Roles].

A breach of this policy is handled under [Disciplinary or contract procedure]. Access that conflicts with this policy and has no exception is removed by the security team after notice to the access owner, or immediately where there is an active risk. The policy is checked against [NIST SP 800-53 Rev. 5 AC-6] on each annual review.

Before adopting the template, read the principle of least privilege for the control it implements, the first 90 days for a schedule to put it into practice, and the methodology for the Access Debt Calculator that sizes the work.

Download

Sources

  1. NIST SP 800-53 Rev. 5 catalog (OSCAL JSON), control AC-6, read 16 Nov 2026
  2. NIST CSRC, SP 800-53 Rev. 5.1.1 catalog, control AC-6, read 16 Nov 2026
  3. AWS, security best practices in IAM, read 16 Nov 2026
  4. Google Cloud, using IAM securely, read 16 Nov 2026
  5. Microsoft, what is Privileged Identity Management, read 16 Nov 2026
  6. Microsoft, access reviews in Microsoft Entra ID, read 16 Nov 2026

Last reviewed 16 Nov 2026.