ClearBreach
On this page

← Playbooks

Your SituationWe had a privacy incident →

In the middle of a breach?

ClearBreach shows whether you must report, to whom and by when, under each law that applies, and writes the reports.

What to do now →
PIPEDAAB PIPABC PIPAAll sectors

Ransomware Attack, What Canadian Organizations Must Do

By Yong Du · Updated April 17, 2026

Share on LinkedIn

Ransomware is treated as a confirmed breach under PIPEDA and PIPA, exfiltration does not need to be proven. How to assess and respond.

⚡ In an active breach right now?

Use the quick reference guide, built for use during an incident.

Open response guide →

This playbook is educational and does not constitute legal advice. It is grounded in the text of PIPEDA, Alberta PIPA, and BC PIPA and published guidance from the OPC, OIPC Alberta, and OIPC BC. If your situation involves regulatory investigation, litigation risk, or circumstances not addressed here, engage a qualified privacy lawyer.

What makes ransomware different from other breaches

Most breach scenarios leave access probability as an open question. Ransomware removes that ambiguity. When ransomware executes on your systems, the attacker has been inside your environment. Access is confirmed or highly probable, and the act is deliberate and malicious.

These two facts, confirmed access and malicious intent, point strongly to a real probability of misuse, one of the two factors PIPEDA names. Ransomware attacks almost always trigger RROSH when personal information was present on affected systems. The question is rarely whether you have reporting obligations. It is how quickly you can satisfy them.

A second characteristic matters: ransomware attacks are ongoing breaches. Attackers commonly spend days or weeks in a network before deploying the encryption payload. Your containment date is not your breach start date.


Immediate containment, ransomware-specific

Do not pay the ransom before obtaining legal advice. Payment may violate Canadian or US sanctions regulations if the attacker is a designated entity. This determination must happen before any payment is made, regardless of operational pressure.

Do not wipe affected systems before forensic review. Destroying evidence before your incident response investigation is complete will undermine your breach report and can count against you if an investigation follows.

Ransomware-specific steps:

  • Isolate affected systems from the network immediately, do not shut them down unless instructed by your incident response firm
  • Disable compromised accounts and revoke active sessions
  • Engage your cyber insurer before taking further action, most policies require notification before remediation begins
  • Engage an incident response firm if you do not have internal forensic capability
  • Preserve all available logs, including firewall, endpoint, and authentication logs from the period before the encryption event
  • Identify the dwell time, when did the attacker first enter the environment? This is your breach start date, not the encryption date

What drives RROSH in a ransomware attack

Three factors make ransomware consistently meet the RROSH threshold:

1. Malicious intent is confirmed. A deliberate, malicious cause raises the probability of misuse, which weighs heavily under PIPEDA and Alberta PIPA. Ransomware is never accidental.

2. Access is confirmed or highly probable. Attackers who deploy ransomware have already accessed your systems. Modern ransomware groups routinely exfiltrate data before encrypting, even if you do not see evidence of exfiltration, regulators expect you to treat access as confirmed unless forensic evidence affirmatively rules it out.

3. Sensitive data raises the risk. If employee records, customer financial information, health data, or credentials were on affected systems, each data type adds weight. Organizations that assume "we're a small business, our data isn't that sensitive" consistently underestimate this factor.

The only factor that commonly reduces the risk in a ransomware attack is confirmed encryption at rest at the time of the attack. If affected data was encrypted with keys not accessible to the attacker, access is not confirmed. This must be established forensically, not assumed.


Likely verdict range

RROSH in most cases where personal information was present on affected systems.

A finding of no reporting obligation is rare in ransomware attacks and generally requires: (a) confirmed encryption at rest, (b) only non-sensitive personal information (contact details only, no financial, health, or credential data), and (c) rapid containment with no evidence of exfiltration.

If you are uncertain, assume RROSH and assess as forensic information becomes available. Reporting on an RROSH verdict and subsequently establishing that harm risk was lower is far better than failing to report and being found in violation.

Is your incident one of the "almost always reportable" ones? That is the decision ClearBreach makes, under PIPEDA, Alberta PIPA and BC PIPA at once. See it made on a real case →


Scenario-specific obligations and complications

Sanctions risk before paying ransom. Canadian and US sanctions lists include some individuals and groups linked to ransomware. Paying a sanctioned entity exposes your organization to regulatory penalties independent of the privacy breach. Obtain legal advice specifically on this point before any payment decision.

Dwell time determines your breach start date. The report must give the date or period of the breach, which in a ransomware attack starts when the attacker first accessed your environment, not when encryption was detected. The reporting clock itself runs from when you determine the breach occurred, so do not hold the report while dwell time is worked out; supplement it.

Third-party vendor involvement. If ransomware entered through a managed service provider, cloud platform, or software supplier, the vendor is a party to the breach. Describe the vendor's involvement and your coordination with them in your regulator submissions. Your service agreement should obligate the vendor to cooperate, document every communication.

Alberta PIPA individual notification timing. Under the OIPC Alberta's April 2024 streamlined review process, organizations that notify affected individuals simultaneously with regulatory reporting receive a private closing letter rather than a public investigation. The practical implication: do not delay individual notification to await regulatory direction.

BC PIPA covers your activity in BC. If your organization operates in BC, including employees working there, BC PIPA applies to that information. Serving BC clients from Alberta or another province is interprovincial and falls under PIPEDA. BC PIPA has no breach reporting duty, so a report to the OIPC BC is voluntary, although the BC Commissioner expects affected people to be told where there is a risk of harm. See BC PIPA Breach Reporting.

For Ontario organizations. Ontario has no provincial private-sector privacy legislation, PIPEDA is the applicable framework. Report to the OPC at priv.gc.ca. No separate provincial regulator report is required. See Ontario Data Breach Reporting Requirements.


Documents you will need

For a ransomware attack where RROSH is confirmed:

  • Internal Incident Record: required under PIPEDA, good practice otherwise; begin populating immediately, retain for 24 months
  • OPC PIPEDA Breach Report: required if PIPEDA RROSH threshold is met (almost certain in a ransomware attack involving personal information)
  • OIPC Alberta PIPA Notification Form: required if Alberta PIPA applies; email to breachnotice@oipc.ab.ca
  • OIPC BC voluntary report: BC PIPA requires none; recommended for a significant breach in your BC activity
  • Individual Notification Letter: required under PIPEDA when RROSH is met; in Alberta when the commissioner directs, and best sent with the report
  • AB PIPA Individual Notice (s.19.1): the contents Alberta requires when the commissioner directs you to notify individuals

ClearBreach tells you which of these you need, and gives you each one from your assessment answers.


Common mistakes, ransomware specifically

Waiting for full forensic confirmation before notifying. Regulators do not require certainty, they require action as soon as you determine RROSH is present on the available information. Waiting weeks for a forensic report before filing is one of the most common compliance failures in ransomware incidents.

Treating the encryption date as the breach date. Ransomware attackers are typically present in your environment for days or weeks before deploying the payload. Your breach report must reflect the actual breach start date once dwell time is established.

Assuming encryption at rest means no breach. If data was encrypted but the attacker had access to the encryption keys (for example, keys stored alongside the data, or keys accessible through compromised admin accounts), encryption does not reduce the access probability. This requires forensic confirmation to establish.

Wiping systems before forensic review. Operational pressure to restore systems is real. But destroying evidence undermines your ability to complete an accurate breach report, and regulators may draw adverse inferences from gaps in your investigation record.


What regulators have found

OIPC Alberta: An Alberta pharmacy reported that ransomware first gained access to its systems on May 29, 2022, but the encryption event that triggered detection did not occur until September 16, 2022. The attacker had nearly four months of undetected access. OIPC Alberta required notification to all patients whose records were on the affected systems, even though the organization could not confirm data had been exfiltrated. Inability to rule out exfiltration is itself sufficient for a RROSH finding when the exposed data includes patient health information.

OPC (federal): Canada's Privacy Commissioner investigated a ransomware attack on an agricultural services company serving farms across Ontario and Eastern Canada. An attacker obtained valid administrator credentials through an unknown vector and accessed company systems remotely, with no multifactor authentication in place to stop them. The OPC found four compounding safeguard gaps: no MFA, no network segregation, no data encryption, no detection tools. Eight hundred and forty-five individuals had their SINs, banking details, credit card numbers, and passport data exposed. The case confirms that MFA is not a best practice. It is the control whose absence makes every other safeguard negotiable.

Ontario IPC + OIPC BC (joint investigation): The Information and Privacy Commissioners of Ontario and British Columbia jointly investigated a 2019 cyberattack on a national medical laboratory company, which affected the personal health information of millions of customers, mostly in Ontario and BC. The commissioners found the company had not taken reasonable steps to protect the information, that its information technology security policies and practices were inadequate, and that in one instance it had collected more information than necessary. They issued orders, which the company complied with. The report, dated 2020, was published in 2024 after the company's court challenge to its release failed.

Sources: OIPC Alberta, Decision P2023-ND-001, Breach notification decisions; OPC, PIPEDA Findings #2023-002, Investigations into businesses; Ontario IPC + OIPC BC, Investigation Report 20-02 (2020), OIPC BC Investigation Reports


MSP note

If you are an MSP and your client was hit by ransomware, your obligations depend on whether you handle personal information on the client's behalf. If you do, and you almost certainly do, you have obligations as a service provider under PIPEDA and as an organization under Alberta PIPA.

Engage your client immediately. Document every communication. Your service agreement should define which party leads regulatory notification, confirm this before acting unilaterally on the client's behalf. If the ransomware entered through your systems or through a tool you manage, you are a direct party to the breach, not just a service provider.

ClearBreach MSP tier allows you to run a structured assessment for your client within your account. Use it to establish the RROSH verdict before advising the client on their regulatory obligations.




Ready to assess this breach? Find out whether you must report it, to whom and by when, under each law that applies, with the regulator reports and notification letters to send. See it done on a worked case →

The demonstration is the real assessment, already answered for a fictional company, with three answers left for you to change. It ends on the verdict and the documents it produced. See a real verdict → to run it on your own breach.

Frequently asked questions

Do I have to report a ransomware attack under PIPEDA?

Yes, if personal information was present on affected systems and there is a real risk of significant harm (RROSH). Ransomware attacks almost always trigger RROSH because access is confirmed and the intent is malicious, which together make misuse likely. You must report to the OPC as soon as feasible after determining RROSH is present, and notify affected individuals directly.

What is the reporting deadline for a ransomware attack under PIPEDA?

PIPEDA requires reporting 'as soon as feasible' after determining RROSH is present. The Act sets no number of days, so do not hold the report back. Do not wait for forensic completion, report on available information and supplement as your investigation continues. Delaying while you gather more information is not an acceptable reason for late filing.

Is my ransomware breach start date the day the encryption happened?

No. Ransomware attackers typically spend days or weeks inside a network before deploying the encryption payload. Your breach start date is when the attacker first gained unauthorized access, not the encryption event. Use dwell time analysis by your incident response firm to establish the correct start date, and use that date in your OPC report.

Should I pay the ransom?

Obtain legal advice before making any payment. Payment may violate Canadian or US sanctions regulations if the attacker is a designated entity, a determination that must happen before payment regardless of operational pressure. Most cyber insurers also require notification before any payment is made.

Do I have to notify affected individuals after a ransomware attack?

Under PIPEDA, yes, if RROSH is present you must notify affected individuals directly. Notification must not be only a public notice unless direct notification is not reasonably possible. The notification must describe the breach, the personal information involved, steps your organization has taken, steps individuals can take to protect themselves, and your contact information.

Ready to assess this breach?

See whether you must report, to whom and by when, under each privacy law that applies to you, with the reports and letters to show for it.

How ClearBreach handles a breach →

See plans and pricing

Privacy case of the month

Once a month, a five-minute read: a real case a Canadian privacy commissioner investigated, what went wrong, and what to check in your own organization so it doesn't happen to you. Written for organizations under federal, Alberta and BC privacy law. Not written for Quebec.

We send one email to confirm. Nothing else arrives until you confirm, and an unconfirmed address is deleted after 7 days. Sent by ClearBreach Technologies Inc. Mailing address and contact details · Privacy policy