NIS2 update, November 2026: rewards for vulnerabilities and new EVAL_MMS versions
During the 17 November 2026 periodic check of our legislation hub NIS2 Directive in Romania, we found two changes that concern entities within the scope of Government Emergency Ordinance (GEO) No. 155/2024: a bill supplementing the ordinance has passed the Senate, and DNSC, the National Cyber Security Directorate, has published new versions of its maturity self-assessment tools. Both are now marked on the hub with an “Updated” label.
1. PL-x 729/2026: vulnerability reward programmes run by DNSC
The legislative proposal registered on 29 July 2026 (BP 610/2026), initiated by 9 deputies, was adopted by the Senate on 2 November 2026 (L593/2026). On 9 November it was registered with the Chamber of Deputies, the deciding chamber, as PL-x 729/2026 and sent to the Committee for Information Technology and Communications for a report. The deadline for amendments is 18 November and for the report 26 November 2026. The urgent procedure was not approved.
The text adopted by the Senate adds a new article to GEO No. 155/2024, art. 361, and a new point (h) to art. 24(4) covering the organisation and management of these programmes. In short:
- DNSC may launch and manage vulnerability identification and reporting programmes, with cash rewards for validated vulnerabilities, for its own networks and systems and for those of public authorities, public institutions and other public-law entities in the national civilian cyberspace.
- Including a network or system in a programme requires the prior, express and written consent of everyone entitled to authorise testing. The consent identifies exactly what may be tested and the limits of testing.
- The programmes complement the coordinated vulnerability disclosure process under art. 36. Vulnerabilities found are reported and handled under the same rules.
- Rewards go to natural or legal persons, under eligibility and validation criteria set for each programme, within the approved budget. The maximum reward per vulnerability and the total fund are announced to participants before the programme starts.
- Testing may start only after DNSC approves the programme, the consents are obtained and the participant expressly accepts the conditions. Each programme sets at least the scope, permitted methods, duration, technical and operational limits, the reporting method and the conditions for suspension or termination.
- Prohibited activities include unauthorised access to, copying, deletion or modification of data, brute-force attacks, phishing and other social engineering, malware, keeping access after the authorisation ends, and public disclosure of vulnerabilities outside the coordinated disclosure process.
- Going beyond the limits ends the authorisation and the right to a reward, without removing civil, administrative or criminal liability. Participation is voluntary and does not require any particular result.
The Government would approve, by decision and within 90 days of the law entering into force, the implementing rules: launching and approving programmes, selecting networks and systems, participation conditions, reporting and validating vulnerabilities, awarding rewards, data protection, and monitoring, suspension and termination.
What it means for entities
The bill creates no new obligations for essential or important entities and does not include any network automatically: it covers the systems of DNSC and of public-law entities, and only with their written consent. For a public authority or institution within the scope of GEO No. 155/2024, such a programme could complement its own testing. The bill builds on the framework for good-faith vulnerability research introduced by Law No. 123/2026 in art. 36(11) of the ordinance. The final text may differ from the one adopted by the Senate; its status is tracked in the In progress section of the hub.
2. EVAL_MMS: versions 1.1 and 3.1
On its Obligations of registered entities page, DNSC has replaced the tools for self-assessing the maturity of risk-management measures with new versions: EVAL_MMS_B v1.1 for the basic level, EVAL_MMS_I v3.1 for the important level and EVAL_MMS_E v3.1 for the essential level. The download links have changed; the tools table on the hub now has the new ones. The ENIRE@RO tool, used for the risk-level assessment, remains at version 2. The tools are in Romanian.
DNSC has not published a list of changes between versions on the page. In practice: download the tool from dnsc.ro before each self-assessment and keep the version used in your compliance file. The first self-assessment is due within 60 days of submitting the risk-level assessment (art. 18(7) of GEO No. 155/2024), then yearly (art. 12(4)), and essential entities submit a remediation plan within 30 days (art. 12(5)). The thresholds and method are explained in our articles on maturity self-assessment with EVAL_MMS and on the remediation plan.
What has not changed
As of 17 November 2026, no new DNSC acts have been published in the Official Gazette. Of the 14 acts required by art. 65 of GEO No. 155/2024, 4 are still the only ones published; the rules on incident reporting and the order setting the frequency of security audits are still missing. Directive (EU) 2022/2555 has not been amended, and the only implementing act remains Implementing Regulation (EU) 2024/2690.
Frequently asked questions
Is the vulnerability reward programme already law?
No. The bill was adopted by the Senate on 2 November 2026 and is now before the Chamber of Deputies, the deciding chamber, as PL-x 729/2026. Once adopted and promulgated, the Government must approve the implementing rules within 90 days of the law entering into force, and DNSC must approve each programme.
Can I get a reward today for a vulnerability reported to a public institution?
No. Until the law, the implementing rules and a DNSC-approved programme are in place, there is no reward framework. Vulnerabilities are reported through the coordinated vulnerability disclosure process under art. 36 of GEO No. 155/2024.
Do the programmes also cover private companies?
In the text adopted by the Senate, the programmes cover the networks and systems of DNSC and of public authorities, public institutions and other public-law entities, and only with the written consent of the persons entitled to authorise testing. Rewards can go to natural or legal persons who take part in a programme.
Must a self-assessment done with an earlier EVAL_MMS version be redone?
The DNSC tools page does not say. For future self-assessments, use the version currently published on dnsc.ro and keep the version used in your compliance file. If a self-assessment is under way, ask DNSC for confirmation.
Sources: the PL-x 729/2026 page on cdep.ro and the text adopted by the Senate; the DNSC page “Obligațiile entităților înregistrate”; legislatie.just.ro and EUR-Lex. Checked on 17 November 2026. Romanian legal acts are published only in Romanian; the summaries here are our working translations.
Complete legislation: all NIS and NIS2 acts in Romania, with the status of each, are on the NIS2 Directive in Romania hub.



