The Canadian Program for Cyber Security Certification (CPCSC) is how the federal government verifies that defence suppliers protect sensitive unclassified contract information. As of November 14, 2026, Level 1, an annual self-assessment of 13 controls, is live and appears in select defence contracts, while Levels 2 and 3 are still being built, with phased introduction signalled from spring 2027 but no firm date. If you handle defence drawings, specifications or similar information, the practical move is to complete Level 1 now and start Level 2 groundwork, because scoping and remediation take months.
This article is general information. Requirements are set contract by contract, so always confirm against the solicitation. For a short definition, see What is CPCSC?.
What the CPCSC Is and Who Runs It
The CPCSC is a certification program for defence suppliers under the responsibility of Public Services and Procurement Canada (PSPC) and National Defence (BDC, 2026). The Standards Council of Canada, the Canadian Centre for Cyber Security and Treasury Board Secretariat also support the program (SAV Associates, 2026).
The technical standard behind it is ITSP.10.171, published by the Cyber Centre. It is a Canadian version of NIST SP 800-171 with "no substantial technical changes"; the differences reflect Canadian laws and policies (Canadian Centre for Cyber Security, 2025). Its requirements are organized into 17 families, from access control and incident response to supply chain risk management. The standard took effect on April 2, 2025, and its second release is dated October 28, 2025 (Canadian Centre for Cyber Security, 2025).
What Information It Protects
The program protects "specified information", which ITSP.10.171 defines as information, other than classified, that a Government of Canada authority identifies and qualifies in a contract as requiring safeguarding (Canadian Centre for Cyber Security, 2025). That can include non-public engineering drawings and test results, information on controlled goods, and Protected A, B or C information tied to the contract (BDC, 2026). The contract decides what counts. If it is unclear, ask the contracting authority rather than guess.
The Three CPCSC Levels
| Level | How it is verified | Scope of controls | Status as of November 14, 2026 |
|---|---|---|---|
| Level 1 | Annual self-assessment and attestation | 13 core controls | Available since April 1, 2026, and required in some defence contracts |
| Level 2 | External assessment by a certification body accredited by the Standards Council of Canada, plus annual confirmation | 98 controls, per PSPC figures reported by BDC | Under development |
| Level 3 | Assessment by National Defence, plus annual confirmation | Reserved for high-risk work such as weapon systems and information shared with Five Eyes partners | Under development |
Source: BDC, 2026. BDC notes that the Level 2 and 3 figures may change. Reported control counts for Level 3 already differ: BDC gives about 200, while an independent tracker reports that PSPC restated it as more than 130 in a September 29, 2026 revision (Hans Study, 2026). Treat Level 3 details as unsettled.
The required level is named in the solicitation and contract, and BDC notes that subcontractors that handle the information must also hold the appropriate certification (BDC, 2026).
Level 1: The 13 Controls
Level 1 is a self-assessment, not an audit. The supplier declares compliance on a federal government site, must be able to show proof that each control is in place, and records the result and expiry date in its CanadaBuys supplier profile. Where a contract requires Level 1, the self-assessment is needed at contract award, not during tendering (BDC, 2026).
The 13 controls, with their ITSP.10.171 identifiers (Pilotcore, 2026; identifiers confirmed against ITSP.10.171):
| ITSP.10.171 ID | Control | What it means in a small supplier |
|---|---|---|
| 03.01.01 | Account management | Every account is approved, named, reviewed and removed when people leave |
| 03.01.02 | Access enforcement | People only reach the files and systems their role needs (least privilege) |
| 03.01.20 | Use of external systems | Rules for personal devices, home computers and outside cloud services |
| 03.01.22 | Publicly accessible content | Nothing sensitive goes on the website or public file shares |
| 03.05.01 | User identification and authentication | Unique logins, no shared accounts |
| 03.05.02 | Device identification and authentication | Only known, managed devices connect |
| 03.05.03 | Multi-factor authentication | MFA on accounts that reach in-scope systems |
| 03.08.03 | Media sanitization | Drives and USB keys wiped or destroyed before disposal or reuse |
| 03.10.01 | Physical access authorizations | A list of who may enter areas holding in-scope systems |
| 03.10.07 | Physical access control | Locks, badges or sign-in for those areas |
| 03.13.01 | Boundary protection | A managed firewall and monitored internet edge |
| 03.14.01 | Flaw remediation | Patching on a defined schedule |
| 03.14.02 | Malicious code protection | Endpoint protection on in-scope devices |
Level 1 goes further than the U.S. baseline in one notable way: the 15 basic safeguarding requirements in U.S. federal acquisition clause FAR 52.204-21 do not include multi-factor authentication (Acquisition.gov, 2026), while CPCSC Level 1 does.
CPCSC Timeline as of November 14, 2026
Published timing has moved more than once, and we could not confirm the latest PSPC program pages directly while preparing this article. The table separates what is confirmed from what is reported.
| Date | Milestone | Confidence |
|---|---|---|
| April 2, 2025 | ITSP.10.171 takes effect (Canadian Centre for Cyber Security, 2025) | Confirmed, primary source |
| April 1, 2026 | Level 1 available to suppliers (BDC, 2026) | Confirmed by multiple sources |
| April 14, 2026 | Government formally introduces Level 1 (SAV Associates, 2026) | Reported by secondary sources |
| Summer 2026 | Level 1 becomes a condition of award in some defence contracts (BDC, 2026) | Confirmed by multiple sources |
| September 29, 2026 | PSPC program overview revised; Levels 2 and 3 described as under development with no date (Hans Study, 2026) | Reported by an independent tracker; low confidence |
| Spring 2027 to spring 2028 | Level 2 and Level 3 requirements gradually incorporated into select contracts (Pilotcore, 2026; Hans Study, 2026) | Planning assumption, not a confirmed date |
BDC's September 2026 summary still gives spring 2027 for Level 2 (BDC, 2026). Our view: plan for Level 2 clauses appearing in select contracts during 2027, and check the PSPC program overview and each CanadaBuys solicitation before committing budget to a specific date.
How CPCSC Relates to CMMC
The U.S. Cybersecurity Maturity Model Certification (CMMC) and CPCSC share a lineage, but they are separate programs.
- Same roots, different revisionsITSP.10.171 is a Canadian version of NIST SP 800-171 (Canadian Centre for Cyber Security, 2025). Canada's standard is derived from Revision 3, published in May 2024, while CMMC remains based on Revision 2 (BDC, 2026; NIST, 2024). CMMC Level 2 requires all 110 Revision 2 controls (Latham & Watkins, 2026), compared with the 98 reported for CPCSC Level 2.
- No automatic reciprocityA valid CMMC certification may be recognized by Canada case by case, after verifying scope and, if needed, specific controls (BDC, 2026).
- CMMC is itself in fluxThe U.S. defence acquisition rule that put CMMC requirements into contracts took effect on November 10, 2025, starting with Phase 1 self-assessments (Federal Register, 2025). On July 13, 2026, the U.S. Department of War suspended Phase 2, the third-party assessment phase that was due on November 10, 2026, while Phase 1 self-assessments remain in place (WilmerHale, 2026). A review task force has suggested Phase 2 could restart with a narrower population, but as of November 14, 2026 we found no announced restart date (Federal News Network, 2026).
If you sell to both governments, build one control environment and map it to both standards, but keep separate scoping, attestations and evidence for each program.
How to Prepare: A Plan for Suppliers of 10 to 500 People
Step 1: Confirm Whether It Applies
Read the security requirements in the contracts and solicitations you pursue. Ask whether you receive or create specified information, directly or as a subcontractor. If a prime passes you drawings, specifications or schedules for a defence program, assume CPCSC will reach you.
Step 2: Scope Tightly
Scope is everything that stores, processes or transmits specified information: people, locations and technology. It can be company-wide or a restricted enclave, and BDC notes that good scoping can significantly reduce complexity and cost (BDC, 2026). For example, a supplier might keep defence files in a dedicated Microsoft 365 site, accessed only from managed laptops used by one project team. Remember that cloud services and IT providers with access to that data are part of the picture.
Step 3: Complete Level 1 Now
Walk the 13 controls against your scoped environment, record each as met, partial or missing, close the gaps and keep evidence: screenshots, configuration exports, access lists, patch reports and sign-in logs. Then complete the self-assessment and record the result in CanadaBuys before a contract requires it. Set a renewal reminder, since it is annual.
Step 4: Run a Level 2 Gap Assessment Against ITSP.10.171
Level 2 covers all 17 families, including audit logging, configuration management, incident response, security awareness training and supply chain risk. Assess against the full standard, then rank gaps by effort and cost, and start with the ones that need new tooling or new processes, since those take longest. Ongoing vulnerability management supports several of these requirements at once.
Step 5: Document as You Go
Write a system security plan describing the scoped environment and how each requirement is met, and a plan of action for open gaps with owners and dates. Assessors test what is written against what is running, so documentation needs to match reality.
Step 6: Budget and Book Early
Level 2 costs have not been confirmed (BDC, 2026), and the pool of accredited certification bodies is still forming: PSPC has said the Standards Council of Canada will begin accepting certification body applications between April 2026 and March 2027, according to an independent tracker (Hans Study, 2026). Get indicative quotes once bodies are accredited, and plan remediation in the 2027 budget.
Step 7: Use What You Already Have
If you hold CyberSecure Canada certification or have implemented the Cyber Centre's baseline controls, you are likely to find much of Level 1 already covered. ISO 27001 and CMMC work also transfers, though the mapping needs checking control by control. Our guide on choosing a cyber security framework explains how these fit together.
What Remains Unconfirmed
As of November 14, 2026, we could not confirm a firm date for Level 2 or Level 3, the final Level 3 control count, or Level 2 assessment costs. We also could not read the PSPC program pages directly for this update and relied on the Business Development Bank of Canada and secondary trackers for the program's current wording. We will update this article when PSPC confirms dates.
How Cyberphore Can Help
Our compliance readiness team runs CPCSC scoping, Level 1 control reviews and ITSP.10.171 gap assessments, and helps assemble the evidence an assessor or contracting authority will ask for. Every team member holds industry certifications such as CISSP, CISM, OSCP or GIAC, and pricing is quoted in CAD after a free scoping call.



