Insights

NIS2 in Greece: Law 5160/2024 and Decision 1689/2025 explained

Who NIS2 covers in Greece under Law 5160/2024, what Ministerial Decision 1689/2025 requires in practice, and a 30-day plan for IT leads to get started.

If your company, or its Greek subsidiary, has 50 or more staff and works in energy, transport, health, manufacturing, food or IT services, NIS2 probably applies to you already. In Greece it is not a future directive. A law has been in force since November 2024, and a detailed ministerial decision has spelled out the technical measures since May 2025.

This guide is for IT leads and for international groups with Greek operations. It covers who is in scope, what the Greek rules actually require, and where to start.

This is general information, not legal advice.

Why it matters now

Directive (EU) 2022/2555 (NIS2) was transposed into Greek law by Law 5160/2024 (Government Gazette A' 195, 27 November 2024). The competent authority is the National Cybersecurity Authority (Εθνική Αρχή Κυβερνοασφάλειας), which supervises in-scope entities and acts as the single point of contact.

On 6 May 2025 Greece published Joint Ministerial Decision 1689/2025 (Gazette B' 2186), the "National Framework of Cybersecurity Requirements for Essential and Important Entities". It lists the concrete organisational and technical measures entities must apply. If you have read NIS2 at EU level, this decision is where Greece gets specific.

Penalties are significant. For breaches of the risk-management and incident-reporting duties, article 26 of Law 5160/2024 sets fines of up to €10 million or 2% of worldwide annual turnover for essential entities, and up to €7 million or 1.4% for important entities, whichever is higher. The law also allows a temporary ban on individuals in management roles.

Who is in scope

Size

As a rule, NIS2 covers medium-sized and larger enterprises as defined in Commission Recommendation 2003/361/EC. In practice, a company stops being "small" once it has 50 or more staff, or both turnover and balance sheet above €10 million.

There are exceptions. DNS service providers, top-level domain registries and trust service providers are in scope regardless of size. Smaller entities can also be designated if, for example, they are the sole provider of a critical service in the country.

Sector

Annex Example sectors
Annex I (sectors of high criticality) Energy, transport, banking, financial market infrastructure, health, drinking water, wastewater, digital infrastructure (telecoms, cloud, data centres), ICT service management (managed service and managed security providers), public administration
Annex II (other critical sectors) Postal and courier, waste management, chemicals, food, manufacturing (e.g. medical devices, electronics, machinery), digital providers (online marketplaces, search engines, social networks), research

The annex alone doesn't tell you your category. Under article 4 of Law 5160/2024, Annex I entities are generally essential only if they exceed the medium-enterprise ceilings, meaning large companies. Medium-sized Annex I entities, and Annex II entities, are important. The difference matters: it changes the maximum fine and how closely you are supervised. Sector source: EY, Law 5160/2024. The Authority offers a scope self-check tool.

Financial entities covered by DORA (Regulation (EU) 2022/2554) mainly follow DORA for risk management and incident reporting, as the more specific rule.

What you have to do

1. Register with the Authority

Entities self-declare on nis2register.cyber.gov.gr "without delay" and keep the entry up to date. You will need the company's Greek tax number (ΑΦΜ), business registry number (ΓΕΜΗ), legal representative, type of services, and its IP ranges and domain names.

That last item is harder than it looks. Groups with several brands often find forgotten subdomains, old marketing sites or a legacy mail server when they try to list everything.

2. Management accountability

The management body approves the risk-management programme, provides resources, and ensures periodic cybersecurity training for management and staff (Decision 1689/2025, art. 4).

3. A named security officer

You appoint an Information and Communication Systems Security Officer (ΥΑΣΠΕ) (Law 5160/2024, art. 15(5)), the contact point with the Authority, who reports directly to the management body (art. 7). For a subsidiary, decide early whether this person sits locally or at group level, and make sure the Greek board can show oversight.

4. Policies and technical measures

The decision requires a general security policy approved by management plus topic-specific policies (art. 6), covering among others access control, backups, cryptography and network security. Examples of technical measures from the same decision:

  • multi-factor authentication where required by data classification (art. 13)
  • changing default passwords at installation (art. 14)
  • installing security patches within a reasonable time, and periodic automated vulnerability scanning (art. 17)
  • at least an annual external penetration test (art. 18)
  • minimal open ports, network segmentation, secure remote access and DNS security (art. 19)
  • email filtering and blocking known malicious domains (art. 20)

5. Annual self-assessment

Every year, and after a serious incident, entities run a self-assessment using a guide issued by the Authority and send the results with a corrective-action plan (art. 18). Group-wide ISO 27001 evidence helps, but it will need mapping to the Greek framework.

6. Incident reporting

Significant incidents follow a staged process: an early warning within 24 hours, a notification within 72 hours and a final report within one month (Law 5160/2024, art. 16(4)). An incident is significant if it causes severe operational disruption or financial loss, or considerable damage to others.

A 30-day starter checklist

  • Run the Authority's scope check for each Greek entity.
  • Inventory every domain, subdomain and public IP the Greek entity uses.
  • Complete or update the registry entry.
  • Appoint the ΥΑΣΠΕ and record the decision in board minutes.
  • Enforce MFA on email, VPN and admin accounts.
  • Close unnecessary internet-facing ports, especially remote desktop.
  • Put patching and a recurring vulnerability scan on a schedule.
  • Test one restore from backup.
  • Write down who notifies the Authority within 24 hours, and how.

Common mistakes

Assuming group compliance covers Greece. The Greek decision has its own structure, registry and self-assessment. Map your controls to it rather than assuming.

Leaving it to the IT provider. Accountability stays with management, and the decision also requires supplier risk management (art. 12).

Policies without evidence. Accountability is shown with board minutes, training records, network diagrams and audit reports (art. 3), not a policy file nobody reads.

Forgotten internet-facing systems. An unmaintained server or subdomain is often the weakest point, and it is visible from outside before the internal team notices it.

Where to start

Much of NIS2 can't be seen from outside: policies, training, procedures. Some of it can: which systems you expose to the internet, whether you run unsupported software, and whether your website and email are configured correctly.

VelonRadar checks that public picture of your domain daily, and VelonGrade turns it into an A–F grade with the fixes that raise it. It reads public information only, unless you choose to connect your own tools, so it doesn't replace a penetration test or the self-assessment. It is a quick way to see what an attacker, or an insurer, sees first. We're in private beta and the check is free: request it here.

Want us to check this for you?

A free check using public information only. We reply within one working day.

Free check