Skip to content
FortaRisks
Back to blogCompliance

CMMC: for a Canadian supplier, a commercial requirement before a regulatory one

November 5, 2026 · 7 min read

Our position · compliance and defence

Take a typical case: a machine shop in Quebec makes parts for a subcontractor of a large US prime contractor. It has never signed a contract with the Pentagon. Yet one morning, the email arrives: "Please confirm your CMMC status and your SPRS score before the order is renewed."

Our position: for a Canadian supplier, CMMC is already a commercial requirement, before it is a regulatory one. It is not Washington that sets it, it is the customer. And the suspension of phase II, announced in July, does not change that: it moves a date, not an obligation. It is a position, not a certainty: depending on your customer and the kind of information you receive, the requirement may stay theoretical for a few more years. But that is rarely your call.

What CMMC is, on one page

The US Department of Defense's Cybersecurity Maturity Model Certification (CMMC) programme verifies that a supplier protects two kinds of information it receives under a contract:

  • Federal contract information (FCI): non-public information provided by or generated for the government under a contract.
  • Controlled unclassified information (CUI): a more sensitive category, such as technical drawings, specifications or export-controlled data.

Three levels, set by the programme rule (32 CFR part 170, in force since 16 December 2024). Status: confirmed by the Federal Register.

  • Level 1: 15 basic security requirements for FCI, from FAR clause 52.204-21, with an annual self-assessment.
  • Level 2: the 110 requirements of NIST SP 800-171 revision 2 for CUI, with either a self-assessment or an assessment by an accredited third party (C3PAO), depending on the contract.
  • Level 3: additional requirements drawn from NIST SP 800-172, assessed by the government, for the most sensitive programmes.

CMMC invents almost nothing. Since 2017, DFARS clause 252.204-7012 has required any supplier handling CUI to implement NIST SP 800-171 and to report an incident within 72 hours. CMMC adds what was missing: verification.

The timeline: one phase in force, one suspended

  • Phase I, since 10 November 2025. The acquisition rule (48 CFR, DFARS clause 252.204-7021) came into force that day. Level 1 and Level 2 self-assessments can be required as a condition of contract award. The rule phases in over three years: from 10 November 2028, the CMMC requirement will appear in every contract where the supplier processes FCI or CUI. Status: confirmed by the Federal Register.
  • Phase II, planned for 10 November 2026, suspended. It was meant to make third-party assessment the norm for Level 2. On 13 July 2026, the department suspended it, along with phases III and IV, and set up a task force to review the programme within 60 days. According to the law firms following the file (Morgan Lewis, WilmerHale, DLA Piper), phase I remains fully in force. Status: reported.
  • The stated reason. According to the same sources, the department's chief information officer pointed to a bottleneck: more than 100,000 companies to assess for about a hundred accredited assessors. Status: reported.
  • At the time of writing, the task force's recommendations, delivered around mid-September according to industry observers, have not been published, and no new phase II date has been announced. Status: reported; check the department's CMMC page before any decision.

Why a suspension is not an exemption

The underlying obligation has not moved. DFARS clause 252.204-7012 still applies to every contract that touches CUI. What is suspended is the arrival of third-party assessment, not the obligation to implement the 110 requirements.

A self-assessment is a commitment. A score posted in the Supplier Performance Risk System (SPRS) is an attestation made to the US government. The Department of Justice pursues false cybersecurity claims under the False Claims Act. In 2022, Aerojet Rocketdyne agreed to pay US$9 million to resolve allegations that it failed to meet its cybersecurity obligations; in 2025, MORSECORP agreed to pay US$4.6 million, in part over an SPRS score that did not reflect the real state of its controls. Status: confirmed by the Department of Justice. A foreign supplier is not out of reach once it signs an attestation in the chain.

Primes are not waiting. A large integrator answerable for a chain of hundreds of suppliers will not take the risk of waiting for the new date. It flows the requirement down by contract, asks for the SPRS score, sometimes for evidence. That is how CMMC reaches Canada: through the purchase order, not through the law.

The link with Canada's CPCSC

Canada has its own programme: the Canadian Program for Cyber Security Certification (CPCSC), required in select defence contracts from summer 2026. We covered it in our Level 1 guide and in our piece on Canada's regulatory acceleration.

Three facts that matter to a supplier working on both sides of the border. Status: confirmed by Public Services and Procurement Canada.

  • The same controls. According to the government, the Canadian standard is technically identical to the 172 controls of NIST SP 800-171 and 800-172 that underpin CMMC.
  • Three comparable levels. Level 1: an annual self-assessment of 13 requirements. Level 2: an external assessment every three years by an accredited certification body. Level 3: an assessment every three years by National Defence. The Level 2 timeline is not published yet; some law firms point to spring 2027 (reported).
  • Case-by-case recognition. Canada may accept a valid CMMC status, case by case, after confirming that the assessment covers the required scope, and reserves the right to verify specific controls.

What it changes: there are not two programmes to run, there is one set of controls to demonstrate twice, with different evidence. A supplier that builds its NIST SP 800-171 once serves its US and Canadian customers with the same work.

The method: five steps, without waiting for a date

  1. Scope the CUI. Which information received from your customers is marked CUI, or should be? Where does it come in, where is it stored, who can access it? A narrow scope is the most profitable decision: a well-bounded enclave costs less than the whole company.
  2. Measure the gap against the 110 requirements. A control-by-control gap analysis, with the expected evidence for each, not a general impression.
  3. Compute the SPRS score honestly. The department's assessment methodology starts at 110 and subtracts 1 to 5 points per unmet requirement. A negative score is not a fault; an inflated score is.
  4. Write the plan of action (POA&M). Each unmet requirement gets an owner, a date and a budget. For a conditional status, the rule only allows some requirements to be deferred, and for 180 days only.
  5. Keep the evidence current. Logs, configurations, signed procedures, access reviews. A control without evidence does not exist on assessment day, and a control proven once may no longer work the day after.

What an executive should ask this week

  1. Do we receive, directly or through a customer, information that falls under CMMC or the CPCSC?
  2. If a prime asked for our SPRS score tomorrow, what number would we give, and who would sign it?
  3. Does our set of controls serve both programmes, or are we preparing two separate files?

What do you think?

Our position: CMMC is already in Canada, through contracts, and the phase II suspension is time to use rather than a reason to wait. Too heavy for a 40-person shop? Maybe, if the scope is not bounded. Tell us in the comments whether a customer has already asked for your CMMC status, and what you answered.

FortaRisks' Compliance module maps your controls once to 40+ frameworks, including NIST SP 800-171 and the CPCSC's ITSP.10.171, built on the 1,534+ SCF controls, with the gap and the evidence per requirement. Our free CPCSC Level 1 assessment shows your starting point, and thirty minutes with an expert is enough to scope your perimeter.

Sources: Federal Register, CMMC programme rule, 32 CFR part 170 (15 Oct. 2024) · Federal Register, CMMC acquisition rule, 48 CFR (10 Sept. 2025) · NIST, SP 800-171 revision 2 · Acquisition.gov, DFARS clause 252.204-7012 · US Department of Justice, Aerojet Rocketdyne settlement (2022) · US Department of Justice, MORSECORP settlement (2025) · Public Services and Procurement Canada, CPCSC Level 1 backgrounder. Monitoring, named in the text: Morgan Lewis, WilmerHale, DLA Piper on the phase II suspension.

Where do you stand?

Measure your gap in five minutes, free

Reading about a framework is one thing, knowing where you stand is another. Our self-assessments give you a score per domain and the gaps to close first: Law 25, NIS2, DORA, SOC 2, CPCSC.