Intruder

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

Connect with an API token

1. In Intruder:

   1. In the Intruder portal, go to My account (https://portal.intruder.io/settings/account) and locate the API Access Tokens section.
   2. Provide a name for the token (for example Safeguard) and, optionally, an expiry date (leave blank for no expiry).
   3. Enter your account password and select OK. The token is generated.
   4. Use the Copy button to copy the token and save it now; you won't be able to access it again.

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

   Intruder access tokens are personal access tokens linked to your Intruder user account, so the token has that user's access. Intruder documents no read-only scope for tokens; use a user with the least privileged role that can see the targets and issues. Base URL and account fields are not needed for Intruder.

   Source: developers.intruder.io, developers.intruder.io, checked 2026-10-07.

2. On Compliance › Connectors, open Intruder, 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

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