Socket

Connect Socket to collect vulnerability scanning evidence with automated compliance tests, switched on per workspace.

Connect with an API token

1. In Socket:

   1. On the Socket dashboard, go to Settings in the left-hand menu.
   2. Click the API Tokens tab.
   3. Click + Create API token in the upper-right corner.
   4. In the dialog, set a name and choose only the scope alerts:list (List all alerts).
   5. Click Confirm to generate the token, and copy it.

   Where to find the other values:

   • Organization (optional): Your Socket organization slug; the token is created inside the organization you are viewing in the dashboard (the API's organizations endpoint lists the organizations associated with the token).

   Source: docs.socket.dev, docs.socket.dev, checked 2026-10-07.

   The permissions Safeguard needs: alerts:list.

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

   Field	What to enter
   API token	Required. Stored encrypted and never shown again.
   Organization (optional)	—

3. Click Connect with token.

Frameworks

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

• Vulnerability Scanning 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