Trunk native VLAN is VLAN 1
At a glance
Base severity
Area
Platform
Evidence level
Benchmark reference
Reads the export, not the device
ConfigProof reads a configuration export. This control is evaluated against the objects in that file, and it reports what the file says. It does not connect to the device and sees no traffic, so a finding here describes the configuration, not what the firewall is doing right now.
Why it matters
Untagged traffic on the trunk lands in VLAN 1; double-tagging attacks can reach other VLANs through it.
How to fix it
Web interface
The steps below are written for the web interface. A finding raised on your own export carries the same steps with your object names filled in.
- In the Meraki Dashboard: Switching > Switch ports > select the trunk ports > Edit > Native VLAN: an unused VLAN, matching the neighbor.
Command line
This analyzer version writes no command text for this control. The steps above are the remediation it offers.
How to confirm the fix
- In the Meraki Dashboard: Switching > Switch ports shows a native VLAN other than 1 on every trunk.
Limits
- No limitation is recorded for this control beyond the one that applies to all of them: it reads a configuration export.
Compliance references
No benchmark recommendation is mapped to this control in this version.
More in Interfaces and Segmentation
- MS-SEC-001Access ports without BPDU guard
- MS-SEC-003Trunk carries every VLAN
- MS-SEC-004User ports in the default VLAN
- MS-SEC-005DHCP guard allows any DHCP server
- MS-SEC-006Dynamic ARP inspection off
- MS-SEC-008RSTP disabled
- MR-SEC-004Guest-style SSID bridged into the LAN
- MX-MGT-004Spoofing protection not blocking
See it on your own firewall
One complete analysis of one firewall costs nothing. A card is required and nothing is charged.