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.
- Sectors. Annex I (high criticality) covers energy, transport, banking, financial market infrastructure, health, drinking and waste water, digital infrastructure, ICT service management (managed service and managed security service providers), public administration and space. Annex II adds postal and courier, waste management, chemicals, food, manufacturing of medical devices, electronics, machinery and vehicles, digital providers (marketplaces, search engines, social networks) and research.
- Size. In practice, 50 or more employees, or annual turnover and balance sheet both above €10 million. Below that you are generally out of scope unless you are, for example, a DNS service provider, a TLD registry, a trust service provider or a public electronic communications provider.
- Essential or important. The law classes entities as essential (βασικές) or important (σημαντικές). Most security duties are the same; essential entities get proactive supervision, a few extra measures and higher fines.
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.
- Registration. Entities register at nis2register.cyber.gov.gr. After several extensions, the final deadline was 30 September 2025 (KYA 1990/2025). The same platform handles first-time registration and updates, and changes to your details have to be entered within three months (KYA 1381/2025). We found no newer deadline for late registrants as of November 2026, which means you should register now rather than wait for one.
- The ΥΑΣΠΕ. Article 15(5) of the law requires a security officer (Υπεύθυνος Ασφάλειας Συστημάτων Πληροφορικής και Επικοινωνιών) who handles all contact with the Authority and coordinates compliance and incident reporting. Ministerial Decision 1899/2025, in force since 1 November 2025, sets the rules: the officer must be one of your own executives (another company in the same group is the only exception), with either a relevant degree, five years of security experience, or a recognised certification plus two years of experience. The role cannot be combined with the GDPR data protection officer, and the officer reports directly to management.
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 articles | What you build |
|---|---|---|
| (a) Risk analysis and security policies | 4 governance, 5 risk management, 6 policies, 7 roles, 9 compliance monitoring | Risk assessment and treatment plan, general security policy plus the 11 topic policies, board approval records |
| (b) Incident handling | 24 incident management | Central, tamper-resistant logs with a defined retention period, alerting, a named incident coordinator on staff, runbook |
| (c) Business continuity, backups, crisis management | 25 continuity and crisis management | Automated backups with restricted access, periodic restore tests, BIA, DR plan; crisis procedures for essential entities |
| (d) Supply-chain security | 12 suppliers and ICT providers | Inventory of direct ICT suppliers, security clauses in contracts, scoped third-party access |
| (e) Secure acquisition, development, maintenance, vulnerabilities | 14 secure configuration, 15 secure development, 16 change management, 17 vulnerabilities | Hardened baselines, code review and CI, controlled changes, patching in reasonable time (especially internet-facing systems), tested patches |
| (f) Assessing effectiveness | 8 independent audit (essential only), 18 effectiveness | Annual external pentest, annual self-assessment sent to the Authority; internal pentest and independent audits for essential entities |
| (g) Cyber hygiene and training | 20 malware protection, 21 training | Endpoint protection with automatic updates, application control, email filtering, training with a minimum syllabus |
| (h) Cryptography | 22 cryptography | Encryption at rest and in transit, key management policy |
| (i) HR security, access control, asset management | 10 HR security, 11 assets, 13 access control, 23 physical security | Asset register covering on-prem and cloud, data classification, unique identities, least privilege, leaver process |
| (j) MFA and secure communications | 13 access control, 19 network security | MFA based on classification, firewalls, segmentation, controls on unknown devices |
Reading the decision end to end, these are the obligations teams most often miss:
- Eleven named topic policies (Article 6): access control, asset management, acceptable use, removable media, incident management, supply chain, network security, security testing, backups, cryptography, and physical security. All approved by management.
- An external penetration test at least once a year, or after a serious incident, for essential and important entities alike (Article 18). Essential entities also need an internal pentest every year.
- An annual self-assessment using the Authority's guide, sent to the Authority with a corrective action plan (Article 18). The Authority's gap-analysis tool, built with ENISA, has 169 control points in 24 sections; use it as your checklist.
- A named incident coordinator on your own staff (Article 24), even if a provider runs your SOC.
- Evidence. Article 3 says supervisors will look at documents, inspect a sample of systems and interview staff. A policy nobody follows fails all three.
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.
| Step | Deadline (Art. 16) | Content |
|---|---|---|
| Early warning | Within 24 hours of becoming aware | Suspected malicious cause, possible cross-border impact |
| Incident notification | Within 72 hours of becoming aware | Update plus initial assessment of severity and impact, indicators of compromise |
| Intermediate report | On request from the Authority | Status updates |
| Final report | Within one month of the 72-hour notification | Detailed 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.
- Approval and oversight (Law Art. 14(1), KYA Art. 4): management approves the risk-management programme, funds it and is accountable for its failures. The law gave existing entities three months from entry into force to approve the measures, so that deadline is long gone.
- Training (Art. 14(2)): board members take cybersecurity training, and the company provides similar training to staff at least once a year.
- Unified cybersecurity policy (Art. 15(5)(b)): one policy following the official template, referring to your detailed policies. Essential entities submit it to the Authority for approval at least once a year; for important entities, submission becomes mandatory only if a decision says so.
- Fines (Art. 26): up to €10 million or 2% of worldwide turnover for essential entities and €7 million or 1.4% for important ones for breaches of Articles 15 or 16, plus separate fines of up to €200,000 for failing the management approval duty and €100,000 for the training duty.
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
- Confirm scope and registration; appoint and declare the ΥΑΣΠΕ.
- Build the asset register (systems, data categories, cloud accounts, SaaS) and the list of direct ICT suppliers. Classify data into three or four levels.
- Enforce MFA for every human on email, identity provider, cloud consoles, VPN and admin tools. Remove shared and long-lived admin credentials.
- Turn on central logging for identity, cloud control plane and firewalls, and agree a retention period.
- Take the Authority's self-assessment tool once to get your gap list.
Days 31 to 60: detection, recovery and the paperwork that matches
- Alerts on the logs that matter (privileged logins, disabled logging, mass deletions), routed to a person on call.
- Backups that a compromised admin cannot delete, plus a timed restore test. See our disaster recovery guide for RPO and RTO per system.
- Vulnerability scanning and a patch policy with deadlines by severity, starting with internet-facing systems.
- Write the general policy and the 11 topic policies from how you actually work; get them approved by the board.
- Incident response policy and runbook with the 24/72-hour reporting steps and a named coordinator.
Days 61 to 90: prove it works
- External penetration test, with a remediation plan prioritised by severity.
- A tabletop exercise: a ransomware scenario run against the runbook, with the clock running.
- Board and staff training, with attendance records.
- Final self-assessment and corrective action plan, submitted to the Authority as required, and continuous checks so you notice drift.
The controls are the same on every platform; only the tools change.
| Control | AWS | Azure | On-prem |
|---|---|---|---|
| Identity and MFA | IAM Identity Center with your IdP (setup guide) | Entra ID with Conditional Access | AD or Entra ID with MFA on VPN and admin access |
| Central, protected logs | Organization CloudTrail to a log-archive account | Log Analytics or Microsoft Sentinel | Syslog to a SIEM (for example Wazuh) on a separate host |
| Threat detection | GuardDuty, Security Hub | Microsoft Defender for Cloud | EDR on endpoints and servers, IDS at the perimeter |
| Immutable backups | AWS Backup with vault lock, cross-account | Azure Backup immutable vaults | Offline or immutable copy outside the domain |
| Configuration baseline | AWS Config, SCPs | Azure Policy | CIS benchmarks, GPOs, configuration management |
| Encryption | KMS | Key Vault | Disk 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.