Guide · Technology, Privacy and AI
Cybersecurity and Incident Response in Canada
Cybersecurity obligations in Canada now come from privacy law, sector regulators and new federal cyber legislation. This guide explains Bill C-8's telecommunications security powers, the not-yet-in-force Critical Cyber Systems Protection Act, OSFI's B-13 guideline and 24-hour incident reporting, breach notification rules, ransomware considerations, governance and insurance.
Key takeaways
- Bill C-8 received royal assent on 15 June 2026 as S.C. 2026, c. 9.
- Telecom security order violations can cost corporations up to CAD 10 million, or CAD 15 million for repeats.
- The Critical Cyber Systems Protection Act, with 72-hour incident reporting, is not yet in force.
- Federally regulated financial institutions must report cyber incidents to OSFI within 24 hours.
- Ransom payments are not banned but can breach sanctions law if the recipient is a listed person.
Cybersecurity law in Canada: what applies now
Cybersecurity obligations in Canada come from several sources rather than a single statute. Privacy laws require organizations to protect personal information with appropriate safeguards and to report qualifying breaches. Sector regulators, most notably the Office of the Superintendent of Financial Institutions (OSFI), impose detailed technology and cyber risk expectations and incident reporting deadlines. Directors' duties, securities disclosure rules and contracts add further obligations. In June 2026, Parliament added a new layer: S.C. 2026, c. 9 (Bill C-8) gave the federal government powers to secure telecommunications networks and enacted the Critical Cyber Systems Protection Act for operators of vital systems, although that second part is not yet in force.

For most businesses, the practical cybersecurity questions are the same: what security is legally required, who must be notified after an incident and how quickly, how to handle ransomware demands, how to protect investigation findings, and how insurance and contracts allocate the losses. This page addresses each, and explains where the new federal legislation stands as of November 2026.
The threat environment explains the regulatory attention. Ransomware, business email compromise, supply-chain attacks through software and managed service providers, and data theft for extortion affect organizations of every size. Regulators now expect boards to treat cyber risk as an enterprise risk, with clear ownership, regular reporting and tested response plans.
Bill C-8 and the Critical Cyber Systems Protection Act
Telecommunications security
Part 1 of S.C. 2026, c. 9 amended the Telecommunications Act. Under s. 15.1, if the Governor in Council believes on reasonable grounds that it is necessary to secure the Canadian telecommunications system against any threat, including interference, manipulation, disruption or degradation, it may by order prohibit a telecommunications service provider from using products and services provided by a specified person, or direct it to remove such products from its networks.
Contravening a security order or related regulation is a violation carrying administrative monetary penalties of up to CAD 10 million for a corporation, and up to CAD 15 million for a subsequent contravention, with each day of a continuing violation a separate violation (ss. 72.131–72.132).
Critical Cyber Systems Protection Act
Part 2 enacts the Critical Cyber Systems Protection Act (CCSPA). Once in force, it will apply to designated operators in sectors listed as vital services and systems: telecommunications services, interprovincial or international pipeline and power line systems, nuclear energy systems, federally regulated transportation systems, banking systems, and clearing and settlement systems. Designated operators will be required to:
- establish, implement and maintain a cyber security programme for their critical cyber systems, and notify the appropriate regulator when it has been established;
- mitigate supply-chain and third-party cyber risks;
- report cyber security incidents affecting critical cyber systems to the Communications Security Establishment within a prescribed period not exceeding 72 hours (s. 17), and then notify their regulator;
- keep records and comply with cyber security directions issued by the government; and
- face administrative monetary penalties, set by regulation, of up to CAD 15 million per violation for organizations (s. 91), with directors and officers potentially liable as parties.
The coming-into-force provision states that Part 2 comes into force on a day or days fixed by order of the Governor in Council, and the consolidated Act is marked as not in force. Operators in the listed sectors should use the time before designation to align their programmes with the Act's structure. Our insight on the Critical Cyber Systems Protection Act tracks implementation.
Sector rules: OSFI B-13 and financial institutions
Federally regulated financial institutions (FRFIs), including banks, federally regulated insurers and trust and loan companies, are subject to OSFI's Guideline B-13, Technology and Cyber Risk Management, dated July 2022. B-13 sets outcomes and principles covering governance and risk management, technology operations and resilience, and cyber security, including threat assessment, secure design, detection, incident response and recovery. Under OSFI's Technology and Cyber Security Incident Reporting advisory, FRFIs must report a technology or cyber security incident to OSFI's Technology Risk Division and their lead supervisor within 24 hours, or sooner if possible.
Other regulated sectors have parallel expectations. Securities regulators expect registrants and marketplaces to manage cyber risk, provincial energy regulators address grid security, and health information custodians face health privacy statutes. Federally regulated financial institutions must also manage third-party technology risk under OSFI's Guideline B-10, which is directly relevant to cloud and managed service providers. Our financial services regulatory page covers these expectations in context.
Breach notification and regulator engagement
When a cybersecurity incident involves personal information, privacy breach rules apply in parallel with any sector reporting. Under PIPEDA, an organization must report to the Privacy Commissioner of Canada any breach of security safeguards that creates a real risk of significant harm to an individual, notify affected individuals as soon as feasible and keep records of all breaches for 24 months. Quebec requires prompt notice to the Commission d'accès à l'information and affected persons where an incident presents a risk of serious injury, and Alberta's statute has its own notification requirement.
| Who | Trigger | Deadline | Source |
|---|---|---|---|
| Privacy Commissioner of Canada and individuals | Real risk of significant harm | As soon as feasible | PIPEDA s. 10.1 |
| Quebec CAI and affected persons | Risk of serious injury | Promptly | Quebec private-sector act s. 3.5 |
| OSFI (FRFIs) | Technology or cyber incident meeting OSFI criteria | Within 24 hours | OSFI advisory |
| Communications Security Establishment (designated operators) | Cyber security incident affecting critical cyber systems | Prescribed period of up to 72 hours (once in force) | CCSPA s. 17 |
| Securities markets (reporting issuers) | Material change or material fact | Material change: immediately by news release | Provincial securities law |
Engaging with regulators well matters as much as meeting deadlines. Initial reports are often made before the facts are known, so they should be accurate but appropriately qualified and updated as the investigation progresses. Consistency between what is said to regulators, affected individuals, insurers, customers and, for listed issuers, the market is essential. Our insight on real risk of significant harm explains how organizations assess the PIPEDA threshold.
Engage legal counsel at the start of an incident, before forensic firms are retained. Retaining the forensic investigator through counsel, for the purpose of legal advice in contemplation of litigation, gives the best chance of protecting the investigation under solicitor-client or litigation privilege, which can matter greatly if regulatory proceedings or class actions follow.
Ransomware and extortion
Canada does not prohibit ransom payments as such, but paying is never a purely technical decision. Legal considerations include:
- Sanctions: a payment to a threat actor who is, or is owned or controlled by, a person listed under Canadian sanctions regulations may contravene the Special Economic Measures Act or other sanctions statutes; the identity behind ransomware groups is often uncertain, so screening and threat intelligence are essential.
- Proceeds of crime and AML: financial institutions and virtual currency dealers involved in making payments have reporting obligations under the PCMLTFA.
- Notification: paying does not remove privacy notification duties; stolen data must be presumed compromised even if the attacker promises deletion.
- Insurance: many cyber policies require insurer consent before payment and impose conditions on negotiators and payment channels.
- Law enforcement: reporting to police and the Canadian Centre for Cyber Security can support investigation and, in some cases, decryption.
- Governance: boards should document the decision, the alternatives considered and the basis for any payment.
Our insight on ransomware payments explores these factors in more detail.
Cybersecurity governance, contracts and insurance
Directors are expected to oversee cybersecurity as part of their duty to act in the best interests of the corporation and with the care, diligence and skill of a reasonably prudent person. In practice this means understanding the organization's key cyber risks, approving the risk appetite, receiving regular reporting on controls and incidents, and ensuring that response plans are tested through exercises involving senior management. For reporting issuers, material cyber risks and incidents must be considered in continuous disclosure.
Contracts allocate much of the risk. Technology and outsourcing agreements should cover security standards, audit and testing rights, breach notification by the vendor within short timeframes, cooperation in investigations, data return and deletion, subcontractor controls and liability for security failures, including whether the usual liability cap applies to data breaches. Customer contracts may impose security obligations and notification commitments that run alongside statutory duties. See our technology transactions and outsourcing page.
Cyber insurance can fund incident response, business interruption, extortion, regulatory defence and third-party claims, but coverage depends on policy wording, exclusions (for example for war or state-backed attacks, or failure to maintain specified controls) and compliance with notice and consent conditions. Policies should be reviewed with the incident response plan so that the right people know how to notify insurers and which vendors are pre-approved. Renewal questionnaires should be answered carefully, since inaccurate answers about controls can jeopardize coverage.
Cybersecurity and securities disclosure
For reporting issuers, a serious cyber incident is also a disclosure question. Under provincial securities law, a material change in the issuer's business, operations or capital must be disclosed immediately by news release and followed by a material change report, while material facts must be reflected in periodic disclosure. After the Supreme Court of Canada's broad reading of "material change" in Lundin Mining Corp. v. Markowich, 2025 SCC 39, issuers should not assume that an operational disruption such as a ransomware attack falls outside the timely disclosure obligation.
Issuers should therefore include their disclosure committee in the incident response plan, assess materiality early and repeatedly as facts develop, and avoid selective disclosure to analysts or major customers. Risk factor disclosure should describe cyber risks specifically rather than generically, and statements about the incident should be consistent with what is reported to regulators and affected individuals. Insider trading restrictions should be considered while the incident is undisclosed. Our continuous disclosure compliance page explains the framework.
Cybersecurity due diligence in transactions
Buyers and investors increasingly treat cybersecurity as a core diligence topic, because an undisclosed compromise can surface after closing and because remediation costs can be significant. Diligence typically covers the target's security governance and policies, recent assessments and penetration tests, incident history and notifications, open regulatory inquiries, key vendors and their security terms, insurance coverage and claims, and compliance with any sector-specific requirements such as OSFI guidance or, in future, the Critical Cyber Systems Protection Act. Technical assessments by independent specialists can complement document review where the target's systems are central to the deal.
Findings should be reflected in transaction terms: specific representations on incidents and security practices, indemnities or escrows for known issues, pre-closing remediation covenants and integration plans that address identity management and network connections on day one. Integration itself is a period of elevated risk, as attackers target newly connected networks and confused reporting lines.
Incident response step by step
Preparing before an incident
The most effective cybersecurity measures are taken before anything goes wrong. A practical readiness programme includes an incident response plan with named roles and out-of-band contact details; pre-agreed engagement terms with counsel, forensic investigators and communications advisers, approved by the insurer where required; offline, tested backups of critical systems; a current data map showing where personal information sits and which jurisdictions' residents are affected; template notifications for each regime; and tabletop exercises at least annually that include executives and directors. Organizations that rehearse these steps make better decisions under pressure and can show regulators that they took their obligations seriously.
- Contain: isolate affected systems, preserve logs and evidence and stop further data loss.
- Mobilize: convene the incident response team, notify insurers and engage counsel and forensic support.
- Assess: determine what systems and data are affected, whose information is involved and in which jurisdictions.
- Notify: make regulator, individual, customer and law enforcement notifications that are required or advisable, within the applicable timeframes.
- Communicate: prepare consistent internal and external communications, including bilingual notices where needed.
- Recover: restore systems from clean backups and verify integrity before reconnecting.
- Remediate and learn: fix root causes, update controls and record lessons learned, and prepare for regulatory follow-up and potential litigation.
Illustration: a hypothetical Canadian logistics company discovers that an attacker has encrypted its servers and claims to have stolen customer and employee data. Within hours, it must contain the attack, notify its insurer and retain counsel and forensic investigators; within days, it must assess whether there is a real risk of significant harm under PIPEDA and a risk of serious injury for Quebec residents, decide on notifications and evaluate whether paying the ransom could breach sanctions law. Cybersecurity class actions often follow significant breaches, so every step should be documented; see our insight on data breach class actions.
How TRW & Co helps
We advise organizations and their boards on Canadian cybersecurity law: incident response and multi-regime notifications, privileged forensic investigations, ransomware decision-making including sanctions screening, preparation for the Critical Cyber Systems Protection Act and telecommunications security orders, OSFI B-13 alignment, cyber clauses in technology and outsourcing contracts, and cyber insurance coverage questions. Where regulatory proceedings or litigation require Canadian-licensed counsel, we work with them closely. This page is general information, not legal advice. If you are responding to an incident or preparing for one, please contact us.
Frequently asked questions
Is the Critical Cyber Systems Protection Act in force?
Not yet. It was enacted as Part 2 of S.C. 2026, c. 9 (Bill C-8), which received royal assent on 15 June 2026, but Part 2 comes into force on a day or days fixed by order of the Governor in Council, and the consolidated Act is marked as not in force. Operators in the listed vital sectors should prepare now.
How quickly must a cyber incident be reported in Canada?
It depends on the regime. PIPEDA requires breach reports as soon as feasible where there is a real risk of significant harm. Quebec requires prompt notice where there is a risk of serious injury. OSFI expects federally regulated financial institutions to report within 24 hours. Once in force, the CCSPA will require reports within a prescribed period of up to 72 hours.
Is it illegal to pay a ransom in Canada?
There is no general prohibition, but a payment may contravene sanctions law if the recipient is a listed person or is owned or controlled by one, and insurers often impose conditions. Paying does not remove privacy notification obligations. Any decision should be documented and made with legal, forensic and insurer input.
What does OSFI Guideline B-13 require?
B-13, dated July 2022, sets expectations for federally regulated financial institutions on technology and cyber risk governance, technology operations and resilience, and cyber security, including threat assessment, detection, incident response and recovery. It is outcome-based and applied proportionately to each institution's size, complexity and risk profile.
Can a forensic investigation report be kept privileged?
Possibly. The best approach is to retain forensic investigators through legal counsel, for the purpose of providing legal advice and in contemplation of litigation, and to limit distribution of their reports. Privilege is assessed on the facts, and reports prepared mainly for business or operational purposes may not be protected.
Sources
- An Act respecting cyber security, amending the Telecommunications Act (S.C. 2026, c. 9)
- Critical Cyber Systems Protection Act (consolidated, not in force)
- Telecommunications Act (S.C. 1993, c. 38)
- OSFI Guideline B-13: Technology and Cyber Risk Management
- OSFI: Technology and Cyber Security Incident Reporting
- Personal Information Protection and Electronic Documents Act (S.C. 2000, c. 5)
General information only, not legal advice. References to statutes, courts and authorities describe published law and practice at the date shown.