CMMC and NIST SP 800-171 readiness for defence suppliers
The requirement arrives through a contract clause, usually from a prime. The first thing it needs is a boundary: which systems hold the information, and which people and vendors touch them.
The short version
CMMC readiness is preparing a defence supplier to show that the NIST SP 800-171 requirements are met in the systems that hold controlled unclassified information, before a contract requires proof. Only the assessors the program authorizes can award a CMMC level; our work is the readiness that comes before.
Canadian suppliers meet the same requirements in their own program; CPCSC for defence suppliers explains how it lines up with CMMC.
What the rules say, and what is still moving
The CMMC Program rule, 32 CFR Part 170, took effect on 16 December 2024, and the US defence department’s DFARS rule that puts the requirement into contracts took effect on 10 November 2025. The first is published in the Federal Register, and the text is in 32 CFR Part 170.
Level 2 of the program is defined as identical to the requirements of NIST SP 800-171 Revision 2, even though NIST has since published Revision 3, which supersedes Revision 2. NIST’s page for Revision 3 says so. The consequence is practical: assess against the revision your contract names, and read the clause before the standard.
The US defence department publishes the schedule by which each phase of CMMC reaches contracts, and it has been changing, so we work from its current CMMC page and not from a date written here. It is at the DoD CIO’s CMMC page.
What readiness produces
- A scoped boundary drawn from the real network and cloud tenants, which is often the largest saving.
- A requirement-by-requirement assessment, each with the artifact that shows it is met, in the style of the evidence pack.
- A remediation plan with owners and dates, using programme and identity work.
- Supplier flow-down checks, through vendor risk management.
How the work is bounded
The scope is agreed in writing before work starts, and the engagement is quoted in writing with it.
SecHB does not issue certifications, attestations or audit opinions: those come from accredited certification bodies, CPA firms and QSAs. The work here is what an organization does to be ready for them.
Nothing here is legal advice. Where a question turns on the law, the work is done alongside the client’s counsel, not instead of them.
Questions we are asked
What does CMMC readiness cover?
CMMC readiness is preparing a defence supplier to show that the NIST SP 800-171 requirements are met in the systems that hold controlled unclassified information, before a contract requires proof.
When did the CMMC rules take effect?
The CMMC Program rule, 32 CFR Part 170, took effect on 16 December 2024, and the US defence department’s DFARS rule that puts the requirement into contracts took effect on 10 November 2025.
Which revision of NIST SP 800-171 does CMMC use?
Level 2 of the program is defined as identical to the requirements of NIST SP 800-171 Revision 2, even though NIST has since published Revision 3, which supersedes Revision 2.
When will a contract require a given level?
The US defence department publishes the schedule by which each phase of CMMC reaches contracts, and it has been changing, so we work from its current CMMC page and not from a date written here.
Do you award a CMMC level?
Only the assessors the program authorizes can award a CMMC level; our work is the readiness that comes before.
Tell us what the contract clause says
Send the clause and say which systems touch the information. The reply says what a scope would cover. Related: the United States page.