SekitCrosswalk
ISO/IEC 27001:2022 · derived mapping target

A.8.2Privileged access rights

Tightly control and monitor privileged accounts that can make far-reaching changes, since their misuse or compromise causes outsized damage.

Mapped from the Sekit CSF

The Sekit controls that cover this requirement, lens by lens.

RCF-0006Roles & responsibilities · TechnicalenablesConfiguring system permissions so each security responsibility can only be exercised by the assigned person is the technical precondition that makes A.8.2's privilege restriction enforceable rather than aspirational.RCF-0070Privileged access management · PolicyenablesMandating separate dedicated admin accounts with management approval and a current register is the policy foundation A.8.2's privileged access control depends on.RCF-0071Privileged access management · ProcesssupportsApproving, time-limiting and logging privileged grants, with regular re-justification, is the day-to-day discipline that keeps A.8.2's privileged access controlled rather than only documented.RCF-0072Privileged access management · TechnicalsupportsVaulting admin credentials and alerting on unusual administrative activity gives A.8.2 the technical constraint and visibility it requires over privileged sessions.RCF-0166Local admin control · PolicyenablesRequiring that day-to-day accounts have no admin rights, with privilege granted only on approval, is the policy basis A.8.2's tight control over privilege depends on.RCF-0167Local admin control · ProcesssupportsKeeping local admin rights limited to a current, approved list and re-verifying it regularly operationalizes A.8.2's expectation that privilege stays tightly scoped.RCF-0168Local admin control · TechnicalsupportsEnforcing standard-user sessions technically, so gaining admin rights requires separate approved credentials, is the mechanism that makes A.8.2's local admin restriction stick in practice.RCF-0335Cloud IAM · ProcesssupportsReviewing cloud access rights on a recurring cycle and removing leavers' access the day they go extends A.8.2's privileged access discipline into cloud environments.RCF-0336Cloud IAM · TechnicalsupportsEnforcing MFA and role-based permissions instead of standing cloud admin rights is the technical control that delivers A.8.2's least-privilege objective in the cloud.

NIST CSF 2.0 counterparts

Reached through the Sekit CSF controls both map to — a mapping, not a formal equivalence.

Cyber Essentials counterparts

Evidence that proves this control

What an auditor, or Sekit's evidence engine, asks for.

Local admin and removable-media controls
The rules on who may have administrator rights on their own device and on the use of USB sticks and external drives.
From the Sekit evidence catalog

In practice

Privileged access fails audits most often on the local admin question, not the domain admin one. What works: separate admin accounts from everyday accounts so nobody does routine work while logged in as an administrator, grant local admin only on approval and per need, and vault or time-limit privileged access rather than leaving it standing. Cloud roles need the same discipline: MFA required everywhere and role-based permissions instead of a handful of accounts with standing owner access. Auditors pull the list of everyone with admin rights, on laptops and in the cloud console, and ask who approved each one and when it was last reviewed.

Common gaps

Several long-serving employees still hold local administrator rights granted years ago for a project that ended, with no record of a recent re-justification.
Cloud console access includes a handful of accounts with standing owner-level permissions instead of role-based access scoped to what each person needs.
The privileged access register exists but was not updated when two administrators left the company, so their accounts remained active for weeks.

Questions your auditor will ask

How is administrator access separated from everyday user accounts?
Administrative privileges live in dedicated accounts separate from daily-use accounts, granted only with management approval and tracked in a current register.
Who currently has local administrator rights, and how was that access approved?
A short, approved list of people, reviewed on a regular schedule, and every grant is tied to a specific need documented at the time of approval.
Is multi-factor authentication required for privileged access to cloud environments?
Yes, MFA is enforced for everyone with cloud access, with role-based permissions replacing standing administrator rights wherever the platform supports it.
How often is privileged access reviewed to remove rights no longer needed?
Cloud and local admin access are both reviewed on a recurring cycle, trimming permissions that exceed the role and removing leavers' access immediately.

Where regulation demands it

NIS2 art. 11.3 specifically requires controls for privileged and administrative accounts, separate from ordinary access. ENS op.acc.4 expects a formal process governing how access rights are granted and withdrawn.

Related controls

Via the shared Sekit CSF topic, not the framework's own index.

Ask Sekura: “What evidence proves A.8.2?”
Also via MCP, free with account