Back to blog
CMMC

CPCSC Level 1: The Readiness Guide for Canadian Defence Suppliers

T

TEKAP Team

admin

23 octobre 2026
10 min de lecture
CPCSC Level 1: The Readiness Guide for Canadian Defence Suppliers

CPCSC is now a current requirement. Level 1 opened to suppliers on April 1, 2026, and has appeared in several National Defence solicitations since the summer. The next step is close: Level 2, which adds a third-party assessment, will be required for certain contracts starting in spring 2027.

This guide explains what Level 1 means in practice: the 13 controls, the attestation process, how Canada handles existing CMMC certifications, and a 90-day plan that also prepares you for Level 2. All information comes from Public Services and Procurement Canada (PSPC) guidance, last updated September 29, 2026, and the Canadian Centre for Cyber Security.

Where things stand in October 2026

Level 1 is now active. National Defence is including it in certain contracts. Requirements follow each contract's risk level, so not every defence contract is affected. Commercial off-the-shelf purchases, for example, may be exempt.

Level 2 is next. It will apply to certain contracts starting in spring 2027 and will require an assessment every three years by a certification body accredited by the Standards Council of Canada (SCC). An annual affirmation between assessments is expected. Details will be confirmed when PSPC releases its Level 2 guidance.

The scope is growing. PSPC has said sensitive non-defence contracts will also use this standard, depending on each contract's risk.

When Level 1 applies, PSPC makes it a legal requirement at contract award, not at bid. Suppliers must still record their attestation and its expiry date in their CanadaBuys profile and provide it when bidding on contracts that require Level 1. If you wait until award to start, you will be implementing controls while the contract decision is pending. The safest approach is to complete your attestation before the solicitation.

Who is in scope

CPCSC protects Specified Information (SI): sensitive, unclassified government information that a contract identifies as requiring protection when it sits in a supplier's systems. Three categories come up most often:

  • contract details not intended for public release, such as statements of work, pricing, schedules and technical drawings;
  • controlled goods information;
  • protected information.

If your systems store, process or transmit this kind of information under a defence contract, you are in scope. Subcontractors handling SI under a defence contract are included too, because the requirement follows the information, not the contract tier. That is why prime contractors will want to check your readiness.

The three CPCSC levels

Level 1 — Basic cyber hygiene

  • Requirements: 13 requirements from ITSP.10.171
  • Assessment: annual self-assessment, no external assessor
  • Timing: in select contracts since summer 2026

Level 2 — Advanced controls

  • Requirements: the full ITSP.10.171, about 98 requirements in 17 families
  • Assessment: SCC-accredited certification body every three years (annual affirmation expected)
  • Timing: in select contracts from spring 2027

Level 3 — Critical programs

  • Requirements: enhanced requirements beyond Level 2
  • Assessment: conducted by National Defence
  • Timing: phased rollout, after Level 2

The levels build on each other: the 13 Level 1 controls are part of Level 2. Work you do now still counts if a future contract requires Level 2.

The program is based on ITSP.10.171, the technical standard published by the Canadian Centre for Cyber Security. It uses the same baseline as NIST SP 800-171, which is also the foundation of the US CMMC program. That matters for suppliers working on both sides of the border.

The 13 Level 1 controls, in plain language

PSPC groups the 13 requirements into six cyber hygiene practices. Use this list as a self-audit: any control you cannot document today is a gap to close before your next bid.

Access control: who can reach your systems

  1. Manage user accounts. Keep a full inventory of accounts and what they can access. Create accounts at hiring, disable them at departure or role change, and review the list at least quarterly. Do not use shared or generic accounts.
  2. Grant only the access people need. Assign access by role group, limit admin rights to those who actually require them, and review shared-drive permissions regularly.
  3. Use only approved systems and devices. Keep a one-page list of systems approved for Specified Information. No personal email, personal cloud storage or personal devices for government work. Ask your cloud vendors where data is hosted and which foreign jurisdictions can access it. If your contract involves Protected B information, expect its security clauses to require storage in Canada.
  4. Keep sensitive information off public channels. One person reviews website updates, releases and social media posts before publication to make sure they contain no SI, client names or confidential technical details.

Identification and authentication: who uses your systems

  1. Individual accounts and strong passwords. Every user has their own credentials, passwords meet strength rules, and screens lock after inactivity (PSPC recommends 15 minutes on laptops and 5 on phones).
  2. Approve devices before they connect. Keep an inventory of approved devices (owner, model, approval date) and block everything else, including on company Wi-Fi and USB ports.
  3. Enable MFA. Level 1 requires multi-factor authentication on privileged accounts and on systems that store SI. An authenticator app is preferred, with a recovery process planned for lost devices.

Media protection: retiring storage the right way

  1. Wipe or destroy old devices. Drives, printers, USB keys and phones are wiped with software that makes recovery impossible, or physically destroyed. A disposal log records what, when, how and where.

Physical protection: premises and equipment

  1. Track who can enter secure areas. Know who holds keys, badges or codes for areas containing SI. Access ends at departure or role change, and temporary access has an expiry date.
  2. Control physical entry. Use locks, keycards, visitor logs and escorts wherever SI is present. Printed SI goes in locked cabinets, not the printer tray.

System and communications protection: networks

  1. Basic network protections. A firewall controls traffic, unwanted inbound connections are blocked, and public-facing systems are kept separate from internal ones. Changes are logged.

System and information integrity: threats

  1. Apply security updates. Turn on automatic updates, apply critical patches promptly, and log major updates on key systems.
  2. Run antivirus and anti-malware. Use real-time protection with current definitions on workstations and servers, and keep a record of incidents and how they were resolved.

You do not need a formal security program or major purchases to meet these controls. PSPC is clear that a few pages of short written rules, shared with staff and backed by evidence, are enough for Level 1.

How to attest

  1. Scope it. List where Government of Canada information is stored, which systems, devices and people access it, and which cloud services hold it. PSPC's Level 1 scoping guide walks through this step by step.
  2. Complete the self-assessment. The Cyber Centre's online tool shows your status against the 13 controls. PSPC estimates a prepared organization can finish it in under an hour. The tool is recommended but not required. It ends with a results page and an expiry date: save it, because keeping it is your responsibility.
  3. Record it in CanadaBuys. Enter the attestation and its expiry date in your organization's supplier profile, then use it when bidding on contracts that require Level 1. Repeat every year.

Keep your evidence. The attestation is made in good faith and it binds your organization. PSPC asks suppliers to keep evidence for the attestation cycle, or at least one year: account and device lists, access review notes, policies, training records, patch and disposal logs, visitor logs, firewall settings and MFA configuration screenshots. The contract technical authority or your prime contractor may ask to see them.

Already CMMC certified?

CPCSC and CMMC use the same technical controls, and PSPC says suppliers should not have to meet two separate standards. A valid CMMC certification is one way to meet Level 1. Canada accepts it case by case after confirming the assessment covers the required scope, and may still check specific controls through the contract technical authority. Proof is sent to PSPC's Cyber Security Program by email.

Three common situations:

  • You sell only to DND. Attest at Level 1, and assess your gap to Level 2 if your contracts involve a large volume of SI.
  • You sell to DND and the US Department of Defense. Run both as one program: build the documentation once, present it twice.
  • You are already CMMC certified. Submit it to PSPC and confirm scope coverage before assuming equivalence.

Your 90-day plan: October to January

Days 1–30 (to mid-November): map. Trace where SI enters, moves through and rests in your systems, including at cloud vendors. Inventory accounts, devices and physical access. Rate each of the 13 controls as met, partial or missing. A poorly defined scope puts controls in the wrong place.

Days 31–60 (to mid-December): close the gaps. Work in order of impact. MFA on privileged accounts, disabling orphaned accounts and blocking unapproved devices take days, not months. Write the short policies Level 1 expects: passwords, approved systems, granting access, device approval and media destruction.

Days 61–90 (to mid-January): prove and attest. Assemble the evidence file, complete the self-assessment, save the results page and record the attestation in CanadaBuys. Schedule the quarterly account review and the annual renewal.

Looking ahead: if your contracts involve a lot of SI, use the time before spring 2027 to measure your gap against the full Level 2 requirements. Organizing your Level 1 evidence so it also serves Level 2 saves you from doing the work twice.

Quebec suppliers: you don't need to start from scratch. Companies registered in Quebec can join the Communauté de pratique Défense, a Cybereco initiative partly funded by Quebec's Ministère de l'Économie, de l'Innovation et de l'Énergie. Its diagnostic helps you determine whether you are in scope (days 1–30). Its templates align with NIST SP 800-171 and ITSP.10.171, so you can adapt your policies in days 31–60 instead of writing them from scratch. Forums and workshops connect you with other companies working on the same requirements. The community provides tools and support but does not assess or certify: the attestation remains yours.

A small business with a simple setup can complete this 90-day plan in-house. Outside help is most useful in complex environments: multiple sites, hybrid cloud, layered subcontracting, or preparation for Level 2.

Frequently asked questions

What's the difference between CPCSC and CMMC? CPCSC is Canada's program for Government of Canada contracts; CMMC is the US program for Department of Defense contracts. Both protect sensitive unclassified information and are based on NIST SP 800-171, which Canada adapted as ITSP.10.171.

Does every DND contract require Level 1? No. Requirements depend on each contract's risk level. Some contracts, such as commercial off-the-shelf purchases, may not require certification at all.

We're a subcontractor. Are we in scope? Yes, if you handle Specified Information under a defence contract. The obligation follows the information, not the contract tier.

How much does Level 1 cost? The self-assessment and online tool are free. The real cost is closing gaps, which for most small and mid-sized suppliers means internal hours and configuration changes rather than purchases.

Do we need the attestation to bid? It is formally required at contract award, but PSPC also asks for it in your CanadaBuys profile and when you bid on a contract that requires Level 1. Have it in hand before the solicitation comes out.

How long do we keep the evidence? For your attestation cycle, or at least one year.

What's in Level 2? The full ITSP.10.171 standard, about 98 requirements across 17 families, assessed every three years by an SCC-accredited body, with an annual affirmation expected. It applies to select contracts from spring 2027. The 13 Level 1 controls are part of it.

From reading to attestation

Level 1 solicitations are already out. Suppliers that cannot demonstrate the 13 controls may not be ready when a contract requiring CPCSC attestation comes up.

TEKAP supports defence suppliers in Quebec and across Canada with CPCSC and CMMC advisory, in French and English: scoping Specified Information, gap analysis against the 13 controls, implementation, evidence files, attestation and Level 2 gap assessment. The gap analysis gives you a clear picture of where you stand and a prioritized list of actions.

Book your CPCSC gap analysis →

Sources

Need Expertise in Cybersecurity?

Our team of experts can help you implement the best practices discussed in this article. Contact us for a personalized consultation.

Contact Our Experts