BitSight

Connect BitSight to collect vendor procurement evidence with automated compliance tests, switched on per workspace.

Connect with an API token

1. In BitSight:

   1. In Bitsight, go to Settings › Account › User Preferences.
   2. For a token tied to one user's permissions (least privilege), sign in as that user and, in the User API Token section, click Generate New Token. Generating a new user token replaces and invalidates that user's previous token.
   3. Alternatively, a Bitsight Admin can create a Company API Token: in the Company API Token section, enter a description in the New Token field, click Generate, then copy the token right away and store it securely.

   Where to find the other values:

   • API token: Settings › Account › User Preferences: the user token is shown in the User API Token section; a company token is shown once, when it is generated.
   • Company ID (optional): This is your company's unique identifier (GUID). Bitsight documents getting it from the GET: Portfolio Details API endpoint, in the entity_guid value for My Company or a subsidiary.

   Help-center pages return 403 to anonymous browser-style fetches; their text was read through the help center's own public article API on help.bitsighttech.com. Company API tokens carry admin privileges, inherit the generating admin's Access Control Group and role, are shown only once and stay valid until an admin deletes them. User API tokens use the user's own permissions; one token per user, and the docs say a generated token stays displayed on the User Preferences page, so one_time_display is left unset because it differs by token type (company token: once; user token: remains visible). Bitsight does not document a read-only token scope; least privilege comes from the role of the user who generates a user token. Tokens are used as the HTTP basic-auth username with an empty password against https://api.bitsighttech.com. The pages do not show a UI location for the company GUID. Verification: the help-center article API (help.bitsighttech.com/api/v2/help_center/...) supported every step; the claim that the signing-in user's role must be able to view the company rating was not in the sources and was removed. The article says only Bitsight Admins can generate company tokens.

   Source: help.bitsighttech.com, help.bitsighttech.com, help.bitsighttech.com, checked 2026-10-07.

   The permissions Safeguard needs: view the company's own rating.

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

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

3. Click Connect with token.

Frameworks

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

• Vendor Procurement 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