Escape

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

Connect with an API token

1. In Escape:

   1. Sign in to Escape and open your settings at https://app.escape.tech/user/profile/.
   2. Copy your API key from that page.
   3. To limit what the key can read, have a global admin create a role in Roles Management with read permissions only and bind it to the user whose key Safeguard uses, within the projects Safeguard should read.

   Escape's public documentation does not cover every step.

   Escape's public API docs only say the API key is found in your Escape settings (user profile); they do not quote the field or button labels. The key is tied to the user, so its access follows that user's roles. Creating roles requires a global admin role (Enterprise RBAC); the exact read permission names were not on the fetched page. API base: https://public.escape.tech/v3, header X-ESCAPE-API-KEY.

   Source: docs.escape.tech, docs.escape.tech, checked 2026-10-07.

   The permissions Safeguard needs: read.

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

   Field	What to enter
   API key	Required. Stored encrypted and never shown again.

3. Click Connect with token.

Frameworks

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