Bugsnag
Connect Bugsnag to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Record your Bugsnag connection as observability evidence. Automated collection is not available for this provider yet.
| Category | Observability |
| Connect with | API token |
| What a connection produces | Connection record |
Connect with an API token
-
In Bugsnag:
- In your BugSnag dashboard, open your user settings (keyboard shortcut g then u).
- Select Personal auth tokens.
- Generate a new auth token and copy it.
Where to find the other values:
- Base URL (optional): BugSnag's API is at https://api.bugsnag.com; BugSnag Enterprise (on-premise) installations use their own API endpoint.
Bugsnag's public documentation does not cover every step.
BugSnag's Data Access API docs (developer.smartbear.com/bugsnag/docs/data-access) show only a sign-in prompt, so the steps come from BugSnag's SSO/SCIM setup page and the README of BugSnag's official Ruby API client. Personal auth tokens act with the permissions of the user who creates them; BugSnag does not document a read-only token scope, so create it from a user whose collaborator role gives only the access needed. The SCIM page specifies an organization administrator, which is required for SCIM but not stated as required for Data Access API reads. The exact name of the generate button, whether the token is shown only once, and where the organization ID or slug is shown in the UI were not found on a readable official page.
Source: docs.bugsnag.com, raw.githubusercontent.com, checked 2026-10-07.
-
On Compliance › Connectors, open Bugsnag, 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) — -
Click Connect with token.
Frameworks
Bugsnag publishes no API for what these tests check, so its evidence is an attestation: connect it to record the connection, then attest the result. An accepted attestation counts toward each control below.
| Framework | Evidence | Controls | Tests |
|---|---|---|---|
| SOC2 | Attestation | CC6.2, CC6.3 | 1 |
| ISO/IEC 27001 | Attestation | A.5.18 | 1 |
| HIPAA Security Rule | Attestation | 164.308(a)(3) | 1 |
| PCI DSS | Attestation | 7.2.4 | 1 |
| NIST CSF 2.0 | Attestation | PR.AA-05 | 1 |
These tests are switched on per workspace by the Safeguard team.
Related
- Observability 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