Skip to main content

Cisco Meraki Discovery

Vulcan discovers your Cisco Meraki cloud-managed infrastructure via the Meraki Dashboard API, providing visibility into organizations, networks, and devices.

Overview​

Meraki discovery connects to the Meraki Dashboard API to enumerate:

  • Organizations — Your Meraki orgs and their settings
  • Networks — MX, MS, MR, MV, and MT networks
  • Devices — All Meraki hardware with serial, model, firmware

Discovered Resources​

Node TypeDescription
meraki.organizationMeraki organization
meraki.networkNetwork (site/location)
meraki.applianceMX Security Appliance
meraki.switchMS Switch
meraki.wirelessMR Access Point
meraki.cameraMV Smart Camera
meraki.sensorMT Sensor

Setup​

1. Enable Dashboard API​

In the Meraki Dashboard:

  1. Go to Organization → Settings
  2. Scroll to Dashboard API access
  3. Enable API access

2. Generate API Key​

  1. Click your profile (top-right corner)
  2. Go to API access
  3. Click Generate new API key
  4. Copy the key immediately (it's only shown once)

3. Configure in Vulcan​

  1. Go to Discovery → Meraki tab
  2. Enter your API key
  3. Optionally specify an Organization ID to limit scope
  4. Click Run Discovery

Required Permissions​

The API key grants read access based on your Meraki admin role:

  • Full admin: Access to all orgs you manage
  • Read-only admin: Sufficient for discovery
  • Org-specific admin: Limited to assigned organizations
Security Best Practice

Create a dedicated read-only admin account for Vulcan to follow least-privilege principles.

API Rate Limits​

Meraki API has rate limits:

  • 5 API calls per second per organization
  • Vulcan respects these limits automatically

Compliance Integration​

Discovered Meraki assets are evaluated against compliance frameworks:

  • Network segmentation verification
  • Firmware version auditing
  • Security policy configuration checks

Topology Visualization​

Meraki networks appear in the topology view with:

  • Organization → Network → Device hierarchy
  • Device connectivity and relationships
  • Geographic location from device coordinates