NIS2 remediation plan in Romania: from self-assessment to a management-approved plan
A NIS2 remediation plan is the document in which an essential entity shows how, and by when, it will fix the gaps found in its maturity self-assessment. Under article 12(5) of Romania’s GEO 155/2024, it must be sent to DNSC, the national cybersecurity authority, within 30 days of the self-assessment and must be endorsed by management.
Key points
- The maturity self-assessment is annual, is sent to DNSC and is endorsed by management (art. 12(4)).
- Essential entities send, within 30 days of the self-assessment, an action plan to remedy the deficiencies (art. 12(5)).
- Management bodies approve the measures, oversee implementation and are accountable for breaches (art. 14(1)).
- A useful plan is prioritised by risk and has named owners, realistic deadlines, a budget and closure evidence for each measure.
- The same plan becomes the reporting tool for management and the basis for discussion during the security audit.
What does the law say?
Three provisions of GEO 155/2024 fit together:
- art. 12(3): when management bodies find that the measures in the DNSC order are not met, they apply the necessary corrective measures without undue delay;
- art. 12(4): essential and important entities carry out and submit, every year, a self-assessment of maturity endorsed by management;
- art. 12(5): within 30 days of the self-assessment, essential entities send DNSC an action plan to remedy the deficiencies, endorsed by management.
The benchmark is DNSC Order 1/2026: 218 controls in three assurance levels (34 Basic, 133 Important, 218 Essential), with maturity thresholds of 2.5, 3 and 3.5. The EVAL_MMS tools are explained in our guide to the maturity self-assessment.
Important entities have no legal 30-day deadline for a plan, but art. 12(3) applies to them as well: identified gaps must be corrected. A written plan is the simplest way to show that this is happening.
Why a list of “failed” controls is not enough
The self-assessment produces a list of scores. If the remediation plan simply copies that list and adds a general deadline (“by year end”), three problems appear:
- No priorities. A missing control on multi-factor authentication for remote access does not weigh the same as an unfinished annual review procedure.
- No owner. Without a named person, the measure belongs to “IT”, which means nobody.
- No way to verify. Without closure evidence, neither management nor the auditor can say whether the measure is in place.
A remediation plan is a management tool, not a form.
Building the plan step by step
- Start from the self-assessment results control by control, not only from the overall score. Record the current and target level for each control.
- Group gaps into measures. Several controls are often closed by a single measure, for example one identity management solution covering several access control requirements.
- Prioritise by risk. Use the entity’s risk analysis: which measure most reduces the likelihood or impact of a significant incident? Key measures in the DNSC catalogue come first.
- Assign a named owner to each measure and a plan coordinator, usually the person responsible for network and information system security.
- Set realistic deadlines in stages: what closes now, within 90 days, within 12 months.
- Estimate resources: budget, internal time, suppliers. Art. 14(3) requires management to allocate the resources needed.
- Define closure evidence: approved document, verified configuration, test report, log, training record.
- Submit the plan to management for approval and keep proof of the approval.
- Send the plan to DNSC within 30 days of the self-assessment (essential entities).
- Track monthly and report quarterly to management.
Recommended structure of a plan entry
| Field | Example |
|---|---|
| Measure ID | M-07 |
| Controls covered | Authentication and remote access controls from the DNSC catalogue |
| Gap found | VPN access for suppliers without multi-factor authentication |
| Associated risk | Unauthorised access with a compromised password |
| Priority | High |
| Measure | Mandatory multi-factor authentication for all remote access accounts |
| Owner | A named person, not a department |
| Deadline | A specific date |
| Resources | Licences, internal hours, supplier |
| Closure evidence | Configuration export, access test, updated procedure |
| Status | Not started / In progress / Closed / Verified |
A table like this, kept up to date, is enough to answer questions from management, DNSC and the auditor.
How to prioritise with limited resources
Not every gap can be closed in the same year. A practical order:
- Now: low-cost measures with high risk impact, such as multi-factor authentication (art. 13(j)), tested and isolated backups (art. 13(h)), removing unused accounts, an incident notification procedure.
- Within 90 days: missing policies and procedures, an updated risk analysis, assessment of critical suppliers (art. 13(d)), training for management bodies (art. 14(2)).
- Within 12 months: larger technical projects, network segmentation, centralised logging and traceability (art. 11(4)), continuity exercises.
Postponed measures stay in the plan with a justification and temporary compensating controls. A plan that admits what cannot be done now is more credible than one promising everything in three months.
The role of management
Management does more than sign. Under art. 14(1), management bodies approve the measures, oversee their implementation and are accountable for breaches. In practice this means they:
- approve the plan and its budget;
- receive a short periodic report: how many measures are closed, what is late and why, which risks remain open;
- decide when a measure is postponed and formally accept the residual risk;
- make sure the security officer has the authority and resources required.
Members of management bodies must also attend accredited training under art. 14(2). The remediation plan is the most concrete material they can use to exercise oversight.
The remediation plan and the audit
The cybersecurity audit is mandatory (art. 11(5)), but its frequency has not yet been set by DNSC order. Whatever the timing, the auditor will look for exactly what a good plan contains: known gaps, documented decisions, closure evidence. The rules on auditors and incompatibilities are covered in our NIS auditor guide.
For companies within a group, the plan should reflect which controls are central, local or shared, as set out in DNSC Decision 3/2026. Each entity owns its plan. See our article on NIS2 in groups of companies.
Common mistakes
- copying the control list without grouping it into measures;
- giving every measure the same deadline;
- naming “IT” or “the supplier” as owner;
- no approved budget, so deadlines are only formal;
- closed measures without evidence;
- never updating the plan after submission, so it reappears unchanged at the next self-assessment.
How ProDefence can help
Through our NIS2 compliance consulting we turn self-assessment results into a prioritised remediation plan with measures, owners, deadlines and closure evidence, ready for management approval and submission to DNSC. Consulting starts at EUR 10,000 per project.
If the entity does not yet have an experienced internal security officer, our outsourced NIS2 officer service (from EUR 1,200 per month, 12-month contract) takes over plan coordination and reporting to management. Missing policies and procedures can be covered with our NIS2 documentation packages: EUR 1,500 for an important entity, EUR 2,000 for an essential entity, one-off payment, single-organisation licence. ProDefence is not VAT-registered, so displayed prices are final.
The CysNIS platform keeps control assessment, risks and planning in one place, clearly separating legal obligations, technical recommendations and indicative results. Through the DNSC-attested NIS auditors on its team, ProDefence can also carry out the audit, subject to the incompatibility rules between consulting and auditing for the same entity.
Remediation plans almost always include training measures, and these do not have to be built from scratch. The tiered courses on CysEdu (in Romanian) can cover staff training, while CysGame (in Romanian) offers free interactive quizzes and missions on phishing, ransomware and data protection, useful for recurring awareness campaigns.
Frequently asked questions
Who must send a remediation plan to DNSC?
Essential entities, within 30 days of completing the self-assessment, under art. 12(5) of GEO 155/2024. Important entities have no such deadline, but they must apply corrective measures without undue delay, so a written plan is just as useful for them.
Who signs the plan?
The plan must be endorsed by the entity’s management. Management bodies approve the risk management measures and are accountable for breaches (art. 14(1)), so their formal, documented approval is essential. The security officer coordinates but does not replace management.
How often should the plan be updated?
The self-assessment is annual, so the plan is rebuilt at least once a year. In between, update it whenever a measure closes, after significant incidents and after major system changes. Monthly tracking and a quarterly report to management is a reasonable rhythm.
What if I cannot close every gap by the planned date?
Keep the measure in the plan with a justified new deadline, temporary compensating controls and formal acceptance of the residual risk by management. What matters is that the decision is documented, not hidden.
Does the remediation plan replace the audit?
No. The self-assessment and the plan are produced by the entity, while the audit is an independent evaluation required by art. 11(5). Its frequency has not yet been set by DNSC order. A well-maintained plan makes the audit faster and cheaper.
Can one plan cover every company in a group?
Not entirely. Central or shared controls can be described once, but each entity performs its own self-assessment and owns its plan, according to the rules in DNSC Decision 3/2026.
Sources
- GEO no. 155/2024, art. 11-14, consolidated text: https://legislatie.just.ro/Public/DetaliiDocument/293121
- DNSC Director’s Order no. 1/2026, Official Gazette no. 712 of 27 August 2026: https://legislatie.just.ro/Public/DetaliiDocument/313799
- DNSC Decision no. 3/2026, Official Gazette no. 798 of 21 September 2026
- Law no. 124/2025 approving GEO 155/2024, Official Gazette no. 638 of 7 July 2025
Alexandru Angheluș, ProDefence. Cybersecurity and NIS2 compliance specialist leading the ProDefence team, which includes DNSC-attested NIS auditors.



