GUIDE · ZERO TRUST NETWORK

Network access control (NAC) and 802.1X: how it works and how to enable it

This guide explains how network access control and 802.1X authentication work, when it is worth enabling them and in what order. By the end you will know which devices to inventory, how to handle those that cannot authenticate, how to move from observation to blocking and how to check that the control really works.

Updated october 2026
8 min read
Altovar Technical Editorial Team

1. What network access control is

Network access control, often referred to by the acronym NAC, decides whether a device may connect to the network and, if so, to which zone. The principle is simple: before granting access, the network verifies who or what is connecting. This applies to office workstations, laptops, printers, connected equipment and devices brought in by guests. The control applies to everything, not only to company devices, and therefore requires an inventory that does not depend on the goodwill of whoever plugs something in.

The benefit is avoiding a free network socket or a poorly protected Wi-Fi network becoming an entry point with access to everything. An unknown device can be isolated in a quarantine zone, instead of being left on the internal network. The control does not replace user authentication, but adds a check on the device that connects. The result is one more check, not a guarantee.

2. How 802.1X works in practice

A mechanism widely used for this purpose is 802.1X, which authenticates the connection at the port before allowing traffic through. It involves three roles: the device requesting access, the switch or Wi-Fi access point acting as the controller, and an authentication server that verifies the credentials or certificate. Until the server confirms identity, the port stays closed to ordinary traffic.

The practical advantage is that the same check can apply to both cable and corporate Wi-Fi, and can automatically assign the right zone based on identity. A device that fails authentication stays out of the internal network, or ends up in a guest or quarantine zone. The configuration must be designed together with segmentation, because authentication decides who gets in and the rules decide where they can go.

3. Prerequisites: inventory and compatible infrastructure

Before enabling the control you need an inventory of workstations, devices and printers, indicating which can authenticate and which cannot. Many production devices, sensors and older equipment do not support this type of authentication. For them, a declared alternative is needed, rather than leaving them silently open. This choice must be made together with the systems manager, who knows the operational value of those devices and the risk of stopping them.

A compatible infrastructure is also needed: switches and access points that support the function, an authentication server with documented certificate management and a corporate directory from which identities can be read. Ask your supplier to verify every device and every operating system you will use, because compatibility varies greatly from one model to another. Also check the operating system versions on workstations, because an update can change how authentication behaves.

  • Inventory of workstations, laptops, printers and connected devices.
  • List of devices that do not support authentication, with a declared solution for each.
  • Switches and access points that support port-based control.
  • An authentication server with documented certificate management.
  • A corporate directory as the reference for users and groups.

4. Phased rollout

Enabling the control all at once is the fastest way to stop work. Proceed with an observation mode, in which the network records who connects without preventing it, and only afterwards move to blocking on limited groups of ports. The observation period serves to discover forgotten devices before they become a problem. During observation nothing changes for the user, so it is the right moment to correct the inventory without rushing.

  1. Build the inventory and mark the devices that cannot authenticate.
  2. Configure the authentication server and connect it to the corporate directory.
  3. Enable observation mode on the switches in a low-impact area.
  4. Analyse the devices that connect and correct the gaps in the inventory.
  5. Assign the target zones: employees, guests and quarantine.
  6. Move to blocking on a first group of ports, verifying that work continues.
  7. Extend the control to other groups, documenting each exception with an owner and an expiry date.

5. Devices that cannot authenticate

For devices that do not support 802.1X there are fallback solutions, such as authentication based on the device's network address. These are less robust, because an address can be copied, and should be used only as a documented exception. An address copied from an authorised device is enough to pass the check, so the strict firewall rule is part of the defence, not a detail. The fallback should be limited to the zone where the device is needed and accompanied by a strict firewall rule that allows only the necessary flows.

For these cases, ask your supplier to specify the solution, the residual risk and the replacement plan. An old device that cannot be updated may remain in use for years: it is better to keep it in an isolated zone with a clear owner than to leave it on the office network without control. If the manufacturer no longer guarantees updates, the issue also becomes a replacement decision to plan.

6. Common mistakes

The most frequent mistake is enabling blocking before having the inventory, and discovering the next day that a printer in the accounts department or a point-of-sale system no longer connects. The second is applying authentication to employees while leaving the port open for everyone else, on the assumption that nobody will notice. An unmonitored port becomes the simplest point of entry.

Other mistakes are operational: expired certificates that lock everyone out at once, former employees' accounts still enabled in the directory, and guest zones that are not genuinely separated from the internal network. Every certificate expiry date should be in the owner's calendar, with an advance reminder. A former employee's account still active should be disabled on the same day the relationship ends, not when someone remembers it.

7. How to verify it works

Verify three things. First: an unauthorised device does not gain access to the internal network. Second: an authorised device connects without manual intervention and ends up in the right zone. Third: failed attempts are logged and reach the people who need to read them. Repeat the test every time you change switches, access points or the authentication server. After any change to groups or roles in the directory, the test must be repeated on the accounts involved.

Also ask to see the log of failed authentications for a trial period and compare it with the inventory. Devices that appear in that log and are not in the inventory are the work to do in the next period, not a technical detail to ignore. If the log is empty, first check that log collection is working, because an apparent silence may only be hiding a fault.

8. How to start

This week, build the device list for a pilot area, for example the administrative offices. For each device, note whether it can authenticate, who uses it and which zone it should be in. This document is the basis for any later decision. You will also need it to explain to management why the control starts with that area and which criteria you used to choose it.

Then ask your supplier to verify the compatibility of the switches and access points and to propose an observation mode for that area, without blocking. Only after an observation period, with a correct inventory, should you consider actual blocking. The move to blocking must be communicated to the people in the area in advance, with a channel for reporting problems in the first period.

Frequently Asked Questions

Does network access control also cover Wi-Fi?

Yes, and it is one of the most common uses. Corporate Wi-Fi can use the same authentication as cable, with personal credentials or certificates instead of a shared password. This makes it simpler to revoke access when a person leaves the organisation, without changing the password for everyone. Check with your supplier which mobile devices support the chosen method.

Is it legally required?

No reference regulation prescribes it by name. The GDPR requires security measures appropriate to the risk, and the NIS2 Directive, transposed in Italy by D.Lgs. 138/2024, requires organisations within its scope to manage risk in a documented way, which generally includes access control.

What about a printer that cannot authenticate?

It should be recorded as a documented exception. It is usually placed in a dedicated zone, with a rule that allows only print traffic from authorised users. The residual risk should be noted, and the printer replaced once the model becomes difficult to manage securely.

Is a certificate really needed, or is a password enough?

A password is easier to steal or guess than a certificate installed on the device. For this reason certificates are generally preferable, but they require serious management: distribution, renewal and revocation. A password used for port authentication, without other controls, remains a weak point.

Who should manage the authentication server?

A person or supplier with clear responsibility for the service. The server is a critical point: if it stops, many devices are locked out of the network. A written recovery procedure, a defined emergency mode and a periodic check of certificates and of the accounts linked to the directory are needed.

About this content

General informational guide. Regulations and technical requirements change over time: always check the official sources and assess your specific case with a qualified technical or legal advisor.

GET IN TOUCH

Talk to our team.

We'll show how Altovar integrates into your infrastructure. No commitment, no sales pitch. Just a technical conversation.

BOOK A DEMO →