WEBVTT

1
00:00:00.000 --> 00:00:03.200
This video adaptation was generated with Notebook LM.

2
00:00:03.200 --> 00:00:06.000
So, we're diving into a really practical explainer today.

3
00:00:06.000 --> 00:00:08.000
Looking back at an insightful piece of analysis

4
00:00:08.000 --> 00:00:12.000
from the October 7th, 2026 edition of the Law Right newsletter.

5
00:00:12.000 --> 00:00:14.000
The central question we're tackling,

6
00:00:14.000 --> 00:00:16.000
"Your business could stop tomorrow.

7
00:00:16.000 --> 00:00:19.000
Who has prepared the first 24 hours?"

8
00:00:19.000 --> 00:00:21.000
Like I just mentioned, we are going to explore

9
00:00:21.000 --> 00:00:25.000
exactly how to navigate those initial, absolutely critical moments

10
00:00:25.000 --> 00:00:27.000
of a potential cyber incident, and we're going to do it

11
00:00:27.000 --> 00:00:30.000
by focusing on calm, structured preparation.

12
00:00:30.000 --> 00:00:33.000
Section 1, the fictional "morning" scenario.

13
00:00:33.000 --> 00:00:36.000
Let's look at a hypothetical crisis.

14
00:00:36.000 --> 00:00:38.000
Imagine this for a second.

15
00:00:38.000 --> 00:00:40.000
It's 8 o'clock in the morning, your staff arrive,

16
00:00:40.000 --> 00:00:43.000
they sit down at their desks, and suddenly realize

17
00:00:43.000 --> 00:00:46.000
they literally cannot open any of their files.

18
00:00:46.000 --> 00:00:48.000
So, you call up your IT supplier,

19
00:00:48.000 --> 00:00:51.000
and they give you that classic, casual recommendation.

20
00:00:51.000 --> 00:00:54.000
"Hey, just try restarting the computers."

21
00:00:54.000 --> 00:00:57.000
But then, a client calls you up to report receiving

22
00:00:57.000 --> 00:01:01.000
a really suspicious message sent directly in your firm's name.

23
00:01:01.000 --> 00:01:04.000
At this exact moment, what are you even dealing with?

24
00:01:04.000 --> 00:01:08.000
Is it just an outage, an intrusion, a massive data leak?

25
00:01:08.000 --> 00:01:12.000
The terrifying reality is, nobody actually knows.

26
00:01:12.000 --> 00:01:14.000
Because nobody knows what's happening yet,

27
00:01:14.000 --> 00:01:17.000
the absolutely crucial point here is this.

28
00:01:17.000 --> 00:01:19.000
Your very first task is to organize a response

29
00:01:19.000 --> 00:01:21.000
without destroying the evidence

30
00:01:21.000 --> 00:01:23.000
that's going to help you explain the event later.

31
00:01:23.000 --> 00:01:25.000
Remember that supplier who suggested

32
00:01:25.000 --> 00:01:27.000
just restarting the computers?

33
00:01:27.000 --> 00:01:29.000
Well, an improvised cleanup like that

34
00:01:29.000 --> 00:01:32.000
could completely erase the exact logs you're going to need.

35
00:01:32.000 --> 00:01:34.000
So, your absolute priority right now?

36
00:01:34.000 --> 00:01:35.000
Preservation.

37
00:01:35.000 --> 00:01:38.000
Section 2, the 2026 Belgian signal.

38
00:01:38.000 --> 00:01:40.000
Looking at CCB notifications.

39
00:01:40.000 --> 00:01:44.000
To really understand why all this preparation is so vital,

40
00:01:44.000 --> 00:01:46.000
let's look at a concrete signal launched alongside

41
00:01:46.000 --> 00:01:48.000
the Center for Cybersecurity Belgium's

42
00:01:48.000 --> 00:01:52.000
Closed Business Day campaign on October 5th, 2026.

43
00:01:52.000 --> 00:01:54.000
The sheer volume of incident notifications here

44
00:01:54.000 --> 00:01:56.000
is incredibly telling.

45
00:01:56.000 --> 00:01:59.000
The CCB received 588 notifications

46
00:01:59.000 --> 00:02:03.000
just between January 1st and September 28th of 2026.

47
00:02:03.000 --> 00:02:06.000
If you compare that to the 635 notifications they received

48
00:02:06.000 --> 00:02:09.000
throughout the entire year of 2025,

49
00:02:09.000 --> 00:02:11.000
you're looking at nearly the exact same number of incidents,

50
00:02:11.000 --> 00:02:14.000
but compressed into a much shorter window.

51
00:02:14.000 --> 00:02:16.000
Now, we have to be super precise

52
00:02:16.000 --> 00:02:18.000
about what these numbers actually mean.

53
00:02:18.000 --> 00:02:20.000
These figures represent specific reports

54
00:02:20.000 --> 00:02:22.000
received by the CCB over different periods.

55
00:02:22.000 --> 00:02:23.000
That is it.

56
00:02:23.000 --> 00:02:26.000
They are not some comprehensive census

57
00:02:26.000 --> 00:02:27.000
of all attacks out there.

58
00:02:27.000 --> 00:02:29.000
They aren't a count of unique victims,

59
00:02:29.000 --> 00:02:31.000
and they absolutely do not calculate the probability

60
00:02:31.000 --> 00:02:34.000
of an attack happening to your specific business.

61
00:02:34.000 --> 00:02:36.000
But what they do provide, for sure,

62
00:02:36.000 --> 00:02:37.000
is a very clear signal

63
00:02:37.000 --> 00:02:40.000
that the operational environment is highly active.

64
00:02:40.000 --> 00:02:43.000
Section 3, distinct duties and timetables.

65
00:02:43.000 --> 00:02:45.000
When an incident actually hits,

66
00:02:45.000 --> 00:02:47.000
the clock immediately starts ticking.

67
00:02:47.000 --> 00:02:50.000
But you have to ask yourself which clock.

68
00:02:50.000 --> 00:02:52.000
You really cannot just apply

69
00:02:52.000 --> 00:02:54.000
a single blanket timetable here.

70
00:02:54.000 --> 00:02:56.000
For instance, for specific in-scope entities

71
00:02:56.000 --> 00:02:58.000
facing a significant incident,

72
00:02:58.000 --> 00:03:00.000
the NIS-2 framework triggers a requirement

73
00:03:00.000 --> 00:03:02.000
for an early warning within 24 hours.

74
00:03:02.000 --> 00:03:04.000
The GDPR, on the other hand,

75
00:03:04.000 --> 00:03:06.000
asks a completely separate question.

76
00:03:06.000 --> 00:03:08.000
Has a personal data breach occurred?

77
00:03:08.000 --> 00:03:10.000
You literally have to classify the incident

78
00:03:10.000 --> 00:03:13.000
before you can even know which clock you're racing against.

79
00:03:13.000 --> 00:03:16.000
Moving to Section 4, the GDPR reporting rules.

80
00:03:17.000 --> 00:03:20.000
Let's look strictly at the GDPR for a moment.

81
00:03:20.000 --> 00:03:23.000
The timeline for the data controller here is rigid.

82
00:03:23.000 --> 00:03:26.000
Once you hit that point of awareness of a personal data breach,

83
00:03:26.000 --> 00:03:29.000
you have to notify the competent supervisory authority

84
00:03:29.000 --> 00:03:30.000
without undue delay.

85
00:03:30.000 --> 00:03:33.000
And where feasible, this notification needs to happen

86
00:03:33.000 --> 00:03:35.000
within 72 hours of awareness.

87
00:03:35.000 --> 00:03:37.000
The only exception?

88
00:03:37.000 --> 00:03:39.000
If the breach is unlikely to result

89
00:03:39.000 --> 00:03:41.000
in a risk to individuals' rights and freedoms.

90
00:03:41.000 --> 00:03:45.000
Honestly, that 72-hour window feels incredibly tight

91
00:03:45.000 --> 00:03:48.000
when people are right in the middle of a chaotic crisis.

92
00:03:48.000 --> 00:03:49.000
And guess what?

93
00:03:49.000 --> 00:03:51.000
Your duties don't necessarily stop

94
00:03:51.000 --> 00:03:53.000
at just notifying the authorities.

95
00:03:53.000 --> 00:03:55.000
If the personal data breach is likely to result

96
00:03:55.000 --> 00:03:58.000
in a high risk to the rights and freedoms of natural persons,

97
00:03:58.000 --> 00:04:00.000
the GDPR requires direct communication

98
00:04:00.000 --> 00:04:01.000
to the affected people,

99
00:04:01.000 --> 00:04:04.000
subject to the specific conditions of Article 34.

100
00:04:04.000 --> 00:04:07.000
So now you're juggling regulatory reporting

101
00:04:07.000 --> 00:04:10.000
and victim communication all at the same time.

102
00:04:10.000 --> 00:04:12.000
The method you use for that communication

103
00:04:12.000 --> 00:04:14.000
is also strictly defined.

104
00:04:14.000 --> 00:04:16.000
After notifying the Belgian Data Protection Authority,

105
00:04:16.000 --> 00:04:19.000
you absolutely must use their dedicated reporting portal.

106
00:04:19.000 --> 00:04:22.000
If you panic and try to just send off a simple email

107
00:04:22.000 --> 00:04:23.000
to notify them of a breach,

108
00:04:23.000 --> 00:04:26.000
they've made it crystal clear it will not be processed.

109
00:04:26.000 --> 00:04:29.000
You have to follow their established channels.

110
00:04:29.000 --> 00:04:32.000
Section 5, Offline Preparedness Proposals.

111
00:04:32.000 --> 00:04:35.000
So keeping all these complex legal frameworks in mind,

112
00:04:35.000 --> 00:04:38.000
how do you actually operate when your screens just go dark?

113
00:04:38.000 --> 00:04:40.000
The author of the Law Right article

114
00:04:40.000 --> 00:04:42.000
proposes a really practical approach.

115
00:04:42.000 --> 00:04:44.000
First up, prep an offline crisis sheet

116
00:04:44.000 --> 00:04:46.000
and an independent communication channel,

117
00:04:46.000 --> 00:04:49.000
mostly because your normal email is probably compromised.

118
00:04:49.000 --> 00:04:52.000
Second, have specialists validate your isolation instructions

119
00:04:52.000 --> 00:04:54.000
so you can actually contain the incident

120
00:04:54.000 --> 00:04:56.000
while still preserving the evidence.

121
00:04:56.000 --> 00:04:59.000
And third, maintain a strict written chronology,

122
00:04:59.000 --> 00:05:01.000
making sure to carefully separate established facts

123
00:05:01.000 --> 00:05:03.000
from mere suspicions.

124
00:05:03.000 --> 00:05:05.000
Now, to ensure those steps will actually work

125
00:05:05.000 --> 00:05:06.000
when you need them,

126
00:05:06.000 --> 00:05:10.000
another great proposal is to run a 30-minute fictional exercise.

127
00:05:10.000 --> 00:05:13.000
You can use a scenario exactly like the one we talked about earlier.

128
00:05:13.000 --> 00:05:16.000
The goal here isn't to solve some massive technical puzzle,

129
00:05:16.000 --> 00:05:19.000
it's to uncover missing authority or unclear instructions

130
00:05:19.000 --> 00:05:21.000
long before a real crisis hits.

131
00:05:21.000 --> 00:05:23.000
Like, who actually has the authority

132
00:05:23.000 --> 00:05:26.000
to approve a client message when the entire network is down?

133
00:05:26.000 --> 00:05:28.000
You've got to test your operations to find out.

134
00:05:28.000 --> 00:05:30.000
Before we wrap up,

135
00:05:30.000 --> 00:05:33.000
we do need to clearly define the nature of these recommendations.

136
00:05:33.000 --> 00:05:36.000
It's vital to remember that these drafts remain proposals.

137
00:05:36.000 --> 00:05:38.000
They are purely practical advice

138
00:05:38.000 --> 00:05:40.000
belonging to the author of the newsletter,

139
00:05:40.000 --> 00:05:43.000
and they create no universal legal duties whatsoever.

140
00:05:43.000 --> 00:05:46.000
Furthermore, while they will absolutely enhance your response,

141
00:05:46.000 --> 00:05:48.000
these steps offer no guarantee

142
00:05:48.000 --> 00:05:51.000
of preventing incidents from happening in the first place.

143
00:05:51.000 --> 00:05:53.000
And that brings us right to the core message

144
00:05:53.000 --> 00:05:55.000
of this 2026 law-right analysis.

145
00:05:55.000 --> 00:05:58.000
Preparation cannot guarantee freedom from incidents,

146
00:05:58.000 --> 00:06:01.000
but it significantly reduces improvised decisions

147
00:06:01.000 --> 00:06:03.000
when time matters most.

148
00:06:03.000 --> 00:06:05.000
You really don't want to be guessing the law

149
00:06:05.000 --> 00:06:08.000
or trying to figure out who's in charge while critical evidence

150
00:06:08.000 --> 00:06:10.000
is literally being erased.

151
00:06:10.000 --> 00:06:13.000
So, I'll leave you with this final, crucial question to consider

152
00:06:13.000 --> 00:06:15.000
for your own organization.

153
00:06:15.000 --> 00:06:17.000
Pre has prepared your first 24 hours.
