Engineers checking a network device togetherTwo engineers with a laptop in a server roomIT team working in a modern computer lab on a follow-up assessment
How to secure a Cisco Meraki network

How to Secure a Cisco Meraki Network: a 12-step hardening guide

The order we recommend to clients: lock the Dashboard first, then the edge, then segmentation, wireless, switching, logging and lifecycle, and finish by re-assessing.

25+ yearsIT & cybersecurity experience
Certified expertsCISSP · C|CISO · Cisco · Microsoft
Read-only methodNo configuration changes, ever
Southern California & nationwideIrvine-based · remote audits
How to secure a Cisco Meraki network · Orange County, CA

Twelve steps, in the order that reduces risk fastest

This guide follows the ten domains of the Cisco Meraki security audit. Each step names the Dashboard area, the change and how to validate it. Use the Meraki security checklist alongside it.

01

Require MFA or enforced SSO for every Dashboard administrator

Start in Organization › Administrators. Confirm every account shows two-factor or is federated through SAML with MFA enforced at the identity provider. Remove pending invitations you do not recognize.

Related review: Meraki Dashboard security · Checklist
02

Cut full-organization administrators to documented need

Map each full admin to a job responsibility. Move the rest to network-scoped or read-only roles, and create a documented emergency-access account.

Related review: Meraki Dashboard security · Checklist
03

Inventory and restrict API keys

List every active key, its owner and its consumer. Add IP restrictions where the integration has a fixed egress, rotate anything unowned, and revoke keys for staff who have left.

Related review: Meraki Dashboard security · Checklist
04

Review inbound rules and set the default to deny

Remove any-to-any permits. For each remaining inbound rule, record the business owner, source, destination and service. Confirm the inbound default action is deny.

Related review: Meraki MX firewall security · Checklist
05

Eliminate Internet-exposed RDP, SMB and database services

Walk port forwarding, 1:1 and 1:many NAT. Anything that exposes remote desktop, file sharing, a database listener or a management interface moves behind VPN or a zero-trust access path with MFA.

Related review: Meraki MX firewall security · Checklist
06

Turn on prevention: IDS/IPS, AMP and content filtering

Validate licensing and application compatibility, then move IDS/IPS from detection to prevention, enable Advanced Malware Protection and remove security categories from content-filtering allowlists.

Related review: Meraki MX firewall security · Checklist
07

Fix segmentation: guest, IoT, management and VLAN 1

Confirm guest and IoT networks cannot reach internal addressing, management lives on its own VLAN reachable only from the administrative network, no subnets overlap and VLAN 1 carries nothing.

Related review: Meraki switch security · Checklist
08

Harden every SSID

No open or WPA1/TKIP SSIDs. Guest SSIDs: LAN access off, client isolation on. Enterprise SSIDs: two RADIUS servers, no fail-open, PMF enabled, Air Marshal monitoring on.

Related review: Meraki access point security · Checklist
09

Harden switch ports and NAC

User ports become access ports with an access policy and a restricted fallback VLAN. Trunks get an explicit VLAN list. Enable DHCP server policy, ARP inspection, storm control and set the STP root by design.

Related review: Meraki switch security · Checklist
10

Limit VPN to documented flows

Trim AutoVPN exported subnets, replace broad VPN firewall permits, confirm third-party peers, retire legacy client VPN technology and give the client VPN pool its own addressing.

Related review: Meraki VPN security · Checklist
11

Make alerts and logs reach someone

Assign monitored alert recipients. Forward firewall, IDS, switch and wireless events to syslog or your SIEM. Confirm NetFlow and SNMP settings are intentional.

Related review: Meraki Dashboard security · Checklist
12

Plan lifecycle and re-assess

Replace end-of-support hardware, bring firmware current and consistent, document maintenance windows, then run a follow-up read-only assessment to prove the roadmap closed.

Related review: Meraki Dashboard security · Checklist
31%of breaches began with vulnerability exploitation, with third parties involved in 48%Verizon Data Breach Investigations Report 2026
$4.99Mglobal average cost of a data breach, a record highIBM Cost of a Data Breach Report 2026
99%+of identity-based attacks can be blocked by multi-factor authenticationMicrosoft Digital Defense Report 2025

Related Meraki assessments

See what a baseline assessment looks like

See what a baseline assessment looks like

Real pages from the five sample deliverables for a fictional three-site organization.

Sample report
One package, one fixed price

One package, one fixed price

Every step above, evidenced read-only across your whole Dashboard organization.

Pricing
Ali Hassani, CISO and cybersecurity consultant, standing in a professional data center
Who performs the assessment

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.

How-to FAQ

Frequently asked questions

Can OC Security Audit make these changes for us?

No. The audit is independent and read-only. IT Perfection can implement the steps if you want hands-on help, and the audit’s validation procedures confirm the outcome.

In what order should we do this?

The order above: management plane first, because every other fix is only as safe as the admins who can undo it; then the Internet edge, segmentation, wireless, switching, VPN, logging and lifecycle.

How do we know when we are done?

Run a follow-up read-only assessment. The comparison report shows resolved, repeated, new and reopened items against the baseline.

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.

Service area

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.

Start with a baseline you can measure against

A read-only Cisco Meraki security audit shows exactly which of the twelve steps apply to your organization.