EvidenceSheet

7.2.6 Query access to stored cardholder data restricted

When users query databases or other stores holding cardholder data, that access must be restricted so that: users get to the data by way of applications or other programmatic methods, with their access and allowed actions set by their roles and least privilege; and direct access to, or querying of, stored CHD repositories is limited to the responsible administrators. The guidance defines programmatic methods with examples such as database stored procedures, and advises that granting access to these repositories follow the same role-based process as any other access. Applicability: covers the controls on users querying stored cardholder data; application and system accounts fall instead under Requirement 7.2.5 (and its sub-requirement) and 8.6.1 to 8.6.3. Objective under the customized approach: direct, unfiltered ad hoc queries against cardholder data repositories are prohibited except by an authorized administrator.

Source: PCI DSS v4.0.1, 7.2.6. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open PCI DSS v4.0.1 in the compliance library.

Version 4.0.1 is the active version; 4.0 has been retired. Appendix A1 applies only to multi-tenant service providers, A2 only to card-present POS POI terminals that still use SSL or early TLS, and A3 only when a payment brand or acquirer requires it. Which requirements apply to you follows your validation type.

4
artefacts
1
held by a system
0
at each review
moderate
to go live
Cloud console / configuration management
where the evidence lives
teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

  • Configuration showing end users access CHD only through applications, views or stored procedures · Cloud console / configuration management

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

  • Database user and role listing for cardholder data repositories, showing who has direct query rights · Policy repository / GRC workspace
  • List of responsible database administrators authorized for direct access · Document repository
  • Procedure for granting query access to CHD repositories · Policy repository / GRC workspace

First move

Start with the 1 of 4 artefacts that already live in a system (Cloud console / configuration management); keep the periodic reviews but log each one as a dated record with a named reviewer.

Common gaps auditors find

Do this for your whole sheet

Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.

Build my evidence sheet

7.2.5.1 Application and system account access reviewed periodically · 7.3.1 Need-to-know access control system covers all components