Cynet

Record your Cynet connection as endpoint detection & response evidence. Automated collection is not available for this provider yet.

Connect with an API token

1. In Cynet:

   1. In the Cynet console, navigate to Settings > Users & Roles from the Cynet toolbar and click the API Users tab.
   2. Click New.
   3. Enter a name for the API user and select a role from the dropdown list.
   4. Select which sites the API user should have access to from the sites list.
   5. Click Add.
   6. Copy the Secret Key displayed and save it somewhere safe, then click Close. The Secret-Key is shown only once; the Access-Key stays visible on the API Users page.
   7. Call Cynet's Get Token API with the Access-Key and Secret-Key to obtain an access token, which is sent as a Bearer token on every API call.

   Where to find the other values:

   • Account / Org / Workspace (optional): In the Cynet 360 console, Global Settings > Client Site Manager > Sites Status lists your sites with their client IDs (per Cynet's API V1 reference); single-tenant customers contact Cynet to receive their client ID.

   Cynet shows the secret only once, so copy it before you leave the page.

   An API user has a name, a role, and access to all sites or specific sites; Cynet's article does not name a read-only role, so pick the least-privileged role available. The access token from Get Token stays valid for the Inactivity Logout Time set under Settings > Users & Roles > Settings, from issuance regardless of use, and each user can have one valid token at a time, so a stored token will expire. On-premises Cynet 360 (API V1) instead uses a local user's username and password with the Cynet API User permission, and its tokens last 60 minutes. The SaaS API base URL was not found in the pages read. The API reference pages render in the browser; their Markdown was read through the docs site's own Stoplight API on help.api.cynet.com. Verification 2026-10-07: removed the unsourced claim that the SaaS siteGuid appears in the console URL; the client ID location comes from Cynet's API V1 (Cynet 360) call-format page. Cynet's article does not name a read-only role, so pick the least-privileged role available.

   Source: help.cynet.com, help.api.cynet.com, help.api.cynet.com, help.api.cynet.com, help.api.cynet.com, help.api.cynet.com, checked 2026-10-07.

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

   Field	What to enter
   API token / Personal access token	Required. Stored encrypted and never shown again.
   Base URL (optional)	—
   Account / Org / Workspace (optional)	—

3. Click Connect with token.

Frameworks

Cynet publishes no API for what these tests check, so its evidence is an attestation: connect it to record the connection, then attest the result. An accepted attestation counts toward each control below.

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