CIS Controls v8 covers 23.1% of CFTC System Safeguards (17 CFR 37, 38, 39, 49)
9 of the 39 controls in CFTC System Safeguards (17 CFR 37, 38, 39, 49) are already satisfied by evidence you collected for CIS Controls v8. 30 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.
What this leaves you to do
CFTC System Safeguards (17 CFR 37, 38, 39, 49) has 39 controls. Holding CIS Controls v8 already evidences 9 of them, so the work in front of you is 30 controls, not 39, which is 77% of the standard rather than all of it.
That is the whole claim. We do not know your hourly rate, how long a control takes you, or how many people you have, so there is no figure here in dollars or weeks. Every number in that sentence comes from the two counts above it and can be re-derived from the free tools without taking our word for any of it.
This number is directional. It says how much of CFTC System Safeguards (17 CFR 37, 38, 39, 49) your CIS Controls v8 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.
44 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.
Regular audit log review is the log maintenance and analysis element named.
Documented role based access rights deliver the least privilege element named in the category.
A secure configuration process is the baseline configuration management element.
A detailed asset inventory is the authorised and unauthorised device inventory element.
Automated patch management is the patch management element of systems operations.
A secure application development process covers requirements and development standards.
Separate production and non production environments enable pre production testing.
Developer training in secure coding is the secure coding training element named.
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