Skip to content
Phalanx
roRequest a quote
Menu+

Resources ·

DNSC Order 1/2026: what you need to know about the new control catalogue

The 218-control catalogue is now public on Portal Legislativ. In short: how assurance levels work, dual scoring, N/A rules, and assessment and reporting deadlines.

On 6 August 2026, DNSC published in the Official Gazette (no. 712 bis) Order no. 1/2026 approving the cybersecurity maturity measures and assessment methodology. On 14 September, Order no. 2/2026 (OG 792) followed, adding group-level applicability and bounded N/A exclusions. Both annexes, the control catalogue and the consolidated methodology, are freely readable on Portal Legislativ (documents 314682 and 314683), so the old “annex unavailable” blocker is gone.

What the catalogue contains: 218 controls, six functions, three levels

Order 1/2026 Annex 1 lists 218 rows (controls) across six functions: Identify, Protect, Detect, Respond, Recover, Govern. Each control has a unique code (e.g. ID.AM-1, PR.AC-1) and flags whether it is a key measure (29 total) or a management aspect (15).

Applicability is not binary. There are three cumulative assurance levels:

Assurance level Applicable controls Who falls here
Basic 34 Essential entities with reduced risk profile / Important entities
Important 133 (includes the 34 Basic) Important entities, standard Essential entities
Essential 218 (all) Essential entities with high risk profile

Cumulative principle: an entity at Important level must also implement the Basic controls. At Essential level, all 218 apply.

Scoring: two scores per control, hierarchical averages, thresholds

The methodology (Art. 2) requires two integer scores 1-5 for each applicable control:

  1. Documentation score: does the policy/procedure exist and is it current?
  2. Implementation score: is the measure effectively applied and demonstrable?

No flat average across all controls. Hierarchical averages are calculated: control → subcategory → category → function → entity total score For Essential entities: averages are also calculated separately for key measures and management aspects.

Pass thresholds (Art. 2 para. 3):

Level Total score Each category / key measure
Basic ≥ 2.5 ≥ 2.5
Important ≥ 3 ≥ 3
Essential ≥ 3.5 ≥ 3

An Essential entity with total score 3.8 but a single category at 2.9 does not pass.

N/A exclusions: not a free pass, capped and prohibited

Order 2/2026 (new Art. 4) introduces strict N/A rules:

Level Max N/A exclusions allowed
Basic 1
Important 3
Essential 5

Absolute prohibitions: key measures cannot be excluded, and management aspects at Essential level cannot be excluded.

An N/A-marked control does not escape scoring: the methodology substitutes 2.5 (Basic) or 3 (Important/Essential) into the average calculations. The written justification goes into the Statement of Applicability.

Maturity assessment: deadlines, which clock, what gets filed

OUG 155/2024 (Art. 18) sets two distinct deadlines:

Activity Deadline Clock starts from
Risk assessment + first maturity assessment 60 days Communication of the classification decision (not receipt, not registration)
Subsequent annual assessment Annual Date of previous assessment (management-assumed)

Key: the 60-day clock does not start from registration (that is 30 days after classification, Art. 18(2)), but from communication of the decision by the supervising authority / DNSC.

Filing with DNSC / sector authority happens after the assessment is complete and approved by management. There is no automatic submission from the platform: official channels (e-mail, portal, post) are used.

Important vs. Essential entities: corrective action plans

  • Essential entities: if the assessment misses thresholds, the corrective action plan must be prepared and transmitted to DNSC within 30 days of the assessment (OUG Art. 12(5)).
  • Important entities: The methodology (Art. 3) requires a plan when thresholds are missed, with implementation dates the entity undertakes, but imposes no universal statutory 30-day filing deadline. Treating an internal plan for an Important entity as “legally overdue” is a misinterpretation.

Three-year reassessment: not universal

DNSC Order 2/2025, Art. 5(5), requires the risk score to be recalculated every 3 years and whenever the sector’s high impact threshold is exceeded:

  • General rule: recalculate every 3 years
  • Exception: the entity already applies the highest level of cybersecurity measures under Order 1/2026
  • Event trigger: the sector’s high impact threshold is exceeded
  • Separate rule, not a reassessment exception: banking and financial market infrastructure entities under DORA do not carry out the risk-level assessment at all (Methodology Art. 6, as replaced by Order 1/2026 Art. V)

An automated “over 3 years = overdue” flag is incomplete.

Group policies: adoption ≠ local implementation

DNSC Decision 3/2026 (norms, OG 798/21 Sept.) clearly distinguishes:

  • Adopted at group level: the policy exists centrally
  • Implemented locally: implementation evidence and metrics exist at each entity’s level
  • Shared: a single service instance serves multiple entities

A group policy does not automatically populate implementation scores. Each entity must have local evidence (configurations, logs, attestations, reports).

What this means for you, now

  1. Stop waiting for the annexes: they are public. You can start mapping controls against what you already have.
  2. Determine your assurance level: Basic / Important / Essential dictates how many controls you must address.
  3. Prepare the Statement of Applicability: with written justifications for each N/A (max 1/3/5).
  4. Separate assessment completion from DNSC filing: two steps, two evidence trails.
  5. Check if you are DORA: if yes, the 3-year reassessment rule does not apply the same way.

How Phalanx works with Order 1/2026

Phalanx lets you organise the assessment of controls under DNSC Order 1/2026, as amended, and their supporting evidence: the catalogue is imported with source codes, key/management flags, the two scores (documentation/implementation), N/A justifications, and assessment snapshots. The 60-day / annual deadlines are tracked automatically, but filing remains manual, through official channels.

Want to see how this looks in the platform?

Tell us which regulations apply to you and we will show you the part that matters for you. A person answers, not a qualification form.

Request a quote