
Privacy breach assessment and notification support
After a cyber incident, someone has to turn log files and mailbox exports into a defensible answer to three questions: whose information was involved, how much risk it creates, and who has to be told. We do the technical half of that work alongside your legal counsel.
Reviewed by the ITRS security team · Last updated
This page is general information, not legal advice. For advice on your obligations, speak with your lawyer.
IT Rapid Support does the technical half of a privacy breach assessment alongside your legal counsel: establishing whose personal information was involved, what evidence shows it was accessed or taken, and what that means for the real-risk-of-significant-harm test and notification.
From incident facts to breach analysis
Most privacy breaches start as an IT problem: a compromised Microsoft 365 mailbox, a ransomware event on a file server, a laptop left in a taxi, a misconfigured SharePoint link. The privacy question only becomes answerable once the technical facts are pinned down. What did the attacker actually reach? For how long? Was anything copied out, or only viewed? Were the files encrypted at rest?
Our work starts with the forensic record rather than assumptions. We preserve and review sign-in logs, the Microsoft 365 unified audit log, mailbox access records, endpoint telemetry and firewall data, then write down what the evidence shows and what it cannot show. That written account is what your counsel, your insurer and, if needed, a regulator will rely on, so we keep facts and inferences clearly separated.
If the incident is still active, containment comes first. Our digital forensics and incident response teams handle that side; this service picks up once the facts are stable enough to assess.
Real risk of significant harm assessment
Under the Personal Information Protection and Electronic Documents Act (PIPEDA), an organization must report a breach of security safeguards to the Office of the Privacy Commissioner of Canada (OPC) and notify affected individuals when it is reasonable to believe the breach creates a real risk of significant harm (RROSH). The Act lists the factors as the sensitivity of the information and the probability that it has been, is being or will be misused. Other regimes use their own tests: Quebec's private-sector law uses a 'risk of serious injury' test, Ontario's PHIPA sets out specific situations in which health custodians must notify the Information and Privacy Commissioner of Ontario (IPC), and Alberta's PIPA has its own commissioner-notification rule.
We supply the technical inputs those tests depend on: exactly which data types were exposed, whether encryption or access controls held, whether there is evidence of exfiltration, and whether the data has appeared anywhere it should not. Counsel makes the legal call; we make sure it rests on accurate facts.
Building the affected-party list from evidence
Notification is only as good as the list behind it. A breached mailbox might hold ten years of attachments; a file share might contain spreadsheets nobody remembers creating. We build the list from the data itself:
- Identify the exact mailboxes, folders, sites or systems in scope, bounded by the dates the evidence supports.
- Search and extract the content using defensible methods, preserving hashes and an audit trail.
- Classify the personal information found (identifiers, financial, health, government ID numbers, credentials) so sensitivity can be assessed per person rather than per incident.
- De-duplicate individuals across sources and match them to the best available contact details.
- Flag records for residents of provinces with their own rules, such as Quebec, Alberta or British Columbia, so counsel can apply the right regime.
- Deliver a reviewed, versioned list with a methodology note that explains how it was built.
Notices and regulator reports with counsel
PIPEDA's Breach of Security Safeguards Regulations set out what a report to the OPC must contain, including a description of the circumstances, the date or period of the breach, the personal information involved, the number of individuals affected, the steps taken to reduce harm, and a contact person. Notices to individuals must describe the breach and the steps people can take to protect themselves. Quebec's Regulation respecting confidentiality incidents has its own list for notices to the Commission d'accès à l'information (CAI) and to affected people.
We draft the technical portions of these documents in plain language and check every factual statement against the evidence. Counsel owns the final wording and decides what is sent, when and to whom.
Breach records you must keep
PIPEDA requires organizations to keep a record of every breach of security safeguards involving personal information under their control, whether or not it met the reporting threshold, and the regulations require those records to be kept for 24 months after the organization determines the breach occurred. Quebec requires a register of confidentiality incidents, with entries kept for at least five years. We produce a record entry for the incident we worked on and can help you set up a register for the smaller events that never become a full investigation.
What we don't do
We are a forensic and IT firm, not a notification vendor. We do not run call centres, print and mail large notice campaigns, or sell credit monitoring or identity-theft protection. When an incident needs those services, we tell you early so counsel or your insurer can arrange them, and we supply the clean list and the facts those providers need.
We also do not give legal advice. Breach decisions belong to your organization and its lawyers; our job is to make sure those decisions are based on what actually happened.
Frequently asked questions
Under PIPEDA, a breach of security safeguards is the loss of, unauthorized access to or unauthorized disclosure of personal information resulting from a breach of an organization's security safeguards, or from a failure to establish those safeguards. It must be reported to the Privacy Commissioner, and affected people notified, when it creates a real risk of significant harm.
Contain the incident first, then establish the facts: what data was involved, whose it was, and whether it was accessed or taken. Those facts drive the real risk of significant harm assessment, the notices and regulator report your counsel signs off, and the breach record you must keep for 24 months.
Yes. Preserving evidence and containing the incident should not wait. Many organizations bring in counsel early so the investigation can be directed through them; we will work with whichever counsel you choose.
No. We provide the technical facts and a clear account of what the evidence does and does not show. The decision to report or notify is yours, made with legal advice.
Yes. We carry $2M in cyber liability insurance and write our reports to be read by insurers and counsel. Tell us who needs the findings and we will format them accordingly.
Related work.
- Case studyFrom Breach Forensics to a Company-Wide Identity PlanFrom reconstructing a 2018 mailbox compromise minute by minute to scoping centralized Entra ID and Intune management for a 40 to 50 person pharma firm.
- Case studyCleaning Up a Microsoft 365 Tenant for a Fire Protection & Security CompanyHow IT Rapid Support audited every Microsoft 365 group for a GTA fire protection company, fixed mail routing, and cut an 82,456-item mailbox by 62%.
Related.
- PracticePrivacy, Data Governance & AIPIPEDA and Quebec Law 25 readiness, data mapping, breach notification and AI governance.
- ServiceDigital forensics in Toronto: computers, phones, Microsoft 365 and Google WorkspaceIT Rapid Support provides digital and computer forensics services for businesses in Toronto, the GTA and Ontario, focused on Microsoft 365, Exchange Online and Google…
- ArticleWho to tell after a cyber incident in CanadaAfter a cyber incident, the list of people who may need to hear from you is longer than most organizations expect: privacy regulators, police, the Cyber Centre, your…
- PagePrivacy breach and notification FAQShort answers to the Canadian breach questions that come up first: does this count, is there a real risk of significant harm, who has to be told and when, what records…
Not sure what your obligations require of your systems?
Speak with our privacy practice. We are staffed 24/7. Active incident? Call (289) 582-9930, 24/7.
