Send Cisco Meraki logs to LogPulse

From the Meraki Dashboard API: intrusion and malware events of the MX appliances, configuration changes by admins, and assurance alerts of the whole organization.

In short
To send Cisco Meraki logs to LogPulse, add Cisco Meraki under Configure → Sources → Cloud. LogPulse reads the Meraki Dashboard API itself, without an agent. Events land in the firewall, audit, network indexes with source meraki and fill the Intrusion Detection, Change, Alerts data models.

Overview

How Cisco Meraki data reaches LogPulse
Vendor
Meraki Dashboard API
Collect
Integration pollerreads new events, maps the fields
Store
index=firewall
index=audit
index=network
  1. Meraki Dashboard API to Integration poller
  2. Integration poller to index=firewall
  3. Integration poller to index=audit
  4. Integration poller to index=network

LogPulse signs in to Cisco Meraki with the credential you give it and fetches new events every five minutes by default. You can set the interval per integration, from one minute to 24 hours.

What you need

  • A Meraki API key of a read-only organization admin
  • In LogPulse: a role that may manage API keys. Cloud integrations fall under that right.

1. Create a credential in Cisco Meraki

Field in LogPulseWhere you find it
API keyIn the dashboard: My profile, API access, Generate API key. A read-only admin is enough. Stored encrypted and never shown again.
Organization IDAt the bottom of every dashboard page, or under Organization, Settings.
API host (optional)Only outside the global region: api.meraki.ca, api.meraki.cn, api.meraki.in or api.gov-meraki.com.

2. Add the integration in LogPulse

Go to Configure → Sources → Cloud and choose Cisco Meraki. Fill in the fields, tick the data sources you want and save. LogPulse first tests the connection with your credential and tells you what is wrong when it fails.

Tip: Secrets are stored encrypted and never shown again. To change one, paste a new value; the rest stays.

What arrives

Data sourceIndexSourceSourcetypeWhat it holds
Security eventsfirewallmerakimeraki:organizationsecurityIDS/IPS alerts and AMP file verdicts of the MX appliances: source and destination, signature, priority and whether it was blocked.
Configuration changesauditmerakimeraki:auditEvery change in the dashboard: admin, network, page, setting and the old and new value.
Assurance alertsnetworkmerakimeraki:assurancealertsAlerts on devices and networks: offline, VPN down, high usage, with severity and whether they were resolved.

The index is the kind of data and the source is the product, so detection rules for that kind of data find Cisco Meraki without changes.

Note: Per-device event logs (flows, URLs) come in over syslog to a LogPulse agent, not through the API.

Fields and data models

Data modelWhat you get
Intrusion DetectionIDS/IPS and malware events with source, destination and signature.
ChangeDashboard changes with admin, setting and old and new value.
AlertsAssurance alerts with severity and status.

Field names follow the CIM field names. These are the fields LogPulse sets on Cisco Meraki events; a field is left out when Cisco Meraki did not send a value.

  • action
  • category
  • change_type
  • description
  • dest
  • dest_category
  • dest_id
  • dest_ip
  • dest_name
  • dest_port
  • disposition
  • dvc_mac
  • file_hash
  • file_type
  • id
  • network
  • new_value
  • object
  • object_attrs
  • object_category
  • old_value
  • severity
  • signature
  • signature_id
  • src
  • src_ip
  • src_mac
  • src_name
  • src_port
  • status
  • transport
  • url
  • user
  • user_id
  • user_name
  • vendor_action

The original record of Cisco Meraki is kept with each event under raw, so nothing the vendor sent is lost.

3. Check the data

The first events arrive within a few minutes. Check what came in:

earliest=-1h index IN (firewall, audit, network) source IN (meraki)
| stats count by index, source, sourcetype

The integration page in LogPulse shows when it last read events and the last error, if any.

Troubleshooting

The connection test names what is wrong. These are the answers you are most likely to see.

What you seeWhat to do
Meraki refused the API key.Generate a new key in the dashboard under My profile, API access, and paste it in the integration.
The API key has no access to this organization ID.Check the organization ID at the bottom of a dashboard page, and that the admin who owns the key is an admin of that organization. Read-only is enough.
apiHost is the API host of your region, e.g. api.meraki.comLeave the API host empty unless your organization is in Canada, China, India or the US government region.
The test passes but no events arrive.Run the search above over a longer time. No results: check on the integration page that the data source is switched on and when it last read events. Cisco Meraki may also simply have had nothing new.

Frequently asked questions

How do I send Cisco Meraki logs to LogPulse?
Add the Cisco Meraki cloud integration under Configure, Sources, Cloud in LogPulse and fill in API key, Organization ID. LogPulse reads the Meraki Dashboard API itself, every five minutes by default; there is nothing to install.
Which permissions does LogPulse need in Cisco Meraki?
A Meraki API key of a read-only organization admin. Read access is enough for collecting logs.
Which index does Cisco Meraki data go to?
The index is the kind of data: firewall, audit, network. The source is the product: meraki. Each data source has its own sourcetype, listed on this page.
Which data models does Cisco Meraki fill?
Intrusion Detection, Change, Alerts. Detection rules and dashboards written for a data model work on Cisco Meraki without changes.
Does this integration bring in Meraki device logs?
No. It reads the organization endpoints of the Dashboard API: security events, configuration changes and assurance alerts. Device syslog (flows, URLs, events) comes in through the LogPulse agent as a syslog source.