NIS2 compliance in Greece: the technical measures (Law 5160/2024)

· 9 min read · security · compliance

Most NIS2 guides for Greece are written by law firms. This one is for the people who have to build it: what Law 5160/2024 and its ministerial decisions actually require, and the order we would implement it in.

Not legal advice. This is an engineer's reading of the law and the ministerial decisions, written to help you plan the technical work. Whether you are in scope, and as which type of entity, is a legal question. Confirm it with your lawyer and the National Cybersecurity Authority before you rely on anything here.

NIS2 compliance in Greece means meeting Law 5160/2024 and the decisions issued under it: register with the National Cybersecurity Authority, appoint an in-house security officer (ΥΑΣΠΕ), implement the 22 requirement areas of Joint Ministerial Decision 1689/2025, report significant incidents within 24 and 72 hours, and run an annual self-assessment and external penetration test.

Everything below was checked against the official texts in November 2026. If you run on AWS, our NIS2 checklist for AWS is the service-by-service deep-dive; this guide covers the whole programme, whatever you run on.

Who is in scope

You are likely in scope if you are a medium or large company in a sector listed in the law's annexes. Some providers are in scope whatever their size, and many smaller suppliers feel NIS2 indirectly through their customers' contracts.

The Authority publishes a scope test (τεστ υπαγωγής) on its NIS2 page. Run it, then have a lawyer confirm the result. If you are a cloud, data centre, managed service or managed security provider, note that the EU Implementing Regulation 2024/2690 sets more detailed technical requirements for you, on top of the Greek framework.

Registration and the security officer (ΥΑΣΠΕ)

In-scope entities register on the Authority's platform and declare a named security officer. The general deadline has passed, so if you are in scope and not registered, this is the first thing to fix.

That second point changes how outside help fits. An external consultant, MSSP or fractional CTO can do much of the work and support the ΥΑΣΠΕ, but on our reading of the decision they cannot hold the role for you. Pick the internal person first and build the programme around them.

The required measures: Article 15 and KYA 1689/2025

Article 15 of Law 5160/2024 copies the ten minimum measures of Article 21 of the directive. KYA 1689/2025 (ΦΕΚ Β' 2186, 6 May 2025) turns them into 22 requirement areas (Articles 4 to 25) with concrete obligations. The table maps one to the other and shows what each means in a typical cloud or on-prem estate.

Law 5160/2024, Art. 15(2)KYA 1689/2025 articlesWhat you build
(a) Risk analysis and security policies4 governance, 5 risk management, 6 policies, 7 roles, 9 compliance monitoringRisk assessment and treatment plan, general security policy plus the 11 topic policies, board approval records
(b) Incident handling24 incident managementCentral, tamper-resistant logs with a defined retention period, alerting, a named incident coordinator on staff, runbook
(c) Business continuity, backups, crisis management25 continuity and crisis managementAutomated backups with restricted access, periodic restore tests, BIA, DR plan; crisis procedures for essential entities
(d) Supply-chain security12 suppliers and ICT providersInventory of direct ICT suppliers, security clauses in contracts, scoped third-party access
(e) Secure acquisition, development, maintenance, vulnerabilities14 secure configuration, 15 secure development, 16 change management, 17 vulnerabilitiesHardened baselines, code review and CI, controlled changes, patching in reasonable time (especially internet-facing systems), tested patches
(f) Assessing effectiveness8 independent audit (essential only), 18 effectivenessAnnual external pentest, annual self-assessment sent to the Authority; internal pentest and independent audits for essential entities
(g) Cyber hygiene and training20 malware protection, 21 trainingEndpoint protection with automatic updates, application control, email filtering, training with a minimum syllabus
(h) Cryptography22 cryptographyEncryption at rest and in transit, key management policy
(i) HR security, access control, asset management10 HR security, 11 assets, 13 access control, 23 physical securityAsset register covering on-prem and cloud, data classification, unique identities, least privilege, leaver process
(j) MFA and secure communications13 access control, 19 network securityMFA based on classification, firewalls, segmentation, controls on unknown devices

Reading the decision end to end, these are the obligations teams most often miss:

The decision applies proportionality (Article 3): size, data criticality and cost all count. That is a reason to scale controls to your risk, not a reason to skip a whole area.

Incident notification: 24 hours, 72 hours, one month

Significant incidents go to the Authority's CSIRT on a fixed clock that starts when you become aware of the incident, not when you finish investigating it.

StepDeadline (Art. 16)Content
Early warningWithin 24 hours of becoming awareSuspected malicious cause, possible cross-border impact
Incident notificationWithin 72 hours of becoming awareUpdate plus initial assessment of severity and impact, indicators of compromise
Intermediate reportOn request from the AuthorityStatus updates
Final reportWithin one month of the 72-hour notificationDetailed description, root cause, mitigations, cross-border impact

An incident is significant if it has caused or could cause severe operational disruption or financial loss, or considerable damage to others. Where an incident could affect your service recipients, you also have to tell them without undue delay. The engineering consequence: your logs must already answer "when did this start, what was touched, who was affected" on day one. Our incident response runbook template has a section you can adapt for the 24/72-hour reports.

What management is personally responsible for

The board approves the measures, oversees them and answers for failures. NIS2 is not something management can delegate to IT and forget.

A 90-day technical plan for an SME

Ninety days is enough to get from nothing to a defensible baseline with evidence, if the ΥΑΣΠΕ has a clear mandate and someone technical to do the work. This is the order we use.

Days 1 to 30: know what you have and close the obvious doors

Days 31 to 60: detection, recovery and the paperwork that matches

Days 61 to 90: prove it works

The controls are the same on every platform; only the tools change.

ControlAWSAzureOn-prem
Identity and MFAIAM Identity Center with your IdP (setup guide)Entra ID with Conditional AccessAD or Entra ID with MFA on VPN and admin access
Central, protected logsOrganization CloudTrail to a log-archive accountLog Analytics or Microsoft SentinelSyslog to a SIEM (for example Wazuh) on a separate host
Threat detectionGuardDuty, Security HubMicrosoft Defender for CloudEDR on endpoints and servers, IDS at the perimeter
Immutable backupsAWS Backup with vault lock, cross-accountAzure Backup immutable vaultsOffline or immutable copy outside the domain
Configuration baselineAWS Config, SCPsAzure PolicyCIS benchmarks, GPOs, configuration management
EncryptionKMSKey VaultDisk encryption, internal PKI, TLS everywhere

If you already have ISO 27001 or SOC 2

You have most of the substance. ISO 27001 covers much of the KYA's content, and SOC 2 evidence for access reviews, change management and incident response carries over (see our SOC 2 on AWS checklist). The Greek-specific gaps are usually the ΥΑΣΠΕ appointment, the 11 named policies in the official structure, the annual self-assessment and pentest, and the 24/72-hour reporting flow to the Authority's CSIRT.

Where to start this week

Run the Authority's scope test, check that you are registered and that a qualified ΥΑΣΠΕ is declared, then take the self-assessment once to see the size of the gap. Our free cloud readiness scorecard gives a quick technical baseline in the meantime.

If the gap list is long and your team is already busy shipping, that is the work we do. Our cloud audit measures your AWS, Azure or on-prem estate against these requirements and gives the ΥΑΣΠΕ a prioritised plan, and managed DevOps keeps the logging, backups, patching and evidence running afterwards, so the annual self-assessment is a report rather than a scramble.

Frequently asked questions

Which Greek decision lists the NIS2 security measures?

Joint Ministerial Decision 1689/2025 (ΦΕΚ Β' 2186, 6 May 2025) sets the national framework of cybersecurity requirements for essential and important entities under Law 5160/2024. It contains 22 requirement areas, from governance and risk management to backups, logging, penetration testing and incident management, applied proportionately to the size and risk of each entity.

Can an external consultant be our ΥΑΣΠΕ?

On our reading, no. Ministerial Decision 1899/2025 says the entity appoints one of its own executives, with an exception only for companies in the same group. The officer needs a relevant degree, five years of security experience, or a certification plus two years. Consultants can support the role. Confirm your case with a lawyer.

What are the NIS2 incident reporting deadlines in Greece?

For a significant incident, Article 16 of Law 5160/2024 requires an early warning to the National Cybersecurity Authority's CSIRT within 24 hours of becoming aware, an incident notification with an initial assessment within 72 hours, intermediate reports on request, and a final report within one month of the notification.

Do important entities need penetration tests under KYA 1689/2025?

Yes. Article 18 requires both essential and important entities to run an external penetration test at least once a year or after a serious incident, and to fix the findings based on a prioritised plan. Essential entities must also run an annual internal penetration test. Both types send an annual self-assessment to the Authority.

Tell us what you need