ISO 27002:2022 covers 58.5% of NIST Cybersecurity Framework 2.0
62 of the 106 controls in NIST Cybersecurity Framework 2.0 are already satisfied by evidence you collected for ISO 27002:2022. 44 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 Cybersecurity Framework 2.0 has 106 controls. Holding ISO 27002:2022 already evidences 62 of them, so the work in front of you is 44 controls, not 106, which is 42% of the standard rather than all of it.
That is the whole claim. 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.
In money, using only our numbers. The full report is $299 and names 62 controls of NIST Cybersecurity Framework 2.0 you do not have to implement again, which is $4.82 per control identified. That arithmetic uses our price and our count and assumes nothing about you.
In your hours, using your assumption. We do not know what a control costs you to implement, so pick the column that looks like your organisation. These are your figures, not our claim.
| If a control takes you | 4 hours | 8 hours | 16 hours |
|---|---|---|---|
| the 62 already evidenced are | 248 hours | 496 hours | 992 hours |
| and the 44 remaining are | 176 hours | 352 hours | 704 hours |
Multiply by your own rate. We publish no rate because we have not measured yours, and a number built on an invented rate is the kind of claim this platform exists to argue against.
This number is directional. It says how much of NIST Cybersecurity Framework 2.0 your ISO 27002: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.
194 candidate mappings were examined and 93 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.
Assessment of security events to decide their nature is the analysis required.
Monitoring requires correlation of information from multiple sources.
Event reporting requires information on events to reach the responsible staff.
Threat intelligence must be analysed and fed into security activities.
Assessment decides whether an event is classified as an incident against criteria.
Monitoring requires networks and network services to be watched for anomalies.
Physical security monitoring of premises is the same outcome.
Monitoring covers user activity and system use for anomalous behaviour.
Claims that did not hold
85 proposed mappings for this pair were rejected. They are kept in the graph rather than deleted, so what was thrown out is as inspectable as what survived. A crosswalk that never rejects anything is not being judged.
Held back 2026-08-19. Generated by the retired metered path, refuted at 56 percent wherever re-judged. Pair pulled from sale pending a rebuild on the Max plan.
Claimed at high confidence before it was rejected.
did not survive the adversarial verification pass run by qwen3-235b-a22b-2507 via openrouter. No per-edge rationale was recorded at the time, so the process is stated rather than a reason invented.
Claimed at medium confidence before it was rejected.
did not survive the adversarial verification pass run by qwen3-235b-a22b-2507 via openrouter. No per-edge rationale was recorded at the time, so the process is stated rather than a reason invented.
Claimed at medium confidence before it was rejected.
did not survive the adversarial verification pass run by qwen3-235b-a22b-2507 via openrouter. No per-edge rationale was recorded at the time, so the process is stated rather than a reason invented.
Claimed at medium confidence before it was rejected.
did not survive the adversarial verification pass run by qwen3-235b-a22b-2507 via openrouter. No per-edge rationale was recorded at the time, so the process is stated rather than a reason invented.
Claimed at low confidence before it was rejected.
retired metered-API path. 56 percent of its output was refuted wherever it was re-judged, so its residue is not trusted evidence. Superseded by judgement on the Claude Max plan 2026-08-19.
Claimed at medium confidence before it was rejected.
Held back 2026-08-19. Generated by the retired metered path, refuted at 56 percent wherever re-judged. Pair pulled from sale pending a rebuild on the Max plan.
Claimed at high confidence before it was rejected.
retired metered-API path. 56 percent of its output was refuted wherever it was re-judged, so its residue is not trusted evidence. Superseded by judgement on the Claude Max plan 2026-08-19.
Claimed at medium confidence before it was rejected.
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