ISO 27001:2022 covers 50% of NIST SP 800-218
21 of the 42 controls in NIST SP 800-218 are already satisfied by evidence you collected for ISO 27001:2022. 21 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
NIST SP 800-218 has 42 controls. Holding ISO 27001:2022 already evidences 21 of them, so the work in front of you is 21 controls, not 42, which is 50% 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 NIST SP 800-218 your ISO 27001:2022 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.
61 candidate mappings were examined and 2 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.
Identifying, specifying and approving application security requirements is the same task.
Extending security requirements down the ICT supply chain is communicating them to providers.
Explicit traceable allocation of security ownership covers development roles.
Role appropriate current security training is the same training obligation.
Security testing defined for acceptance sets the release criteria.
Separating and securing development and test environments is the same requirement.
Protecting user endpoints applies directly to developer workstations.
Managing read and write access to source code and libraries prevents unauthorised modification.
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