Fast-Track · Weeks, Not Months

Bill C-26 / CCSPA Readiness Canada

Cyber Security Readiness for Canadian Critical Infrastructure under Bill C-26 / CCSPA

Praxis-Q prepares Canadian critical-infrastructure operators - telecom, finance, energy, transport - for the Critical Cyber Systems Protection Act (CCSPA) under Bill C-26: cyber security program design, incident reporting workflows and supply-chain risk controls aligned to expected regulatory direction.

At a Glance

Act

CCSPA / C-26

Penalty

to $15M

Reporting

Mandatory

Market

Canada

Canada's critical-infrastructure cybersecurity bill has a long history — it died on the order paper as Bill C-26 when Parliament prorogued in January 2025, was reintroduced as Bill C-8, and received Royal Assent on June 16, 2026. The Telecommunications Act amendments in Part 1 took effect immediately; the substantive Critical Cyber Systems Protection Act (CCSPA) obligations in Part 2 come into force in stages on dates to be fixed by order of the Governor in Council, with the designated operator classes, reporting thresholds, and detailed programme requirements still to be filled in by regulation. In practice this means the law is now real, but exactly who is in scope and exactly what the reporting deadline will be are not yet finalized. The CCSPA applies to 'designated operators' of critical cyber systems across six federally regulated sectors: telecommunications, interprovincial pipelines and power lines, nuclear energy, transportation, banking, and clearing and settlement systems. Once designated, an operator has 90 days to establish a cybersecurity programme covering risk identification (including supply-chain and third-party risk), protection of critical systems, incident detection, and impact minimization — the programme must be submitted to the relevant regulator, kept current, and reviewed at least annually.

Bill C-26 Canada

Bill C-26 / CCSPA Readiness Canada

Cyber Security Readiness for Canadian Critical Infrastructure under Bill C-26 / CCSPA

The Problem

Canada Bill C-26 (CCSPA) will compel critical-infrastructure operators to harden systems and report incidents on strict timelines, with penalties up to $15M. Most designated operators are not yet ready.

What We Do

  • Scoping
  • Program Design
  • Controls
  • Incident Reporting
  • Assurance

What You Get

  • Designation and scope assessment
  • Cyber Security Program (CSP) design
  • Mandatory incident reporting workflows
  • Supply-chain and third-party risk controls
  • Maps to NIST CSF and ISO 27001
  • Sector-regulator alignment (OSFI, CRTC)
  • Tabletop exercises and IR readiness
  • Board and executive reporting

Why weeks, not months

AI-assisted evidence review, one client portal

Every Bill C-26 Canada engagement runs on the Praxis-Q compliance platform. You upload evidence per control, AI scores it against the requirement, and your auditor reviews in the same workflow — from scoping through to the issued, publicly verifiable certificate.

AI evidence scoring

Every upload is scored against the control before an auditor sees it — gaps surface in minutes, not at the review meeting.

One client portal

Scoping, evidence, auditor queries and status live in one place. No email chains, no spreadsheet trackers.

Auditor sign-off

Praxis-Q auditors review inside the same workflow, so review rounds shrink and the certificate issues sooner.

Who is a 'designated operator' under the CCSPA

Schedule 2 of the Act lists the classes of operators in scope, and as of Royal Assent that schedule was still to be populated by regulation — meaning the exact list of covered entities within the six eligible sectors (telecom, pipelines/power lines, nuclear, transportation, banking, clearing/settlement) is still being finalized. Organisations in these sectors should assume designation is likely and start preparing rather than waiting for the final list.

The five required elements of a cybersecurity programme

The Act requires programmes addressing: identification and management of cyber risks including supply-chain and third-party risk; protection of critical cyber systems from compromise; detection of cybersecurity incidents; minimization of the impact of incidents; and any other matter prescribed by regulation. Programmes must be documented, submitted to the sector regulator, and reviewed annually at minimum.

72-hour incident reporting to the CSE

Operators must report cybersecurity incidents affecting critical systems to the Communications Security Establishment (CSE) within a timeframe expected not to exceed 72 hours, with the exact period to be set by regulation. The reporting threshold is broad — incidents that interfere or 'may interfere' with vital service continuity or system security must be reported, with the relevant regulator also notified.

Board and officer accountability

Directors and officers face personal liability for CCSPA violations they direct, authorize, assent to, acquiesce in, or participate in — independent of whether the corporation itself is prosecuted. A documented due-diligence defense exists, which makes board-level cyber governance and a well-evidenced compliance programme a direct legal protection, not just good practice.

Penalties and building the programme ahead of designation

Administrative monetary penalties reach up to $500,000 per violation for individuals and $15 million per violation for organisations (statutory maximums, with actual amounts to be set by regulation), plus criminal offences carrying up to five years' imprisonment for indictable offences. Given the phased coming-into-force and pending regulations, we help likely-designated operators build the cybersecurity programme, supply-chain risk process, and incident reporting workflow now, so the transition once regulations land is operational rather than a scramble.

Frequently Asked Questions

Who does Bill C-26 apply to?
Operators of vital services and systems in federally regulated sectors - telecommunications, finance, energy and transportation - designated under the Critical Cyber Systems Protection Act.
What are the penalties under Bill C-26?
Significant administrative monetary penalties - up to $15M for organizations - plus potential personal liability and enforceable directions from the regulator.
Is Bill C-26 in force yet?
It is advancing through Parliament with regulations expected to follow. Designated operators should build readiness now, as compliance timelines are expected to be tight once in force.
Is Bill C-8 in force yet?
Partially. The Telecommunications Act amendments (Part 1) took effect immediately on Royal Assent, June 16, 2026. The Critical Cyber Systems Protection Act obligations (Part 2) — the cybersecurity programme and incident reporting requirements — come into force on dates still to be fixed by order of the Governor in Council, with implementing regulations yet to be finalized.
Is this the same bill as Bill C-26?
Yes in substance — Bill C-26 died on the order paper when Parliament prorogued in January 2025 and was reintroduced as Bill C-8 in the new Parliament, carrying forward the same Critical Cyber Systems Protection Act framework.
How do we know if our organisation will be a 'designated operator'?
The designated operator classes are set out in Schedule 2 of the Act, which is populated by regulation rather than fixed in the legislation itself. Organisations in the six eligible sectors (telecom, pipelines/power lines, nuclear, transportation, banking, clearing/settlement) should monitor the regulatory process closely, since designation determines whether the Act's obligations apply.
What's the incident reporting deadline once we're designated?
The Act sets an outer limit expected not to exceed 72 hours to report a qualifying cybersecurity incident to the CSE, with the exact reporting period and format to be specified by regulation. The threshold for what counts as reportable is broad, covering incidents that interfere or may interfere with a vital service or system.
Does complying with ISO 27001 or SOC 2 already satisfy the CCSPA?
Those frameworks cover much of the same ground — risk management, incident detection, supply-chain risk — but the CCSPA has its own specific programme elements, submission-to-regulator requirement, and statutory reporting deadline that a generic ISO or SOC 2 programme won't automatically satisfy without being explicitly mapped to the Act's requirements.
What should we do now, given the regulations aren't finalized?
Build the cybersecurity programme, supply-chain risk assessment process, and incident detection/reporting workflow against the Act's five core elements now, using the CSE's existing guidance as a baseline. Waiting for final regulations before starting means a compressed timeline once your organisation is designated and the 90-day programme-establishment clock starts running.

Ready to Get Started?

Tell us the scope and an assessor replies within 24 hours.

Free gap analysis · Proposal in 24 hours · No obligation