Cisco Meraki SM
Connect Cisco Meraki SM to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Cisco Meraki SM to collect mdm evidence with automated compliance tests, switched on per workspace.
| Category | MDM |
| Connect with | API token |
| What a connection produces | Automated compliance tests |
| Cisco Meraki SM's guide | developer.cisco.com |
Connect with an API token
-
In Cisco Meraki SM:
- Sign in to the Meraki dashboard as an administrator with read-only access to the organization (the API key inherits the same permissions as the account that generates it; a read-only admin's key can make only GET requests). SAML/SSO administrators cannot generate API keys.
- Go to Organization › Configure › API & Webhooks and open the API keys and access tab (or avatar icon › My Profile › API Access).
- Select Generate API Key and copy it immediately; the moment you generate the key is the only time you can record it.
Where to find the other values:
- Network ID: Not documented in the fetched pages; the value has the form N_1234567890.
Cisco Meraki SM shows the secret only once, so copy it before you leave the page.
Cisco Meraki SM's public documentation does not cover every step.
Meraki API keys have no per-key scopes; the grant sm:config:read was not found as a selectable option, so restrict access through the generating admin's read-only role. Where the dashboard shows the Network ID was not sourced.
Source: documentation.meraki.com, developer.cisco.com, checked 2026-10-07.
The permissions Safeguard needs:
sm:config:read. -
On Compliance › Connectors, open Cisco Meraki SM, click Connect, choose API token and fill in:
Field What to enter API key Required. Stored encrypted and never shown again. Network ID Required. For example: N_1234567890 -
Click Connect with token.
Frameworks
Safeguard's automated tests read Cisco Meraki SM and map to the controls below. When a test passes, the result is evidence toward each control it maps to, in every framework listed. It is evidence toward a control, not proof that the control is met on its own.
| Framework | Evidence | Controls | Tests |
|---|---|---|---|
| SOC2 | Automated tests | C1.1, CC6.1, CC6.2, CC6.5, CC6.7, CC6.8, CC7.1 | 8 |
| ISO/IEC 27001 | Automated tests | A.5.9, A.5.11, A.6.5, A.8.1, A.8.7, A.8.8, A.8.9, A.8.24 | 8 |
| HIPAA Security Rule | Automated tests | 164.308(a)(3), 164.308(a)(5), 164.310(d)(1), 164.312(a)(1) | 8 |
| PCI DSS | Automated tests | 3.5.1, 6.3.3, 8.2.8, 12.5.1 | 6 |
| NIST CSF 2.0 | Automated tests | ID.AM-01, PR.AA-03, PR.AA-05, PR.DS-01, PR.PS-01, PR.PS-02 | 8 |
These tests are switched on per workspace by the Safeguard team.
Related
- MDM connectors
- Compliance connectors: how connecting works, card statuses and multiple accounts
- Connector setup reference: every connector in one table
- Frameworks and connectors: how connectors provide evidence for frameworks