Hands-on tutorial
Tutorials · Compliance
Canada's PIPEDA and Provincial Privacy Laws: Network Safeguards and Breach Records
What Canadian privacy law expects from your network: PIPEDA's safeguards principle, breach reporting and record-keeping, Quebec's Law 25, and the controls that support them.
Quick answer
PIPEDA (the Personal Information Protection and Electronic Documents Act) governs how private-sector organisations in Canada handle personal information in commercial activity. Alberta, British Columbia and Quebec have their own substantially similar private-sector laws; Quebec's Law 25 added strict breach and privacy-by-default rules.
PIPEDA's safeguards principle requires security appropriate to the sensitivity of the information, and its breach rules require reporting breaches that create a real risk of significant harm to the Privacy Commissioner, notifying affected people, and keeping records of every breach for 24 months.
This guide explains network controls that commonly support compliance. It is not legal advice; confirm your obligations with your legal or compliance adviser.
Key terms
- RROSH
- Real risk of significant harm: the test for whether a breach must be reported and individuals notified under PIPEDA.
- OPC
- Office of the Privacy Commissioner of Canada.
- Law 25
- Quebec's modernised privacy law, with obligations phased in from 2022 to 2024.
Before you start
- An inventory of personal information and where it is stored and transmitted
- Your privacy officer's policies
- Network diagrams and an asset list
Step by step
Classify sensitivity
Rank data by sensitivity: financial, health and identity data need the strongest protection. Map where it lives on the network.
Apply layered safeguards
Use physical, organisational and technical measures: segmentation, firewalls, MFA for administrators, encryption in transit and patched devices.
Limit collection on network services
Guest Wi-Fi portals and CCTV should collect only what is necessary, with clear notices and defined retention.
Log to support breach assessment
Centralised, time-synchronised logs let you work out what was accessed, which is needed to assess whether a breach creates a real risk of significant harm.
Keep a breach register
Record every breach of security safeguards, including those not reported, and keep the records for at least 24 months.
Plan the response
Define who assesses incidents, who reports to the OPC (and provincial regulators), and how individuals are notified.
Check cross-border transfers
If personal information is processed outside Canada, including in cloud services, be transparent about it and protect it by contract; Quebec requires a privacy impact assessment first.
Pro tips
- Treat Quebec residents' data with Law 25 requirements in mind.
- Keep evidence of safeguards for regulator questions.
- Review guest Wi-Fi retention and consent wording with your privacy officer.
Standards and references
FAQ
Frequently asked questions
Do small businesses need to follow PIPEDA?
Yes, if they collect, use or disclose personal information in commercial activity in a province without substantially similar legislation, or across borders.
How long must breach records be kept?
At least 24 months under the PIPEDA breach regulations.
Is there a federal replacement for PIPEDA?
Reform bills have been proposed; check the current status with your adviser.
Keep learning
Related guides
GDPR for network teams
Read more →Network security incident response
Read more →NavCloud
Read more →Guest Wi-Fi sign-in for hotels
Read more →GDPR for Network Teams: Practical Security Controls and Checklist
What the EU General Data Protection Regulation expects from your network: security of processing, access control, logging, encryption, guest Wi-Fi data, CCTV, retention and breach readiness, with a checklist you can apply.
Read more →PCI DSS v4.0 for Networks: Segmentation, Firewalls and Wi-Fi
How the Payment Card Industry Data Security Standard applies to your network: defining the cardholder data environment, segmentation to reduce scope, firewall and router rules, wireless, logging, testing and secure management.
Read more →Stuck on a step?
Ask Navijin technical support or an authorised partner for help with your configuration.