Security Questionnaire Mapper

Cardholder data and PCI DSS: the clause the question tests

Whether card data passes through the service, and on what PCI DSS attestation.

How the customer usually asks it

example

"Do you store, process or transmit cardholder data?"

Read this question

Anchor clauses

1 framework
FrameworkAnchor clause
PCI DSS v4.0.13.2.1 Data retention and disposal minimise stored account data · 12.5.2 Annual and change-driven scope confirmation

Every framework that anchors this family is listed here; a register shows the ones ticked for the customer.

Evidence expected

The PCI DSS attestation of compliance or self-assessment for the service, with its scope, and the data flow showing where account data goes.

The clauses, with what an assessor asks for

PCI DSS 3.2.1 Data retention and disposal minimise stored account data

What it asks for, in one line (the standard's own text is not quoted here):

The entity limits stored account data through policies, procedures and processes governing how long data is kept and how it is disposed of, which address at minimum: (1) every location where account data is stored; (2) any sensitive authentication data (SAD) held before authorization completes; (3) restricting the volume held and the retention period to what legal, regulatory and/or business needs demand; (4) defined retention periods for stored account data, each with a documented business justification; (5) processes to securely delete account data, or make it unrecoverable, once the retention policy says it is no longer needed; and (6) a check performed at least every three months confirming that account data held beyond its retention period has been made unrecoverable or deleted securely. Applicability: where the data is stored by a third-party service provider such as a cloud provider, the entity is responsible for working with it to understand how the provider satisfies this requirement, with considerations including secure deletion of every geographic instance of a data element. Objective under the customized approach: account data is kept only where needed, for the shortest necessary time, and is securely removed or made unrecoverable afterwards. Future-dated (bullet covering SAD stored before authorization completes): treated as a best practice up to 31 March 2025 and mandatory since then.

Evidence an assessor expects: Data retention and disposal policy with retention periods and business justification per data type; Inventory or data-flow map of all account data storage locations, including backups, archives, removable media, paper and call recordings; Quarterly purge verification records (at least every three months) with results and sign-off; Secure deletion tool configuration or output (for example NIST SP 800-88 aligned wiping) and sample evidence of unrecoverable data; Pre-authorization SAD handling and retention records
Where answers usually fall short: Retention policy omits backups, log files or call-recording platforms where PAN also lands; Quarterly check is not performed or has gaps longer than three months
Source: PCI DSS v4.0.1
PCI DSS 12.5.2 Annual and change-driven scope confirmation

What it asks for, in one line (the standard's own text is not quoted here):

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.

Evidence an assessor expects: 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; Third-party connection inventory
Where answers usually fall short: No scope reconfirmation after a significant change such as a new payment channel; Backups or chargeback and refund flows omitted from data mapping
Source: PCI DSS v4.0.1
No ISO 27001 clause anchors this family, so with ISO 27001 held the register marks the question "beyond your certificate". That is a fact about where the clause sits, not about the controls you run.

Other families in data protection and encryption