Skip to main content
The Cisco Meraki module addresses no addresses in your network. Instead it needs an API key—and therefore nothing you would have to enter target by target. The wizard shows four steps for this module: Basics › Authentication › Schedule › Summary All but Authentication are the same for every module—see Creating a Scan Job. A connected gateway is required.

​
Prerequisites

The scan reads the organization through the Meraki cloud.

​
Ports and protocols

​
Permissions

The API key belongs to a dashboard administrator with read access to the organization; organization-wide read permissions are sufficient. One API key captures the whole organization with all its networks and devices.

​
The key

Here the Authentication step carries no Windows credentials but the Meraki API key. The entry for it has the type API Key and consists of a single, masked field. You choose it in the same searchable picker as with the other modules and create missing ones through New Credentials… or One-Time Credentials… directly here. Entries of this type are managed under Scan › Credentials.
Unlike with Active Directory and Windows (AD), credentials are mandatory here: without an entry the step cannot be passed.

​
Without targets or options

This module carries no table with targets. The Customize button does not appear here either: Cisco Meraki brings no options of its own. That leaves only the scheduling to be decided for the job. Which types this scan produces is under Network and Devices. How you watch the job afterwards is in Managing Jobs.