User access review export
The shortest fixed clock in these texts is 4,380 hours (every six months), set by PCI DSS 7.2.4. Paste one job that feeds this consumer, for example quarterly_access_review_export, weekly, and the register reads its period against the clocks below, names the gap in hours, and carries the question for its owner.
Matched on the job name or the consumer column by these words: access review, access recert, entitlement review, user review, uar, access certification, recertification, access review.
The clock each rule sets
| Regime | Clock | Clause |
|---|---|---|
| PCI DSS | 4,380h | PCI DSS 7.2.4 User accounts and privileges reviewed every six monthsat least once every six months |
| ISO 27001 | no clock | ISO 27001 5.18 Access rights |
| SP 800-53 | no clock | SP 800-53 AC-2 Account managementa defined frequency |
| HIPAA | no clock | HIPAA 164.308(a)(4)(ii)(C) Access Establishment and Modification (Addressable) |
Questions this page answers
How often does PCI DSS v4.0 require user access review export?
Every six months (4,380 hours): PCI DSS 7.2.4, User accounts and privileges reviewed every six months. 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.
How often does ISO/IEC 27001:2022 require user access review export?
The text of ISO 27001 5.18 (Access rights) sets no fixed period: no period set by the text. Provision, review, modify and remove access rights in line with the access control policy.
How often does NIST SP 800-53 Rev 5 require user access review export?
The text of SP 800-53 AC-2 (Account management) sets no fixed period: a defined frequency. Requires 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.
How often does HIPAA Security Rule require user access review export?
The text of HIPAA 164.308(a)(4)(ii)(C) (Access Establishment and Modification (Addressable)) sets no fixed period: no period set by the text. Implement policies that document, review, and modify a user's right of access. NIST recommends periodic recertification and just-in-time elevation for privileged tasks.
What does the register ask the owner of a user access review export job?
Who receives the export, who signs each review, and where does the signed review rest?
The clauses in full
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.
What an assessor asks to see: Semi-annual user access review records for each in-scope system, with review dates; Evidence that inappropriate access found was removed or corrected, such as closed tickets; Management sign-off acknowledging access remains appropriate; Inventory of third-party, vendor and cloud-service accounts included in the review scope. Where it usually falls short: Reviews cover employees but omit vendor accounts and cloud console users
Provision, review, modify and remove access rights in line with the access control policy.
Guidance beside it, ISO 27002 5.18: Requires access rights to information and other associated assets to be provisioned, reviewed, modified and removed in accordance with the organisation's topic specific policy and rules on access control.
What an assessor asks to see: access_provision_records; access_review_reports; access_revocation_logs; role_definition_documents. Where it usually falls short: Reviews lack documented corrective actions
Requires 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.
What an assessor asks to see: Account type register showing which account types are permitted and which are prohibited; Provisioning and deprovisioning tickets carrying documented approval by the responsible party; Leaver reconciliation between the human resources record and account disablement dates; Periodic account recertification results with evidence that revocations were executed. Where it usually falls short: Shared and service accounts sit outside the joiner mover leaver process entirely
Implement policies that document, review, and modify a user's right of access. NIST recommends periodic recertification and just-in-time elevation for privileged tasks.
What an assessor asks to see: Quarterly access recertification reports; Modification approval records; Privileged access management logs; Manager attestations. Where it usually falls short: Recertification not performed
Requirement text is our own statement of each clause, from the standards published at compliance.theartofservice.com, the same publisher as this register, read against the published text of each standard: our statement of each clause, not the instrument verbatim. Run this job through the register