ClearBreach

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 →

← Quick reference guides·All breach response guides →

Your SituationWe had a privacy incident →

PIPEDAAB PIPABC PIPAAll sectors

Unauthorized Employee Access, Quick Reference Guide

By Yong DuPublished Reviewed

Share on LinkedIn

Immediate steps when a current or former employee accesses personal information beyond their authorization, PIPEDA, Alberta PIPA, and BC PIPA.

Typical verdict

Case-by-case, depends on what was accessed, for how long, and whether exfiltration evidence exists

Reporting deadline

As soon as feasible (PIPEDA) or without unreasonable delay (Alberta PIPA) once RROSH is determined, the HR investigation does not pause your reporting clock

Documents you will need

  • → Internal Incident Record (required under PIPEDA; good practice otherwise)
  • → Audit log exports, preserve immediately
  • → OPC PIPEDA Breach Report (if PIPEDA RROSH triggered)
  • → OIPC Alberta Notification Form (if AB PIPA applies)
  • → OIPC BC Voluntary Report (if BC PIPA applies, voluntary but recommended)
  • → Individual Notification Letters, to affected individuals, not to the employee

Do not

  • ✕ Treat it as an HR matter only, the breach assessment runs in parallel with any disciplinary process
  • ✕ Inform the employee the breach review is under way before revoking their access
  • ✕ Wait for the HR or legal investigation to conclude before determining RROSH
  • ✕ Accept the employee's stated motivation as a substitute for an evidence-based RROSH assessment
  • ✕ Assume RROSH is absent because the information was only viewed, not copied or exfiltrated
  • ✕ Let audit logs auto-delete, platforms often purge logs after 30–90 days

First 30 minutes

  • Revoke the employee's access to all systems holding personal information immediately, before informing the employee that a review is under way
  • If a former employee: revoke every remaining credential at once, email, VPN, cloud platforms, third-party SaaS tools, shared passwords, physical access cards
  • Preserve audit logs immediately, confirm log retention settings in Google Workspace, Microsoft 365, and all relevant platforms before any system changes
  • Designate a breach assessment lead separate from the HR process lead
  • Record the exact date and time the incident was discovered, this starts your response clock

Within 24 hours

  • Export all available audit logs for the employee's account activity, note what systems, what records, and what time periods are covered
  • Determine the scope: what categories of personal information could the employee have accessed within their system permissions?
  • Identify the individuals affected (customers, employees, or both) and which provinces they are in (determines whether AB PIPA and BC PIPA apply alongside PIPEDA)
  • Begin your RROSH assessment, do not wait for the HR investigation to produce findings
  • Document the employee's stated account if they have been interviewed, include what they said and when

Within 72 hours

  • Complete your RROSH assessment and determine your verdict
  • If no audit logs exist: assess on the worst-case scope of what the employee could have accessed given their system permissions
  • If PIPEDA RROSH threshold is met: file OPC Breach Report as soon as feasible, the HR investigation does not delay this
  • If Alberta PIPA applies and RROSH is met: notify OIPC Alberta (breachnotice@oipc.ab.ca) and affected individuals simultaneously
  • If BC PIPA applies: BC PIPA has no breach reporting duty: a report to the OIPC BC is voluntary and encouraged for significant breaches, and the BC Commissioner expects affected people to be told directly where there is a risk of harm
  • Send individual notifications directly to each person whose records were accessed, this is notification to those individuals, not to the employee who accessed them
  • If RROSH is not met: document the assessment and reasoning in your Internal Incident Record

Ongoing, until resolution

  • Close the access control gap that enabled the breach, offboarding failure, permission over-provisioning, or both
  • Update your Internal Incident Record as new information emerges, if material new facts arise after notification, send a follow-up to regulators and affected individuals
  • Review and update your offboarding checklist and credential revocation process for all departing employees
  • Retain all records (audit log exports, assessment records, notifications sent) for 24 months minimum from date of discovery
  • If the employee or former employee is subject to legal proceedings, coordinate evidence preservation with legal counsel, do not delete records as part of routine clean-up

Alberta PIPA, specific steps

  • Notify the OIPC Alberta and affected individuals simultaneously, this triggers the streamlined review process and a private closing letter rather than a public investigation
  • Complete the official OIPC Alberta Notification Form, do not substitute an informal letter
  • Attach the AB PIPA Individual Notice (s.19.1) to your OIPC Alberta submission (Section D)
  • Submit by email to breachnotice@oipc.ab.ca

BC PIPA, specific steps

  • BC PIPA applies to your activity in BC, including employees working there. Serving BC clients from another province is interprovincial and falls under PIPEDA
  • If BC PIPA applies: BC PIPA has no breach reporting duty: a report to the OIPC BC is voluntary and encouraged for significant breaches, and the BC Commissioner expects affected people to be told directly where there is a risk of harm
  • Do not substitute a general public notice for direct individual notification

MSPs, if managing this for a client

  • Confirm in writing with the client who leads regulatory notification before acting on their behalf, the client is the accountable party under PIPEDA and PIPA
  • If the unauthorized access was by one of your own employees into a client's systems: your obligation runs in two directions, your own regulatory and contractual notification, and notifying the client so they can manage their own obligations
  • Run a ClearBreach assessment under your MSP account for the affected client organization
  • Document all client communications with timestamps and keep the client's incident record separate from your own

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

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

Want the full background?

Read the educational playbook for this scenario.

Read playbook →

Find out what this incident requires of you

See whether you must report, to whom and by when, under each privacy law that applies to you.

How ClearBreach handles a breach →

See plans and pricing →