FedRAMP Moderate covers 60% of NIST SP 800-172
21 of the 35 controls in NIST SP 800-172 are already satisfied by evidence you collected for FedRAMP Moderate. 14 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-172 has 35 controls. Holding FedRAMP Moderate already evidences 21 of them, so the work in front of you is 14 controls, not 35, which is 40% 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 21 controls of NIST SP 800-172 you do not have to implement again, which is $14.24 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 21 already evidenced are | 84 hours | 168 hours | 336 hours |
| and the 14 remaining are | 56 hours | 112 hours | 224 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 SP 800-172 your FedRAMP Moderate 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.
48 candidate mappings were examined and 4 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.
Terms and conditions for external systems restrict access to organization provisioned resources.
External systems are permitted only after verifying controls or agreeing a connection.
FedRAMP requires information flows separated logically or physically between domains.
Flow enforcement against approved policies controls transfers between connected domains.
Alerts and advisories from named external bodies are the threat intelligence intake.
FedRAMP fixes annual risk assessment, which is the assessment the threat intelligence guides.
The FedRAMP system security plan records the controls selected and is reviewed annually.
FedRAMP fixes annual assessment of controls by an accredited assessor.
Claims that did not hold
4 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.
judged against NIST SP 800-172 content that was corrected the same day. 3.13.2e now carries its issued requirement (introduce unpredictability into operations) not least privilege, and 3.14.3e carries scope inclusion or network segregation not supply chain provenance. Refuted 2026-08-19.
Claimed at high confidence before it was rejected.
judged against NIST SP 800-172 content that was corrected the same day. 3.13.2e now carries its issued requirement (introduce unpredictability into operations) not least privilege, and 3.14.3e carries scope inclusion or network segregation not supply chain provenance. Refuted 2026-08-19.
Claimed at high confidence before it was rejected.
judged against NIST SP 800-172 content that was corrected the same day. 3.13.2e now carries its issued requirement (introduce unpredictability into operations) not least privilege, and 3.14.3e carries scope inclusion or network segregation not supply chain provenance. Refuted 2026-08-19.
Claimed at high confidence before it was rejected.
judged against NIST SP 800-172 content that was corrected the same day. 3.13.2e now carries its issued requirement (introduce unpredictability into operations) not least privilege, and 3.14.3e carries scope inclusion or network segregation not supply chain provenance. Refuted 2026-08-19.
Claimed at high 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