Symantec Endpoint

Connect Symantec Endpoint to collect endpoint detection & response evidence with automated compliance tests, switched on per workspace.

Connect with an API token

1. In Symantec Endpoint:

   1. Sign in to the Symantec Endpoint Security cloud console for your region as a user with the default Super Administrator or Administrator role (duplicated copies of those roles cannot manage client applications).
   2. Go to Integration › Client Applications and select Add.
   3. In the Add client application dialog box, type a name for the application and select Add.
   4. (Optional) In the flyout pane, on the Details tab, configure the privileges for the client application, then select Save.
   5. On the Client Application Management page, find the new application, select the menu icon and then select Client Secret to view the Client ID, Client Secret and OAuth Credentials values.

   Where to find the other values:

   • Client ID: Integration › Client Applications: the Client Application Management page lists each application with its Client ID; the menu icon › Client Secret shows it as well.
   • Client secret: Integration › Client Applications, menu icon on the application's row › Client Secret.
   • Region: The region of the cloud console you sign in to: North America (sep.securitycloud.symantec.com, API api.sep.securitycloud.symantec.com), Europe (sep.eu.securitycloud.symantec.com, API api.sep.eu.securitycloud.symantec.com) or India (sep.in.securitycloud.symantec.com, API api.sep.in.securitycloud.symantec.com).
   • OAuth token (optional): Not described on the fetched Broadcom pages. The API reference is at apidocs.security.com, or Integration › API Documentation in the cloud console.

   Symantec Endpoint's public documentation does not cover every step.

   The Broadcom page says only that privileges are configured on the flyout's Details tab; it does not list the privilege names, so the exact 'View' option label was not verified. Client ID, Client Secret and OAuth Credentials stay viewable from the menu icon after creation (the page does not say they are shown once). The Customer ID and Environment ID appear in the Client Application Management page header. Maximum 63 client applications per environment. API reference: apidocs.security.com, or Integration › API Documentation in the cloud console.

   Source: techdocs.broadcom.com, techdocs.broadcom.com, techdocs.broadcom.com, checked 2026-10-07.

   The permissions Safeguard needs: View.

2. On Compliance › Connectors, open Symantec Endpoint, click Connect, choose API token and fill in:

   Field	What to enter
   Client ID	Optional.
   Client secret	Optional. Stored encrypted and never shown again.
   Region	Required. For example: us

   Or, instead: OAuth token (optional).

3. Click Connect with token.

Frameworks

Safeguard's automated tests read Symantec 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.

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