CFTC System Safeguards (17 CFR 37, 38, 39, 49) covers 9.2% of PCI DSS 4.0
23 of the 249 controls in PCI DSS 4.0 are already satisfied by evidence you collected for CFTC System Safeguards (17 CFR 37, 38, 39, 49). 226 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 PCI DSS 4.0 your CFTC System Safeguards (17 CFR 37, 38, 39, 49) 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.
51 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.
Requires regular periodic objective testing and review covering all required test types.
Requires vulnerability testing no less frequently than quarterly for covered entities.
Requires penetration testing of defined scope at a risk determined frequency.
Requires annual internal penetration testing by independent or non operating personnel.
Requires annual external penetration testing by independent contractors for covered entities.
Findings from required testing must be documented and remediated in a timely manner.
Requires a written security incident response plan with defined content and escalation.
Incident response plan must be tested at least annually for covered entities.
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