The moment the cable of a camera on an outside wall is unplugged, that switch port becomes a network socket open to anyone standing in the car park. VLAN separation limits where traffic can go; it doesn’t question who is connected to the port. Below we compare 802.1X (EAP-TLS) and MAC Authentication Bypass (MAB) on camera ports, and give an example configuration on the Cisco IOS and RADIUS side, typical drop-outs during camera replacement and the troubleshooting order in the console.
Why camera ports need port authentication
A camera port is riskier than a desktop port for three reasons. First, physical access: it’s in unsupervised places such as car parks, perimeter fences and warehouse docks, and the cable is often exposed behind the camera. Second, continuity: the port is active and authorized 24/7; if a laptop is plugged in between, nobody notices. Third, the target: the camera VLAN can usually reach the NVR, the VMS and sometimes the management network. An attacker copies the camera’s IP and MAC address and takes over this access. If the cable is exposed, so is the port.
We explained the reasons for moving camera traffic to a separate segment in the why a camera VLAN is needed article. Port authentication puts an identity check at that segment’s door.
Comparing 802.1X, MAB and port security
| Method | What it verifies | Strength | Operational load |
|---|---|---|---|
| Port security (static/sticky MAC) | MAC registered on the switch | Low; MAC can be copied | Switch intervention on every replacement |
| MAB | MAC list in RADIUS | Low–medium; strengthened by policy | Central list, no certificates |
| 802.1X EAP-PEAP | Username and password | Medium; credentials can be read from the device | Password management |
| 802.1X EAP-TLS | Device certificate | High; private key on the device | PKI, certificate distribution and renewal |
The realistic goal on site is a mixed setup: 802.1X on cameras that support EAP-TLS, MAB on those that don’t, and the port unauthorized if both fail. Port security remains a temporary measure at small sites without RADIUS infrastructure; since it requires logging into the switch on every camera replacement, it becomes unmanageable as the site grows.
EAP-TLS on cameras: certificates and support checks
In EAP-TLS (RFC 5216), the camera presents a client certificate to the RADIUS server, and the RADIUS server presents its own server certificate to the camera. Before starting the project, the answers to these questions should be on the table for each camera model:
- From which firmware version is 802.1X and EAP-TLS supported?
- How are the client certificate and CA certificate uploaded: web interface, HTTP API, device management software?
- Can the camera generate a key and CSR on the device?
- Is there a factory-installed device identity certificate? Some manufacturers offer an IEEE 802.1AR-compliant device identity (IDevID); if RADIUS is set to trust this manufacturer’s CA, the certificate upload step during installation can disappear.
- EAPOL version and re-authentication behavior: some cameras experience a brief stream interruption during periodic re-authentication. Measure it in the pilot; don’t assume.
EAP-TLS has a known “chicken and egg” problem: the camera needs the network to get the certificate and the certificate to get onto the network. There are two practical solutions: uploading the certificate on an isolated staging network in the workshop, or admitting the camera with MAB into a restricted staging VLAN that can only reach the certificate distribution server. Use a separate template with the Client Authentication purpose for the camera certificate; don’t mix it up with the HTTPS server certificate. We covered the certificate lifecycle in detail in the HTTPS and certificate management on IP cameras and NVRs guide.
Switch and RADIUS configuration example
The example below is the classic (IBNS 1.0) command structure long used on Cisco IOS and IOS XE. In newer IOS XE versions, the same logic is built with the access-session and policy-map type control subscriber structure (IBNS 2.0); the switch can convert classic commands automatically. Addresses and VLAN numbers are examples.
aaa new-model
aaa authentication dot1x default group radius
aaa authorization network default group radius
aaa accounting dot1x default start-stop group radius
!
radius server NAC-1
address ipv4 10.10.5.10 auth-port 1812 acct-port 1813
key <shared-secret>
!
dot1x system-auth-control
!
interface GigabitEthernet1/0/12
description CAM-B1-012 car-park-entrance
switchport mode access
switchport access vlan 30
authentication host-mode single-host
authentication order dot1x mab
authentication priority dot1x mab
authentication port-control auto
authentication periodic
authentication timer reauthenticate server
authentication event server dead action authorize vlan 30
authentication event server alive action reinitialize
authentication violation restrict
mab
dot1x pae authenticator
dot1x timeout tx-period 10
spanning-tree portfast
There are a few camera-specific decisions in this configuration:
- single-host: there should be a single device behind the camera port. If a small switch is plugged in between, the second MAC counts as a violation; this line stops the “intermediate switch to connect an extra device to the camera” trick on site.
- tx-period 10: on a camera that doesn’t support 802.1X, the switch waits for EAPOL attempts to time out before moving to MAB. With the default 30 seconds and retry count, this can reach a minute and a half. Shortening it brings back video from a restarted camera sooner.
- server dead action: lets cameras that restart while RADIUS is unreachable be admitted to the camera VLAN. It’s a deliberate security trade-off; assess it together with RADIUS redundancy. The
server alive action reinitializeline re-authenticates these ports when the server comes back. For the switch to be able to consider the server “dead”,radius-server dead-criteriaandautomate-testersettings must also be made at the global level; if forgotten, these lines never take effect. - authentication timer reauthenticate server: the re-authentication period is set by the Session-Timeout value from RADIUS. Policy stays central.
On the RADIUS side, the camera policy should include at least these conditions:
- 802.1X rule: the certificate was issued by the corporate camera CA and hasn’t been revoked; the certificate subject matches the camera name in the inventory. Result: the camera VLAN and a camera-specific access list.
- MAB rule: in MAB requests, the RADIUS Service-Type value arrives as Call-Check and the MAC address is in the Calling-Station-Id field. Grant access if the MAC is in the “camera” identity group and the request comes from the expected switch and port (NAS-IP-Address, NAS-Port-Id).
- Authorization result: instead of only assigning a VLAN, if the switch supports it, return a downloadable ACL or group tag that lets the camera reach only the NVR and infrastructure services. A laptop that gets onto the network with a copied MAC can then do only what the camera can do.
- Default: all non-matching requests are rejected.
Microsoft NPS is enough for EAP-TLS; on the MAB side, however, it requires MAC addresses to be defined as user objects, which makes management cumbersome in large corporate camera systems. With a high camera count, a NAC solution with profiling and identity group support, or a well-designed FreeRADIUS policy, is more sustainable. The use of RADIUS attributes with 802.1X is explained in RFC 3580.
Camera replacement and fault scenarios
| Scenario | Symptom | Mitigation |
|---|---|---|
| A faulty camera replaced with a new one (MAB) | Port unauthorized, camera on but no video | A step in the replacement work order to add the new MAC to RADIUS |
| A faulty camera replaced with a new one (EAP-TLS) | EAP doesn’t start or there’s no certificate | Pre-loading certificates on spare cameras, or a staging VLAN |
| Camera reset to factory settings | 802.1X setting and certificate deleted | Camera configuration backup and restore procedure |
| Certificate expired | Mass camera loss on the same day | Expiry date monitoring and staggered renewal |
| Camera moved to another port | NAS-Port binding rejects it | Reflecting the move in RADIUS through a change record |
Almost all of these scenarios are process problems, not technical ones. If a “MAC/certificate updated” step isn’t added to the field technician’s camera replacement form, the 802.1X project is bypassed at the first fault: on the night shift, the port is opened with authentication open to bring video back, and it stays that way. That’s the common bypass. Process first, then enforcement mode.
Troubleshooting: authentication errors
show authentication sessions interface GigabitEthernet1/0/12 details
show access-session interface GigabitEthernet1/0/12 details
show dot1x interface GigabitEthernet1/0/12
show radius statistics
test aaa group radius camera-test <password> new-code
In the session output, first look at which method was tried (dot1x or mab), then the result and the assigned VLAN/ACL. Error patterns that recur on site:
- dot1x gets no response, MAB succeeds: 802.1X is off on the camera or not supported. If that’s the expected behavior, there’s no problem; if not, check the camera settings.
- EAP-TLS starts but RADIUS rejects: RADIUS logs show “unknown CA”, “certificate expired”, or that the client certificate lacks the Client Authentication purpose.
- The camera rejects the RADIUS certificate: the corporate CA chain hasn’t been uploaded to the camera, or the camera clock is wrong.
- Authentication succeeds, no video: the assigned downloadable ACL may be blocking the NVR’s RTSP request or response. Check the ACL hit counters.
- Periodic interruption: if the stream drops during re-authentication, lengthen the Session-Timeout value and confirm the firmware behavior with the manufacturer.
Authentication errors and unexpected MAC changes are also security events; we explained sending these records to central monitoring in the anomaly monitoring on the camera network guide. For an organization-wide NAC migration, the phased 802.1X and NAC migration plan article is complementary.
Commissioning checklist
- Model, firmware, MAC and 802.1X/EAP-TLS support columns are filled in the camera inventory.
- A separate CA template for the camera client certificate and revocation (CRL/OCSP) access are defined.
- RADIUS is redundant with at least two servers; the server-unreachable behavior on switches has been chosen deliberately.
- In the first phase, logs were collected in monitor mode (open authentication); devices that would be rejected were seen before enforcement.
- The move to enforcement mode is done per building or switch, in a maintenance window and with a rollback plan.
- Camera replacement, move and factory reset procedures are updated; the field team has been briefed.
- Unused camera ports are shut down or in a parking VLAN.
To plan the 802.1X and MAB rollout on camera ports together with the switch infrastructure and segmentation design, see our camera cybersecurity hardening and camera VLAN and network segmentation service pages.
Frequently asked questions
Do all cameras support 802.1X?
No. Many models in the enterprise segment support EAP-TLS; budget series and older firmware may lack support or offer only EAP-PEAP. Verify support per model and firmware with the datasheet and testing; use MAB on devices without support.
Does MAB alone provide enough security?
MAB looks only at the MAC address, and a MAC address can be copied. Used together with NAS-Port binding, profiling and an authorization policy that allows only the NVR, it meaningfully reduces the risk of unauthorized devices; but it isn’t as strong as 802.1X EAP-TLS.
If the RADIUS server can’t be reached, do cameras drop out of recording?
It depends on the configuration. Already authenticated sessions continue until re-authentication time. If a critical VLAN setting granting access to the camera VLAN while the server is unreachable isn’t configured on the switch, cameras that restart during that time aren’t admitted to the network.
Is PoE cut if 802.1X authentication fails?
No. PoE power delivery and 802.1X are independent of each other; the camera powers up, but because the port stays unauthorized, no data traffic passes. On site, this comes in as the complaint “the camera is on but there’s no video”.