Lesson 1

Is it a breach? Recognise, contain, escalate

Video
2 min
Reading
12 min
Exercise
6 min
Total
20 min

Educational content, not legal advice.

In this lesson you will

  1. Tell a breach of security safeguards and a confidentiality incident apart from an ordinary security event.
  2. Take reasonable containment steps in the first hour without destroying the evidence.
  3. Escalate to the person accountable for privacy, and start the record from minute one.

Video lesson

Length: 1:53
Read the transcript

Welcome to Valdra Academy. This is lesson one of Breach Response Lab. Over six lessons you will work one incident from the first report to the closed file, and this lesson covers the first hour: is it a breach, what do you do now, and who needs to know?

Our fictional company is Larchfield Payroll Services, a payroll provider in Montreal, Toronto and Calgary. On Monday morning a coordinator admits typing their password into a fake sign in page. An hour later IT finds their mailbox forwarding everything outside, and foreign sign ins to the payroll drive.

Is that a breach? Under the federal law, a breach of security safeguards is the loss of, or unauthorized access to or disclosure of, personal information resulting from a failure of safeguards. PIPEDA s.2(1) (breach of security safeguards) In Quebec, a confidentiality incident also covers use not authorized by law. P-39.1 s.3.6

You do not wait for proof. In Quebec the duty to act starts when you have cause to believe an incident occurred, and you take reasonable measures to reduce the risk of injury and prevent it happening again. P-39.1 s.3.5, first and second paragraphs, s.3.7 So Larchfield cuts the access, exports the logs before cleaning up, and starts a log at minute one.

Then it escalates. In Quebec that is the person in charge of the protection of personal information. P-39.1 s.3.1 Federally, the individuals accountable for compliance. PIPEDA Sch.1 cl. 4.1, 4.1.3 And because Larchfield holds this data for its clients, they will need to hear from it too.

Recap: recognise it, contain it without destroying evidence, escalate, and write everything down. Next: assessing the risk.

Notes

The call nobody wants

Sooner or later every organization that holds personal information gets the call: an email was sent to the wrong person, a laptop went missing, an account was taken over. What happens in the first hours decides most of what follows: how much harm reaches the people concerned, what the regulators will be told, and what the file will show when someone reads it a year later.

This course works one incident from the first report to the closed file, and builds a breach kit one lesson at a time. This first lesson answers three questions: is this a breach, what do we do right now, and who needs to know inside the organization?

Meet Larchfield, and its bad Monday

Larchfield Payroll Services Inc. is a fictional payroll and HR records provider with offices in Montreal, Toronto and Calgary. It runs payroll for about 300 employers in Quebec, Ontario and Alberta, including federally regulated employers such as interprovincial trucking and courier firms, so it holds names, addresses, social insurance numbers, bank account numbers and salaries for thousands of their employees.

On a Monday morning a payroll coordinator in Toronto tells the help desk that they typed their password into a page that looked like the company sign in page. An hour later IT finds a rule in the coordinator's mailbox forwarding every message to an outside address, and sign ins from an unfamiliar country to the shared drive where payroll exports are kept. We will follow this incident through all six lessons.

Is it a breach? Two definitions

Canada has more than one definition, and an organization working in Quebec and other provinces needs both.

  • Federal private sector law. 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. PIPEDA s.2(1) (breach of security safeguards)
  • Quebec private sector law. A confidentiality incident is access not authorized by law to personal information, use not authorized by law, communication not authorized by law, or loss of personal information or any other breach of its protection. P-39.1 s.3.6

The Quebec definition names unauthorized use as well as access and communication. P-39.1 s.3.6 So an employee who looks up a client's records for a personal reason is a confidentiality incident in Quebec even if nothing ever left the building.

A security event is not always a breach

Security teams see events all day: a phishing email caught by the filter, a failed sign in attempt, malware stopped on a machine that holds no personal information. None of those is a breach on its own. The question that turns an event into an incident is simple: was personal information lost, or accessed, used or communicated without authority? If the answer is yes, or you cannot yet rule it out, handle it as an incident.

You do not wait for proof. The Quebec duty to act starts when the enterprise has cause to believe a confidentiality incident has occurred. P-39.1 s.3.5, first and second paragraphs, s.3.7 At Larchfield, an outside forwarding rule and foreign sign ins to the payroll drive are cause to believe, even before anyone knows which files were opened.

Contain it in the first hour

In Quebec, an enterprise that has cause to believe an incident occurred takes reasonable measures to reduce the risk of injury and to prevent new incidents of the same nature. P-39.1 s.3.5, first and second paragraphs, s.3.7 Under the federal law, personal information is protected by security safeguards appropriate to its sensitivity. PIPEDA Sch.1 cl. 4.7 Payroll exports with social insurance numbers and bank details sit near the top of any sensitivity scale.

A good first hour usually looks like this.

  • Cut the access. Reset the password, end every active session, remove the forwarding rule, and turn on multifactor sign in if it was off.
  • Keep the evidence. Export the sign in logs, the mailbox rule and the list of files touched before anything is cleaned up. Do not wipe the laptop or delete the mailbox: the evidence is what lets you say later who was affected and who was not.
  • Look for the rest. Check whether the same password works elsewhere and whether other mailboxes received the same phishing email.
  • Start the log at minute one. Every action, who took it, and the time.

Containment and evidence pull in different directions. Deleting the attacker's rule stops the leak; exporting it first keeps the proof. Do both, in that order.

Escalate to the right person

In Quebec, the person exercising the highest authority in the enterprise is the person in charge of the protection of personal information, and may delegate that function in writing. P-39.1 s.3.1 That person is consulted when the enterprise assesses the risk of injury from an incident. P-39.1 s.3.5, first and second paragraphs, s.3.7 Under the federal law, the organization designates one or more individuals who are accountable for its compliance. PIPEDA Sch.1 cl. 4.1, 4.1.3 Either way, the help desk ticket goes to that person the same morning.

Most organizations name a small incident team ahead of time: the privacy lead, IT or security, a senior decision maker, someone for communications, and legal counsel when needed. Names, phone numbers and a backup for each role belong on one page that works when email does not.

Larchfield has one more call to make. It holds this information for its clients. For clients the federal law covers, an organization stays responsible for personal information it transfers to a third party for processing. PIPEDA Sch.1 cl. 4.1, 4.1.3 For its Quebec clients, a provider must also notify the client's person in charge of the protection of personal information without delay of any violation of confidentiality. P-39.1 s.18.3 para 2 subpara 2, para 3 So Larchfield's clients will need to hear from it early. Lesson 4 covers who notifies whom.

Write it down from the start

Every breach of security safeguards goes in a federal record kept for 24 months. PIPEDA s.10.3(1)-(2); SOR/2018-64 s.6 In Quebec, every confidentiality incident goes in a register that the Commission can ask to see. P-39.1 s.3.8 The log you start in the first hour becomes the backbone of that record. Lesson 5 covers the record and the register.

What decides the next step

Whether Larchfield reports to a regulator and notifies people depends on the risk. The federal law calls for a report as soon as feasible when a breach creates a real risk of significant harm, and sets no fixed number of hours. PIPEDA s.10.1(1)-(3), (6) Quebec calls for prompt notice when an incident presents a risk of serious injury, also with no fixed number of hours. P-39.1 s.3.5 Lesson 2 runs both tests on Larchfield's facts. The template for this lesson is the incident intake form and first hour log.

Worked example

Larchfield's first hour

Fictional organization. Larchfield Payroll Services Inc. is invented for this course. Any resemblance to a real company is a coincidence.

This is the first page of Larchfield's incident log, as the IT lead kept it on Monday morning.

TimeWhat happened or was doneBy
09:40Payroll coordinator (Toronto) reports entering their password on a page that looked like the sign in pageHelp desk
09:48Ticket raised as a possible incident; IT lead pagedHelp desk
10:35Mailbox rule found forwarding all mail to an outside address; foreign sign ins to the payroll exports drive since SaturdayIT lead
10:41Rule, sign in logs and drive access log exported and saved to the incident folderIT lead
10:44Password reset, all sessions ended, rule removed, multifactor sign in enforced on the accountIT lead
10:52Same phishing email found in 11 other mailboxes; deleted, no other clicks found so farIT lead
11:05Privacy lead (delegated in writing by the president) and the COO told; incident team called for 11:30IT lead

What the team decided at 11:30. It is a breach under the federal definition and a confidentiality incident under the Quebec one: there is cause to believe an outsider accessed payroll exports. PIPEDA s.2(1) (breach of security safeguards) P-39.1 s.3.6 Containment is done for this account. The open questions are which files were opened and whose data was in them, which drives the risk assessment in lesson 2. The privacy lead will brief the client relationship managers before noon, because the federally regulated clients stay responsible for the data they hand Larchfield. PIPEDA Sch.1 cl. 4.1, 4.1.3

What went well, and what did not. The evidence was exported before the cleanup. But the forwarding rule had been running since Saturday, and nobody looked at the drive access log over the weekend. That goes on the list for lesson 6.

Scenario exercise · Allow 6 min

Event or incident?

You are the privacy lead at a Quebec retailer with stores in Quebec and Ontario. Four reports arrive in the same week:

  1. The email filter blocked 40 phishing emails aimed at the finance team. Nobody clicked.
  2. A store manager emailed a spreadsheet of 60 customers' names and phone numbers to the wrong supplier. The supplier says they deleted it.
  3. A customer service agent looked up their neighbour's purchase history out of curiosity.
  4. A backup drive holding customer addresses was left in a taxi and has not been found.

For each one, say whether it is a confidentiality incident under Quebec law, and what your first step is.

Show the model answer
  1. Not an incident. No personal information was accessed, used, communicated or lost. Log it as a security event and keep the filter report.
  2. Incident. Communication not authorized by law. First step: get the supplier's written confirmation that the file was deleted and not forwarded, then record it. P-39.1 s.3.6
  3. Incident. Access and use not authorized by law, even though nothing left the store. First step: remove the agent's access pending review and preserve the system's access log. P-39.1 s.3.6
  4. Incident. Loss of personal information. First step: find out whether the drive was encrypted and what exactly was on it, and report the loss to the taxi company. P-39.1 s.3.6

Why this is the strongest answer

Quebec counts access, use and communication not authorized by law, loss, and any other breach of protection as a confidentiality incident. P-39.1 s.3.6 Once there is cause to believe one occurred, the enterprise takes reasonable measures to reduce the risk of injury. P-39.1 s.3.5, first and second paragraphs, s.3.7 Whether any of the three incidents is reported to the Commission depends on the risk of serious injury, which is the next lesson. P-39.1 s.3.5 Recording events that turn out not to be incidents, and why, saves the argument later.

Template to download

Incident intake and first hour log

A one page intake form and a timed log for the first hours of an incident: what was reported, whether it is a breach or confidentiality incident, the containment and evidence steps, and who was told.

Check your understanding

Scenario questions. Answer them all, then check: you will see why each option is right or wrong.

Question 1 of 5

A receptionist at a Quebec accounting firm emails a client list to the wrong address and the recipient replies that they deleted it. Which statement is right?

Question 2 of 5

IT sees an outside forwarding rule on a manager's mailbox but cannot yet say which emails left. What should happen now?

Question 3 of 5

In the first hour after an account takeover, which order of steps keeps both the people affected and the evidence safe?

Question 4 of 5

Your Quebec enterprise never formally named a privacy officer. Who holds that role when an incident happens?

Question 5 of 5

A payroll provider in Ontario finds a breach in data it processes for client employers that are federally regulated. Why call the clients early?

Sources cited in this lesson

  1. PIPEDA s.2(1) (breach of security safeguards) official text current to 2026-09-30, checked on 2026-10-29
  2. P-39.1 s.3.6 official text current to 2026-10-15, checked on 2026-10-29
  3. P-39.1 s.3.5, first and second paragraphs, s.3.7 official text current to 2026-10-15, checked on 2026-10-29
  4. PIPEDA Sch.1 cl. 4.7 official text current to 2026-09-30, checked on 2026-10-24
  5. P-39.1 s.3.1 official text current to 2026-10-15, checked on 2026-10-29
  6. PIPEDA Sch.1 cl. 4.1, 4.1.3 official text current to 2026-09-30, checked on 2026-10-24
  7. P-39.1 s.18.3 para 2 subpara 2, para 3 official text current to 2026-10-15, checked on 2026-11-01
  8. PIPEDA s.10.3(1)-(2); SOR/2018-64 s.6 official text current to 2026-09-30, checked on 2026-11-03
  9. P-39.1 s.3.8 official text current to 2026-08-12, checked on 2026-10-24
  10. PIPEDA s.10.1(1)-(3), (6) official text current to 2026-09-30, checked on 2026-11-03
  11. P-39.1 s.3.5 official text current to 2026-10-15, checked on 2026-11-01

Get the full course

One payment of 59 USD. Every lesson, the knowledge checks, the final exam and the certificate open on your account. The first lesson is free to read.

Prices are in US dollars. Terms of sale · Privacy notice

You can ask for a full refund of a course within 14 days of buying it, if you have not passed its final exam.