Canada now has a federal law that will force banks, telecoms, pipelines, nuclear operators and federally regulated transport to run a cyber security programme and report incidents within 72 hours, but the core of it is not yet in force. Bill C-8, An Act respecting cyber security, amending the Telecommunications Act and making consequential amendments to other Acts, received Royal Assent on 15 June 2026 as Statutes of Canada 2026, chapter 9. Part 1 gives the government powers to secure the telecommunications system, and Part 2 enacts the Critical Cyber Systems Protection Act (CCSPA), which waits for an order of the Governor in Council and for regulations that will name the classes of designated operators. This guide explains who will be covered, the CCSPA duties section by section, the telecom order powers, penalties including director liability, and how to prepare before commencement. It is for CISOs, risk and compliance leads and legal teams in federally regulated Canadian sectors and at their suppliers.
Status checked 27 October 2026. Royal Assent 15 June 2026. On the Justice Laws website (current to 30 September 2026), Part 2 (the CCSPA) and Schedules 1 and 2 are marked "not in force"; they come into force on a day or days fixed by order of the Governor in Council (section 16 of the Act). Schedule 2, which will list the classes of operators and their regulators, has no entries yet. Part 1 (Telecommunications Act amendments) is not marked as pending. This page is not legal advice; confirm commencement and regulations before acting on dates.
Key takeaways
- It is law, but the CCSPA is waiting: Royal Assent came on 15 June 2026; the CCSPA starts only when the Governor in Council fixes a date and populates Schedule 2.
- Six vital services: telecommunications, interprovincial or international pipelines and power lines, nuclear energy, federally regulated transportation, banking, and clearing and settlement systems.
- Programme in 90 days, incident report within 72 hours: designated operators must establish a cyber security programme within 90 days of becoming a member of a class and report incidents to the Communications Security Establishment within a prescribed period of no more than 72 hours.
- Supply chain is explicit: the programme must manage supply chain and third-party product and service risks, and identified risks must be mitigated as soon as they are identified.
- Directors can be named: a director or officer who directed, authorised, assented to, acquiesced in or participated in a violation is party to it, with administrative penalties of up to CAD 500,000 for individuals and CAD 15 million for others per violation, per day.
Scope: who and what is covered
The CCSPA works in three layers: vital services and systems (Schedule 1), classes of operators with their regulators (Schedule 2), and the operator's own "critical cyber systems" supporting those services.
| Schedule 1 vital service or system | Likely federal regulator named in the Act |
|---|---|
| Telecommunications services | Minister of Industry |
| Interprovincial or international pipeline and power line systems | Canadian Energy Regulator |
| Nuclear energy systems | Canadian Nuclear Safety Commission |
| Transportation systems within the legislative authority of Parliament | Minister of Transport |
| Banking systems | Superintendent of Financial Institutions |
| Clearing and settlement systems | Bank of Canada |
The Act names these six regulators in its definitions; which class of operator each one supervises will be set when Schedule 2 is filled in by order. Treat the pairing above as indicative.
- Adding services: the Governor in Council may add a service or system to Schedule 1 by order if it is vital to national security or public safety (section 6).
- Designated operators: classes of operators are added to Schedule 2 by order (section 7). An operator in a listed class that owns, controls or operates a critical cyber system must comply (section 8).
- Who is not directly covered: provincially regulated sectors such as most electricity distribution, water and hospitals are outside federal reach unless they fall in a federal class. Suppliers are reached indirectly through the operator's supply chain duties.
- Privacy: privacy law still applies in parallel. See the Canada PIPEDA and Bill C-27 Guide.
Key obligations
Critical Cyber Systems Protection Act (Part 2)
| Section | Duty | Deadline |
|---|---|---|
| 9(1) | Establish a cyber security programme that identifies and manages organisational cyber risks including supply chain and third-party products and services, protects critical cyber systems, detects incidents, minimises their impact, and meets any prescribed requirement | Within 90 days after becoming a member of a class |
| 9(2), 10 | Notify the appropriate regulator in writing that the programme is established, then provide the programme | Immediately after establishment; programme within 90 days |
| 11 | Request an extension from the regulator in writing | Before the deadline |
| 12 | Implement and maintain the programme | Continuous |
| 13 | Review the programme and amend it where needed; notify the regulator whether changes were made | Start each prescribed date or anniversary; complete within 60 days; notify within 30 days |
| 14 | Notify material changes in ownership or control, supply chain or use of third parties, and report resulting programme changes | Changes notified; programme changes within 90 days |
| 15 | Mitigate identified supply chain and third-party risks; CSE may issue guidelines (15.1) | As soon as identified |
| 17, 18 | Report a cyber security incident to the Communications Security Establishment, then notify the regulator with a copy | Prescribed period of no more than 72 hours; regulator immediately after |
| 20 to 25 | Comply with cyber security directions from the Governor in Council and keep them confidential | As set in the direction |
| 30 | Keep records of programme steps, incidents, supply chain mitigation and directions, in Canada | Continuous |
- Limits on directions: a direction may not require decoding of encrypted private communications or interception of private communications (sections 20(1.1) and 20(6)). The Governor in Council must consider operational, privacy, financial and service impacts (20(3)), and the Minister must notify the national security review bodies NSICOP and NSIRA within 90 days (20(5)).
- Confidential information: disclosure of confidential information is restricted, with sharing governed by sections 23 and 26 to 29.
Telecommunications Act amendments (Part 1)
- New policy objective: "to promote the security of the Canadian telecommunications system" is added to section 7.
- Governor in Council orders (new section 15.1): can prohibit a provider from using products or services from a specified person or require their removal, where necessary and reasonable given the threat. Orders may carry non-disclosure provisions and prevail over conflicting CRTC decisions.
- Minister's orders (new section 15.2): can prohibit or set conditions on services and products, require removal, terminate agreements, and require security plans, reviews and standards.
- Penalties (new section 72.131): administrative penalties of up to CAD 25,000 for an individual (CAD 50,000 for a subsequent violation) and up to CAD 10 million for others (CAD 15 million for a subsequent violation), each day a separate violation.
Timeline and current status
| Date | Event |
|---|---|
| 18 June 2025 | First reading in the House of Commons (45th Parliament, 1st session) |
| 3 October 2025 | Second reading agreed; referred to committee |
| October 2025 to January 2026 | House committee study, with amendments |
| 26 March 2026 | Third reading motion in the House |
| June 2026 | Passed by the Senate |
| 15 June 2026 | Royal Assent: S.C. 2026, c. 9 |
| To be fixed by order | Commencement of Part 2 (CCSPA), Schedules 1 and 2, followed by regulations designating classes and setting the reporting period |
| Five years | Part 3 requires a parliamentary review of the Act |
Bill C-8 revives the approach of Bill C-26, which died on the order paper when the previous Parliament was dissolved. Amendments in committee, as reported in debate summaries, added privacy considerations, protections for encrypted communications and the mandatory review; verify specific amendments against the enacted text.
Enforcement and penalties
| Feature | CCSPA (Part 2) |
|---|---|
| Maximum administrative monetary penalty | CAD 500,000 for an individual; CAD 15,000,000 in any other case, per violation (section 91, amounts fixed by regulation) |
| Continuing violations | A separate violation for each day (section 94) |
| Directors and officers | Party to the violation if they directed, authorised, assented to, acquiesced in or participated in it, whether or not the operator is proceeded against (section 93) |
| Defence | Due diligence (section 92) |
| Purpose | Penalties promote compliance and are not intended to punish (section 89) |
| Violation or offence | Proceeding one way precludes the other (section 95) |
| Limitation period | Three years after the regulator becomes aware (section 96) |
The Act also creates offences for some contraventions; check the enacted text for the fine levels before quoting them. See the Board and Director Cyber Liability Guide for how director exposure compares with NIS2 and NYDFS.
What it means for AI agents and non-human identities
- Critical cyber systems include the machines that run them: the programme must "protect critical cyber systems from being compromised", which in practice covers service accounts, OT controller credentials, certificates and API keys. See the Service Account Security Guide.
- Third-party products and services: section 9(1)(a) names third-party products and services. A managed service provider's remote access account or a SaaS integration token is a third-party risk to document and mitigate under section 15.
- Incident detection: the 72-hour clock needs detection of abnormal machine identity use, such as a token used from a new location or a service account touching new systems. See the Secrets Management Guide.
- AI agents in operations: an agent with access to a network management platform or a payment system is part of the critical cyber system. Give it an owned identity, scoped permissions and logging, and include it in the programme inventory. See the Agent Identity and Access Guide.
Compliance steps
- Decide if you are likely in scope: map your services to the six Schedule 1 categories and your federal regulator. Suppliers to those operators should expect contract flow-down.
- Identify critical cyber systems: list the systems whose compromise would affect the vital service, including identity infrastructure, OT, payment and network management systems.
- Draft the programme now: structure it on the five section 9(1) elements, using the NIST CSF 2.0 or the CCCS baseline controls as the frame, so it can be adopted inside the 90-day window.
- Build the reporting path: agree who decides an incident is reportable, how to reach the CSE's Canadian Centre for Cyber Security, and how the regulator is notified with a copy. Rehearse a 72-hour timeline, recognising the final period may be shorter.
- Inventory suppliers and third parties: rank them by access to critical cyber systems and add security, notification and audit clauses; prepare to notify material supply chain changes.
- Set records in Canada: confirm that programme, incident and direction records can be kept in Canada.
- Prepare for directions: define who receives a cyber security direction, how it is kept confidential and how compliance is evidenced.
- Brief the board: explain section 93 director exposure and the due diligence defence, and record board oversight of the programme.
Decision guidance
- Wait or prepare: waiting for regulations is risky because the 90-day clock starts when your class is added; drafting the programme now costs little if you already run an ISO/IEC 27001 or CSF programme.
- Telecom providers: expect both Part 1 orders and CCSPA duties. Build one product and supplier register that serves both.
- Banks: OSFI's existing technology and cyber expectations already cover much of the programme; map rather than rebuild.
- Smaller operators: the Act does not scale by size; regulations may. Track the consultation.
Measuring readiness
- Critical cyber system inventory: share of systems supporting the vital service with an owner and classification.
- Reporting drill time: hours from detection to a filed report in exercises, against 72.
- Supplier coverage: share of suppliers with access to critical systems under security clauses.
- Machine identity hygiene: service accounts and keys with an owner and rotation date.
- Programme review: annual review completed within 60 days and notified within 30.
Framework mapping
| CCSPA duty | NIST CSF 2.0 | NIST SP 800-53 Rev 5 |
|---|---|---|
| 9(1)(a) identify and manage risk, including supply chain | GV.RM-01, GV.SC-01, ID.RA-01 | PM-9, SR-3 |
| 9(1)(b) protect | PR.AA-01, PR.AA-05 | IA-2, IA-5, AC-6 |
| 9(1)(c), (d) detect and minimise impact | RS.CO-02 | IR-6 |
| 13 annual review | ID.IM-01, GV.OV-01 | PM-1 |
| 15 supply chain mitigation | GV.SC-01 | SR-3, SR-11 |
Common failure patterns
- Treating it as still a bill: the Act has Royal Assent; only commencement and regulations are pending.
- Scoping only IT: pipeline, power line and nuclear operators must include OT systems that support the vital service.
- Supplier access left out: remote access by vendors is a common entry point, as the Colonial Pipeline Ransomware Attack 2021 showed with an unused VPN account.
- No owner for the reporting decision: incidents found on a Friday miss the clock.
- Records held abroad: group tooling that stores incident records outside Canada conflicts with section 30.
Practitioner checklist
- Map services to Schedule 1 and identify your likely regulator.
- Track the Governor in Council order and regulations that will populate Schedule 2.
- Inventory critical cyber systems, including identity, OT and machine credentials.
- Draft a programme covering the five section 9(1) elements.
- Rehearse CSE incident reporting and regulator notification within 72 hours.
- Add security and notification clauses for suppliers with access to critical systems.
- Confirm records can be kept in Canada.
- Brief directors on section 93 and document oversight and due diligence.
Standards and references
- Parliament of Canada: Bill C-8, Royal Assent text
- Parliament of Canada: LEGISinfo, Bill C-8 (45-1)
- Justice Laws Website: S.C. 2026, c. 9 coming-into-force status
- openparliament.ca: Bill C-8 debates and status
- JURIST: Canada parliament passes cybersecurity bill
- NIST: Cybersecurity Framework 2.0
Related NHI Mgmt Group resources: Critical Infrastructure Regulation Map · Critical Infrastructure Identity Security Guide · Cyber Incident Reporting Requirements Map · Canada ITSG-33 and CCCS Cloud Medium Profile Guide. This guide summarises Canada's Bill C-8 and the Critical Cyber Systems Protection Act and is not legal advice.