firefly corporate boardroom dark blue tones, eu regulatory document, cybersecurity concept, 642851

NIS2 & Your Business: What Greek Companies Need to Know

The regulation is live. The deadline has passed. Most Greek companies are still not ready.

The EU’s Network and Information Security Directive — NIS2 — came into force across member states in October 2024. It is the most significant piece of cyber security legislation the European Union has ever produced. It affects thousands of Greek companies across energy, transport, banking, healthcare, digital infrastructure, and manufacturing.

And yet, in boardrooms across Athens, Thessaloniki, and Piraeus, the conversation has barely started.

This is not an IT compliance exercise. NIS2 is a governance obligation — one that sits squarely on the desk of the CEO and the board, not the CISO. The penalties for non-compliance are not theoretical. The personal liability provisions are not boilerplate. And the window to get ahead of regulatory scrutiny is closing faster than most organisations realise.

This article is written for CEOs, CFOs, and board members who need to understand what NIS2 actually requires — in plain language, without the technical jargon.—

What Is NIS2, and Why Does It Matter More Than NIS1?

The original NIS Directive (2016) was the EU’s first attempt at a harmonised approach to cyber security across member states. It was, by most accounts, inconsistently implemented and too narrow in scope. NIS2 is its successor — and it is fundamentally different in three ways.

First, the scope is dramatically wider. NIS1 covered a relatively small number of “operators of essential services.” NIS2 covers two categories: Essential Entities and Important Entities. Essential Entities include sectors like energy, transport, banking, financial market infrastructure, health, drinking water, wastewater, digital infrastructure, and public administration. Important Entities add a second tier — including postal services, waste management, chemicals, food production, manufacturing, and digital providers.

If your company operates in any of these sectors and meets certain size thresholds (generally: 50+ employees or €10M+ annual turnover), NIS2 almost certainly applies to you.

Second, the obligations are more demanding. NIS2 requires organisations to implement risk management measures across ten specific areas, including incident handling, business continuity, supply chain security, access control, cryptography, and multi-factor authentication. These are not aspirational guidelines — they are mandatory requirements.

Third, the enforcement is real. NIS2 introduces fines of up to €10 million or 2% of global annual turnover for Essential Entities — whichever is higher. For Important Entities, the maximum is €7 million or 1.4% of global turnover. More significantly, it introduces personal liability for senior management. Under NIS2, CEOs and board members can be held personally responsible for cyber security failures.—

What Does NIS2 Actually Require of Your Organisation?

Article 21 of NIS2 sets out the core security measures that covered organisations must implement. Translated into board language, these fall into five practical obligations:

1. You Must Have a Risk Management Process

NIS2 requires organisations to conduct regular cyber risk assessments and implement proportionate security measures based on the results. This is not a one-time checkbox — it is an ongoing governance process. Your board must be able to demonstrate that you understand your cyber risk exposure and are actively managing it.

This is precisely where most Greek companies are weakest. Risk assessments exist — but they are typically compliance-driven, point-in-time exercises that produce reports nobody reads. NIS2 requires something more rigorous: a process that produces actionable intelligence, not administrative paperwork.

2. You Must Report Incidents — Fast

NIS2 introduces strict incident reporting timelines. Significant cyber incidents must be reported to the national competent authority within 24 hours of detection (early warning), with a full incident notification within 72 hours, and a final report within one month.

In Greece, the competent authority is the National Cyber Security Authority (ΕΑΠΔ). Your organisation must have a clear, tested incident response process that can meet these timelines. If you have never run an incident response exercise, you are not prepared.

3. Your Supply Chain Is Your Responsibility

One of the most significant expansions in NIS2 is supply chain security. You are now responsible for the cyber security posture of your critical suppliers and service providers. If a third-party vendor causes a breach of your systems, NIS2 does not treat that as a mitigating factor — it treats it as your failure to manage third-party risk.

For Greek companies with complex supplier relationships — particularly in shipping, manufacturing, and energy — this is a substantial new obligation.

4. Your Board Must Be Informed and Accountable

Article 20 of NIS2 is the provision that has received the least attention — and arguably deserves the most. It requires that management bodies of covered entities approve, oversee, and take accountability for cyber security risk management measures. Board members must receive adequate training to understand cyber risks.

This is not a technical requirement. It is a governance requirement. Your board cannot delegate cyber security entirely to the IT department and remain compliant with NIS2. The board must be able to demonstrate active oversight — which requires regular, meaningful reporting on cyber risk in terms the board can understand and act on.

5. You Must Register with the Competent Authority

Covered entities in Greece are required to register with the National Cyber Security Authority. Many organisations that fall within NIS2’s scope have not yet done so. This is not optional — and failure to register is itself a compliance failure.—

The Personal Liability Provision: What Every Greek CEO Needs to Understand

Article 20 of NIS2 goes further than most CEOs realise. It explicitly states that member states shall ensure that natural persons responsible for Essential or Important Entities can be held liable for infringements of NIS2 obligations.

In practice, this means that in the event of a significant cyber incident — particularly one that results from a failure of governance rather than an unforeseeable technical attack — the CEO or board members responsible for oversight can face personal sanctions. These may include temporary bans from management roles.

This provision changes the conversation fundamentally. Cyber security is no longer a matter of corporate liability alone. It is a matter of personal accountability for the individuals at the top of the organisation.

For a Greek CEO or CFO, the question is no longer “what does our IT department do about cyber security?” The question is: “can I personally demonstrate that I understood our cyber risk exposure and took proportionate action to manage it?”—

Where Most Greek Companies Are Today

Based on our advisory work across Greek organisations, we see three common situations:

The Unaware: Organisations that do not yet know whether NIS2 applies to them, have taken no steps toward compliance, and have no cyber risk governance process in place. These organisations face the highest regulatory risk.

The Administratively Compliant: Organisations that have engaged a consultant to produce a gap analysis report, have a document trail, but have not implemented meaningful changes to their risk management or governance processes. These organisations have reduced their exposure but remain vulnerable to substantive enforcement.

The Strategically Prepared: Organisations that have integrated NIS2 compliance into their broader cyber risk governance framework — with board-level reporting, quantified risk assessments, tested incident response procedures, and documented supply chain security reviews. These organisations are not just compliant — they have used NIS2 as a catalyst to build genuine resilience.

The difference between the second and third category is not primarily a matter of budget. It is a matter of approach. Compliance without substance is a liability. Compliance with substance is a competitive advantage.—

What Should Your Board Be Asking Right Now?

If you are a CEO, CFO, or board member of a Greek company that may fall within NIS2’s scope, these are the six questions your board should be able to answer today:

  1. Are we a covered entity under NIS2? Do we meet the sector and size criteria for Essential or Important Entity status?
  2. Have we registered with the ΕΑΠΔ? If not, when will we do so?
  3. What is our current cyber risk exposure, expressed in financial terms? Not a colour on a heat map — a number.
  4. Do we have a tested incident response process that can meet NIS2’s 24-hour and 72-hour reporting requirements?
  5. Have we assessed the cyber security posture of our critical suppliers? Do our contracts with third parties reflect NIS2’s supply chain requirements?
  6. Does our board receive regular, meaningful cyber risk reporting that enables active oversight — not just an annual briefing from the IT department?

If you cannot answer all six questions with confidence, you have work to do.—

The Cost of Getting This Wrong

The financial exposure from NIS2 non-compliance is real — but it is secondary to the operational and reputational consequences of a significant cyber incident in a poorly prepared organisation.

Consider the scenario: a Greek shipping company suffers a ransomware attack that disrupts port operations for 72 hours. Under NIS2, they are required to notify the competent authority within 24 hours. They have no incident response plan. They notify on day four. The investigation reveals that a third-party supplier was the entry point — and the company had no supply chain security review in place. The competent authority opens an enforcement investigation.

The fine — potentially millions of euros — is painful. The reputational damage with clients, partners, and investors is potentially more so. And the personal liability exposure for the CEO who signed off on the annual cyber security budget without understanding what it actually bought is the part nobody anticipated.

NIS2 compliance is not just about avoiding penalties. It is about building an organisation that can withstand the attacks that are coming — because they are coming.—

How Arctos Intelligence Can Help

Arctos Intelligence specialises in helping Greek CEOs, CFOs, and boards understand and manage cyber risk in financial terms. Our NIS2 & DORA Readiness engagement is a project-based service that delivers:

  • A full gap analysis against NIS2 Article 21 requirements
  • A prioritised remediation roadmap with cost estimates
  • A board-ready compliance report that demonstrates active governance oversight
  • Guidance on registration with the ΕΑΠΔ and ongoing reporting obligations

We do not produce compliance documents for the sake of compliance. We help organisations build the governance infrastructure that makes compliance meaningful — and that protects both the organisation and the individuals responsible for leading it.

If you are not certain whether NIS2 applies to your organisation, or if you know it applies and have not yet taken substantive action, the right time to start was six months ago. The second best time is now.—

Arctos Intelligence provides cyber risk quantification and advisory services to CEOs, CFOs, and boards across Greece, UAE, and the Balkans. All engagements are strictly confidential.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top