Skip to content
Compliance for Technical Staff

Lesson 7: Respond when something goes wrong

You will be able to: recognize a possible incident, escalate it promptly, and contain it without destroying the evidence needed to understand it.

About 3 min

You do not have to decide whether something is a “breach.” That is a legal determination that depends on the data, the people affected, where they are, and which laws and contracts apply. Your job is to recognize that something might be wrong and escalate it through the incident process quickly.

Speed matters because notification obligations differ, and some clocks start when the organization becomes aware:

  • GDPR: a controller notifies the supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware of a personal data breach, unless it is unlikely to result in a risk to people.
  • HIPAA: a covered entity notifies affected individuals without unreasonable delay and no later than 60 calendar days after discovering a breach. A breach is treated as discovered on the first day it is known (or with reasonable diligence would have been known) to any workforce member other than the person who committed it.
  • DFARS 252.204-7012: a defense contractor reports cyber incidents affecting covered defense information to DoD within 72 hours of discovery.
  • Contracts with customers often set their own notice periods.

Contain without destroying evidence. Revoke credentials and block access, but preserve logs, snapshots, and records of what was exposed before you change or delete anything. Afterwards, a blameless review turns the incident into tracked improvements.

Sources: GDPR, Art. 33(opens in a new tab)45 CFR Part 164 Subpart D, § 164.404(opens in a new tab)DFARS 252.204-7012, (c)(opens in a new tab)

Exercise 1 of 2: A public bucket on a Friday evening

Make three decisions. After each one, see what happens next.

  1. 1/3

    Friday, 6:10 p.m. While debugging, you notice that a storage bucket holding nightly customer exports has been publicly readable for three days. Its access log shows downloads from IP addresses you do not recognize.

    What do you do first?

Apply it 2 of 2: After the incident

Which outcome of the post-incident review best supports both compliance and improvement?

Choose the best outcome.

Key points

  • You do not decide whether it is a breach. Escalate through the incident process quickly.
  • There is no universal notification deadline. GDPR, HIPAA, DFARS, and contracts all differ.
  • Contain without destroying evidence: preserve logs and inventories before changing or deleting.
  • Post-incident reviews should produce owned, dated, verified corrective actions, not blame.