Dev Blog
NIS2 · Article 21 · Network access control · Asset management · SME · EAP-TLS · Cloud NAC

How Arbiter supports NIS2 compliance

15 November 2026 14 min read

NIS2 Article 21 lists ten minimum security measures, (a) to (j), that essential and important entities must have in place.

No single product covers all ten. Policies, training and crisis management depend on people, not software. Network access control (NAC) covers several measures directly and provides evidence for many more: which devices are on your network, who owns them and how each one got in.

The ten NIS2 Article 21 measures and how Arbiter helps with each one

At a glance:

  • (a) Risk analysis and information system security policies: agentless device discovery and an asset register where you record each device's owner, criticality and classification
  • (b) Incident handling: an Internet-only access profile you can assign to devices Intune reports as non-compliant, MAC spoofing alerts (including authentication downgrades) and events streamed to your SIEM
  • (c) Business continuity and crisis management: an on-site Edge appliance that keeps known devices online if a site loses its link to the cloud
  • (d) Supply chain security: guest and contractor accounts that expire automatically, a record of each guest accepting your acceptable use policy and restricted VLANs for third-party equipment
  • (e) Acquisition, development and maintenance, including vulnerability handling and disclosure: network access control that admits only authorised devices and gives each one the VLAN, ACL or role your policy sets
  • (f) Assessing effectiveness: a Policy Simulator to test a rule before you save it, monitor mode for phased rollouts, hit counts that show what matches and an audit log of most configuration changes
  • (g) Basic cyber hygiene and training: certificates in place of shared Wi-Fi passwords, a flag on devices still using the default SNMP community and a view of open ports from the optional Edge scan
  • (h) Cryptography and encryption: certificate-based 802.1X and encrypted, mutually authenticated links from every site to the cloud
  • (i) Human resources security, access control policies and asset management: Default Deny access policies built on certificate identity, device type, group and MDM state, plus an asset register your own rules can fill in, with named reviewers and retired devices kept on record
  • (j) Multi-factor or continuous authentication and secured communications: device certificates and MDM posture checked at every connection and re-authentication (user MFA stays with your identity provider)

Denying devices and assigning VLANs, ACLs or roles needs an access-control tier with enforcement on.

(a) Risk analysis and information system security policies

What Arbiter does. Finds and profiles the devices on your network without agents, using what your network and MDM already report. You record each device's owner, site, criticality, data classification and business function.

Evidence today. A register you can export as CSV or pull as JSON through the API. An inventory dashboard by device type, criticality and site that you can save as a PDF.

(b) Incident handling

Compliance checks for Intune-managed devices. Arbiter reads each device's compliance state from Microsoft Intune through the Graph API, with read-only access. Sync runs every 60 minutes by default and you can run it as often as every 5 minutes or on demand. Assign an Internet-only access profile to devices that Intune reports as non-compliant. Arbiter then tells the switch to apply an ACL you define on it, such as one that allows internet access but blocks your internal network. Pair the profile with a short session timeout and the device re-authenticates within minutes against the latest compliance state. When a connected device goes from compliant to non-compliant, Arbiter acts at the next sync: it sends a Change of Authorization (CoA) through your on-site Edge to apply the new policy to the live session. Live updates cover devices that Intune reports by MAC address. Other devices, including those that pass through an Intune grace period, pick up the change when they next authenticate. If syncing stops, a compliant result stops counting 24 hours after the last successful sync by default, while a non-compliant result still applies. See the Intune setup guide.

MAC spoofing detection. Every 30 seconds Arbiter checks new authentications for three spoofing patterns. MAC flapping means three or more MAC addresses authenticate on one wired switch port within 5 minutes. MAC on multiple ports means one address appears on three or more ports over a span of 5 to 10 minutes, so quick roams are ignored. An authentication downgrade means a device that recently used EAP-TLS now gets in through MAC Authentication Bypass (MAB). You can change the counts and time windows for the first two or switch any pattern off. Each event records the MAC addresses involved and the time, plus the switch and port for the port patterns. It comes with a recommended block rule. Apply it in one click and it takes effect at the next authentication under the policy it is attached to. Or dismiss the event and add an optional note. Either way Arbiter records who acted and when. Events stream to Microsoft Sentinel, Splunk, Elastic, syslog or a webhook. See the SIEM integration guides.

Evidence today. A security event history that shows who acted and when. The Intune compliance chart on the inventory dashboard. An authentication log you can filter by device, kept for 24 hours by default. To keep it longer, raise retention or stream it to your SIEM.

(c) Business continuity and crisis management

What Arbiter does. If a site loses its link to the cloud, the on-site Edge appliance keeps known devices online. That covers devices the cloud admitted in the last 30 days and any device with an in-date certificate from your tenant CA. Offline decisions reach the authentication log once the link returns. For a device with no certificate and no recent approval, your switches' fallback settings decide what happens while a site is offline. Arbiter can support you with the required configuration, starting with our network device guides.

Evidence today. Offline decisions in the authentication log. Edge status and certificate expiry in the portal.

(d) Supply chain security

What Arbiter does. Sponsored guest and contractor accounts that expire automatically. A captive portal that records each guest's acceptance of your acceptable use policy. Third-party equipment identified by manufacturer and type, then placed on restricted VLANs by policy.

Evidence today. Guest account and acceptance records. Inventory by manufacturer.

(e) Security in network and information systems acquisition, development and maintenance, including vulnerability handling and disclosure

What Arbiter does. With enforcement on, only authorised devices connect: certificates through 802.1X with EAP-TLS, allow-listed devices through MAB and Default Deny for everything else. With EAP-TLS enforced on every switch port and SSID in scope, Arbiter gives you strong evidence for point 6.7.2(g) of the Implementing Regulation's annex, which covers letting only authorised devices onto your network. Each device gets its VLAN, ACL or role by type, certificate, MDM state or group. Arbiter also records firmware and OS versions where your network or MDM reports them.

Evidence today. Access policy export. The VLAN and the matched policy, recorded on every authentication.

(f) Assessing effectiveness

What Arbiter does. Test a rule before you save it: the Policy Simulator checks it against a device's recorded profile and tells you how many of your devices would match. During a phased rollout, monitor mode admits devices that your deny policies or Default Deny would have refused and records what would have happened. Hit counts and RADIUS Insights show what is matching in production. Most configuration changes land in an audit log with who made them and when.

Evidence today. Hit counts and the audit log in the portal. The audit log can also stream to your SIEM.

(g) Basic cyber hygiene and training

What Arbiter does. Certificates replace shared Wi-Fi passwords where EAP-TLS is used. Edge SNMP discovery flags devices still answering on the default SNMP community. With Edge scanning on, Arbiter also shows open ports such as Telnet, SMB and RDP.

Evidence today. Counts of devices on the default SNMP community and of open ports.

(h) Cryptography and encryption

What Arbiter does. Devices prove who they are with certificates, not passwords: 802.1X runs as EAP-TLS, widely regarded as the industry gold standard for network authentication. The device and the network both prove their identity and there is no password to steal or phish. Each tenant gets its own certificate authority. You can also bring your own. Devices enrol over SCEP, including from Intune. Each site reaches the cloud over mutual-TLS RadSec, so RADIUS never crosses the internet in cleartext. Arbiter renews the cloud server certificates and the Edge tunnel certificates automatically.

Evidence today. The certificate identity on every EAP-TLS device record. The TLS version and cipher of every EAP-TLS authentication handled in the cloud. Your PKI configuration.

(i) Human resources security, access control policies and asset management

What Arbiter does. Default Deny for 802.1X and MAB. Policies built on certificate identity, device type, group, Intune compliance and Jamf managed state. An asset register with owner, criticality, data classification, business function and site, which your own rules can fill in by device type, MDM state or group. Groups can be marked out of scope. Retired and disposed devices stay on record. Each asset can have a named reviewer and a review due date.

Evidence today. Register and policy exports. A change history for every asset, with the old value, the new value and who made it. Review status with a named reviewer and a due date. A dated evidence report indexed to the ten measures. The Intune compliance chart on the inventory dashboard.

(j) Multi-factor or continuous authentication, secured communications and secured emergency communication systems

What Arbiter does. Checks each device's certificate at every connection and re-authentication, together with its MDM posture. Intune compliance follows the device, including wired adapters that Intune does not report, which are matched through the device certificate. A compliance result expires if the MDM data behind it goes stale. See the Intune setup guide.

Evidence today. How every device authenticates (certificate or MAC address). The Intune compliance chart on the inventory dashboard.

The NIS2 asset register: what an assessor gets today

Arbiter builds the register from what your network already reports. You add what only you know: owner, site, criticality, data classification and business function.

The export has one row for each in-scope network interface, so a laptop with wired and Wi-Fi adapters appears twice. Here is a sample with some of its columns:

MAC Address,Vendor,Device Class,Auth Type,NAS Name,Lifecycle,First Seen (UTC),Last Seen (UTC),Owner,Site / Location,Criticality,Business Function,Data Classification,Review Status
3c22fb1a074d,"Apple, Inc.",Operating System,dot1x,SW-DUB-01,active,2026-09-02 08:14:03 UTC,2026-11-14 09:02:51 UTC,IT Operations,Dublin,medium,Finance workstation,internal,Up to date
000e7f8445e6,Hewlett Packard,Printer or Scanner,mab,SW-DUB-01,active,2026-08-19 10:41:27 UTC,2026-11-14 08:55:10 UTC,Facilities,Dublin,low,Office printing,internal,Never reviewed
00065b1c22a0,Dell Inc.,Operating System,dot1x,SW-DUB-02,retired,2025-03-11 09:20:44 UTC,2026-10-30 17:05:12 UTC,Finance,Dublin,medium,Finance workstation,internal,Not due (retired or disposed)

Each row also records the switch port the device last connected on. The Register CSV also lists retired and disposed devices, marked in its Lifecycle column.

A change history for each asset

Every edit your team makes to an asset is recorded with the old value, the new value and who made it. That covers single and bulk edits, imports, adding or removing group members and changes to status, VLAN or device details. Deletions are recorded with who made them and a short copy of the register entry. Changes Arbiter makes itself are recorded too: ratings from your saved rules, removals by endpoint retention and merges of scan records that held details your team entered.

Updates Arbiter takes from the network and your MDM, such as device class, vendor, IP address, the status each sign-in sets and MDM state, are not recorded change by change; the register shows their latest values. Each asset has a change history in its detail panel. You can also filter the audit log by asset. Changes are kept for as long as your audit log retention setting, which is 365 days by default.

Retired and disposed devices stay on record

When a device leaves service you can retire it or mark it disposed, with a reason and the disposal method. The register keeps it on record with the date and who made the change. Retired assets are left out of the default lists and counts.

Endpoint retention never deletes them, nor any asset your team has recorded an owner, site, rating, classification or review on. If a retired device appears on the network again or your MDM still reports it, the register flags it. Retiring a device does not change its network access.

Owner reviews with a named reviewer and a due date

Each asset can have a named reviewer. When a person marks an asset reviewed, Arbiter records who and when, with an optional note. Editing an asset does not count as a review.

An asset falls due a set number of days after its last review, depending on its criticality: by default 90 days for critical assets, 180 for high and 365 for the rest. You can set each from 30 to 730 days. A one-off due date can bring a review forward but never postpone it. The inventory page shows overdue reviews.

A dated evidence report for your assessor

Download a ZIP for a period of up to 366 days. It holds the register, its change history for that period, review status and register measures, with an index to the ten measures and a SHA-256 manifest. Each download is recorded in your audit log with the file's hash. Arbiter does not keep a copy.

The report supports evidence for selected points. It does not demonstrate compliance. It leaves out free-text asset notes and device names, including their earlier values.

On access-control tiers a daily inventory snapshot can stream to your SIEM for long-term retention. The snapshot carries each asset's lifecycle state but not the other governance fields yet.

Changes made before 16 November 2026 were recorded in less detail: deletions, bulk edits and changes to status, VLAN or device details were not recorded for each asset.

Where to start

Start with the Asset Discovery tier. It builds your register while your policies run in monitor mode, so you see what connects before you enforce anything. Fill in owners, criticality and classification as you go. When your policies match what is really on the network, move to an access-control tier for enforcement, the authentication log, security events and SIEM streaming. The network access controls for (e), (h) and (i) depend on that enforcement.

Frequently asked questions

Which NIS2 Article 21 measures does network access control support?

With enforcement on, it is strongest on access control under Article 21(2)(i), cryptography for network authentication under (h) and the network access part of (e). It also provides evidence for risk analysis, asset inventory, incident handling, business continuity, supply chain security, effectiveness testing, cyber hygiene and device authentication.

How does 802.1X with EAP-TLS support NIS2 Article 21?

With enforcement on, only authorised devices connect and everything else is denied by default. Devices prove who they are with certificates rather than passwords. That supports access control under Article 21(2)(i), the network access part of (e) and cryptography for network authentication under (h).

Is a device certificate the same as MFA under NIS2?

No. Article 21(2)(j) covers multi-factor or continuous authentication. Arbiter checks each device's certificate at every connection and re-authentication, together with its MDM posture. User MFA comes from your identity provider.

Does NIS2 affect suppliers that are not in scope?

It can. Supply chain security is measure (d) and Article 21(3) asks in-scope entities to weigh each direct supplier's vulnerabilities, product quality and security practices. That is why organisations outside NIS2 scope still receive security questionnaires from customers who are in scope.

Has every EU country transposed NIS2?

Not as of November 2026. Member States were due to bring NIS2 into national law by 17 October 2024. On 8 July 2026 the European Commission referred Ireland, Spain, France and the Netherlands to the Court of Justice for failing to transpose it in full. Check the status of national law in each country where you operate.

Is the Edge scan a vulnerability scan?

No. It is a discovery scan that finds devices and open ports. It does not test for vulnerabilities or check versions against vulnerability data.

Where does Arbiter store my data?

In the EU. Arbiter Ltd is registered in Ireland and acts as a data processor under the GDPR.

Where NIS2 stands across the EU in November 2026

  • Not every country has transposed it yet. Member States were due to bring NIS2 into national law by 17 October 2024. On 8 July 2026 the European Commission referred Ireland, Spain, France and the Netherlands to the Court of Justice for failing to transpose it in full. Your obligations and deadlines come from national law. Check where things stand in each country you operate in.
  • Each country names its own regulator. Every Member State designates its own competent authorities and some publish their own guidance on the measures. The authority in your country decides what evidence it needs.
  • The EU rulebook already exists. Implementing Regulation (EU) 2024/2690 spells out the Article 21 measures in technical detail for digital infrastructure, ICT service management and digital providers. That includes in-scope managed service providers. For everyone else it is a benchmark rather than a legal duty.
  • Financial entities follow DORA. Since 17 January 2025 the ICT risk rules of the Digital Operational Resilience Act apply to them instead of Article 21. Arbiter's access-control and authentication records are relevant to DORA Article 9(4)(c) and (d). This post does not map DORA.

Your evidence stays in the EU. For network access control, the records an assessor samples are your authentication log and your device register. Arbiter Ltd is registered in Ireland. Tenant data is hosted in the EU. Arbiter acts as your processor under the GDPR. More on the Security page.

NIS2 suppliers and supervision

Your suppliers get asked. Supply chain security is measure (d). Article 21(3) asks in-scope entities to weigh each direct supplier's vulnerabilities, product quality and security practices. That is why organisations outside NIS2 scope still receive security questionnaires from customers who are in scope. We covered this in how NIS2 supply chain rules reach organisations outside scope.

Your regulator can check. Under Articles 32 and 33, authorities can ask for evidence that the measures are in place. Essential entities can be inspected at any time, including through random checks. Important entities are checked when the authority has an indication that they may not comply.

Sources