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.
This control maps to 32 controls across 15 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.
PCI DSS 4.0 7.2.6 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of PCI DSS 4.0 your existing evidence covers. Hold ISO 27001:2022 and 139 of 280 PCI DSS 4.0 controls already carry evidence.
Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 415 were rejected on the ISO 27001:2022 pair alone.
The graph holds this control, the 32 it maps to, and the evidence behind each claim, over MCP and REST.