In many companies, information security is still treated as an IT issue. As a result, it gets delegated.

→ To the IT department.
→ To external service providers.
→ To “someone who takes care of it.”

What gets overlooked in the process:
Security is not a technical issue.
Security is a business decision.

The good news:
The independent repair shop just around the corner.
A quick look, parts ordered, installed by the afternoon.
And they even threw in a really good cup of coffee for free.

The reality for business leaders?
NIS-2 is fundamentally changing the landscape:
→ Personal liability becomes a reality
→ Responsibility can no longer be delegated (spoiler: it never really could be in the first place!)
→ Ignorance is no defense

Anyone who still believes they can “outsource” information security is losing control over one of the biggest risks facing their company.

The key point?
Resilient companies do things differently:
→ They manage information security from the CEO’s office
→ They embed the issue at the executive level
→ They make informed risk decisions

Because in the end, it’s not about firewalls or tools. It’s about:

  • Business models
  • Delivery capability
  • Reputation
  • Ensuring business continuity

In plain language:
Information security belongs on the executive board’s agenda.
Not in the server room.

Who in your company is REALLY responsible for information security?

Tags

Share post

More articles

One of the core competences of cloud service providers is the safeguarding of infrastructures with regard to IT security. But what should be taken into account when using the cloud? The cloud has many advantages:...
Although the new year is already a few days old, annual kick-off events are still in full swing everywhere. So we too have been thinking about what to expect in terms of information and IT...
ISO 27001 – Management of technical vulnerabilities The newly published ISO 27001:2022 in October 2022 brings a restructured catalogue of measures. Among other things, the new measure A.8.8 – Management of technical vulnerabilities – was...