
By Krikor Tengerian · Co-founder, SecuritAI Technologies Ltd. · November 2026 · 8 min read
You spent a year getting ready for the American program. Now a Canadian contract names a second one, and someone on your team asks the obvious question: do we have to do all of this again?
Most suppliers who sell into both countries reach CPCSC and CMMC in that order of worry. The short answer from Ottawa is encouraging. The longer answer has conditions, and the conditions are where the work is.
This post covers what the two programs share, where they differ on paper, and what Canada has actually said about accepting an American certification. For the Canadian program itself, levels and timelines, start with our CPCSC compliance page.
Public Services and Procurement Canada addresses this directly. Its Level 1 requirements page says the Canadian program aligns with the requirements of the United States Cybersecurity Maturity Model Certification but does not duplicate the American certification system. It adds that both countries use the same technical controls, so suppliers do not need to meet two separate standards.
The same page lists two ways to meet the Level 1 requirement: complete an annual cyber security self assessment, or hold an existing valid CMMC certification.
Then come the conditions. The Government of Canada may accept a contractor's valid CMMC certification on a case by case basis, after confirming that the assessment covers the required scope. Canada reserves the right to verify compliance with specific CMMC controls when necessary, and the page says any verification would be carried out by the contract technical authority. It also gives an address where proof of certification can be sent for verification and assessment.
Suppliers read "same technical controls" and hear "automatic."
That is not what the page says. The words are "may accept" and "case by case," and the test is whether your American assessment covers the scope the Canadian contract requires. A certificate that covers one business unit, one enclave or one set of systems does not answer for systems it never looked at.
So the certificate is the start of the conversation with Canada. What decides it is the scope behind the certificate, and whether you can show that scope on paper.
PSPC's additional information page for suppliers gives the instruction in one line. Defense suppliers should review the ITSP.10.171 standard and contact the program if they are certified under the American one.
Both come from the same family of documents published by the National Institute of Standards and Technology.
On the Canadian side, the standard is ITSP.10.171 from the Canadian Centre for Cyber Security. It describes itself as a Canadian version of NIST SP 800-171 and says there are no substantial technical changes between the two. The differences it names come from Canadian laws, policies and directives.
On the American side, the program is set out in federal regulation at 32 CFR Part 170. That rule says the Level 2 security requirements are identical to the requirements in NIST SP 800-171 Revision 2.
Same family, same subject: protecting sensitive government information that is not classified when it sits on a contractor's systems. Canada calls it specified information. The American documents call it controlled unclassified information. Our post on specified information explains the Canadian term.
Three differences are worth knowing before you assume one maps cleanly onto the other.
The counts are different. The PSPC program overview sets Level 1 at 13 controls, Level 2 at 98 controls and Level 3 at 130 or more. The American regulation defines its security requirements as 15 at Level 1, taken from a federal acquisition clause, 110 at Level 2 from NIST SP 800-171 Revision 2, and 24 at Level 3 selected from NIST SP 800-172.
The revision is different too. The American rule incorporates Revision 2 of the NIST document. ITSP.10.171 keeps the numbering of Revision 3, and it says so: controls that were withdrawn in Revision 3 are labeled "not allocated" to keep the same numbering for interoperability. A control list written against one revision does not line up row for row with the other.
And the assessor is different. In Canada, Level 1 is an annual self assessment, Level 2 is assessed by an accredited certification body, and Level 3 is assessed by National Defence, according to the program overview. Under the American rule, Level 1 is also a self assessment done every year, and a Level 2 certification assessment comes from an assessment organization that the rule calls a C3PAO.
None of this contradicts what PSPC says about shared technical controls. It means the two programs count and number the same body of work differently, and that is exactly why Canada confirms scope before it accepts a certificate.
The Canadian Level 1 scoping guide speaks to suppliers who already know the American approach. It notes that some readers may be familiar with the CMMC Level 1 scoping guidance, and that there may be differences between other countries' requirements and what is expected under CPCSC.
It then lists what you should be ready to share when you declare Level 1 in Canada: a scoping rationale, a simple network diagram, a list of in scope assets, a list of out of scope and specialized assets, the facilities and storage points, proof of security tasks, a list of employees who access the information with their roles, and notes on external systems and remote access.
If you built that package for an American assessment, most of it exists. Check that it describes the systems that will handle Canadian specified information, not only the ones that handle American data.
A practical order of work:
The Canadian pages describe what Canada may accept. They say nothing about what the United States accepts, and this post will not guess. If an American contract requires CMMC, the requirement and the route to meet it are set by that contract and the American rule.
What does carry over is the work itself. The controls come from the same family, so the accounts you reviewed, the devices you listed and the access you restricted are the same facts under either program.
Here is the pattern our team sees with suppliers who work in both countries. They did the work once, for one program, and the proof is scattered. The assessment report is in one inbox, the scope diagram on one laptop and the policy in a shared drive nobody has opened since.
Then the second program asks a simple question: does your assessment cover this scope? Answering is slow, because nobody can put the scope, the controls and the dates on one page.
Recognition between the two programs depends on that page. A supplier who can show what was assessed, when, and which systems it covered is in a position to ask Canada for acceptance. A supplier who cannot is likely to end up doing the work twice.
SecuritComply carries the CPCSC control set, with each requirement tied to the evidence behind it, an owner and a review date. The platform keeps that evidence in one place, so it is ready when a contracting authority or a prime contractor asks. Certification at Level 2 is issued by a certification body accredited by the Standards Council of Canada. Your compliance data stays in Canada.
Built to save your team time and money: every control is tied to its evidence, so your Level 1 self assessment takes less of your time, and at Level 2 you go into the assessment with your evidence already in order.
To see where you stand against the 13 Level 1 controls, run the free self assessment on our CPCSC Level 1 tool, or book a free CPCSC Level 1 Gap Review with our team on the CPCSC compliance page. If you would rather start on paper, the free CPCSC Level 1 Readiness Checklist is on our resources page.
Does Canada accept CMMC in place of CPCSC?
It may. Public Services and Procurement Canada says the Government of Canada may accept a contractor's valid CMMC certification on a case by case basis, after confirming that the assessment covers the required scope.
Are CPCSC and CMMC the same standard?
They come from the same NIST family. PSPC says both countries use the same technical controls. The Canadian standard is ITSP.10.171, a Canadian version of NIST SP 800-171, and the American rule ties its Level 2 requirements to NIST SP 800-171 Revision 2.
How many controls are in each program?
Canada sets 13 controls at Level 1, 98 at Level 2 and 130 or more at Level 3, according to the PSPC program overview. The American regulation at 32 CFR Part 170 defines 15 requirements at Level 1, 110 at Level 2 and 24 at Level 3.
Who verifies a CMMC certification for a Canadian contract?
PSPC says any verification would be carried out by the contract technical authority, and that Canada reserves the right to verify compliance with specific CMMC controls when necessary.
What should I do first if I am already CMMC certified?
Review ITSP.10.171 and contact the Canadian program. That is the instruction on PSPC's additional information page for suppliers.
SecuritComply makes it simple: 17 frameworks and Canadian data residency.
Start Free →