Introduction
Integrating Cisco Maraki with Field Effect MDR allows Field Effect MDR to query your Meraki Dashboard for recent organizational configuration changes and organizational assurance alerts. This level of access to your environment enriching Field Effect MDR's monitoring fidelity, and enables ARO generation, as appropriate, based on high severity alerts.
This article walks through the following:
Requirements
You will need to administrator access your organization's Cisco Meraki and Field Effect MDR environments.
You will allow need the following information from Cisco Meraki:
| Required Information | Description |
| API Key | This will be generated while preparing Cisco Meraki for the integration. You will need to paste it into the MDR Portal. |
| Organization ID | The identifier used by Cisco Maraki to identify the organizations in your tenant. |
| Base URL | Refers to the root address for the Meraki Dashboard API. The base URL is typically https://api.meraki.com/api/v1 |
If you are a partner user with multiple end clients that use Cisco Meraki, you will need to set this integration up for each client individually, as well as have each organizations' Organization ID
Integration Instructions
The following sections walk through the process of integrating Cisco "Meraki with Field Effect MDR; creating an API key in in Cisco Meraki and providing it within the MDR Portal.
Set up Cisco Meraki for the Integration
The following sections outlines the process of setting up Cisco Meraki for this integration.
Create an API Key
- Log into your Meraki Web Management and navigate to Organization > Configure > API & Webhooks.
- From the API Keys and Access tab, click Generate API Key.
- Make note of this API Key, as you will need to paste it into the MDR Portal in the following procedure.
- Select the I have stored my new API key checkbox and click Done.
For more detailed information on Cisco Meraki API Keys, visit their Help Center Documentation.
Gather the Organization ID
Once you have the API key, you will need your organization ID. To do so, run the following command in the command prompt (replace {{api_key}} with the key you generated in the previous step):
For Windows, use the following command:
curl --location "https://api.meraki.com/api/v1/organizations" --header "X-Cisco-Meraki-API-Key: {{api_key}}"For Mac or Linux, use the following command:
curl --location 'https://api.meraki.com/api/v1/organizations' --header 'X-Cisco-Meraki-API-Key: {{api_key}}'This command will return a list of organizations that the API key is valid for. The Copy the "id" shown in the results for the organization, as you will need to paste it into the MDR Portal.
The example below shows the results of running the command above. The organization ID that would need to be copied for this example integration would be "ABCD1234".
{
"id":"ABCD12234",
"name":"Client Name Here",
"url":"https://a123.dashboard.meraki.com/o/blah/manage/organization/overview",
"samlConsumerUrl":"https://a123.dashboard.meraki.com/saml/login/blah/blahblah",
"samlConsumerUrls":["https://a123.dashboard.meraki.com/saml/login/blah/blahblahblah"],
"api":{"enabled":true},
"licensing":{"model":"co-term"},
"cloud": {
"region": {
"name":"North America",
"host":{"name":"United States"
}
}
},
"management": {
"details": [
{
"name":"customer number",
"value":"VALUE"
}
]
}
}For More information on Cisco Meraki Organizations, visit their Help Center documentation.
Complete the Integration in the MDR Portal
After completing the procedure above, log into the MDR Portal's Administration > Integrations Page. From the Cybersecurity tab, click +Add for Cisco Meraki.

The integration wizard will open. Provide the Base URL for your organization, API Key, and Organization ID you gathered in the previous procedure. When ready, click Submit.

You'll be taken back to the integrations page, and the integration card will show that the integration is connected and promoted to the top, alongside any other connected integrations
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article