CPCSC Certification Support (Canadian Program for Cyber Security Certification)
To bid on Defence contracts, cybersecurity must be proven. We get you ready.
Level 1 (self-assessment) or Level 2 (third-party certification) — we help you choose, then take you to ITSP.10.171 compliance.
Who is it for?
Canadian suppliers bidding or planning to bid on National Defence contracts where CPCSC has become — or will become — an eligibility condition.
Tier-one subcontractors handling or hosting Controlled Unclassified Information (CUI/RNC) on federal contracts and required to demonstrate protection of that data in their own systems.
Canadian companies already engaged in the US Defence supply chain (CMMC, NIST SP 800-171) wanting to leverage that work for CPCSC — both frameworks are aligned.
Technology, engineering, professional services, and manufacturing suppliers discovering their next contract with DND, PSPC, or a major defence integrator will require CPCSC certification.
Organizations that received a Level 1 self-assessment request under the PSPC pilot program and want to complete it correctly rather than under pressure.
Canadian SMEs aiming to expand into Canadian or allied defence contracts and wanting to start by building the cyber foundation.
When does it help?
- A recent Defence or PSPC bid mentions CPCSC as an eligibility condition — and you're not certified.
- You're a subcontractor to a major defence integrator who passed down their own ITSP.10.171 requirements, and you don't know where to start.
- You're hesitating between Level 1 (self-assessment, faster, sufficient for some contracts) and Level 2 (third-party certification, required for sensitive contracts) — and you want an outside perspective to decide before investing.
- You already operate under NIST SP 800-171 for US contracts and want to know what CPCSC adds (answer: structure is very close, but the Canadian accreditation ecosystem is distinct).
- You're already certified CMMC Level 2 on the US side and want to leverage that work for CPCSC Level 2 — technically possible and significantly faster.
- You read ITSP.10.171 (97 controls across 17 families) and realize the gap between your current posture and the standard requires a structured approach, not a checklist.
- You confuse CPCSC with CAN/DGSI 104 (CyberSecure Canada) — two distinct Canadian programs with different audiences and requirements.
- Your board or commercial leadership wants to know what defence market access costs in money and time.
What will you receive?
A clear Level 1 or Level 2 recommendation, justified by the contracts you actually target, the type of information handled, and contractual requirements imposed by your defence clients — not by commercial preference.
A complete gap analysis between your current posture and the 97 controls of ITSP.10.171 across 17 families (access control, awareness and training, audit and accountability, configuration management, identification and authentication, incident response, maintenance, media protection, personnel security, physical protection, planning, risk assessment, security assessment, system and communications protection, system and information integrity, system and services acquisition, supply chain risk management).
A realistic estimate of timeline, total cost (Factero fees + assessment body fees for Level 2 + technical investments) and burden on your internal teams.
The policies, procedures, and records required by the standard, drafted and adapted to your reality — not a batch of generic NIST templates hastily translated.
Implementation of missing technical controls with your IT teams or MSP: standard-compliant MFA, FIPS-validated encryption where applicable, logging, privileged access management, configuration management, etc.
The System Security Plan (SSP) — central document of ITSP.10.171 compliance, equivalent to the CMMC SSP — describing scope, controls in place, responsibilities.
The Plan of Action and Milestones (POA&M) documenting acceptable residual gaps and their remediation timeline.
For Level 1: a self-assessment file ready to submit to PSPC, with the necessary evidence.
For Level 2: complete support during certification by the SCC-accredited assessment body: team preparation, question translation, management of any non-conformities.
A maintenance plan over the certification validity period: tracking program changes, recertification preparation, adjustments if your scope evolves.
Not a good fit?
- CPCSC is a demanding engagement — the ITSP.10.171 standard counts 97 technical controls several of which require significant investment (FIPS encryption, configuration management, monitoring, privileged access management). It requires an internal owner (typically the CTO, security lead, or dedicated compliance lead) with a mandate to mobilize IT and operational teams. Without that anchor, even the best external support can't carry through.
- If you have no active or planned defence contract, CPCSC is likely premature. CAN/DGSI 104 (CyberSecure Canada) is a general cybersecurity certification for Canadian SMEs, with proportional effort and significantly lower cost — often a better starting point.
- If you operate only in the US for US defence contracts, CMMC applies, not CPCSC. The two frameworks are technically very close, but accreditation ecosystems and authorities differ.
- If your actual exposure to controlled information (CUI/RNC) is very limited — for example a non-technical service provider with no access to contract data — CPCSC may be disproportionate. We clarify at the discovery call whether certification is actually required for your situation.
- If your current cyber maturity is very low (no MFA deployed, no configuration management, no centralized logging), aiming for CPCSC Level 2 certification in the next 12 months will create more stress than value. We'll propose a phased plan: foundations first, certification later.