Cisco Secure Endpoint
Connect Cisco Secure Endpoint to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Cisco Secure Endpoint to collect endpoint detection & response evidence with automated compliance tests, switched on per workspace.
| Category | Endpoint Detection & Response |
| Connect with | API token |
| What a connection produces | Automated compliance tests |
| Cisco Secure Endpoint's guide | developer.cisco.com |
Connect with an API token
-
In Cisco Secure Endpoint:
- Sign in to the Secure Endpoint Console and go to Accounts › API Credentials.
- Click New API Credential.
- Enter an Application name and set Scope to Read-only.
- Click Create. The API Key Details page shows the API Client ID and the API Key; copy both now.
Where to find the other values:
- Client ID: Shown on the API Key Details page after you click Create (the API Client ID).
- Region: Matches your console's cloud: North America uses api.amp.cisco.com, Europe uses api.eu.amp.cisco.com, Asia Pacific, Japan and China use api.apjc.amp.cisco.com.
Cisco Secure Endpoint shows the secret only once, so copy it before you leave the page.
Cisco Secure Endpoint's public documentation does not cover every step.
The official click path comes from Cisco's AMP for Endpoints tech note (Accounts > API Credentials). Cisco's developer authentication page describes a different flow (Administration > API Clients > Generate API Client) for API clients with a Client Id and Client Password; it was not used for these steps. Cisco says the credentials are displayed once only.
Source: cisco.com, developer.cisco.com, checked 2026-10-07.
The permissions Safeguard needs:
Read-only. -
On Compliance › Connectors, open Cisco Secure Endpoint, click Connect, choose API token and fill in:
Field What to enter Region Required. Client ID Required. API key Required. Stored encrypted and never shown again. -
Click Connect with token.
Frameworks
Safeguard's automated tests read Cisco Secure Endpoint 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 | CC6.8, CC7.1, CC7.2, CC7.3, CC7.4 | 6 |
| ISO/IEC 27001 | Automated tests | A.5.26, A.8.1, A.8.7, A.8.8, A.8.16 | 6 |
| HIPAA Security Rule | Automated tests | 164.308(a)(1), 164.308(a)(5), 164.308(a)(6) | 6 |
| PCI DSS | Automated tests | 5.2.1, 5.3.1, 6.3.3, 12.10.1 | 6 |
| NIST CSF 2.0 | Automated tests | DE.AE-02, DE.CM-09, ID.RA-01, PR.PS-02, RS.MI-02 | 6 |
These tests are switched on per workspace by the Safeguard team.
Related
- Endpoint Detection & Response 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