ClearBreach

← Guides·All breach response guides →

Your SituationWe had a privacy incident →

PIPEDAAB PIPAAll sectors

What Is RROSH? The Breach Reporting Threshold

By Yong DuPublished Reviewed

Share on LinkedIn

Whether your breach meets the real risk of significant harm test that PIPEDA and Alberta PIPA use, factor by factor.

On this page

What is RROSH?

RROSH, Real Risk of Significant Harm, is the threshold that triggers mandatory breach reporting under PIPEDA (s.10.1) and Alberta PIPA (s.34.1). BC PIPA has no breach reporting duty and no equivalent test. Under PIPEDA you must also keep a record of every breach, whether or not it meets the test (s.10.3). ClearBreach runs the assessment under all three laws at once, tells you what each requires, and gives you the OPC report, OIPC Alberta submission and notification letters that follow.

The answer to the RROSH question decides whether:

  • the breach must be reported to the Office of the Privacy Commissioner of Canada (OPC) under PIPEDA, and the people affected notified;
  • the breach must be reported to the OIPC Alberta under Alberta PIPA. The commissioner then decides whether you must notify the people affected, and you may notify them yourself;
  • a voluntary report to the OIPC BC is advisable. BC PIPA requires none, but the BC Commissioner encourages reporting significant breaches and notifying people where there is a risk of harm.

For jurisdiction-specific reporting requirements: PIPEDA Breach Reporting Requirements · Alberta PIPA Breach Notification Requirements · BC PIPA Privacy Breach Reporting Requirements

RROSH is not a high bar that protects organizations from reporting minor incidents. For most breaches involving sensitive personal information, health records, financial data, social insurance numbers, passwords, or contact information combined with other sensitive data, RROSH will be present.

Significant harm includes bodily harm, humiliation, damage to reputation or relationships, loss of employment, business or professional opportunities, financial loss, identity theft, negative effects on credit records, and damage to or loss of property. The harm need not have occurred: a real risk that it could occur is enough.

PIPEDA itself defines significant harm, in s.10.1(7), to include:

  • Bodily harm: physical injury resulting from the breach or its consequences
  • Humiliation: public embarrassment or personal shame resulting from disclosure of sensitive information
  • Damage to reputation or relationships: loss of standing in the community, damaged personal or professional relationships
  • Loss of employment, business, or professional opportunities: job loss, contract termination, or professional licensing issues
  • Financial loss: direct financial theft, fraudulent transactions, or costs incurred by the individual as a result of the breach
  • Identity theft: misuse of personal information to impersonate the individual
  • Negative effects on credit records: fraudulent credit applications, unpaid accounts in the individual's name
  • Damage to or loss of property: physical property damage caused by information disclosure

Alberta PIPA does not define significant harm. It asks whether "a reasonable person would consider" that a real risk of significant harm exists, and the OIPC Alberta's breach decisions weigh the same kinds of harm listed above. BC PIPA has no breach reporting provision, so it has no definition either.


RROSH stands for a real risk of significant harm. It is the test that decides whether a breach must be reported to the regulator and the people affected, under PIPEDA and Alberta PIPA. It turns on two things: how sensitive the information is, and how likely it is to be misused. Ransomware almost always meets it; a recalled email with a name and address usually does not.

What factors decide whether there is a real risk of significant harm?

PIPEDA names two factors in s.10.1(8): how sensitive the personal information is, and how likely it is that it has been, is being or will be misused. The federal commissioner's guidance adds questions under them: who could have seen the information, how long it was exposed, and whether anyone meant harm. How many people are affected, and whether the information was recovered, feed into the same judgement.

How can organizations determine if a real risk of significant harm exists?

Weigh it all together: sensitivity, likelihood of misuse, how many people, and recovery. No single point decides it. If together they make harm a genuine possibility, not a speculative one, the test is met and reporting is mandatory under PIPEDA and Alberta PIPA.

Sensitivity of the personal information

Not all personal information carries equal risk. The more sensitive the information involved in a breach, the higher the probability that harm could result from its disclosure.

High sensitivity: information that almost always elevates RROSH probability when compromised:

  • Social Insurance Numbers (SINs)
  • Financial account numbers, PINs, passwords, and credit card data
  • Health and medical information
  • Biometric data
  • Government-issued identification numbers
  • Information about minors

Moderate sensitivity: information that elevates RROSH probability depending on context:

  • Full name combined with date of birth
  • Home address combined with other identifying information
  • Employment information
  • User credentials (email/password combinations)

Lower sensitivity: information less likely on its own to create significant harm risk:

  • Name and employer alone (publicly available)
  • General demographic information
  • Non-sensitive business contact information

Important: look at the whole set, not each field. Several less sensitive fields can still meet the test if together they enable identity theft, targeted fraud or other harm.

Probability that the information has been or will be misused

This factor examines the likelihood that the personal information will actually be used to harm an individual.

Higher probability of misuse:

  • Intentional attack by a threat actor (ransomware, targeted intrusion, insider theft)
  • Confirmed exfiltration of data from the environment
  • Information sold or posted on dark web marketplaces
  • Breach by a known bad actor or organized criminal group

Lower probability of misuse:

  • Accidental send to wrong recipient within the same organization
  • Paper records lost in transit, no indication of interception
  • System vulnerability accessed but no evidence of data extraction
  • Prompt recovery of lost device with evidence it was not accessed

The key question is: given who had access and what their apparent intent was, how likely is it that the personal information will be used to harm someone?

Number of individuals affected

Scale matters, but it is not the only consideration. A breach affecting thousands of individuals with low-sensitivity information may not reach RROSH. A breach affecting one individual with highly sensitive information (a health record, a SIN) may clearly meet the threshold.

As numbers grow, especially with sensitive data, the risk climbs fast. A breach of 500 employees' SINs and financial data almost certainly meets the test.

Whether the information has been recovered

Recovery of compromised information reduces, but does not eliminate, the probability of harm.

Strong recovery (reduces RROSH probability):

  • Device recovered promptly with verified evidence it was not accessed
  • Misdirected email recalled immediately with confirmation of deletion by recipient
  • Database access revoked before exfiltration is confirmed

Weak or no recovery (increases RROSH probability):

  • Ransomware attack, where copying of the data often cannot be ruled out
  • Stolen device not recovered
  • Credentials compromised in a third-party breach, still circulating
  • No technical confirmation of whether data was accessed

Find out whether your breach meets the test. ClearBreach weighs these factors under PIPEDA, Alberta PIPA and BC PIPA at once, entirely in your browser. You get the answer for each law, then the OPC report, the OIPC Alberta submission and the notification letters it calls for.

How does RROSH apply to common breach scenarios?

The outcome differs by scenario. Ransomware and confirmed copying of data almost always meet the test when personal information was present. Lost or stolen unencrypted devices usually do. An accidental internal disclosure of less sensitive information, quickly recovered, usually does not.

Scenario Typical RROSH Outcome Key Driver
Ransomware (personal data on affected systems) RROSH, almost always Malicious intent, confirmed access, probable exfiltration
Business email compromise, sensitive inbox RROSH, likely High-sensitivity data exposed to external threat actor
Business email compromise, operational inbox only Assessment required Depends entirely on what was in the mailbox
Lost device, unencrypted, sensitive data RROSH, likely Cannot confirm non-access; unrecovered
Lost device, full-disk encrypted, key not compromised Below RROSH, likely Strong encryption makes access unlikely
Accidental send, low-sensitivity data, recovered Below RROSH, likely Low probability of misuse, contained, recovered
Third-party vendor breach Assessment required Treated as your own breach; data sensitivity determines RROSH

Ransomware attacks

Ransomware almost always meets the test when personal information was on the affected systems. The attacker was inside, the intent is criminal, and copying the data first is common.

Business email compromise and phishing

Depends on what was in the compromised mailbox. A mailbox containing health records, financial data, or SINs, high probability of RROSH. A mailbox containing only internal operational communications, lower probability. Always review the full contents of the compromised account before concluding RROSH is absent.

Lost or stolen devices

An unencrypted device containing sensitive personal information, RROSH almost certainly present. An encrypted device with strong credential management, much lower probability. Full-disk encryption is the key mitigating factor.

Third-party vendor breaches

Assess a vendor's breach as if it were your own. The test turns on how sensitive the data you gave the vendor is, and what kind of breach it had. You are responsible for the information whoever holds it.

Accidental disclosure (wrong recipient)

Probability of RROSH depends on: how sensitive the information was, whether it was recovered, who received it, and whether there is evidence it was reviewed or forwarded. A misdirected email containing a single name and address, lower probability. A misdirected file containing hundreds of customers' health records, RROSH almost certainly present.


How does ClearBreach evaluate RROSH?

It tells you whether your breach meets the test under each law, and what that requires. ClearBreach assesses your breach under PIPEDA, Alberta PIPA and BC PIPA at once. It asks for the facts behind each factor: what information was involved and how sensitive it is, evidence of access and intent, how many people, and recovery. For each law it gives one of three findings: reporting required, voluntary report recommended, or no duty to report. Then it lists what that finding requires of you.

The entire assessment runs in your browser. No breach details are transmitted to ClearBreach servers.

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

Sources

  • Personal Information Protection and Electronic Documents Act, s.10.1(7) and (8) (definition and factors), s.10.3 (breach records).
  • Alberta Personal Information Protection Act, s.34.1 (notice to the commissioner) and s.37.1 (notice to individuals when the commissioner requires it, or on your own initiative).
  • Office of the Privacy Commissioner of Canada, What you need to know about mandatory reporting of breaches of security safeguards.

Frequently asked questions

What does RROSH mean?

RROSH stands for Real Risk of Significant Harm. Under PIPEDA and Alberta PIPA, a breach must be reported to the regulator when it creates a real risk of significant harm to an individual. PIPEDA also requires you to notify the people affected. In Alberta, the commissioner decides whether you must notify them, and you may notify them on your own initiative. The risk must be more than speculative. BC PIPA has no such test, because it has no breach reporting duty.

What counts as significant harm under PIPEDA?

Significant harm under PIPEDA includes bodily harm, humiliation, damage to reputation or relationships, loss of employment, business or professional opportunities, financial loss, identity theft, negative effects on credit records, and damage to property. The harm does not need to have occurred, only that there is a real risk it could occur given the nature of the personal information involved and the circumstances of the breach.

What factors decide whether there is a real risk of significant harm?

PIPEDA names two: the sensitivity of the personal information, and the probability that it has been, is being or will be misused. Regulators weigh other questions under them, such as who could have accessed the information, for how long, whether there was malicious intent, how many people are affected and whether the information was recovered. Highly sensitive information combined with confirmed access by a stranger usually meets the test.

Is RROSH the same under PIPEDA, Alberta PIPA, and BC PIPA?

PIPEDA and Alberta PIPA both use a real risk of significant harm, but Alberta's Act asks whether a reasonable person would consider that the risk exists, and it does not define significant harm or list factors. PIPEDA defines both in the Act. BC PIPA has no breach reporting duty and no harm test. ClearBreach assesses a breach under all three at the same time.

What breach scenarios almost always trigger RROSH?

Ransomware attacks with personal information on affected systems, confirmed exfiltration of sensitive data (SINs, health records, financial accounts), and deliberate unauthorized access by a threat actor almost always trigger RROSH. Lost or stolen devices containing unencrypted sensitive data typically trigger RROSH. Accidental internal sends of limited non-sensitive information with prompt recovery are less likely to reach the threshold.

This guide 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.

Find out what this incident requires of you

See whether you must report, to whom and by when, under each privacy law that applies to you.

How ClearBreach handles a breach →

See plans and pricing →