


Meraki Switch Security: 802.1X, management VLANs, trunks and DHCP guard on the access layer
Switch findings are quiet and dangerous: a management VLAN on a user port, a trunk allowing every VLAN, NAC that fails open. We check every port on every MS.
Meraki switch security, port by port
Meraki MS switches decide which VLAN a device lands on, whether it must authenticate first and what it can do to its neighbors. The Meraki switch security review is the Switching & NAC domain of the Cisco Meraki security audit, together with the wired side of Segmentation.
Wireless clients inherit the same VLANs, so this review is read alongside Meraki access point security.
What goes wrong on MS switches
- Management VLAN exposed on access ports; Layer 3 management reachable from user networks
- End-user switch ports configured as trunks; trunks permitting all VLANs
- Switch ports using VLAN 1 as the native or access VLAN
- NAC policy with fail-open access or a single RADIUS server; no restricted or critical VLAN
- DHCP server policy permitting unauthorized servers; ARP inspection off
- STP root bridge not explicitly set; loop guard missing on uplinks
- Storm control not configured on the access layer
- Switch ACLs containing a broad permit
Sample findings
Switching & NAC observations
| Severity | Observation | Site / product | Recommended direction |
|---|---|---|---|
| Critical | Management VLAN is exposed on access ports | Anaheim Data Center / MS | Move management to a dedicated VLAN and remove it from user-facing ports. |
| High | Layer 3 switch management access is reachable from user networks | Anaheim Data Center / MS | Restrict management interfaces to the administrative network. |
| High | NAC policy uses fail-open access | Anaheim Data Center / MS | Disable fail-open or define a restricted fallback VLAN after validating RADIUS resilience. |
| High | End-user switch port is configured as a trunk | Irvine HQ / MS | Convert the port to an access configuration after validating the connected device. |
| High | Trunk permits excessive VLANs | Tustin Clinic / MS | Replace all-VLAN or broad ranges with an approved VLAN allowlist. |
| High | DHCP server policy permits unauthorized servers | Irvine HQ / MS | Enable and validate DHCP server policy with approved server allowlisting. |
| High | Switch ACL contains a broad permit | Tustin Clinic / MS | Replace the broad permit with approved source, destination and service scope. |
| Medium | Access port lacks the expected NAC policy | Irvine HQ / MS | Assign the approved access policy after testing endpoint and fallback behavior. |
| Medium | STP root bridge is not explicitly configured | Anaheim Data Center / MS | Set root and secondary root bridges by design. |
| Low | Storm control is not configured for the access layer | Irvine HQ / MS | Establish tested broadcast, multicast and unknown-unicast thresholds. |
Remediation project: Campus Access Control and NAC
| Target window | 0–7 days |
| Accountable function | Network engineering and identity |
| Related findings | 14 |
| Objective | Every access port authenticates or lands in a restricted VLAN; management is reachable only from the administrative network. |
| Completion evidence | Port configuration export, NAC policy screenshots, re-run read-only assessment. |
Risk distribution (whole organization)
Marlowe Ridge Health Partners, fictional company, illustrative data. Full sample report.
What we check on every switch
- Port type (access/trunk), allowed and native VLANs on every port
- Management VLAN placement and Layer 3 management reachability
- Access policies: 802.1X/MAB, RADIUS servers, fail-open, guest and critical VLANs
- DHCP server policy and allowlisting, ARP inspection
- STP configuration, root bridge, loop guard, BPDU guard where observable
- Storm control thresholds
- Switch ACLs and broad permits
- Layer 3 routing interfaces on switches
- Switch event logging (reported under Logging & Monitoring)
Related Meraki assessments

Dashboard & administrator security
Switch changes are made by admins. Review who they are and how they sign in.
Dashboard securityAlso in this series
Move through the whole Meraki ecosystem from any page.
Ali Hassani, Certified CISO (C|CISO), CISSP
President of OC Security Audit in Irvine, California. 25+ years in IT and cybersecurity leadership, with dozens of Microsoft and Cisco certifications including CCNP, CCNA, MCSE and MCITP. Every Meraki assessment is performed personally, read-only, and reported in plain language for leadership and in full technical detail for the network team.
Frequently asked questions
How many switches can you assess?
All of them. Port configuration is collected per device through the Dashboard API with bounded, rate-limited requests, so a 25-switch campus and a 250-switch estate are both in scope.
Do you need console or SSH access to the switches?
No. Everything is read through the Dashboard API. No device commands are sent.
We do not use 802.1X. Is the review still useful?
Yes. Management VLAN exposure, trunk hardening, DHCP guard, STP and storm control apply regardless, and the report shows what a phased NAC rollout would involve.
Implementation partner
OC Security Audit stays independent and read-only. If you want hands-on administration, IT Perfection can implement the fixes and support ongoing operations.
On-site across Southern California, remote nationwide
Based in Irvine, Orange County. Because the Meraki assessment reads configuration through the Dashboard API, it is delivered remotely for clients anywhere in the United States, with on-site read-outs available across Southern California.
Lock the access layer down to what it should carry
Read-only Meraki switch review, included in the Cisco Meraki security audit. Orange County, Southern California and remote nationwide.