WEBVTT

1
00:00:00.000 --> 00:00:03.840
This audio adaptation was generated with notebook L.M.

2
00:00:03.840 --> 00:00:08.000
So imagine it's, I don't know, 8 a.m. on a Tuesday.

3
00:00:08.000 --> 00:00:11.040
You sit down with your coffee, you open your laptop to start the day,

4
00:00:11.040 --> 00:00:16.800
and nothing, just completely locked out of your own business operations.

5
00:00:16.800 --> 00:00:19.520
Today we're doing a deep dive into a pretty chilling question from the

6
00:00:19.520 --> 00:00:23.360
law-right newsletter back in October of 2026, which is,

7
00:00:23.360 --> 00:00:25.760
"Who was prepared to your first 24 hours?"

8
00:00:25.760 --> 00:00:28.560
You just don't have time to figure out the rules on the fly.

9
00:00:28.560 --> 00:00:31.840
I mean, to understand the urgency here in late 2026,

10
00:00:31.840 --> 00:00:34.480
you just have to look at the numbers coming out of the Center for Cyber

11
00:00:34.480 --> 00:00:36.880
Security Belgium, or the CCB.

12
00:00:36.880 --> 00:00:38.480
What were the numbers looking like?

13
00:00:38.480 --> 00:00:41.840
Well, between January 1st and September 28th,

14
00:00:41.840 --> 00:00:46.800
they received 588 breach notifications, which to put that in perspective,

15
00:00:46.800 --> 00:00:51.520
almost eclipses the 635 notifications they saw in all of 2025.

16
00:00:51.520 --> 00:00:54.960
Wow, so nearly a whole year's worth of reports in just nine months.

17
00:00:54.960 --> 00:00:58.880
It really makes it feel like an attack is just inevitable at this point.

18
00:00:58.880 --> 00:01:02.560
Yeah, though we do have to be a bit careful with how we use those numbers.

19
00:01:02.560 --> 00:01:03.600
Like how?

20
00:01:03.600 --> 00:01:07.840
Well, they reflect reports received over two different periods, right?

21
00:01:07.840 --> 00:01:10.320
It's not a complete census of every single attack,

22
00:01:10.320 --> 00:01:12.320
or even unique victims for that matter.

23
00:01:12.320 --> 00:01:16.400
Oh, got it. So you can't just like plug those figures into a calculator to figure

24
00:01:16.400 --> 00:01:20.400
out your own small businesses, individual probability of getting hit.

25
00:01:20.400 --> 00:01:23.520
Exactly. They aren't a probability metric at all,

26
00:01:23.520 --> 00:01:28.640
but they are a vital signal. A signal that the landscape is highly active,

27
00:01:28.640 --> 00:01:32.640
and that your operations need testing before you become part of those statistics.

28
00:01:33.360 --> 00:01:37.360
Under the GDPR, you have to notify authorities without undue delay,

29
00:01:37.360 --> 00:01:42.160
and wear feasible within 72 hours of awareness unless the risk is unlikely.

30
00:01:42.160 --> 00:01:47.680
Wait, 72 hours? That is not a lot of time. What if it's a really bad breach?

31
00:01:47.680 --> 00:01:50.720
If it's a high-risk situation, you hit article 34 conditions.

32
00:01:51.280 --> 00:01:54.960
That means the breach poses a serious threat to people's personal freedoms or rights.

33
00:01:55.520 --> 00:01:58.400
So in that case, you have to communicate with those individuals directly,

34
00:01:58.400 --> 00:01:59.920
not just tell the regulators.

35
00:01:59.920 --> 00:02:03.520
Juggling all of that while your systems are completely down sounds like a nightmare,

36
00:02:03.520 --> 00:02:06.000
especially since, well, in Belgium,

37
00:02:06.000 --> 00:02:09.360
the Data Protection Authority won't even just take an email, right?

38
00:02:09.360 --> 00:02:11.840
Nope, they will not process a simple email.

39
00:02:11.840 --> 00:02:15.120
They mandate that reporting goes through their specific online portal.

40
00:02:15.120 --> 00:02:16.880
It's like a cruel catch-22.

41
00:02:16.880 --> 00:02:19.760
Your house is on fire, but the fire department will only take your call

42
00:02:19.760 --> 00:02:22.640
if you use the flaming landline inside the kitchen.

43
00:02:22.640 --> 00:02:25.040
Like, you're locked out of your digital infrastructure,

44
00:02:25.040 --> 00:02:29.200
yet you are required to navigate a complex digital portal to report the problem.

45
00:02:29.200 --> 00:02:34.320
Exactly. And the only way to round that paradox is having an offline anchor.

46
00:02:34.880 --> 00:02:38.560
The newsletter's author actually outlines a few preparedness proposals for this.

47
00:02:39.280 --> 00:02:40.560
What kind of proposals?

48
00:02:40.560 --> 00:02:43.200
Things like keeping a physical crisis sheet,

49
00:02:43.200 --> 00:02:47.600
mapping out a strict timeline, and running a fictional 30-minute exercise.

50
00:02:48.480 --> 00:02:51.360
I mean, doing a 30-minute exercise sounds great,

51
00:02:51.360 --> 00:02:54.240
but does that actually guarantee you won't have an incident?

52
00:02:54.240 --> 00:02:55.360
Oh, absolutely not.

53
00:02:56.000 --> 00:02:58.880
These proposals carry no guarantee of preventing incidents.

54
00:02:59.440 --> 00:03:01.760
But what they do is stop you from making

55
00:03:01.760 --> 00:03:05.120
disastrously improvised decisions when the pressure is really on.

56
00:03:05.120 --> 00:03:08.160
Because improvised decisions are usually the worst ones.

57
00:03:08.160 --> 00:03:10.800
I remember in the newsletter's fictional scenario,

58
00:03:10.800 --> 00:03:14.640
a supplier suggests just restarting the frozen computers.

59
00:03:14.640 --> 00:03:15.760
Yes, the reboot.

60
00:03:16.400 --> 00:03:20.960
I mean, I think anyone's immediate desperate instinct is to just reboot the machines,

61
00:03:20.960 --> 00:03:24.720
you know, just hoping it flushes the glitch and saves the workday.

62
00:03:24.720 --> 00:03:26.640
That offline crisis sheet becomes vital

63
00:03:26.640 --> 00:03:29.440
because it separates the established facts from the unknowns.

64
00:03:30.000 --> 00:03:33.040
Right, like, it dictates who your authorized technical contacts are,

65
00:03:33.040 --> 00:03:35.680
so you aren't just taking random advice to pull plugs,

66
00:03:35.680 --> 00:03:39.280
but instead getting validated instructions on how to isolate the network.

67
00:03:39.280 --> 00:03:43.120
Exactly, isolating the network while preserving that RAM data.

68
00:03:43.120 --> 00:03:47.520
A useful response is built entirely on those known responsibilities and preserved evidence.

69
00:03:47.520 --> 00:03:48.480
Makes sense.

70
00:03:48.480 --> 00:03:52.720
The goal of these offline proposals isn't to solve the technical crisis in five minutes.

71
00:03:52.720 --> 00:03:54.880
It's to stabilize the situation.

72
00:03:54.880 --> 00:03:58.560
So the technical experts and legal teams actually have a baseline to work from.

73
00:03:58.560 --> 00:04:01.920
It all comes back to mapping out the escape route before you smell smoke.

74
00:04:01.920 --> 00:04:02.960
Definitely.

75
00:04:02.960 --> 00:04:04.880
So to wrap this up, think about this.

76
00:04:04.880 --> 00:04:07.760
If you're a business lost all digital access right this second,

77
00:04:07.760 --> 00:04:10.000
who is the very first person you would call?

78
00:04:10.000 --> 00:04:13.360
And more importantly, do you actually have their number written down on a

79
00:04:13.360 --> 00:04:15.120
physical piece of paper?

80
00:04:15.120 --> 00:04:16.000
Something to think about.
