Compliance attestation and scope confirmation
The shortest fixed clock in these texts is 8,760 hours (yearly), set by PCI DSS 12.5.2. Paste one job that feeds this consumer, for example pci_scope_confirmation, 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: attestation, aoc, roc export, self assessment, saq, scope confirm, compliance review, scope confirmation.
The clock each rule sets
| Regime | Clock | Clause |
|---|---|---|
| PCI DSS | 8,760h | PCI DSS 12.5.2 Annual and change-driven scope confirmationconfirmed at least once every 12 months |
Questions this page answers
How often does PCI DSS v4.0 require compliance attestation and scope confirmation?
Yearly (8,760 hours): PCI DSS 12.5.2, Annual and change-driven scope confirmation. The entity must document its PCI DSS scope and confirm it at least once every 12 months, plus whenever the in-scope environment changes significantly. The scoping validation must at minimum: identify all data flows across payment stages (for instance authorisation, capture, settlement, chargebacks, refunds) and every acceptance channel (for instance card-present, card-not-present, e-commerce); update all data-flow diagrams under Requirement 1.2.4; identify every place where account data is held, processed or sent, including places outside the current CDE, applications handling CHD, data transmitted across networks and systems, and backups of files; identify all components in, connected to, or able to affect the CDE; identify all segmentation controls and the environments segmented from the CDE, with justification for out-of-scope environments; identify all third-party connections with CDE access; and confirm all these items are included in scope. Applicability: this is the entity's own confirmation and is separate from, and not replaced by, the assessor's scoping check during the annual assessment. Objective under the customized approach: scope is checked periodically and after significant change through thorough analysis and suitable technical measures.
What does the register ask the owner of a compliance attestation and scope confirmation job?
Which data flows, components and segmentation controls did the last confirmation list, and what changed since?
The clauses in full
The entity must document its PCI DSS scope and confirm it at least once every 12 months, plus whenever the in-scope environment changes significantly. The scoping validation must at minimum: identify all data flows across payment stages (for instance authorisation, capture, settlement, chargebacks, refunds) and every acceptance channel (for instance card-present, card-not-present, e-commerce); update all data-flow diagrams under Requirement 1.2.4; identify every place where account data is held, processed or sent, including places outside the current CDE, applications handling CHD, data transmitted across networks and systems, and backups of files; identify all components in, connected to, or able to affect the CDE; identify all segmentation controls and the environments segmented from the CDE, with justification for out-of-scope environments; identify all third-party connections with CDE access; and confirm all these items are included in scope. Applicability: this is the entity's own confirmation and is separate from, and not replaced by, the assessor's scoping check during the annual assessment. Objective under the customized approach: scope is checked periodically and after significant change through thorough analysis and suitable technical measures.
What an assessor asks to see: Annual scope confirmation report with date and approver; Updated data-flow diagrams by payment stage and channel; Account data location register including backups and out-of-CDE findings; Segmentation control list with out-of-scope justifications. Where it usually falls short: No scope reconfirmation after a significant change such as a new payment channel
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