CMMC: what defence suppliers need before the next contract
Published · By National Front Corp.
Before the next contract, a defence supplier needs the CMMC status the solicitation names, recorded in the Department of Defense’s Supplier Performance Risk System (SPRS): Level 1 for Federal Contract Information, Level 2 for Controlled Unclassified Information or Level 3 for the most sensitive programs, through a self-assessment or a third-party certification as the contract specifies. The requirement has been appearing in solicitations and contracts in phases since November 2025, and it flows down to subcontractors wherever they are based, including Canadian aerospace and defence firms. Because the status must be in place at the time of award, preparation has to start well before the bid.
This article is general information, not legal advice. Which CMMC requirements apply to your contracts is a question for your legal counsel and your prime contractor or contracting officer; our role is to build and run the controls that put that interpretation into practice.
What is CMMC, and when did it take effect?
The Cybersecurity Maturity Model Certification (CMMC) program verifies that defence contractors actually implement the security requirements already in their contracts. Since the end of 2017, DFARS clause 252.204-7012 has required contractors that handle Controlled Unclassified Information to implement NIST SP 800-171 and to report cyber incidents to the Department of Defense within 72 hours. What CMMC adds is verification, and a status that must be current for a company to win and keep a contract.
Two rules put it in place:
- The program rule, 32 CFR Part 170, took effect on 16 December 2024. It defines the levels, the assessment process and the roles of assessors.
- The acquisition rule, in the DFARS, took effect in November 2025 and puts CMMC requirements into solicitations and contracts.
The rollout is phased over several years. The first phase, which began in November 2025, relies mainly on self-assessments at Levels 1 and 2. The second phase begins one year later, in November 2026, and adds Level 2 certification by third-party assessors as a standard requirement in applicable solicitations. Later phases add Level 3 and extend the requirements to all applicable contracts, including option periods. The Department can also require a higher level earlier on a given contract.
Which level will your contract require?
The level depends on the information you will handle, and the solicitation names it.
- Level 1 applies to Federal Contract Information (FCI). It covers the 15 basic safeguarding requirements of FAR clause 52.204-21. Contractors perform a self-assessment every year, and a senior official affirms the result in SPRS. Every requirement must be met; plans of action are not allowed at this level.
- Level 2 applies to Controlled Unclassified Information (CUI). It is built on the 110 security requirements of NIST SP 800-171 Revision 2, the version the program rule refers to. Depending on the contract, it is met either through a self-assessment or through a certification assessment by an authorized CMMC Third-Party Assessment Organization (C3PAO), every three years, with an annual affirmation in between.
- Level 3 applies to CUI in the most sensitive programs. It requires a final Level 2 certification first, plus 24 selected requirements from NIST SP 800-172, assessed every three years by the Department’s own Defense Industrial Base Cybersecurity Assessment Center (DIBCAC).
How strict are the assessments?
Stricter than many suppliers expect.
- Limited plans of action. A Level 2 assessment can end in a conditional status only if at least 80% of the requirements are met and the open items are among those allowed on a plan of action and milestones (POA&M), which excludes the highest-weighted requirements, with narrow exceptions. Every open item must be closed, and verified in a closeout assessment, within 180 days, or the conditional status expires.
- Documented scope. The assessment covers every asset that processes, stores or transmits CUI, plus the security tools that protect them and other assets inside the boundary. Where CUI lives decides how large, and how costly, the assessment is.
- A system security plan. Assessors expect a current plan describing how each requirement is implemented in your environment, supported by evidence, not only by policies.
- Affirmations with consequences. A senior official affirms compliance after each assessment and every year. An inaccurate affirmation can expose the company to liability under the US False Claims Act.
How do requirements flow down to subcontractors?
Prime contractors must flow CMMC requirements down to subcontractors at every tier that will process, store or transmit FCI or CUI. A subcontractor needs the level that matches the information it handles, which can be lower than the prime’s: a supplier that receives only FCI needs Level 1, while a supplier that receives CUI generally needs Level 2, with the type of assessment set by the prime contract.
There is no exemption for suppliers outside the United States. A machine shop, avionics maker, engineering firm or software company in Canada that works on a US defence program receives the same clauses as a supplier in Virginia. The aerospace cluster in Montreal, with supply chains that run into US programs, is a clear example. The requirement itself usually comes from the Department of Defense and from prime contractors, many of which are headquartered around Washington, D.C.
Export-control rules such as ITAR apply separately, and often to the same technical data, so the two programs are best scoped together.
How should a supplier prepare?
- Confirm the level. Ask your prime or contracting officer which level upcoming solicitations will name, and whether Level 2 will be a self-assessment or a certification.
- Map the data. Find where FCI and CUI enter, where they are stored and who touches them. Many suppliers reduce scope by confining CUI to a dedicated enclave.
- Assess the gaps. Compare your environment against the 15 or 110 requirements and score it the way an assessor would. An independent security assessment gives you that baseline before you commit to a date.
- Remediate and document. Close the gaps, typically in multi-factor authentication, logging and monitoring, configuration management, incident response, media protection and FIPS-validated encryption for CUI, and write the system security plan as you go.
- Book the assessment early. For certification, choose a C3PAO well ahead of the bid; assessor availability can be a constraint, and the status must be in place at award.
- Keep it current. Annual affirmations, changes to the environment and new contracts all require the program to keep running after the assessment.
If a prime has asked about your CMMC status, or you expect CMMC clauses in your next bid, our compliance team can review where you stand in an exploratory meeting and propose a realistic path to the level your contracts require.
Questions we hear often
- Do Canadian companies need CMMC?
- Yes, when they handle Federal Contract Information or Controlled Unclassified Information under a US Department of Defense contract or subcontract. The requirement follows the contract, not the country. Canada is also developing its own Canadian Program for Cyber Security Certification for Canadian defence contracts. Unless a US contract says otherwise, plan for the CMMC level and assessment type that the contract names, and confirm with your prime.
- What is the difference between FCI and CUI?
- Federal Contract Information is information not intended for public release that is provided by or generated for the government under a contract, excluding information the government makes public and simple transactional information such as payment details. Controlled Unclassified Information is information that a law, regulation or government-wide policy requires or permits to be handled with safeguarding or dissemination controls. Export-controlled technical data is a common example of CUI.
- How long does a CMMC status last?
- Level 1 is renewed every year through a new self-assessment and affirmation. Level 2 and Level 3 statuses last three years, with an affirmation by a senior official every year in between. The status must stay current for the whole contract, including option periods, and a significant change to the assessed environment can call for a new assessment before the three years are up.
- Can we use cloud or managed service providers for CUI?
- Yes, with conditions. A cloud service that processes, stores or transmits CUI must meet the FedRAMP Moderate baseline or an equivalent standard. Other external service providers that perform security functions for you fall inside your assessment scope, and their responsibilities should be written in a shared responsibility matrix. Using a provider does not transfer your accountability for meeting the requirements.
- Can the firm that prepares us also certify us?
- No. A Level 2 certification assessment must be performed by a C3PAO authorized by the Cyber AB, the accreditation body for the program, using certified assessors, and conflict-of-interest rules prevent an assessor from certifying an organization it has recently advised. A preparation partner scopes the environment, closes gaps, writes the documentation and runs a mock assessment. The C3PAO then assesses you and issues the result.