# ISO/IEC 27001 8.2 — Privileged access rights

- Source: https://support.icompaas.com/support/solutions/articles/a_gen_iso27001_82_edfff31388-isoiec-27001-82-privileged-access-rights
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [ISO/IEC 27001:2022](https://support.icompaas.com/support/solutions/c_gen_iso27001) › [Technological controls](https://support.icompaas.com/support/solutions/folders/f_gen_cgeniso27001_technologicalcontrols)
- Last updated: 2026-05-30
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

ISO/IEC 27001 · Control 8.2 · Priority: high · Component: Technological controls

### What this control covers

The allocation and use of privileged access rights shall be restricted and managed.

### Why it matters

Identity is the new perimeter — most breaches start with a stolen credential or over-privileged account, so this control is one of the single highest-leverage items you can implement.

### How to implement

#### AWS

Use **IAM Identity Center** (formerly AWS SSO) as the single source of truth for human access; back it with your corporate IdP via SAML/SCIM. Avoid IAM users for people — they don't get MFA-by-default, rotation, or session lifetimes. For workloads, use **IAM Roles** (assumed by EC2/Lambda/EKS service accounts via IRSA) and never long-lived access keys. Run [IAM Access Analyzer](https://docs.aws.amazon.com/IAM/latest/UserGuide/access-analyzer.html) weekly to surface unused access and external-account exposure.

#### Azure

Centralize identity on **Microsoft Entra ID** (formerly Azure AD). Require **Conditional Access** policies: MFA for all admin roles, block legacy auth, location/device gating. Use **Privileged Identity Management (PIM)** to make admin roles just-in-time and time-bound. For Azure resources, prefer **Managed Identities** over service principals with secrets.

#### GCP

Use **Cloud Identity** (or Workspace) as the IdP and **IAM** for resource access. Grant roles at the lowest scope (project > folder > org) using **Workload Identity Federation** for CI/CD and **service accounts** for workloads — never download service-account keys when avoidable. Enable **Policy Intelligence** recommenders to right-size privileges and detect dormant identities.

#### Google Workspace

Enforce **2-Step Verification** (preferably hardware keys for admins) for the entire org, set session length to ≤ 12 hours, and disable less-secure-app access. Use **Context-Aware Access** levels to restrict admin sign-in by IP/device posture. Provision and de-provision users via **SCIM** from your HRIS so leavers lose access on day one.

#### GitHub

Require **SSO + SCIM** from your IdP on the organisation; enforce **2FA** org-wide and use **fine-grained PATs** (or, better, GitHub Apps) instead of classic tokens. Restrict **outside collaborators**, require signed commits on protected branches, and use **OIDC** from Actions to short-lived AWS/GCP/Azure credentials rather than stored secrets.

#### Zoho Mail

Make **two-factor authentication** mandatory for all users (TOTP, OneAuth, or YubiKey) in _Admin Console → Security_. Configure **SAML SSO** against your IdP and disable password-based logins for admins. Use **role-based privileges** (Admin / Spam Moderator / Mail Account Admin) and review the _Login history_ report monthly for anomalies.

### Evidence to collect

-   `identity_scan` — See the iCompaas Evidence library for the canonical source for this evidence type.
-   `infra_scan` — See the iCompaas Evidence library for the canonical source for this evidence type.

IAM analytics (Okta, SailPoint) show privileged roles are restricted and reviewed.

### Quick checklist

-   Management — Management / Rights
-   Identity — Management / Rights
-   Access — Management / Rights

### Related articles on this site

-   [Ensure Access Review is Set Up for External Users in Azure AD Privileged Identity Management (PIM](https://support.icompaas.com/support/solutions/articles/62000229788-ensure-access-review-is-set-up-for-external-users-in-azure-ad-privileged-identity-management-pim)
-   [Ensure AWS Identity and Access Management (IAM) is in use](https://support.icompaas.com/support/solutions/articles/62000234465-ensure-aws-identity-and-access-management-iam-is-in-use)
-   [Ensure to Implement Identity and Access Management (IAM)](https://support.icompaas.com/support/solutions/articles/62000234479-ensure-to-implement-identity-and-access-management-iam-)
-   [Enable Microsoft Entra Authentication for Azure SQL Servers to Centralize Identity and Access Management](https://support.icompaas.com/support/solutions/articles/62000234769-enable-microsoft-entra-authentication-for-azure-sql-servers-to-centralize-identity-and-access-managem)