Cisco Meraki Dashboard

Community Platform

runZero integrates with Cisco Meraki Dashboard by importing data from the Cisco Meraki Dashboard API. This integration allows you to sync data about your devices and network clients from Meraki to provide better visibility of your network.

Getting started with Meraki

To set up an integration with Meraki, you’ll need to:

  1. Generate an API key for your Cisco Meraki Dashboard administrator account.
  2. Configure the Meraki credential in runZero.
  3. Choose whether to configure the integration as a scan probe or connector task.
  4. Activate the integration to pull your data into runZero.

Requirements

Before you can set up the Meraki integration:

  • Make sure you have administrator access to the Meraki Dashboard.

Step 1: Generate an API key in Cisco Meraki Dashboard

  1. Log into Cisco Meraki Dashboard with an administrator account.
  2. Check that access to the Cisco Meraki Dashboard API is enabled. This must be enabled for each organization you would like to sync.
    1. Navigate to Organization > Settings and enable API access under Dashboard API access.
  3. Navigate to My profile to generate an API key. The API key will inherit the same permissions as the account that created it.

Step 2: Add the Meraki API key to runZero

  1. Go to the Credentials page in runZero.
  2. Choose Meraki API Key from the list of credential types.
  3. Provide a name for the credential, like Meraki.
  4. Provide the following information:
    • Meraki API URL - The API Endpoint URL used to access the Cisco Meraki Dashboard API.
    • Meraki API key - The API key for the Cisco Meraki Dashboard administrator account.
  5. If you want other organizations to be able to use this credential, select the Make this a global credential option. Otherwise, you can configure access on a per-organization basis.
  6. Save the credential.

You’re now ready to set up and activate the connection to bring in data from Meraki.

Step 3: Choose how to configure the Meraki integration

The Meraki integration can be configured as either a scan probe or a connector task. Scan probes gather data from integrations during scan tasks. Connector tasks run independently from either the cloud or one of your Explorers, only performing the integration sync.

Step 4: Set up and activate the integration to sync data

After you add your Meraki credential, you’ll need to sync your data from Meraki.

Step 4a: Configure the Meraki integration as a connector task

A connection requires you to specify a schedule and choose a site. The schedule determines when the sync occurs, and the site determines where any new Meraki-only assets are created.

  1. Activate a connection to Meraki. You can access all available third-party connections from the integrations page, your inventory, or the tasks page.
  2. Choose the credentials you added earlier. If you don’t see the credentials listed, make sure the credentials have access to the organization you are currently in.
  3. Optionally provide a list of organization IDs or names to include in the import. The list must be comma-separated. We will only import data for the organizations specified.
  4. Optionally provide a list of network IDs or names to include in the import. The list must be comma-separated. We will only import data for the networks specified.
  5. Optionally provide a comma-separated list of VLANs to exclude from the import. We will not import devices associated with the specified VLANs.
  6. If you want to exclude assets that are not associated with a VLAN, set the Exclude clients with no VLAN option to Yes.
  7. Optionally provide a comma-separated list of SSIDs to exclude from the import. We will not import devices connected on the specified SSIDs.
  8. Enter a name for the task, like Meraki Sync (optional).
  9. Choose the Explorer to perform this connector task from (optional).
  10. Choose the site you want to add your assets to. All newly discovered assets will be stored in this site.
  11. Enter a description for the task (optional).
  12. If you want to exclude assets that have not been scanned by runZero from your integration import, switch the Exclude unknown assets toggle to Yes. By default, the integration will include assets that have not been scanned by runZero.
  13. Schedule the sync. A sync can be set to run on a recurring schedule or run once. The schedule will start on the date and time you have set.
  14. Activate the connection when you are done. The sync will run on the defined schedule. You can always check the Scheduled tasks to see when the next sync will occur.

Step 4b: Configure the Meraki integration as a scan probe

You can run the Meraki integration as a scan probe so that the runZero Explorer will pull your Meraki assets into the runZero Console.

In a new or existing scan configuration:

  • Ensure that the MERAKI option is set to Yes in the Probes and SNMP tab and change any of the default options if needed.
  • Set the correct MERAKI credential to Yes in the Credentials tab.

Step 5: View Meraki assets

After a successful sync, you can go to your inventory to view your Meraki assets. These assets will have a Cisco icon listed in the Source column.

To filter by Meraki assets, consider running the following queries:

Click into each asset to see its individual attributes. runZero will show you the attributes gathered from Meraki.

Updated
Previous: Censys Search & Data Next: CrowdStrike Falcon