videocam_off
This livestream is currently offline
Check back later when the stream goes live
Up next in 10
🛡️ NIS2 Technical Implementation Guide🇪🇺
Is your organization ready for the NIS2 Directive? By October 17, 2024, all essential and important entities across the EU must comply with strict cybersecurity risk-management measures under the Commission Implementing Regulation (EU) 2024/2690.
In this video, we break down the technical and methodological requirements for compliance, aligning with global standards like ISO/IEC 27000, ETSI EN 319401, and CEN/TS 18026:2024.
🔍 What we cover:
✅ Risk Management Frameworks
✅ Incident Response & 24-hour Notification
✅ Business Continuity & Crisis Management
✅ Supply Chain Security
✅ Secure System Development & Maintenance
✅ Cyber Hygiene & Security Training
✅ Cryptography Policies
✅ HR Security Responsibilities
✅ Access Control & MFA
✅ Asset Inventory Management
✅ Physical & Environmental Security
Show More Show Less View Video Transcript
0:00
So, if your business operates in the EU,
0:02
you need to listen up. There's a major
0:05
shift happening in cyber security right
0:07
now. And honestly, ignoring it could be
0:09
a massively costly mistake. It's called
0:12
the NIS-2 directive, and it's basically
0:15
rewriting the rule book for how
0:17
companies have to protect themselves
0:18
online. Let's break down what it is, and
0:21
more importantly, what it actually means
0:23
for you. Look, this isn't just some
0:24
dramatic marketing quote anymore. It's
0:27
the official mindset behind European
0:29
law. We've moved past asking if a
0:31
business will face a cyber attack. The
0:33
real question now is when. And that
0:36
shift, you know, from possibility to
0:38
pure inevitability. That's exactly why
0:40
the U decided it needed to build a much,
0:43
much stronger shield. And these threats,
0:45
they're not just theoretical. This is
0:47
what's happening right now. According to
0:49
the EU's own cyber security agency, get
0:53
this. Over 41% of incidents are DDoS
0:57
attacks, which are designed simply to
0:59
knock you offline and paralyze your
1:01
operations. And right on its heels,
1:03
you've got ransomware making up almost
1:05
26% of attacks, literally holding your
1:07
business hostage. We're talking about
1:09
direct crippling assaults. And then
1:11
there's this number, 11,79.
1:15
That's the number of cyber incidents
1:17
tracked in the EU over just the last
1:19
year. Now to put that in perspective and
1:22
this is what's really alarming. The year
1:24
before that the number was just around
1:27
2500.
1:29
This isn't just a small increase. It's
1:31
an absolute explosion. The game has
1:33
totally changed. So you might be asking
1:36
what went wrong. I mean the EU already
1:39
had a cyber security law, the original
1:41
NIS directive. The idea was good but the
1:45
execution well it was a problem. Every
1:48
country kind of did its own thing,
1:50
interpreting the rules differently. The
1:52
result was this messy patchwork of
1:54
protection with huge dangerous gaps
1:57
which left the whole union at risk. The
2:00
old shield just wasn't cutting it. So
2:02
Europe basically went back to the
2:04
drawing board to build something way
2:05
more robust. And what they came up with
2:07
is the NIS-2 directive. Now this isn't
2:10
just some minor update. It's a complete
2:13
overhaul. It's designed to create one
2:15
single high standard of cyber security
2:17
for everyone. So, let's pop the hood and
2:20
see what's inside. At its heart, NIS2 is
2:22
all about one thing, resilience. It
2:25
massively expands the number of
2:27
industries that have to comply. And
2:29
maybe most importantly, it gets rid of
2:31
the vague guidelines and replaces them
2:33
with crystal clear, strict obligations.
2:36
It's about building a framework that can
2:38
actually handle the pressure of today's
2:40
cyber threats, not just one that looks
2:42
good on paper. The best way to think
2:43
about it is like a mandatory security
2:46
upgrade for the entire EU. NIS-2 casts a
2:49
much wider net pulling in whole new
2:52
sectors that were never covered before.
2:54
And for businesses, what this really
2:56
means is that all that ambiguity is
2:58
gone. Instead, you have direct
3:01
non-negotiable mandates on how to manage
3:03
risk and how to report incidents. The
3:06
goal here is to lift everybody up to a
3:08
higher, more consistent level of
3:10
security. So, how does NIS-2 apply all
3:13
these rules? Well, it starts by
3:15
splitting businesses into two main
3:17
categories. You're either essential or
3:20
you're important. Essential is exactly
3:22
what it sounds like. If your business
3:24
goes down, it could cause a major
3:26
crisis. We're talking energy grids,
3:28
hospitals, that kind of thing. Because
3:31
they're so critical, they face proactive
3:33
supervision, meaning regulators can show
3:35
up for inspections and audits anytime.
3:38
Important entities are still vital, but
3:40
a failure is seen as less catastrophic.
3:43
So, their supervision is mostly
3:44
reactive. It gets triggered after
3:46
something bad happens. The very first
3:49
thing you have to do is figure out which
3:51
bucket you're in. Okay. So, what does
3:53
this all mean for your actual day-to-day
3:55
work? The directives demands really boil
3:58
down to two main things you have to do.
4:01
First, how you manage your risks and
4:03
second, how you report incidents when
4:05
they happen. Let's start with risk
4:07
management. Article 21 says your
4:09
security measures have to be appropriate
4:11
and proportionate. Now, that's not some
4:13
one-sizefits-all checklist. It means
4:16
your defenses have to specifically match
4:18
your risks. And here's the key phrase,
4:20
all hazards approach. You're expected to
4:23
plan for pretty much everything. Not
4:25
just a hacker in a dark room, but state
4:27
sponsored attacks, an angry ex employee,
4:30
or even a physical disaster like a fire
4:32
in your server room. And the second
4:34
piece, incident reporting. This is where
4:36
the pressure really mounts. The second
4:38
you realize you've had a significant
4:40
incident, a clock starts ticking. You
4:42
have just 24 hours to file an early
4:45
warning to your national authority,
4:47
which is usually a CSIRT team. Then you
4:51
have to follow up within 72 hours with a
4:53
much more detailed report about the
4:55
impact and severity. That timeline is
4:58
incredibly tight. It means having an
5:00
incident response plan that's practiced
5:02
and ready to go is not a nice to have.
5:04
It's an absolute must. Okay, so the
5:07
rules are clear. They're strict. The big
5:10
question for everyone is how do you
5:11
actually get this done? Let's walk
5:14
through the playbook. Right, this is the
5:16
question that's probably on every
5:17
leader's mind at the moment. You've got
5:20
these new rules, you've got a deadline,
5:22
and the whole thing can feel pretty
5:23
overwhelming. But the path to getting
5:26
compliant really starts with one simple
5:28
thing. Taking a good, honest look at
5:31
where you are right now. The
5:32
professional tool for doing this is
5:34
called a cyber security maturity model.
5:36
Think of it like a full body health
5:38
checkup for your organization's cyber
5:40
defenses. It doesn't just look at your
5:42
tech. It assesses your processes, your
5:45
tools, and even your people's skills to
5:47
give you a really honest score. This
5:49
process is what shows you your blind
5:51
spots. And it gives you the one thing
5:53
you need most, a concrete step-by-step
5:55
road map to close those gaps and get
5:57
compliant. And what does that compliance
5:59
standard actually look like? Well, it's
6:01
a pretty comprehensive list of security
6:03
basics, and it's not just about
6:05
firewalls. We're talking about having
6:07
official written policies for everything
6:09
from handling incidents to business
6:11
continuity. It forces you to scrutinize
6:14
your entire supply chain because under
6:16
NICE 2, your vendor's risk is now your
6:18
risk. And it really drills down on
6:21
fundamentals like basic cyber training
6:23
for everyone and using strong
6:24
encryption. This is what good looks
6:27
like. So, we've covered what you need to
6:29
do. Now, let's talk about the
6:30
consequences if you don't. Because with
6:33
NIS-2, let me be clear, the stakes have
6:36
never been higher. First off, the
6:38
financial penalties are huge. For those
6:42
essential entities, you're looking at
6:43
fines up to €10 million or 2% of your
6:47
total global annual turnover. For
6:50
important entities, it's up to 7 million
6:53
or 1.4% of global turnover. And here's
6:56
the kicker. They'll hit you with
6:57
whichever of those two numbers is
6:59
higher. These fines are absolutely
7:02
designed to hurt even for the biggest
7:03
companies out there. But it isn't just
7:05
about the company's money. This this
7:08
right here is probably the biggest
7:11
change in NIS-2. It pierces the
7:14
corporate veil. Senior management
7:16
selects can now be held personally
7:19
liable for major security failures.
7:22
Regulators can even temporarily ban them
7:25
from holding management jobs. All of a
7:27
sudden, cyber security isn't just some
7:29
IT problem. It's a personal
7:31
responsibility for every single leader.
7:33
Which brings us to the real fundamental
7:35
question that NIS-2 is forcing every
7:37
organization in Europe to answer. Is
7:40
cyber security just a line item on your
7:42
budget, something you try to keep as low
7:44
as possible, or is it a core foundation
7:46
of your business, just as essential as
7:48
your product, your people, or your
7:50
capital? With these new rules, it's
7:52
pretty clear there's only one right
7:53
answer.
#Business & Industrial
#Law & Government