NIS2 Technical Measures: Mapping Article 21 to Measurable Controls

Which technical controls and evidence does NIS2 Article 21 require? A table mapping the ten areas to controls, technical preparation for the 24/72-hour reporting flow and a gap analysis list.
Technical summary
Technology
NIS2 (EU) 2022/2555, Implementing Regulation (EU) 2024/2690, MFA, SIEM, EDR
Topic
Mapping NIS2 risk management measures to technical controls and evidence
Level
Intermediate
Prerequisites
  • Basic information security management concepts
  • Access to the organization’s asset inventory
  • Knowledge of EU customers’ contractual requirements
In this article7 sections

Your customer in the EU has sent a security questionnaire, and the first question reads, “How do you meet the NIS2 Article 21 measures?” The directive requires “appropriate and proportionate” technical, operational and organizational measures; it doesn’t say with which product, which setting or which evidence they should be met. You have to fill that gap. Below we map the ten areas in Article 21 to concrete security controls and to evidence taken from systems that can be put on the table in an audit.

Who NIS2 affects directly and who indirectly

Directive (EU) 2022/2555 covers medium and large organizations operating in the “highly critical” sectors in Annex I (energy, transport, banking, health, drinking water, digital infrastructure, ICT service management, etc.) and the “other critical” sectors in Annex II (manufacturing, food, chemicals, postal services, waste management, digital providers, etc.). Organizations are divided into “essential” and “important”. The difference lies mainly in the intensity of supervision and the maximum administrative fines; the list of technical measures is the same for both. The deadline for member states to transpose the directive into national law was 17 October 2024. Because transposition has progressed differently from country to country, check the national legislation of the country where your customer is located as well.

Whether a company is in scope can’t be determined just by looking at the country it’s in or the name of its sector; whether it provides services in the EU, its size and the relevant member state’s national legislation are assessed together. For a company based in Türkiye that doesn’t provide services in the EU, the impact usually comes through two routes:

  • Supply chain obligation: The in-scope organization must manage the security risks in its relationships with its direct suppliers and service providers. This obligation comes back to you as contract clauses, security questionnaires and audit rights.
  • Digital providers offering services in the EU: For organizations not established in the EU but serving it, such as cloud, data center, managed service (MSP) and managed security service (MSSP) providers, the directive requires a representative to be appointed in the EU.

Think of a company in the automotive supply industry: as soon as its customer in the EU falls under NIS2, it asks the supplier for concrete commitments and evidence on MFA, patching times, incident notification time and backups. Saying “it doesn’t concern us” doesn’t make these questions go away. Mapping the articles to technical controls is the shorter route.

The ten areas listed in Article 21

Paragraph 2 of Article 21 of the directive requires the measures to cover at least the following areas:

  1. (a) Policies on risk analysis and information system security
  2. (b) Incident handling
  3. (c) Business continuity: backup management, disaster recovery and crisis management
  4. (d) Supply chain security
  5. (e) Security in the acquisition, development and maintenance of network and information systems, including vulnerability handling and disclosure
  6. (f) Policies and procedures to assess the effectiveness of the measures
  7. (g) Basic cyber hygiene practices and cybersecurity training
  8. (h) Cryptography and, where appropriate, the use of encryption
  9. (i) Human resources security, access control and asset management
  10. (j) Multi-factor or continuous authentication, secured voice/video/text communications and secured emergency communications

Article 20 also requires the management body to approve these measures, oversee their implementation and receive training. In other words, the signature sits with management. For certain digital infrastructure providers (cloud, data center, MSP, MSSP, DNS services, etc.), Commission Implementing Regulation (EU) 2024/2690 breaks these areas down into much more detailed technical requirements. Even if it’s outside your scope, keep it at hand when designing controls; it shows what counts as “sufficient” far more clearly than the article text.

Area–technical control mapping table

For each area, the table lists a typical technical control and the evidence an auditor will accept as “implemented”. We deliberately built the evidence column on dated reports and exports taken from systems rather than on screenshots. A screenshot shows a moment; a report shows a process.

Item Technical control Measurable evidence
(a) Risk analysis Asset inventory, criticality class, risk register A report of differences between the inventory and network discovery
(b) Incident handling Central logging, SIEM rules, EDR List of log sources, rule inventory, incident records
(c) Business continuity Immutable backup, offline copy, DR test Restore test report, RPO/RTO measurement
(d) Supply chain Separation of supplier access, recording and approval of remote access List of supplier accounts, session records
(e) Acquisition and maintenance Vulnerability scanning, patch SLA, secure configuration Scan coverage, SLA compliance report
(f) Measuring effectiveness Penetration test, configuration audit, metrics Test report and retest result
(g) Cyber hygiene Hardening baseline, phishing simulation Baseline deviation report, training records
(h) Cryptography Disk encryption, TLS standard, key management Encryption status report, TLS scan output
(i) Access and assets Role-based permissions, periodic access review Signed review record, check of departed staff
(j) MFA MFA on all remote access and administrator accounts MFA registration report, exception list

The table is a starting point, not a matrix. When you add “control owner”, “evidence source system” and “evidence production frequency” columns to each row, it turns into an operable control matrix. A common mistake is a row that is filled in but has no owner. A control without an owner decays. The detailed implementation of row (h) is covered in the applying encryption controls to data at rest and in transit guide, and row (e) in the vulnerability management program guide.

A measurable evidence example: MFA coverage

The sentence “All users have MFA” doesn’t pass an audit on its own. The auditor wants to see the accounts left out of scope. In an environment using Microsoft Entra ID, you can export the registration status with Microsoft Graph PowerShell:

Connect-MgGraph -Scopes "AuditLog.Read.All"
Get-MgReportAuthenticationMethodUserRegistrationDetail -All |
  Where-Object { -not $_.IsMfaRegistered } |
  Select-Object UserPrincipalName, IsAdmin,
    @{n='MethodsRegistered'; e={$_.MethodsRegistered -join ';'}} |
  Export-Csv .\users-without-mfa.csv -NoTypeInformation -Encoding UTF8

The method list is returned as an array; if you don’t join it before writing to CSV, you only see the type name in the column. One more warning: being registered doesn’t mean MFA is enforced. The evidence of enforcement is the scope of the Conditional Access policies and the authentication requirement in the sign-in logs. The “excluded” group list in the policy is the first place to look in the console; apart from the emergency account, nobody should stay there for long. If you keep the registration report and the policy scope together, you have a strong evidence set for area (j).

Technical preparation for incident reporting

Article 23 of the directive provides for staged reporting of a “significant incident”: an early warning within 24 hours of becoming aware of the incident, an incident notification within 72 hours, and a final report no later than one month after the incident notification. If you’re a supplier, your customer contract most likely specifies a shorter deadline. Meeting these deadlines is the infrastructure’s job, not the legal department’s:

  • The detection time must be recorded separately: The time the SIEM or EDR alert was created and the time the analyst accepted the incident should be kept in separate fields. The 24-hour clock starts at the moment of “becoming aware”.
  • Time synchronization: If system clocks drift apart, the incident timeline can’t be built. All servers, network devices and security products should be tied to the same NTP hierarchy. A firewall whose clock is three minutes behind is enough to break the timeline.
  • Log retention depth: The final report asks for the root cause and impact. If the attacker’s initial access was weeks ago and logs are kept for 7 days, the root cause can’t be written. Retention design is explained in detail in the central log retention architecture guide.
  • Impact measurement data: The number of affected users, the duration of the service outage and the type of data affected are inputs to the significance assessment. If the asset inventory doesn’t know which system carries which service, these questions can’t be answered within hours.
  • Out-of-band communication: If email and identity infrastructure are affected, through which channel will the team and managers talk? This channel should be set and tested in advance; the “secured emergency communications” in area (j) is exactly this.

Supply chain security requirements

Area (d) works both ways. You manage your own suppliers; at the same time, you’re a link in your customer’s supply chain. The gaps we run into most often on the technical side:

  • Permanent supplier accounts: VPN accounts opened years ago for a software or maintenance company, with no expiry and no MFA. Control: time-limited accounts, request-based activation, mandatory MFA and session recording.
  • Excessive MSP privileges: The management tool a managed service provider uses across all its customers may be running with domain admin rights in your environment. Control: a separate management account, least privilege, limiting the network segments the tool can reach.
  • Visibility of software components: Without a list of third-party components in critical applications (SBOM), you can’t answer “are we affected?” when a new library vulnerability comes out.
  • Evidence for customers: If the information requested in questionnaires (MFA rate, patching times, date of the last backup test) is collected by hand each time, the figures won’t match between two questionnaires. Produce these metrics from a single, up-to-date source; both customer answers and internal audits speed up.

If you’re in the automotive supply chain, much of the evidence you collect for a TISAX assessment is also useful for NIS2 mapping. For the common points, see the TISAX preparation process and technical evidence guide.

Gap analysis checklist

Use the list below to apply the mapping table to your own environment. For each item, just write “yes / partly / no” and the evidence source. For a “partly” answer, also note which assets are left out; that’s the first thing the auditor will ask.

  • Has the asset inventory been compared with network discovery in the last three months; is there a list of devices outside the inventory?
  • Are all internet-facing services and remote access routes protected with MFA; are the exceptions dated and approved?
  • Are administrator accounts separated from everyday user accounts?
  • Do critical server, firewall, identity and EDR logs flow into a central system and are they kept long enough for incident investigation?
  • Are the moment of becoming aware of an incident and the reporting steps recorded; has the 24/72-hour flow been tested with an exercise?
  • Is at least one copy of the backups immutable or offline; when was the last restore test done?
  • Is vulnerability scanning credentialed, and is a remediation deadline defined for critical findings?
  • Are endpoint disk encryption and a TLS configuration standard defined and measured?
  • Are supplier accounts time-limited, and are sessions recorded?
  • Has the effectiveness of the measures been verified by an independent test (penetration test, configuration audit) in the last year?
  • Has the management body approved the measures, and is management training recorded?

The items that get the most “partly” answers on this list are usually backup testing and supplier accounts. The control exists. Its measurement doesn’t. The process side of business continuity and crisis management is outside the scope of this guide; for backup, DR and crisis organization, the NIS2 business continuity requirements guide is a complement. If you’d like the gap analysis done with an independent eye, our enterprise cybersecurity consulting and control and configuration audit services carry out this mapping together with evidence collection. The full text of the directive is available on EUR-Lex.

Frequently asked questions

Does a company in Türkiye have to comply with NIS2?

This question can’t be answered by looking at the country alone; whether services are provided in the EU, the company’s size and the relevant member state’s legislation are assessed together, and the final assessment should be made with legal counsel. A company that doesn’t provide services in the EU is usually not directly in scope. But because in-scope customers in the EU must manage supply chain security, NIS2 requirements reach the supplier through contract clauses, security questionnaires and audit rights. Some digital providers offering services in the EU may also have an obligation to appoint a representative in the EU.

Does NIS2 require a specific product or standard?

No. The directive is risk-based and technology-neutral; it lists areas but doesn’t name products or brands. The organization’s risk assessment determines what is appropriate and proportionate. Standards such as ISO 27001 are used as mapping references in practice.

What are the incident reporting deadlines in NIS2?

For a significant incident, an early warning is given within 24 hours of becoming aware, an incident notification within 72 hours, and a final report no later than one month after the incident notification. The competent authority may also request an intermediate report. Supplier contracts often give the customer a shorter notification deadline.

Which technical gaps come up most often in a gap analysis?

The ones we see often: undocumented MFA exceptions, permanent supplier accounts without MFA, log retention periods too short for incident investigation, vulnerability scans run without credentials, and restore processes that have never been tried. The common thread is the same: the control exists, but its coverage hasn’t been measured.

Support

Contact us for support or a discovery session on this topic.

Contact form
[email protected]

Eretek Cybersecurity

Firewall, VPN, endpoint security and threat prevention. We reduce the attack surface and measure and report the risks.

Knowledge Center

Other articles