Bugcrowd

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

Connect with an API token

1. In Bugcrowd:

   1. Log into Bugcrowd as an Organization Owner (API key management is available to Organization Owner roles). Tokens are provisioned per user and authorize resources based on that user's role.
   2. Click your profile picture in the top right and select API Credentials from the drop-down menu.
   3. Specify a descriptive name for the credentials (for example Safeguard).
   4. Click Create credentials, then copy the token credentials shown. They are not viewable after the page is refreshed or you move away.
   5. Optional: under Current credentials, click Edit IP Allowlist in the Actions column, click Add Allowlist entry, add Safeguard's outbound IPv4 address, and click Save.

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

   Source: docs.bugcrowd.com, checked 2026-10-07.

   The permissions Safeguard needs: view the programs' submissions. If Bugcrowd restricts API access by IP address, allow Safeguard's outbound address.

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

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

3. Click Connect with token.

Frameworks

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