Cisco Meraki

Cisco Meraki solutions include wireless, switching, security, EMM, communications, and security cameras, all centrally managed from the web.

Asset Types Fetched

• Devices, Software, Application Settings, SaaS Applications, Networks, Accounts/Tenants, Network/Firewall Rules, Network Devices, Alerts/Incidents (if Fetch Air Marshal data is selected in Advanced Settings), Network Routes

Before You Begin

Ports

• TCP port 80/443

Authentication Method

• API Key

Creating an API Key

To create an API key:

1. Navigate to the Admin panel. After logging into the panel, click the username in the top right of the screen and then on My profile:
2. Click My Profile.
3. Under the API Access section, click Generate new API key and save it to a secure location (you will need it later when configuring the adapter).
4. Refer to Enabling APIs for further information.

Permissions

The value supplied in API Key for a user account that has permissions to fetch assets.

Connecting the Adapter in Axonius

1. From the Adapters page, search for Cisco Meraki and select the adapter.
2. Click Add Connection. The Create Connection drawer opens on the Connection Configuration tab.
3. Fill in the sections below, then save the connection.

To check that Axonius can reach the source before you enter credentials, click Check Network Connectivity. For more details, see Adding a New Adapter Connection.

Environment

The instance this connection reads from.

1. CiscoMeraki Domain (required) - The hostname or IP address of the Cisco Meraki server. The domain is: https://api.meraki.com
2. API Prefix (default: api) - An API prefix. Either use the default value displayed or leave empty.

Access

How Axonius authenticates to the instance.

1. API Key (required) - An API key for a user account that has the Required Permissions to fetch assets.

More Options

1. VLAN Exclude List - Enter a comma-separated list of VLANs from which devices are not fetched. If there are any surrounding spaces, they are automatically removed.

2. Exclude No VLAN Clients - Select to not fetch devices which are not associated with a VLAN.

3. SSID Exclude List - Enter a comma-separated list of SSIDs from which devices are not fetched. If there are any surrounding spaces, they are automatically removed.

4. Verify SSL (default: enabled) - Select whether to verify the SSL certificate of the server against the CA database inside of Axonius. For more details, see SSL Trust & CA Settings.

5. HTTPS Proxy - Connect the adapter to a proxy instead of directly connecting it to the domain.

6. Select Gateway – Select the Axonius Gateway to use when connecting adapters whose sources are only accessible by an internal network and not from the primary Axonius instance, which may be an Axonius-hosted (SaaS) instance or Customer-hosted (on-premises / private cloud). To use this option, you need to set up an Axonius Gateway.

To learn more about common adapter connection parameters and buttons, see Adding a New Adapter Connection.

Advanced Settings

1. Fetch clients URLs history - Select this option to fetch clients URLs history.
2. Time in seconds to sleep between each request (optional, default: 0) - Specify sleeping time in seconds between each API request Axonius sends to this adapter.
3. Fetch MDM devices (required, default: true) - Select this option to fetch MDM devices from Cisco Meraki.
4. Fetch additional data for MDM devices - Select this option to fetch the following data for Cisco Meraki MDM devices:
   • Device profiles
   • Restrictions
   • Security centers
   • Installed software
5. Fetch client policies - Select this option to fetch client policies.
6. Fetch firewall rules - Select this option to fetch firewall rules.
7. Fetch Air Marshal data - Select this option to fetch data from the 'getNetworkWirelessAirMarshal' endpoint.
8. Fetch clients (Default: enabled) - Clear this option to stop fetching client devices. SaaS application data derived from clients is not fetched when this option is disabled.
9. Fetch organizations as Accounts (Default: enabled) - Clear this option to stop fetching Cisco Meraki organizations as Accounts.
10. Fetch networks and VLANs as Networks (Default: enabled) - Clear this option to stop fetching Cisco Meraki networks and VLANs as Networks.
11. Collect device clients in the background (Default: disabled) - Select this option to collect the clients of each network device in a background job instead of during the fetch. The fetch becomes shorter, but client host names and addresses can be up to the background interval old, and a new client appears after the next background run.
12. Background device clients interval (hours) (Default: 12) - Enter how often, in hours, the background job collects device clients. Enter a value from 1 to 168. Keep the value close to the length of your discovery cycle.
13. Parse hostname - From the dropdown, select the source data for hostname parsing.

9. Exclude host name from Client device IDs Enable this setting to help reduce duplicate devices in tenants that use MSLA, or where client device host names change frequently.
10. Enable Custom Parsing - Enable this option to define how to parse specific fields from the raw data fetched. You can choose to parse the data into an already existing field, or create a new one. See Adapter Custom Parsing for more information.

Related Enforcement Actions

• Cisco Meraki - Provision Client Policy
• Cisco Meraki - Update Client Policy

Troubleshooting

If your Meraki uses IP restrictions, then make sure you add the IP address of the Axonius instance to the Permissions list.