Privacy breach reporting under PIPEDA
The four PIPEDA breach obligations, the real risk of significant harm test, and what to prepare.
Laws, sector rules, contracts and insurers expect you to protect information and prove it. We close the technical gaps and prepare evidence, alongside your counsel; we do not give legal advice or certify compliance.
Your counsel decides what applies and how to read it; auditors and certifiers decide whether you meet a standard. We turn their requirements into systems, procedures and evidence.
| Requirement | What it covers |
|---|---|
| PIPEDA | Federal private-sector privacy law: ten principles, including accountability, safeguards and openness; breach reporting, notification and records. |
| Quebec Law 25 | A person responsible for personal information (by default the highest authority); incident reporting and register; privacy impact assessments, including before information leaves Quebec. |
| Alberta and BC PIPA | Provincial private-sector laws; Alberta's requires breach notification. |
| PHIPA and similar | Health information custodians, their agents and service providers. |
| OSFI B-13, B-10 | Technology, cyber and third-party risk at federally regulated financial institutions and their vendors. |
| CASL | Email marketing consent, where in scope. |
| CyberSecure Canada | Federal certification for small and medium organizations, based on the Canadian Centre for Cyber Security's baseline controls; issued by accredited bodies. |
| SOC 2, ISO/IEC 27001 | For enterprise clients; from independent auditors and registrars. |
| Insurers, clients | Questions on MFA, EDR, backups, email security, training; clauses on data location, breach notification, subcontractors. |
Early decisions are hard to undo, so the plan names who does each step; we rehearse it with you in a tabletop exercise.
Technical gaps? Security assessments measure controls in depth; cybersecurity closes them: EDR, email security, awareness training.
Identify the laws, sector rules, contracts and frameworks likely to apply; confirm them with your counsel.
Output: Requirements map.
Inventory what personal information you collect, why, where it lives, who sees it and for how long.
Output: Data inventory and flow diagram.
Compare your technical and organizational safeguards with the requirements, and rank gaps by risk.
Output: Gap report and remediation plan.
Update controls, procedures, contracts and training; build the breach plan and register.
Output: Updated safeguards and breach plan.
Assemble what an auditor, insurer or regulator would ask for, and rehearse a breach scenario.
Output: Evidence pack and tabletop results.
No package prices: estimates in Canadian dollars from an agreed scope, taxes shown separately.
Organizations under PIPEDA generally must report breaches of security safeguards that create a real risk of significant harm to the Privacy Commissioner of Canada, notify affected individuals and keep a record of every breach. Quebec's Law 25 and Alberta's PIPA have their own rules.
Not on its own. A Canadian region (such as AWS Canada Central in Montréal or Azure Canada Central in Toronto) supports data residency; access controls, contracts, support access, backups and transfers matter too. We review the whole picture.
Generally yes. Privacy obligations apply regardless of size when you handle personal information in commercial activity, but the work scales down to a focused data inventory, a breach plan and a few well-run controls.
The four PIPEDA breach obligations, the real risk of significant harm test, and what to prepare.
Security in plain language: what could go wrong, how likely it is, what to fix first.
Assessments, endpoint protection, email security, training, incident readiness, and 24/7 monitoring for managed-service clients.
Tell us what has been asked and what information you handle. We will reply to arrange a conversation about getting ready.