← Back to the full issueComing soon visits
Respond

Your business could stop tomorrow. Who has prepared the first 24 hours?

Listen to the analysis

AIVoices and adaptation generated with NotebookLM; video illustrations generated with AI. Targeted local cuts or cards assisted by AI where indicated. Automatic transcription may contain errors. Historical analysis of issue 007, without a current legal update. Later source captures do not establish the historical state. Original retained; no new voice.

Download captions

Read the transcript
This audio adaptation was generated with notebook L.M.
So imagine it's, I don't know, 8 a.m. on a Tuesday.
You sit down with your coffee, you open your laptop to start the day,
and nothing, just completely locked out of your own business operations.
Today we're doing a deep dive into a pretty chilling question from the
law-right newsletter back in October of 2026, which is,
"Who was prepared to your first 24 hours?"
You just don't have time to figure out the rules on the fly.
I mean, to understand the urgency here in late 2026,
you just have to look at the numbers coming out of the Center for Cyber
Security Belgium, or the CCB.
What were the numbers looking like?
Well, between January 1st and September 28th,
they received 588 breach notifications, which to put that in perspective,
almost eclipses the 635 notifications they saw in all of 2025.
Wow, so nearly a whole year's worth of reports in just nine months.
It really makes it feel like an attack is just inevitable at this point.
Yeah, though we do have to be a bit careful with how we use those numbers.
Like how?
Well, they reflect reports received over two different periods, right?
It's not a complete census of every single attack,
or even unique victims for that matter.
Oh, got it. So you can't just like plug those figures into a calculator to figure
out your own small businesses, individual probability of getting hit.
Exactly. They aren't a probability metric at all,
but they are a vital signal. A signal that the landscape is highly active,
and that your operations need testing before you become part of those statistics.
Under the GDPR, you have to notify authorities without undue delay,
and wear feasible within 72 hours of awareness unless the risk is unlikely.
Wait, 72 hours? That is not a lot of time. What if it's a really bad breach?
If it's a high-risk situation, you hit article 34 conditions.
That means the breach poses a serious threat to people's personal freedoms or rights.
So in that case, you have to communicate with those individuals directly,
not just tell the regulators.
Juggling all of that while your systems are completely down sounds like a nightmare,
especially since, well, in Belgium,
the Data Protection Authority won't even just take an email, right?
Nope, they will not process a simple email.
They mandate that reporting goes through their specific online portal.
It's like a cruel catch-22.
Your house is on fire, but the fire department will only take your call
if you use the flaming landline inside the kitchen.
Like, you're locked out of your digital infrastructure,
yet you are required to navigate a complex digital portal to report the problem.
Exactly. And the only way to round that paradox is having an offline anchor.
The newsletter's author actually outlines a few preparedness proposals for this.
What kind of proposals?
Things like keeping a physical crisis sheet,
mapping out a strict timeline, and running a fictional 30-minute exercise.
I mean, doing a 30-minute exercise sounds great,
but does that actually guarantee you won't have an incident?
Oh, absolutely not.
These proposals carry no guarantee of preventing incidents.
But what they do is stop you from making
disastrously improvised decisions when the pressure is really on.
Because improvised decisions are usually the worst ones.
I remember in the newsletter's fictional scenario,
a supplier suggests just restarting the frozen computers.
Yes, the reboot.
I mean, I think anyone's immediate desperate instinct is to just reboot the machines,
you know, just hoping it flushes the glitch and saves the workday.
That offline crisis sheet becomes vital
because it separates the established facts from the unknowns.
Right, like, it dictates who your authorized technical contacts are,
so you aren't just taking random advice to pull plugs,
but instead getting validated instructions on how to isolate the network.
Exactly, isolating the network while preserving that RAM data.
A useful response is built entirely on those known responsibilities and preserved evidence.
Makes sense.
The goal of these offline proposals isn't to solve the technical crisis in five minutes.
It's to stabilize the situation.
So the technical experts and legal teams actually have a baseline to work from.
It all comes back to mapping out the escape route before you smell smoke.
Definitely.
So to wrap this up, think about this.
If you're a business lost all digital access right this second,
who is the very first person you would call?
And more importantly, do you actually have their number written down on a
physical piece of paper?
Something to think about.

A useful response begins with known responsibilities and preserved evidence, before the search for someone to blame.

Areas of lawCybersecurityPersonal dataGovernance
Keywords#incident#NIS2#notification#continuity

Case statusSources revisited on 6 October 2026 · general information, subject to the particular circumstances.

Original conceptual illustration made with AI assistance; no real event or person depicted.
Image and licence. Original conceptual illustration made with AI assistance; no real event or person depicted.

01

A Belgian signal worth preparing for

For its Closed Business Day campaign launched on 5 October, the Centre for Cybersecurity Belgium reports 588 notifications between 1 January and 28 September 2026, compared with 635 throughout 2025. These are reports received by the CCB, not a census of all attacks or unique victims. The comparison also covers different periods. [1]

The figures support preparing an exercise. They do not calculate the probability of an attack on a particular small business. A useful scenario tests your actual operations: unavailable files, a suspicious mailbox or an unreachable provider. Who can decide, and which communication channel will still work?

02

Different duties, different starting points

NIS2 does not automatically cover every business. For an in-scope entity facing a significant incident, the CCB describes an early warning within 24 hours and an incident notification within 72 hours after becoming aware. Specific rules exist, including for trust service providers. Scope and incident classification must be established before applying the timetable. [2]

The GDPR asks a separate question: has there been a personal data breach? The controller must notify the competent supervisory authority without undue delay and, where feasible, within 72 hours of awareness, unless the breach is unlikely to result in a risk to individuals’ rights and freedoms. A high risk may also require communication to affected people, subject to Article 34. Internal documentation remains necessary. [3,4]

Both assessments may be required. An email to the IT supplier replaces neither. Insurance conditions, client commitments and sector-specific rules also need examination. Information may be supplied in stages; waiting for complete certainty can jeopardise a deadline. Equally, do not label every outage a data leak without investigating the facts. [2–4]

03

The Law Right approach: a response sheet that works offline

  1. Prepare an independent crisis channel, authorised decision-makers and technical, legal and insurance contacts. Have specialists validate isolation instructions. Avoid improvised cleanup that erases evidence. Maintain a chronology of observations and decisions, recording what remained uncertain at each stage rather than reconstructing certainty afterwards.
  2. Separate established facts, suspicions and unanswered questions. Arrange appropriate preservation of relevant logs and material. Identify affected systems, information and essential services quickly. Avoid circulating unnecessary personal data within the response group; access should match each person’s role and the operational need.
  3. Run a thirty-minute exercise using a fictional case. Who can reach the right contact? Who assesses notification duties? Who authorises a client message? Preparation cannot guarantee freedom from incidents, but it reduces improvised decisions when time matters. Record the unclear instruction or missing authority uncovered by the exercise and assign its correction.
THE POWER TO CHOOSE · 03

Prepare. Detect. Respond.

Identify contacts, backups and essential services before an incident.

Explanatory visualisation, not a measurement or an individual legal conclusion.
→

Use the first hours to contain, understand and decide: prepare people as well as technology.

Sources and verificationOpen the sources +

Watch the story

AIVoices and adaptation generated with NotebookLM; video illustrations generated with AI. Targeted local cuts or cards assisted by AI where indicated. Automatic transcription may contain errors. Historical analysis of issue 007, without a current legal update. Later source captures do not establish the historical state. Original retained; no new voice.

Download captions

Read the transcript
This video adaptation was generated with Notebook LM.
So, we're diving into a really practical explainer today.
Looking back at an insightful piece of analysis
from the October 7th, 2026 edition of the Law Right newsletter.
The central question we're tackling,
"Your business could stop tomorrow.
Who has prepared the first 24 hours?"
Like I just mentioned, we are going to explore
exactly how to navigate those initial, absolutely critical moments
of a potential cyber incident, and we're going to do it
by focusing on calm, structured preparation.
Section 1, the fictional "morning" scenario.
Let's look at a hypothetical crisis.
Imagine this for a second.
It's 8 o'clock in the morning, your staff arrive,
they sit down at their desks, and suddenly realize
they literally cannot open any of their files.
So, you call up your IT supplier,
and they give you that classic, casual recommendation.
"Hey, just try restarting the computers."
But then, a client calls you up to report receiving
a really suspicious message sent directly in your firm's name.
At this exact moment, what are you even dealing with?
Is it just an outage, an intrusion, a massive data leak?
The terrifying reality is, nobody actually knows.
Because nobody knows what's happening yet,
the absolutely crucial point here is this.
Your very first task is to organize a response
without destroying the evidence
that's going to help you explain the event later.
Remember that supplier who suggested
just restarting the computers?
Well, an improvised cleanup like that
could completely erase the exact logs you're going to need.
So, your absolute priority right now?
Preservation.
Section 2, the 2026 Belgian signal.
Looking at CCB notifications.
To really understand why all this preparation is so vital,
let's look at a concrete signal launched alongside
the Center for Cybersecurity Belgium's
Closed Business Day campaign on October 5th, 2026.
The sheer volume of incident notifications here
is incredibly telling.
The CCB received 588 notifications
just between January 1st and September 28th of 2026.
If you compare that to the 635 notifications they received
throughout the entire year of 2025,
you're looking at nearly the exact same number of incidents,
but compressed into a much shorter window.
Now, we have to be super precise
about what these numbers actually mean.
These figures represent specific reports
received by the CCB over different periods.
That is it.
They are not some comprehensive census
of all attacks out there.
They aren't a count of unique victims,
and they absolutely do not calculate the probability
of an attack happening to your specific business.
But what they do provide, for sure,
is a very clear signal
that the operational environment is highly active.
Section 3, distinct duties and timetables.
When an incident actually hits,
the clock immediately starts ticking.
But you have to ask yourself which clock.
You really cannot just apply
a single blanket timetable here.
For instance, for specific in-scope entities
facing a significant incident,
the NIS-2 framework triggers a requirement
for an early warning within 24 hours.
The GDPR, on the other hand,
asks a completely separate question.
Has a personal data breach occurred?
You literally have to classify the incident
before you can even know which clock you're racing against.
Moving to Section 4, the GDPR reporting rules.
Let's look strictly at the GDPR for a moment.
The timeline for the data controller here is rigid.
Once you hit that point of awareness of a personal data breach,
you have to notify the competent supervisory authority
without undue delay.
And where feasible, this notification needs to happen
within 72 hours of awareness.
The only exception?
If the breach is unlikely to result
in a risk to individuals' rights and freedoms.
Honestly, that 72-hour window feels incredibly tight
when people are right in the middle of a chaotic crisis.
And guess what?
Your duties don't necessarily stop
at just notifying the authorities.
If the personal data breach is likely to result
in a high risk to the rights and freedoms of natural persons,
the GDPR requires direct communication
to the affected people,
subject to the specific conditions of Article 34.
So now you're juggling regulatory reporting
and victim communication all at the same time.
The method you use for that communication
is also strictly defined.
After notifying the Belgian Data Protection Authority,
you absolutely must use their dedicated reporting portal.
If you panic and try to just send off a simple email
to notify them of a breach,
they've made it crystal clear it will not be processed.
You have to follow their established channels.
Section 5, Offline Preparedness Proposals.
So keeping all these complex legal frameworks in mind,
how do you actually operate when your screens just go dark?
The author of the Law Right article
proposes a really practical approach.
First up, prep an offline crisis sheet
and an independent communication channel,
mostly because your normal email is probably compromised.
Second, have specialists validate your isolation instructions
so you can actually contain the incident
while still preserving the evidence.
And third, maintain a strict written chronology,
making sure to carefully separate established facts
from mere suspicions.
Now, to ensure those steps will actually work
when you need them,
another great proposal is to run a 30-minute fictional exercise.
You can use a scenario exactly like the one we talked about earlier.
The goal here isn't to solve some massive technical puzzle,
it's to uncover missing authority or unclear instructions
long before a real crisis hits.
Like, who actually has the authority
to approve a client message when the entire network is down?
You've got to test your operations to find out.
Before we wrap up,
we do need to clearly define the nature of these recommendations.
It's vital to remember that these drafts remain proposals.
They are purely practical advice
belonging to the author of the newsletter,
and they create no universal legal duties whatsoever.
Furthermore, while they will absolutely enhance your response,
these steps offer no guarantee
of preventing incidents from happening in the first place.
And that brings us right to the core message
of this 2026 law-right analysis.
Preparation cannot guarantee freedom from incidents,
but it significantly reduces improvised decisions
when time matters most.
You really don't want to be guessing the law
or trying to figure out who's in charge while critical evidence
is literally being erased.
So, I'll leave you with this final, crucial question to consider
for your own organization.
Pre has prepared your first 24 hours.
Read the full issue

Law Right library

Return to every issue.

Each new issue expands the collection without replacing what came before.

Your network may not share an email address

Secure sign-in will become active once the app has been approved by the network. For this first issue, enter your email below. Your network choice is recorded only as the source; nothing is posted to your account.

LexiTalk to Lexi