Resources · · Updated
NIS2: what comes after registering with the authority
Registration was the first step, not the last. What the law requires after it, in what order, and on what deadlines.
Romania transposed NIS2 through Emergency Ordinance 155/2024, approved with amendments by Law 124/2025. Registration with DNSC starts a sequence of obligations. Their clocks start from different events, and entity category matters.
The order of obligations
| Step | Deadline or reference point |
|---|---|
| Registration notification | Within 30 days of the entity coming within the ordinance’s scope |
| Identification and registration decision | Record when the DNSC decision was communicated, not just when it was issued |
| Risk level evaluation | Submit within 60 days of communication of the decision |
| First maturity self assessment | Within 60 days of transmitting the risk level evaluation |
| Annual self assessment | Endorsed by management and submitted to DNSC and, where applicable, the competent sector authority |
| Remediation plan for essential entities | Endorsed by management, prepared and submitted within 30 days of completing the self assessment |
| Remediation plan when thresholds are not met, including for important entities | With implementation dates the entity commits to; the methodology sets no universal 30-day filing deadline for important entities |
| Security audit | According to the legal requirements and frequency applicable to the entity |
These reference points follow from OUG 155/2024, Articles 12 and 18 and the assessment methodology, Article 3. Completing a document and submitting it are separate steps. Keep evidence of when the decision was communicated and of each submission.
Entity category and assurance level
Classification as an essential or important entity follows legal criteria, including sector, size and the special cases in the ordinance. Essential entities can be supervised proactively; important entities are supervised when there are indications of noncompliance.
Entity category and the assurance level required for the measures are separate questions. Do not infer the assurance level from the label “essential” alone. The risk level evaluation determines the applicable requirements under the methodology.
What you can reuse from ISO 27001
ISO 27001 controls and evidence can support the measures in Article 21 of the directive. A mapping helps reuse existing work, but does not by itself establish compliance with Romania’s NIS2 obligations.
The official annex of DNSC measures and controls is publicly available and contains 218 controls, with applicability depending on assurance level. The formal self assessment is separate from ISO mapping: documentation and implementation of applicable controls must be assessed with reasons and evidence, following the current DNSC methodology.
Check incident reporting and management duties separately. The management body must approve the measures and undergo training. ISO certification does not automatically fulfil these duties.
If you have not registered
First check whether, and since when, your organisation falls within the ordinance’s scope. The initial 2025 deadline is not a single cutoff for every organisation that subsequently comes within scope. If the applicable deadline has passed, prepare the notification through the official channel and check outstanding obligations.
Where to start
List the services you provide and the systems behind them. Then establish the applicable requirements and gather evidence for each step.
Phalanx keeps incident records and records of obligations towards DNSC. Existing ISO controls can support the Article 21 mapping. The platform does not yet implement the formal assessment of the 218-control DNSC catalogue. Check applicable deadlines against the official legislation; submissions use official channels, and their evidence can be kept in the platform.