Access provisioning and review: the clause the question tests
How access is granted, reviewed on a cycle and removed when people move or leave.
How the customer usually asks it
example"How often are user access rights reviewed, and by whom?"
Anchor clauses
6 frameworks| Framework | Anchor clause |
|---|---|
| ISO/IEC 27001:2022 | 5.18 Access rights |
| SOC 2 (Trust Services Criteria) | CC6.2 CC6.2 Registering and authorising users before issuing credentials |
| SIG (Shared Assessments) | domain H Access Control |
| NIST Cybersecurity Framework 2.0 | PR.AA-05 Access permissions, entitlements, and authorizations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties |
| NIST SP 800-53 Rev 5 | AC-2 Account management |
| PCI DSS v4.0.1 | 7.2.4 User accounts and privileges reviewed every six months |
Every framework that anchors this family is listed here; a register shows the ones ticked for the customer.
Evidence expected
The access request and approval records, the last completed access review with its sign-off, and leaver records showing when access was removed.
The clauses, with what an assessor asks for
ISO 27001 5.18 Access rightsProvision, review, modify and remove access rights in line with the access control policy.
Where answers usually fall short: Reviews lack documented corrective actions; Access changes not tied to approved request workflow
Source: ISO/IEC 27001:2022
SOC 2 CC6.2 CC6.2 Registering and authorising users before issuing credentialsNamed only: the criteria are not stated here; see the official text.
Where answers usually fall short: Accounts created without a recorded approval; Leavers retaining active accounts days or weeks after departure
Source: SOC 2 (Trust Services Criteria)
SIG domain H Access ControlWhat it asks for, in one line (the standard's own text is not quoted here):
Implement formal access provisioning, periodic recertification, least privilege, separation of duties, and privileged access management across systems hosting in scope data.
Where answers usually fall short: Privileged accounts shared; User reviews completed without manager attestation
Source: SIG (Shared Assessments)
NIST CSF PR.AA-05 Access permissions, entitlements, and authorizations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of dutiesAccess permissions, entitlements, and authorizations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties
Where answers usually fall short: Standing privileges still common; Access reviews rubber stamped
Source: NIST Cybersecurity Framework 2.0
SP 800-53 AC-2 Account managementRequires accounts to be managed across their full life cycle: permitted and prohibited account types defined, account managers assigned, membership prerequisites and approvals required, accounts created, modified, disabled and removed under documented criteria, usage monitored, and access reauthorized on a defined frequency.
Where answers usually fall short: Shared and service accounts sit outside the joiner mover leaver process entirely; Recertification is signed off in bulk without any account actually being removed
Source: NIST SP 800-53 Rev 5
PCI DSS 7.2.4 User accounts and privileges reviewed every six monthsWhat it asks for, in one line (the standard's own text is not quoted here):
All user accounts and their related access privileges, including third-party and vendor accounts, must be reviewed at least every six months. The review must confirm that accounts and access remain appropriate for each person's job function, any inappropriate access must be dealt with, and management must acknowledge that the remaining access is appropriate. The guidance notes the review is also a chance to catch terminated users and third parties whose access was missed. Applicability: covers every user account and related privilege, including accounts of personnel, of vendors and of other third parties and accounts used to reach third-party cloud services; application and system accounts are handled instead by Requirement 7.2.5 (and its sub-requirement) and by 8.6.1 to 8.6.3. Objective under the customized approach: management periodically verifies that account privilege assignments are correct and remediates nonconformities. Future-dated: treated as a best practice up to 31 March 2025 and mandatory since then.
Where answers usually fall short: Reviews cover employees but omit vendor accounts and cloud console users; Reviewers rubber-stamp lists without evidence of removals being actioned
Source: PCI DSS v4.0.1