PCI DSS 4.0 covers 30.8% of CFTC System Safeguards (17 CFR 37, 38, 39, 49)
12 of the 39 controls in CFTC System Safeguards (17 CFR 37, 38, 39, 49) are already satisfied by evidence you collected for PCI DSS 4.0. 27 are genuine gaps. Every claim below was judged against both control sets and then argued against; the ones that did not survive are published further down with the reason each failed.
This number is directional. It says how much of CFTC System Safeguards (17 CFR 37, 38, 39, 49) your PCI DSS 4.0 evidence satisfies. The reverse pair is a different number, often very different, because a security standard has enormous depth for access control and almost none for lawful basis or data subject rights.
60 candidate mappings were examined and 0 were removed. Signed off 2026-08-19, review level machine verified. Mappings were judged by Claude Code rather than read line by line by a practitioner. Every claim shows its reasoning so you can check it. Ask and a practitioner will review this pair.
Where the gaps are
Coverage is never evenly spread. A source standard usually satisfies one part of a target almost completely and barely touches another, and which part is which is the thing worth knowing before you plan the work.
Theme level, not control level, deliberately. The per-control list of what is evidenced and what is a gap is the report itself, so publishing it here would be publishing the thing being sold.
Claims that held
A sample. Each one names the control whose evidence does the work, the control it satisfies, and why.
Screening personnel before access is the personnel security and screening element.
Daily review of security event and critical system logs is the log maintenance and analysis element.
Authenticating all user and administrator access is the identification and authentication element.
Access assigned by job classification and least privilege is the least privilege element.
A current inventory of system components is the inventory element.
Established change control procedures for production changes is the configuration change element.
Installing applicable security patches within defined timeframes is the patch management element.
Configuration standards covering all system components is the baseline configuration element.
Claims that did not hold
Nothing proposed for this pair was rejected in review. That is unusual and worth knowing rather than hiding: it means the candidate set was small and every candidate held.
The full report
Everything above is a sample. The report is every evidenced control and every gap, with the reasoning and the source document behind each one, in a form you can hand to an assessor. $299, emailed immediately.
Buy this crosswalk