Directive · Cybersecurity · European Union
NIS2 compliance: scope, the 10 security measures and incident reporting
NIS2 compliance means meeting the EU cybersecurity directive as your country has transposed it. Medium and large entities in 18 sectors must apply ten risk-management measures, have management approve and oversee them, and report significant incidents within 24 hours, 72 hours and one month.
What you need to know about NIS2
Who must comply with NIS2?
NIS2 applies through national laws to entities in listed sectors that meet the size cap.
QULDEX helps here first: the readiness check shows where you stand before you commit budget.
What does NIS2 require?
NIS2 requires in-scope entities to apply ten cybersecurity risk-management measures, have their management body approve and oversee them, register with authorities, and report significant incidents on a fixed timeline.
Essential and important entities
Sector plus size decides status and supervision.
In QULDEX: Scoping per legal entityManagement accountability
Approve, oversee, train; personal liability.
In QULDEX: Board approvals trackedTen security measures
Risk, incidents, continuity, supply chain, crypto, MFA and more.
In QULDEX: Measures mapped to ISO 27001Incident reporting
24-hour warning, 72-hour notification, one-month report.
In QULDEX: Timers on every incidentRegistration
Entity details to the national authority.
In QULDEX: Registration trackedFines
At least up to €10m or 2% for essential entities.
In QULDEX: Supervision readinessWhich NIS2 articles matter most?
These 23 provisions carry the obligations most entities work on, grouped by theme. Select any one to see what it requires, typical evidence and the matching ISO 27001 or DORA reference.
Showing up to 6 per group. Search, filter, or open a group to see all 23.
Scope 5
Art. 2Scope and size capApplies to medium and large entities in Annex I and II sectors, and to some entities regardless of size, such as DNS and trust service providers.
In QULDEXEach legal entity records its sector, size and status.
- Typical evidence
- Scoping record
Art. 3Essential and important entitiesEntities are essential or important depending on sector and size; essential entities face proactive supervision.
In QULDEXQULDEX gives this requirement an owner, evidence requests and a review date, and reuses ISO 27001 evidence where it fits.
- Typical evidence
- Classification record
Annex ISectors of high criticalityEnergy, transport, banking, financial market infrastructure, health, drinking water, waste water, digital infrastructure, ICT service management, public administration and space.
In QULDEXQULDEX gives this requirement an owner, evidence requests and a review date, and reuses ISO 27001 evidence where it fits.
Annex IIOther critical sectorsPostal services, waste management, chemicals, food, manufacturing of critical products, digital providers and research.
In QULDEXQULDEX gives this requirement an owner, evidence requests and a review date, and reuses ISO 27001 evidence where it fits.
Art. 3(4)Registration with authoritiesRegisterEntities provide their details to national authorities; digital infrastructure providers register with the single point of contact.
In QULDEXQULDEX gives this requirement an owner, evidence requests and a review date, and reuses ISO 27001 evidence where it fits.
- Typical evidence
- Registration confirmation
Governance 2
Art. 20(1)Management body approval and oversightManagement bodies approve the cybersecurity risk-management measures, oversee them and can be held liable for breaches.
In QULDEXApprovals and oversight reviews are recorded per entity.
- Typical evidence
- Board approvals
- Maps to
- DORA Art. 5ISO 27001 5.1
Art. 20(2)Management trainingMembers of management bodies must follow training, and staff should be offered similar training regularly.
In QULDEXQULDEX gives this requirement an owner, evidence requests and a review date, and reuses ISO 27001 evidence where it fits.
- Typical evidence
- Training records
- Maps to
- ISO 27001 A.6.3
Security measures 10
Art. 21(2)(a)Risk analysis and security policiesPolicies on risk analysis and information system security.
In QULDEXQULDEX gives this requirement an owner, evidence requests and a review date, and reuses ISO 27001 evidence where it fits.
- Typical evidence
- Risk assessment, policies
- Maps to
- ISO 27001 6.1A.5.1
Art. 21(2)(b)Incident handlingProcesses to prevent, detect and respond to incidents.
In QULDEXQULDEX gives this requirement an owner, evidence requests and a review date, and reuses ISO 27001 evidence where it fits.
- Typical evidence
- Incident procedure
- Maps to
- ISO 27001 A.5.24–A.5.26
Art. 21(2)(c)Business continuity and crisis managementBackup management, disaster recovery and crisis management.
In QULDEXContinuity evidence is reused from ISO 22301.
- Typical evidence
- BCP, DR tests
- Maps to
- ISO 22301ISO 27001 A.5.30
Art. 21(2)(d)Supply chain securitySecurity of relationships with direct suppliers and service providers.
In QULDEXSuppliers are assessed and linked to the services they support.
- Typical evidence
- Supplier assessments
- Maps to
- ISO 27001 A.5.19–A.5.22DORA Art. 28
Art. 21(2)(e)Secure acquisition, development and maintenanceSecurity in acquisition, development and maintenance, including vulnerability handling and disclosure.
In QULDEXQULDEX gives this requirement an owner, evidence requests and a review date, and reuses ISO 27001 evidence where it fits.
- Typical evidence
- SDLC policy, vulnerability log
- Maps to
- ISO 27001 A.8.8A.8.25
Art. 21(2)(f)Assessing effectivenessPolicies and procedures to assess whether measures work.
In QULDEXControl tests run on a schedule with results.
- Typical evidence
- Control test results
- Maps to
- ISO 27001 9.1
Art. 21(2)(g)Cyber hygiene and trainingBasic cyber hygiene practices and cybersecurity training.
In QULDEXQULDEX gives this requirement an owner, evidence requests and a review date, and reuses ISO 27001 evidence where it fits.
- Typical evidence
- Awareness records
- Maps to
- ISO 27001 A.6.3
Art. 21(2)(h)Cryptography and encryptionPolicies on cryptography and, where appropriate, encryption.
In QULDEXQULDEX gives this requirement an owner, evidence requests and a review date, and reuses ISO 27001 evidence where it fits.
- Typical evidence
- Crypto policy
- Maps to
- ISO 27001 A.8.24
Art. 21(2)(i)HR security, access control and assetsHuman resources security, access control policies and asset management.
In QULDEXQULDEX gives this requirement an owner, evidence requests and a review date, and reuses ISO 27001 evidence where it fits.
- Typical evidence
- Access reviews, asset inventory
- Maps to
- ISO 27001 A.5.9A.5.15
Art. 21(2)(j)MFA and secured communicationsMulti-factor or continuous authentication, secured voice, video and text, and emergency communications.
In QULDEXQULDEX gives this requirement an owner, evidence requests and a review date, and reuses ISO 27001 evidence where it fits.
- Typical evidence
- MFA settings
- Maps to
- ISO 27001 A.8.5
Incident reporting 4
Art. 23(4)(a)Early warning within 24 hoursSend an early warning to the CSIRT or authority within 24 hours of becoming aware of a significant incident.
In QULDEXEach significant incident starts 24-hour, 72-hour and one-month timers.
- Typical evidence
- Early warning record
- Maps to
- DORA Art. 19
Art. 23(4)(b)Incident notification within 72 hoursUpdate the early warning with an initial assessment of severity, impact and indicators of compromise.
In QULDEXQULDEX gives this requirement an owner, evidence requests and a review date, and reuses ISO 27001 evidence where it fits.
- Typical evidence
- Notification
Art. 23(4)(d)Final report within one monthSend a final report with a detailed description, root cause, mitigation and cross-border impact.
In QULDEXFinal reports draw on the post-incident review.
- Typical evidence
- Final report
Art. 23(1)Informing service recipientsInform recipients of your services about significant incidents likely to affect them, and about threats and remedies.
In QULDEXQULDEX gives this requirement an owner, evidence requests and a review date, and reuses ISO 27001 evidence where it fits.
Supervision 2
Art. 32–33SupervisionEssential entities face proactive supervision; important entities face ex-post supervision after evidence of non-compliance.
In QULDEXQULDEX gives this requirement an owner, evidence requests and a review date, and reuses ISO 27001 evidence where it fits.
Art. 34Administrative finesEssential entities: at least up to €10m or 2% of worldwide turnover; important entities: at least up to €7m or 1.4%.
In QULDEXQULDEX gives this requirement an owner, evidence requests and a review date, and reuses ISO 27001 evidence where it fits.
Nothing matches that search.
Article numbers follow Directive (EU) 2022/2555. National transposition laws can add detail; check your member state's law. Summaries are QULDEX paraphrases, not legal advice.
How do you get NIS2 compliant?
There is no NIS2 certificate. You confirm scope under your national law, register, put the ten measures in place with management approval, and set up incident reporting. Most entities need 6 to 12 months, less with ISO 27001.
Confirm scope per country
Check sector, size and status in each member state's transposition law.
Register with the authority
Submit entity details through the national portal or single point of contact.
Gap assessment against Article 21
Assess the ten measures, reusing ISO 27001 evidence where you have it.
Close the gaps with management approval
Implement measures, approve them at board level and train management.
Set up incident reporting
Define "significant", build the 24-hour, 72-hour and one-month workflow, and test it.
Stay supervision-ready
EssentialProactive audits and inspectionsImportantEx-post supervisionEvery yearReview measures and training
Check the national law and registration deadlines in each member state where you operate. Durations are QULDEX planning ranges.
Which documents does NIS2 compliance need?
National authorities will ask for evidence of each measure. These records cover most of it.
| Document | Article | Where it lives in QULDEX |
|---|---|---|
| Scoping and status assessment | Art. 2–3 | Risk register |
| Registration confirmation | Art. 3(4), 27 | Evidence vault |
| Management approval and training records | Art. 20 | Policy library |
| Risk assessment and security policies | Art. 21(2)(a) | Policy library |
| Incident response procedure | Art. 21(2)(b) | Evidence vault |
| Business continuity and crisis plans | Art. 21(2)(c) | Evidence vault |
| Supplier security assessments | Art. 21(2)(d) | Vendor register |
| Effectiveness assessments | Art. 21(2)(f) | Audit workspace |
| Incident reports (24 h, 72 h, final) | Art. 23 | CAPA automation |
Document names are QULDEX recommendations based on the Directive; national laws may name others.
How long does NIS2 compliance take and what drives the effort?
Most entities need 6 to 12 months. Effort depends on your current security baseline, how many member states you operate in and how many suppliers you rely on.
Where the time goes
Bars show the upper end of each range on one scale (12 months = full width).
What changes the effort
- Member states: each national law can differ
- Entity status: essential entities face proactive audits
- Suppliers: supply chain security covers direct suppliers
- Existing ISO 27001: covers most of Article 21
- Sector rules: implementing acts add detail for digital providers
How ready are you for NIS2?
Check these eight things first. Nothing you enter leaves this page.
How NIS2 maps to ISO 27001, DORA and NIST CSF
ISO 27001 covers most of Article 21, and DORA replaces NIS2 duties for financial entities. One security programme can serve all of them.
NIS2 crosswalk
| NIS2 | ISO 27001:2022 | DORA | NIST CSF 2.0 | Shared evidence |
|---|---|---|---|---|
| Art. 20 Governance | 5.1, 5.3 | Art. 5 | GV.RR | Board approvals |
| 21(2)(a) Risk and policies | 6.1, A.5.1 | Art. 6 | GV.RM, ID.RA | Risk assessment |
| 21(2)(b) Incidents | A.5.24–A.5.26 | Art. 17 | RS.MA | Incident procedure |
| 21(2)(c) Continuity | A.5.29–A.5.30 | Art. 11 | RC.RP | Continuity plans |
| 21(2)(d) Supply chain | A.5.19–A.5.22 | Art. 28 | GV.SC | Supplier assessments |
| 21(2)(e) Vulnerabilities | A.8.8 | Art. 25 | ID.RA | Vulnerability log |
| 21(2)(j) MFA | A.8.5 | Art. 9 | PR.AA | MFA settings |
| Art. 23 Reporting | A.5.26 | Art. 19 | RS.CO | Incident reports |
Indicative mapping for planning, not legal advice. DORA vs NIS2 is compared in full on the blog.
How QULDEX runs NIS2 from scoping to supervision
QULDEX is NIS2 compliance and audit management software built from EGV Group's audit delivery, used by essential and important entities, their advisors and the auditors who check them. Pick your role to see who does what.
For organisations in NIS2 sectors.
- ScopeConfirm status per countryScoping record per legal entity
- GovernApprove and trainBoard approvals and training records
- MeasuresImplement Article 21Ten measures mapped to evidence
- SuppliersAssess suppliersVendor register with assessments
- IncidentsReport significant incidents24 h, 72 h and final-report timers
- SupervisionAnswer the authorityControlled evidence sharing
For NIS2 consultants and internal audit.
- ScopeRun the gap assessmentA reusable NIS2 gap template
- GovernBrief the boardBoard-ready reports
- MeasuresReview evidenceReview and approval states
- SuppliersCheck contractsStatus per supplier
- IncidentsAdvise on significanceDecision record per incident
- SupervisionPrepare responsesAn audit-ready pack
For security auditors and supervisory inspections.
- ScopeAgree scopeScope in a standard format
- GovernReview governanceView-only access to approvals
- MeasuresSample evidenceView-only evidence with download control and an access log
- SuppliersTest supplier controlsSupplier evidence on request
- IncidentsReview reportingIncident history with audit trail
- SupervisionReportFindings into CAPA
Pre-mapped control library
Requirements with owners, test steps and the crosswalk to 50+ frameworks.
Explore →EvidenceSecure evidence vault
Evidence linked to controls and findings, with upload, review and approval history.
Explore →RiskRisk register
Risk assessment and treatment, with decisions traced to the controls they drive.
Explore →FindingsCAPA remediation
Findings from internal and external audits tracked to closure with due dates.
Explore →NIS2 questions people ask
Does NIS2 apply to my company?
It applies if you operate in an Annex I or Annex II sector and are a medium or large enterprise (generally 50+ staff or over €10m turnover), or fall in a category covered regardless of size. Check the law in each member state where you operate.
What are the NIS2 incident reporting deadlines?
An early warning within 24 hours of becoming aware of a significant incident, an incident notification within 72 hours, and a final report within one month.
What are the NIS2 fines?
Member states must allow fines of at least up to €10 million or 2% of worldwide turnover for essential entities, and at least up to €7 million or 1.4% for important entities.
Has every EU country transposed NIS2?
Not all. The deadline was 17 October 2024; most member states have laws in force and the Commission has opened infringement proceedings against late ones. Germany's law has applied since 6 December 2025.
Does ISO 27001 certification cover NIS2?
Much of it. ISO 27001 controls cover most Article 21 measures, but NIS2 adds management liability and training, registration and fixed incident-reporting deadlines.
References
- Directive (EU) 2022/2555 (NIS2). eur-lex.europa.eu
- Commission Implementing Regulation (EU) 2024/2690 on technical and methodological requirements. eur-lex.europa.eu
- NIS2 Implementation Act, Germany, in force 6 Dec 2025. bsi.bund.de
- European Commission NIS2 transposition and infringement updates. digital-strategy.ec.europa.eu
- ISO/IEC 27001:2022. iso.org
Reviewed by
Page history
- : Page first built: provision explorer, ten measures, reporting timeline and readiness check
Find your NIS2 gaps before your authority does
Answer a short readiness check and get a gap summary across the ten measures. No sales call needed to see the result.