ClearBreach
On this page

← Playbooks

Your SituationWe had a privacy incident →

In the middle of a breach?

ClearBreach shows whether you must report, to whom and by when, under each law that applies, and writes the reports.

What to do now →
PIPEDAAB PIPABC PIPAAll sectors

Unauthorized Employee Access, What Canadian Organizations Must Do

By Yong Du · Updated June 13, 2026

Share on LinkedIn

An employee who accesses personal information beyond their authorization has caused a breach, PIPEDA and PIPA obligations apply regardless of intent.

⚡ In an active breach right now?

Use the quick reference guide, built for use during an incident.

Open response guide →

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

When a staff member or former staff member opens records they had no right to see, it is a privacy breach, not only an HR matter. Cut off their access first, save the access logs, and assess the breach while HR does its own work. Without logs, assume they saw everything they could reach.

Which laws apply

Jurisdiction Applies when Regulator
PIPEDA The personal information accessed belongs to individuals in provinces without substantially similar legislation, or the organization conducts interprovincial commercial activity Office of the Privacy Commissioner of Canada (OPC), priv.gc.ca
Alberta PIPA The breach involves your organization's activity in Alberta, including its employees there OIPC Alberta, oipc.ab.ca / breachnotice@oipc.ab.ca
BC PIPA The breach involves your organization's activity in BC, including its employees there OIPC BC, oipc.bc.ca

More than one of these can apply. If the threshold is met, report separately to the OPC and the OIPC Alberta where each applies; a report to the OIPC BC is voluntary.


What makes this scenario different

In most breaches the threat comes from outside: a ransomware group, a phishing attacker, a vendor's compromised system. Here, the person was inside your organization, may still be there, and already had legitimate access to some systems and records.

This creates three complications that do not exist in external breach scenarios.

Without access logs, you cannot see where the line was crossed. Forensics can often show which records an outside attacker reached. An employee who goes beyond their authority uses the same screens, sign-in and systems they use every day. Without logs, you cannot tell what they actually viewed. Then the assessment of the real risk of significant harm (RROSH) cannot be settled, and you must assume the worst case.

The HR response and the breach response run side by side, not one after the other. The most common mistake is treating it as an HR matter, suspending the employee, investigating and calling a lawyer, while the breach assessment waits. PIPEDA and PIPA do not wait for HR. Both run at once.

A former employee signing in is a failure to close their account, not a different kind of breach. It has two parts: the account left open (a gap in your safeguards) and the access itself (the breach). Both need a response, and the cause does not change your duty.


Immediate steps, this scenario specifically

1. Revoke access immediately, do not wait for HR confirmation. If it is a current employee, suspend their access to every system with personal information now, before they are told about the investigation. Otherwise they may delete log evidence or keep looking.

If it is a former employee, close every remaining account at once. Then check everything they had: email, VPN, cloud platforms, other online tools, shared passwords and building access cards.

2. Preserve audit logs before doing anything else. Access logs are your main evidence of what was opened, when and for how long. Make sure they are saved before you change any system. If a platform such as Google Workspace, Microsoft 365 or a CRM holds them, check its settings will not delete them; some delete logs after 30 to 90 days by default.

3. Do not inform the employee that a breach review is under way until access is revoked. Telling them before their access is cut risks deleted logs, more access or data taken. Cut access first.

4. Designate an incident lead separate from the HR lead. The HR investigation and the breach assessment need different leads. HR looks at the employee. The breach assessment looks after the people whose information was opened.


What drives RROSH in this scenario

Factors that push toward RROSH:

  • Audit logs show the employee accessed records beyond their role for an extended period or accessed a large number of records
  • Evidence of exfiltration: files downloaded, emailed to a personal account, copied to a USB drive, or printed
  • The employee had an apparent motivation to misuse the information, departing to a competitor, personal relationship with an affected individual, financial incentive
  • The information accessed is sensitive: health records, financial data, SINs, passwords, information about minors, or records that could enable identity theft
  • The employee accessed records belonging to identifiable individuals who could be harmed, a specific client, a coworker in a vulnerable situation, a public figure

Factors that push against RROSH:

  • Audit logs are complete and show only brief, limited access with no exfiltration activity
  • The information accessed was low-sensitivity, basic contact information with no financial or health data
  • The access was immediately detected and the employee's access was revoked before further access occurred
  • The employee's account is credible and consistent with audit log evidence showing curiosity rather than targeted misuse

The no-audit-log problem: With no logs, you cannot tell what was opened. Unless evidence limits it, assess on the basis that the employee saw everything their permissions allowed, which may be a lot. That is not a reason to delay; it is a reason to assume the wider scope and assess on it.


Likely verdict range

Scenario Typical verdict
Employee accessed records outside their role; audit logs confirm brief viewing, no exfiltration, low-sensitivity data No reporting obligation, but document the assessment and reasoning
Employee accessed client financial records, HR files, or health information outside their role; exfiltration not confirmed but also not ruled out RROSH, probability of misuse cannot be sufficiently reduced
Employee departing to a competitor accessed client list, pricing data, or business-sensitive personal records RROSH, motivation and sensitivity both elevated
Former employee with live credentials logged in after termination; audit logs confirm limited access to non-sensitive records Case-by-case, assess sensitivity and scope
Former employee with live credentials accessed records over weeks or months without detection RROSH, extended unauthorized access with no detection significantly increases probability of misuse
No audit logs; employee had broad system permissions Assess on worst-case scope, RROSH likely unless information held was uniformly low-sensitivity

Does what your staff member opened need reporting? It turns on what they saw and why. That is the decision ClearBreach makes, under PIPEDA, Alberta PIPA and BC PIPA at once. See it made on a real case →


Scenario-specific obligations and complications

If RROSH is determined:

  • OPC notification (PIPEDA): Notify the OPC as soon as feasible after determining RROSH. Do not wait for the HR investigation to conclude.
  • OIPC Alberta notification (AB PIPA): If the breach involves your Alberta activity, notify the OIPC Alberta without unreasonable delay.
  • OIPC BC (BC PIPA): No legal duty to report; a voluntary report is encouraged for a significant breach in your BC activity.
  • Individual notification: Notify each affected individual directly (required under PIPEDA; in Alberta when the commissioner directs, and best sent with the report; expected in BC). This is notification to the people whose records were accessed, not notification to the employee who did the accessing.

If RROSH is not determined:

  • No regulator notification required.
  • No individual notification required.
  • Internal breach record, required under PIPEDA and good practice otherwise: document what was accessed, your RROSH assessment, and your reasoning.
  • Address the underlying access control gap regardless of RROSH determination.

BC PIPA, voluntary reporting option. BC PIPA has no breach reporting or notification duty, so any report to the OIPC BC is voluntary. For a significant breach in your BC activity, the BC Commissioner encourages a report and expects the people affected to be told where there is a risk of harm. See BC PIPA Breach Reporting.

For Ontario organizations. Ontario has no provincial private-sector privacy legislation, PIPEDA is the applicable framework. Report to the OPC at priv.gc.ca. No separate provincial regulator report is required. See Ontario Data Breach Reporting Requirements.

Complication, the affected individuals include coworkers. Often the records opened belong to other employees: their HR files, reviews, medical accommodation records or other personal details. Those coworkers must be told on the same basis as clients or customers. It makes for a delicate workplace situation, but it does not reduce the duty to notify.

Complication, the employee is also a suspect in a legal matter. If the access is part of a bigger matter, such as possible theft of trade secrets, harassment or a criminal referral, bring in a lawyer. The breach assessment still runs alongside it. Evidence may need more careful handling than in a usual breach.


Documents you will need

Regardless of RROSH determination:

  • Internal breach record: date discovered, who accessed what, scope of access based on audit logs, RROSH assessment outcome and reasoning, actions taken
  • Audit log exports, preserve before any system changes

If RROSH is determined, also:

  • OPC breach report (PIPEDA)
  • OIPC Alberta breach report (AB PIPA), if the breach involves your Alberta activity; email breachnotice@oipc.ab.ca
  • OIPC BC voluntary report (BC PIPA), if the breach involves your BC activity and is significant
  • Individual notification letters, for each person whose records were accessed

ClearBreach tells you which of these you need, and gives you the regulator reports and notification letters from your assessment answers.


Common mistakes in this scenario

Treating it only as an HR matter. The employee's conduct is an HR issue. Other people's information being exposed is a privacy breach. Both need a response. Under PIPEDA and Alberta PIPA, disciplining the employee without assessing the breach skips a legal step, whatever HR decides.

Telling the employee before cutting access. If they still have access when they hear, they can delete records, reach further or keep going. Cut access first, then let HR tell them.

Not saving the logs straight away. Logs are evidence, and many organizations wrongly assume they are kept forever. Cloud platforms, CRMs and email systems often keep them only 30 to 90 days by default. Lose them and you cannot assess the breach properly, a gap you cannot repair with a regulator.

Taking the employee's explanation as the answer. "They said they were just curious" is the most common one, and it may be true. It does not replace an assessment based on evidence. Record what they said and what the logs show. If the two match, the explanation counts. If not, the evidence wins.

Not notifying because the information was "only viewed". Viewing personal information without authority is a breach of security safeguards. The test does not need proof that data was taken. Proof it was taken raises the risk; no proof does not remove it.

Leaving the gap open. After the immediate response, fix what allowed it: an account not closed at departure, or permissions wider than the job needed. Regulators expect you to fix the cause, and a second incident through the same gap is much harder to defend.


What regulators have found

OIPC Alberta: A former employee of an Alberta car dealership kept the names, birth dates, contact details and purchase history of about 10,000 customers, and emailed them. The commissioner found a real risk of significant harm: unwanted email alone is not significant harm, but the deliberate misuse, and the former employee presenting as the business, made fraud likely. The lesson for offboarding is direct: access and customer data that leave with an employee are a breach waiting to be used.

OPC (federal): Canada's Privacy Commissioner investigated a major financial institution following the disclosure that a marketing employee had been exfiltrating customer data for over 26 months. The employee copied records from data warehouses to company-wide shared drives, then downloaded the data to USB keys, circumventing controls that would have blocked direct access. Nearly 9.7 million individuals had their names, SINs, dates of birth, addresses, and transaction histories taken and sold to private lenders. The OPC found no monitoring for anomalous transfer patterns, no oversight capable of detecting the behaviour, and no training that would have flagged it. The exfiltration ran undetected not because controls were broken, but because no one was watching the data move.

Sources: OIPC Alberta, Decision P2022-ND-062, Breach notification decisions; OPC, PIPEDA Findings #2020-005, Investigations into businesses


MSP note

If you are an MSP and an employee at your organization accessed a client's data without authorization:

The client organization holds the data and is the accountable party for PIPEDA and PIPA purposes. Your obligation is to notify the client immediately and completely, including what was accessed, when, and what steps you have taken. Do not manage the client's breach notification on their behalf without their explicit direction.

If you are an MSP managing this response for a client whose employee accessed records without authorization, assist the client with the RROSH assessment and notification. Run a ClearBreach assessment under your MSP account for the affected client organization.


Ready to assess this breach? Find out whether you must report it, to whom and by when, under each law that applies, with the regulator reports and notification letters to send. See it done on a worked case →

The demonstration is the real assessment, already answered for a fictional company, with three answers left for you to change. It ends on the verdict and the documents it produced. See a real verdict → to run it on your own breach.


This playbook covers PIPEDA, Alberta PIPA, and BC PIPA obligations for private-sector organizations. If your organization handles personal health information under provincial health legislation, such as Alberta's Health Information Act or BC's E-Health (Personal Health Information Access and Protection of Privacy) Act, unauthorized employee access to that information may trigger additional obligations under those statutes that are not covered here.


Frequently asked questions

An employee accessed client records they were not authorized to view, is this a reportable breach?

It depends on RROSH, real risk of significant harm. The access itself is a breach of security safeguards under PIPEDA regardless of RROSH. Whether you must notify the OPC and affected individuals depends on what was accessed, how sensitive it was, whether evidence of exfiltration exists, and what the employee's apparent motivation was. The internal documentation obligation applies in all cases. Do not treat this as an HR matter only, the privacy breach assessment runs in parallel with any disciplinary process.

A former employee still had access to our systems after they left and logged in, what are my obligations?

This is a breach of security safeguards, both a credential management failure and an unauthorized access event. Start your RROSH assessment immediately based on what audit logs show the former employee accessed. Revoke all remaining credentials at once. The fact that the access resulted from an offboarding failure does not reduce your obligations. If RROSH is present, you notify the applicable regulator and affected individuals on the same timeline as any other breach.

Can I wait until the HR or legal investigation is complete before deciding whether to report?

No. The privacy breach assessment and the HR or legal process run in parallel, they are not sequential. PIPEDA requires notification as soon as feasible after determining RROSH is present. An ongoing internal investigation is not a recognized basis for delaying notification. Assess RROSH on what you know now, notify if the threshold is met, and update affected individuals if material new information emerges from the investigation.

The employee says they were just curious and did not do anything with the information, does that affect RROSH?

Stated motivation is one factor in the RROSH assessment, but it is not determinative. An employee who claims curiosity and whose audit logs show brief views of records with no exfiltration activity presents a lower probability of misuse than one whose logs show extended access, file downloads, or forwarding to a personal email. What the employee says they intended does not override what the evidence shows they did. Document the employee's account, document the audit log evidence, and assess RROSH on the full picture.

Ready to assess this breach?

See whether you must report, to whom and by when, under each privacy law that applies to you, with the reports and letters to show for it.

How ClearBreach handles a breach →

See plans and pricing

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