A.8 Technological controls

A.8.2 Privileged access rights

Not mandatory by default – decided in your SoA

What it means in plain language

Restrict and tightly manage privileged (admin) access.

Is it mandatory? Not automatically. You must consider this control in your Statement of Applicability (6.1.3 d). Include it if your risk assessment, laws, contracts or business needs require it; if you exclude it, write down a justification an auditor will accept.

Why this control matters

Privileged access must be requested, approved, used, reviewed, and removed across systems that can alter security settings, data, or services. The practical risk is not merely having admin accounts, but allowing routine work, emergency elevation, and dormant privilege to blend together without oversight. A controlled approach will separate account types, define approvers, and show how periodic reviews and logging support operational control.

Common auditor findings to check for

Potential gaps to test in your own environment, not a claim about observed audit frequency.

  • Administrators use a single daily account for routine work and privileged tasks, making it impossible to distinguish normal activity from elevated actions in logs.
  • Approval for privileged access is informal or buried in chat messages, so reviewers cannot confirm who authorised access, for what system, and for how long.
  • Monthly reviews exist on paper, but stale accounts, excessive role membership, and emergency access exceptions are not reconciled to HR movements or ticket history.

How you can implement it

Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.

  • Require separate named admin accounts for privileged work and standard accounts for emails, browsing, and collaboration. Access requests should identify the system, business reason, duration, and approving manager or system owner. The access management procedure should describe how just-in-time access, break-glass use, and time-bound memberships are granted and revoked.
  • Use a role catalogue that maps privileged roles to systems and required competencies, then review it whenever a platform changes or a supplier introduces a new console. Security or identity administration should run a monthly attestation, compare active admin membership to tickets and leavers, and escalate unresolved exceptions to the service owner.
  • Log privileged actions in central systems where feasible, including account creation, permission elevation, configuration changes, and security control adjustments. The accountable technical lead should check for orphaned accounts, shared admin credentials, and privilege creep after project work or incidents, then open corrective tickets when excess rights are found.
  • Define an emergency access path for outages or incidents, including approval after the fact, reason capture, and post-use review. Keep a record of when the elevated session began and ended, what changed, and whether the normal control path failed. This supports management review and later corrective action if access was misused or poorly justified.

What an auditor will ask to see

  • Privileged access request showing system, business need, approver, and expiry.
  • Monthly admin review report with removals, exceptions, and follow-up actions.
  • Break-glass session log with time stamps, changes made, and post-use sign-off.

Baseline documents in the kit

These free kit documents help you document or evidence A.8.2. Each one is tailored to your organization when you build your kit.

Connect this work to your ISMS

Review the dependencies with A.5.18 — Access rights and A.8.15 — Logging. Keep the ownership and evidence consistent across these activities.

ISO/IEC 27001 vs SOC 2: evidence you can reuse for the wider implementation context.

Use the SIG and CAIQ questionnaire accelerator to find supporting documents. A mapping is a starting point: verify your actual operating evidence before answering a buyer.

For help adapting this to your environment, explore ISO/IEC 27001 consulting, starting with a free one-hour consultation.

Get these documents tailored to your organization

109 ready-to-edit documents, including all 19 mandatory ones, tailored from a short scoping questionnaire and linked to your risk register and SoA.

Start free

Plain-language interpretation by an ISO/IEC 27001 lead implementer, not the official text of ISO/IEC 27001:2022.