Skip to main content

Cisco Meraki

The Meraki integration reads a Meraki organization through the Dashboard API. The Dashboard is cloud-hosted, so the CyberOptix CTEM Platform collects from it directly. No Integrator is needed, and nothing is installed on your network.

It is read-only. The integration never changes configuration. One integration covers one Meraki organization: every network and device in it.

What it collects​

SyncCollects
Configuration backupFor each MX appliance: its LAN (VLANs or single LAN), static routes, L3 firewall, port forwarding and 1:1 NAT settings, with any secrets stripped, versioned whenever they change; the L3 firewall rules in evaluation order
Configuration reviewEvery configuration backup and NAT sync is reviewed against the configuration review checks, and what they find is raised as vulnerabilities on the device
Network discoveryEach appliance's VLAN and WAN uplink interfaces, the networks its VLANs serve, and its enabled static routes
Host discoveryThe clients each network has seen in the last day, with the device, switch port or SSID they were last seen on
Exposure correlationPort forwarding and 1:1 NAT rules, so an address reachable from outside is tied to what sits behind it

Every sync also reports the organization's devices: appliances, switches, access points, cameras and the rest, with model, serial, firmware and LAN address.

What the Dashboard reports is kept as its own record, alongside hosts and subnets rather than written into them.

Create a read-only API key​

  1. In the Dashboard, create an administrator with Read-only organization access, or use an existing one.
  2. Sign in as that administrator, open My profile, and under API access generate an API key. Dashboard API access must be enabled for the organization under Organization > Settings.
  3. Note the organization ID, shown at the bottom of every Dashboard page.

The CyberOptix CTEM Platform sends the key in an Authorization: Bearer header, never in a URL.

Connect it​

  1. Under Integrations, add Cisco Meraki with the organization ID and the API key.
  2. Enable the syncs you want.

The Dashboard's certificate is always verified against the public certificate authorities. Nothing is pinned, and a certificate that fails verification fails the sync.