• SOC 2 Readiness
  • 24/7 incident line
  • 24/7 security operations team
Whitepaper | Privacy and Compliance

Breach Reporting in Canada: A Practical Guide

Who must be told, how fast and with what evidence, across PIPEDA, Alberta, Quebec and the sector rules

GuardsArm Security Research7 min read5 chapters

Executive Summary

A security incident becomes a legal event the moment personal information is involved. Canada has no single breach law. A private company answers to PIPEDA or a substantially similar provincial statute, a public body to its provincial privacy act, a health custodian to health information legislation, and a regulated operator to its sector regulator as well. One incident can start several clocks.

Most of these regimes share a threshold, a real risk of significant harm, and share an expectation that the organization can say what happened. The second part is where organizations struggle. IBM's 2026 research found the average breach in Canada took 205 days to identify and contain.

You cannot notify accurately about an incident you cannot reconstruct. Reporting is a logging problem before it is a legal one.

This guide maps the main obligations, shows how to run the harm assessment, and sets out the evidence and process that make timely, accurate notification possible.

Key findings:

  • The threshold is similar across most regimes, but recipients, timing and record keeping differ.
  • Under PIPEDA every breach must be recorded for 24 months, including those that are not reported.
  • Quebec requires a register of confidentiality incidents and carries the largest penalties.
  • Regulated sectors add faster, separate reporting to their own regulators.
  • The quality of notification depends on detection, logging and a rehearsed plan.

Inside the whitepaper

01

The Canadian patchwork

The table summarizes the principal regimes. It is a guide to where to look, not a substitute for the statutes.

02

Assessing real risk of significant harm

The assessment is a judgment the organization makes and must be able to defend. Under PIPEDA two factors are named: the sensitivity of the information and the probability it has been or will be misused.

03

What a good notification contains

Regulators and individuals need different things from a notice. Both need accuracy.

04

The evidence you will need

Every question a regulator asks is answered from logs and records. Decide now what you keep.

05

Building the response process

A notification process that works under pressure is short, assigns names and has been rehearsed.

Key Takeaways

  • 1.Canada has several breach regimes. Identify which apply to your organization and data before an incident.
  • 2.Most regimes turn on a real risk of significant harm. Document the assessment whichever way it comes out.
  • 3.PIPEDA requires a record of every breach of security safeguards, kept for 24 months, whether or not it was reported.

Read the full whitepaper

16 pages with every chapter, table, checklist and the phased plan. Tell us where to send it and download it straight away.

Turn this research into a plan

Our team maps findings like these onto your environment and hands you a prioritized roadmap, not another report to file away.

Request a risk review

Related Whitepapers