If your company has more than 50 employees and makes electrical equipment, car parts or machinery, processes food on an industrial scale or delivers parcels, you most likely fall under NIS2. For a Romanian SMB that means registering with DNSC, security measures you can prove, reporting incidents within 24 hours and a mandatory audit carried out by a DNSC-certified auditor.
If you only find out from a questionnaire sent by a large customer, you are already behind: the notification to DNSC is due within 30 days of the date the ordinance applies to you, not the date you found out. Below you will find what the law says, what each DNSC order regulates and what to do, in order.
What NIS2 is and how Romania transposed it
NIS2 is Directive (EU) 2022/2555, which replaced the first NIS directive and greatly widened the list of sectors covered. Romania transposed it through Government Emergency Ordinance (GEO) no. 155/2024, published in the Official Gazette on 31 December 2024 and approved with amendments by Law no. 124/2025, in force since 10 July 2025. The main authority is the National Cyber Security Directorate (DNSC). The ordinance sets the obligations; the technical detail comes through orders of the DNSC director.
Who falls under NIS2: sector, size, exceptions
Scoping takes three steps. The first is the sector: your activity must appear in Annex 1 (sectors of high criticality) or Annex 2 (other critical sectors) of the ordinance.
- Annex 1: energy, transport, banking, financial market infrastructures, health, drinking water, wastewater, digital infrastructure, business-to-business managed ICT services, central public administration, space.
- Annex 2: postal and courier services, waste management, chemicals, production, processing and distribution of food, manufacturing (medical devices and NACE divisions 26–30: electronics, electrical equipment, machinery, motor vehicles, other transport equipment), digital providers, research.
The second step is size, assessed under Law no. 346/2004. A medium-sized enterprise has 50–249 employees and annual net turnover of up to 50 million euros or total assets of up to 43 million euros. Above those thresholds you are a large enterprise. Micro-enterprises (up to 9 employees) and small enterprises (10–49 employees, turnover or assets of up to 10 million euros) are, as a rule, outside NIS2.
The third step is the exceptions, where size does not matter: DNS service providers, TLD name registries, trust service providers, providers of publicly available electronic communications, critical entities and companies that DNSC identifies under Article 9, for example because they are the sole provider of an essential service.
Essential entity or important entity
The category sets the fine ceiling and a few extra obligations. Essential entities are mainly large enterprises in Annex 1, plus some entities regardless of size: central public administration, DNS providers, TLD registries, qualified trust service providers and critical entities (Art. 5). Important entities are medium and large enterprises in Annexes 1 and 2 that are not essential (Art. 6). A 120-person factory in an Annex 2 sector is therefore an important entity, unless DNSC identifies it otherwise.
And if you are below the thresholds? The ordinance requires in-scope entities to take into account the security of their direct suppliers (Art. 11(8)), so the requirements can reach you through contracts even if DNSC asks you for nothing directly.
What your obligations are, concretely
- 1Registration with DNSC, following the requirements of DNSC Order no. 1/2025, and updating your data when something changes.
- 2Risk-management measures (Art. 11 and 13): risk analysis, security policies, cryptography, supplier security, vulnerability management, access and asset control, incident handling, backup and disaster recovery, training, multi-factor authentication. The law also explicitly requires logging of network activity (Art. 11(4)).
- 3Management responsibilities (Art. 14): approve the measures, oversee their implementation, answer for breaches, attend accredited training and appoint a person responsible for network and information system security.
- 4Reporting significant incidents through the national PNRISC platform (Art. 15).
- 5The cybersecurity audit, mandatory for both essential and important entities (Art. 11(5)).
| Obligation | Deadline | Legal basis |
|---|---|---|
| Notifying DNSC for registration | 30 days from the date the ordinance applies to you | Art. 18(2); DNSC Order no. 1/2025 |
| DNSC decision to enter you in the register | 60 days (essential) or 150 days (important) from notification | Art. 18(4)–(5) |
| Appointing the network security officer | 30 days from notification of the decision | Art. 14(3) |
| Risk-level assessment | 60 days from notification of the decision | Art. 18(6); DNSC Order no. 2/2025 |
| Maturity self-assessment of measures | first within 60 days of the risk assessment, then annually | Art. 18(7), Art. 12(4); DNSC Order no. 1/2026 |
| Remediation plan after self-assessment (essential only) | 30 days from the self-assessment | Art. 12(5) |
| Significant incident | early warning within 24 hours, incident report within 72 hours, final report within one month | Art. 15(7) |
| Information on cross-border impact | no later than 6 hours after becoming aware of it | Art. 15(3) |
| Audit results to DNSC | 5 days after the audit ends | Art. 46(8) |
| Action plan after the audit | 15 working days from receiving the report | Art. 57(8) |
| Evidence of implementing the plan | 5 days after the committed deadline | Art. 57(10) |
The NIS2 audit: who can carry it out and how often
Only a cybersecurity auditor holding a valid DNSC certification can carry out the audit (Art. 58(1)). The audited company chooses the auditor and pays for the audit, including an ad-hoc one (Art. 57(4) and Art. 46(9)).
The law strictly separates preparation from verification. You cannot be audited by an auditor who currently provides you with cybersecurity services or is your employee, by one who had a contract for the audited system within the last year, or by one who has already carried out three consecutive audits at the same entity (Art. 58(3)).
Whoever prepares you for the NIS2 audit is not allowed to sign it. The law separated the two roles so that evidence counts at the audit, not promises.
How often? The frequency is set by an order of the DNSC director, based on the risk level (Art. 11(5)). At the November 2026 update we had not found this order published, and Order no. 1/2026 does not regulate the audit. Separately, DNSC can require an ad-hoc audit, for example after a significant incident (Art. 57(2)).
The page on preparing for the NIS2 / DNSC audit explains how we work: scoping, gap analysis, remediation and the evidence file. Our founder holds the DNSC cybersecurity auditor specialisation and his certification as an auditor is in progress, so we do not sign official audit reports.
NIS2 penalties: what a company risks
Fines are set out in Article 60. For the main offences, the higher of the fixed amount and the percentage of worldwide annual turnover in the last financial year applies.
| Offence (examples) | Essential entity | Important entity |
|---|---|---|
| Missing risk-management measures, evading the audit, failing to report significant incidents, breaching management obligations | from 10,000 lei up to 10 million EUR or 2% of worldwide turnover | from 5,000 lei up to 7 million EUR or 1.4% of worldwide turnover |
| Failing to notify for registration, late risk assessment or self-assessment, not sending the audit results | 1,500–500,000 lei | 1,000–300,000 lei |
| Serious infringements (Art. 50(2)): repeated infringements, obstructing the audit or inspection, false information | 3,000–600,000 lei; limits increase by half for repeated infringements | 3,000–600,000 lei; limits increase by half for repeated infringements |
Two clarifications. For the offences in Art. 60(1), you can pay half of the fine imposed if you pay within 15 days of being notified of the sanction (Art. 60(7)). And if an essential entity fails to remedy deficiencies, DNSC can request the temporary suspension of a certification or authorisation and a temporary ban on the chief executive exercising their function (Art. 49).
The first sanctions began in September 2026. DNSC announced that it had started proceedings, first against entities that did not register, followed by those that missed their other obligations. The first organisations received findings notices, which are not yet fining decisions, and DNSC's management said that at first the amounts would be the lowest in the scale (StartupCafe, Ziarul Financiar, 9–10 September 2026, in Romanian).
The DNSC orders: what each one regulates
- Order no. 1/2025, published on 20 August 2025: the requirements for the registration notification process and the method of submitting information.
- Order no. 2/2025, also published on 20 August 2025: the criteria and thresholds for determining how severely a service is disrupted and the methodology for assessing an entity's risk level.
- Order no. 1/2026, published on 27 August 2026: the risk-management measures and the maturity self-assessment methodology. Each entity implements the controls of the assurance level that matches its risk level (Art. IV). The order also amended Order no. 2/2025: financial entities subject to the DORA Regulation no longer carry out the risk-level assessment. The annexes, with the actual list of measures, appeared in Official Gazette no. 712 bis and are not reproduced on the legislative portal.
- Order no. 3/2025, published on 11 December 2025: the supervision and inspection rules and the methodology DNSC uses to prioritise inspections by risk.
The link with ISO 27001
ISO 27001 is a voluntary standard; NIS2 is law. An ISO 27001 certificate does not replace the audit required by GEO 155/2024 and does not cover registration, the risk-level assessment, the annual self-assessment, the reporting deadlines or management training.
On security measures, the overlap is real. Commission Implementing Regulation (EU) 2024/2690, which details the NIS2 measures for cloud, data centre, managed service and other digital providers, states in recital 3 that the requirements are based on standards such as ISO/IEC 27001. ENISA's June 2025 technical guidance includes a mapping table to ISO/IEC 27001:2022, but notes that the table does not measure equivalence and does not show whether the standard fully covers the requirements. If you already run an ISO 27001 system, a gap analysis shows what is missing on top of it; for the basic measures, see also our cybersecurity guide for SMBs.
The NIS2 compliance plan for an SMB, step by step
- 1Scope yourself in writing: the sector (your NACE code against the annexes), size under Law 346/2004 and the exceptions. Keep the reasoning for registration and the audit.
- 2Check your registration. If you have not notified DNSC, do it now: the obligation remains, and DNSC can notify unregistered entities on its own initiative (Art. 18(12)).
- 3Within 30 days of the DNSC decision, appoint the network security officer and schedule the accredited training for management.
- 4Build the asset inventory and the risk analysis; DNSC can request them at any time (Art. 11(7)).
- 5Calculate the risk level under Order no. 2/2025 and submit the assessment within 60 days of the decision. The result determines which controls from Order no. 1/2026 apply to you.
- 6Carry out the maturity self-assessment and turn the gaps into a plan with owners and deadlines. Essential entities send the plan to DNSC within 30 days.
- 7Implement first what reduces risk most: multi-factor authentication, backups verified by restore, centralised logging, vulnerability management, security requirements in supplier contracts.
- 8Write the incident response plan around the 24-hour, 72-hour and one-month deadlines: who decides, who reports in PNRISC, who informs customers. Test it with management.
- 9Assemble the evidence file (approved policies, logs, test reports, training records) and choose a DNSC-certified auditor who meets the independence rule.
If you have already registered and want to know what an auditor would find, the article on the NIS2 / DNSC readiness check goes into detail on what is checked and in what order.
Conclusion
NIS2 asks for a process you can prove: reasoned scoping, deadlines met, measures matched to risk and evidence that an independent auditor can verify. The earlier you start, the more the audit becomes a confirmation rather than a list of deficiencies. If you want to find out which category your company falls into and what the first step is, let us talk for 30 minutes.
Sources
- GEO no. 155/2024 on cybersecurity of network and information systems in the national civil cyberspace, consolidated version, Romanian Legislative Portal: Articles 5–9, 11–15, 18, 46–50, 57–60, Annexes 1 and 2.
- Law no. 124/2025 approving GEO no. 155/2024, Official Gazette no. 638 of 7 July 2025
- DNSC Director's Order no. 1/2025, Official Gazette no. 776 of 20 August 2025: registration notification.
- DNSC Director's Order no. 2/2025, Official Gazette no. 776 of 20 August 2025: disruption criteria and risk-level methodology.
- DNSC Director's Order no. 3/2025, Official Gazette no. 1149 of 11 December 2025: supervision, verification and inspection.
- DNSC Director's Order no. 1/2026, Official Gazette no. 712 of 27 August 2026: risk-management measures and maturity self-assessment.
- Law no. 346/2004 on small and medium-sized enterprises, consolidated version: Article 4, size categories.
- Directive (EU) 2022/2555 (NIS2), 14 December 2022, EUR-Lex
- Commission Implementing Regulation (EU) 2024/2690, 17 October 2024, EUR-Lex: recital 3.
- ENISA, NIS2 Technical Implementation Guidance, version 1.0, 26 June 2025: mapping table to standards.