The problem: The security operations team (the SOC) finds customer data exposed on the internet and mentions it in a team chat. Two days later, by chance, the compliance lead hears about it. The rule says the regulator must be told within 72 hours of the company becoming aware. The notice goes out late. In the review, the SOC says, “Compliance should have asked us.” Compliance says, “The SOC never told us what data it was.”
Words used here: the SOC is the team that watches alerts and deals with attacks. A regulator is the official body that checks companies follow the law. A notice is the formal report a company must send after certain incidents. Many privacy rules give 72 hours, so check the time that applies to you.
Think of a relay race
Two runners meet at the line. The first holds out the baton. The second is looking at the track ahead. The baton hits the ground. Afterwards, the first says, “I handed it to you,” and the second says, “I never felt it.” Both are telling the truth. The race is lost anyway.
The SOC and compliance are the two runners. The 72 hours is the race.
What it looks like at work
On Tuesday at 9 am, a SOC analyst finds a storage folder with customer records open to the internet. He closes it, writes a note in the team chat, and moves on to the next alert. The compliance lead sees a message about it on Thursday morning, by chance, in a different channel. By then, 48 hours of the 72 have gone.
She asks what data it was and how many people were affected. The SOC lead says the log shows 1,200 records, but he is not sure which fields. These are example numbers. Compliance cannot decide if the notice is required without that answer. The notice goes out on Monday, a day late, and the regulator asks why.
- 11. Tuesday 9 amSOC finds open customer records
- 22. Chat noteClosed, noted in chat, analyst moves on
- 33. ThursdayCompliance hears by chance, 48 hours gone
- 44. No factsWhich data? Which fields? Not known
- 55. Late noticeSent Monday, a day late. Regulator asks.
Both teams have a fair point. The SOC acted quickly on the technical problem, which is what they are trained to do, and no one told them that a clock was running. Compliance knows the rule well but depends on the SOC to say that something happened. Neither team dropped the baton on purpose. The handover has no named person on either end.
You will notice it when:
- Incident news travels by chat and not by a ticket.
- Compliance hears about incidents by accident.
- Nobody can say who decides whether something is reportable.
- The 72 hours are counted from different starting points by different people.
- Reviews after an incident end with “we should communicate better.”
What exactly needs fixing
The fix is not a better apology. It is a named owner of the clock, a shared list of steps, and a practice run before the real one. This card shows the whole problem on one page:
The SOC found exposed customer data but compliance heard two days later, and the regulator notice went out late.
The hand-off between the SOC and compliance, and the 72-hour notice rule.
A serious breach is reported days late and the regulator acts.
- Late-notice finding
- Possible fine
- Strained teams
- Weeks on the review
- 11. Name a clock ownerOne person starts the clock, writes the time and watches it
- 22. One checklistConfirm, scope the data, decide, draft, send, each with a name
- 33. Drill twice a yearA made-up incident, timed, with a no-blame review
Who fixes it: CISO with SOC, compliance and legal
By when: owner and checklist in 2 weeks
A blank copy of this card is in the Tools section.
Why it happens
- Nobody owns the start of the clock. The SOC assumes compliance will ask. Compliance assumes the SOC will say.
- The SOC and compliance use different tools. An alert is not a notice.
- “Aware” is not defined. When did the company become aware: when the alert fired, or when someone confirmed the data?
- The steps are in people’s heads. There is no shared checklist.
- Nobody practises. The first time the hand-off runs is during a real incident.
What happens if you ignore it
The next incident has the same gap, and the regulator is watching.
- A late notice is a finding on its own, even if the incident was small.
- A fine or an order is possible, depending on the rule and the size.
- The two teams stop sharing information, to avoid being blamed.
- Staff spend weeks on the review instead of on prevention.
At a glance
| Question | Answer |
|---|---|
| How likely is it to hurt us? | Likely, wherever two teams share one deadline with no owner. |
| Worst case? | A serious breach is reported days late and the regulator acts. |
| What does it cost? | A late-notice finding, a possible fine, and strained teams. |
| What if we wait? | The next incident repeats the gap. |
| What does the fix cost? | One named person, one page, and two short drills a year. |
How to fix it, step by step
Name an owner, share one checklist, then drill.
- Name one clock owner. One person who starts the clock, writes the time, and watches it. A deputy covers when they are away.
- Define “aware.” Agree it with legal. For example: the moment the SOC confirms that personal data may be involved.
- Write one shared checklist. Short steps, each with a name: confirm, scope the data, decide if reportable, draft the notice, send.
- Make the SOC tell the clock owner by phone. Not by chat. Within one hour of confirming.
- Agree who decides “reportable.” Usually legal or compliance, with the SOC giving facts.
- Drill twice a year. Use a made-up incident, run the checklist, and time it.
- Hold a no-blame review after each drill and each real event. Write down one thing to change each time.
The picture shows the order: name an owner, share one checklist, then drill. The drill is what proves the first two work.
Who to bring in: The CISO (names the clock owner), the SOC lead and the compliance lead (share the checklist), legal (defines “aware” and decides reportable), and communications if customers must be told.
Tools and templates
Incident clock checklist
| Step | Who | Target time from awareness |
|---|---|---|
| Confirm data may be involved | SOC lead | Within 1 hour |
| Phone the clock owner and note the start time | SOC lead | Within 1 hour |
| Find what data and how many people | SOC lead and IT | Within 24 hours |
| Decide if reportable | Legal, with compliance | Within 36 hours |
| Draft and approve the notice | Compliance and legal | Within 60 hours |
| Send the notice | Clock owner | Before 72 hours |
Blank finding card
| Field | Write here |
|---|---|
| What is broken | One line, in plain words |
| Where it is | The system, team, or process |
| What could go wrong | In one sentence |
| What it costs us | Money, time, a failed audit, lost trust |
| The fix | The exact action |
| Who fixes it | One name or one team |
| By when | A date, not “soon” |
Email to start the talk
Subject: Who owns the clock when data is exposed
Hi both. In the review of last week’s exposure, we saw that the SOC and compliance each thought the other would start the notice clock. I would like us to name one owner, agree what “aware” means, and keep one shared checklist. Can we meet for 45 minutes this week? I am not looking for who dropped it. I am looking for a hand-off that works the next time, with a name beside every step.
Field tip
When something might be an incident, say the time out loud: “It is 9:10. The clock starts now.” Then write it down.
Words used in this chapter
- SOC: the security operations team that watches alerts and deals with attacks.
- Regulator: the official body that checks companies follow the law.
- Notice: the formal report a company must send after certain incidents.
- Aware: the moment the company is treated as knowing about the incident.
- Reportable: an incident that must be reported by law or contract.
- Drill: a practice run with a made-up incident.