Skip to main content

​
What this check does

DSALTA lists the collaborators of your Bugsnag organization (GET /organizations/{id}/collaborators), leaves out pending invitations, and reads each collaborator’s two-factor flag. A collaborator whose flag is off fails the check, and so does one for whom Bugsnag returns no value at all — a status that cannot be verified is reported separately in the result and is never treated as compliant.
This check also runs on 19 other integrations — see MFA should be enabled for all users for the full list.
Passes when: Every Bugsnag collaborator has two-factor authentication enabled, and none has an undeterminable status.
This check reads the live collaborator list on every run, not the Access page. If Bugsnag returns no collaborators at all, the run ends in an error rather than a pass. The Source Data tab lists collaborators without two-factor and, separately, collaborators whose status Bugsnag did not report.

​
Why this matters

Every account on the organization’s error-monitoring platform must be protected with multi-factor authentication. Bugsnag error reports carry stack traces, request data and user metadata from production, so a password alone on any collaborator exposes that data.

​
How to fix

Enable two-factor authentication for every Bugsnag collaborator
  1. Ask each flagged collaborator to sign in to app.bugsnag.com, open My account settings, and enable two-factor authentication with an authenticator app.
  2. Sign in as an organization Admin, open Settings → Organization → Collaborators, and confirm every collaborator now shows two-factor enabled.
  3. Remove any collaborator who will not enrol and no longer needs Bugsnag access.
Once resolved, DSALTA records a 200 (compliant) result on this test’s Source Data tab at the next scheduled run.

​
Frequently asked questions

Once a day, at 02:00 America/New_York, while the integration is connected. A run is skipped entirely if the integration is not in a connected state, or if the test has been deactivated.To see a fix reflected sooner, open the test from Data Library → Tests and click Run in the Run Test row. You need Full Access to run a test on demand.
The Status column answers “did the check run?”, not “did I pass”. Completed means DSALTA reached your system and finished evaluating — a check that ran and found a problem is still Completed.To see what it found, open the test and read the result code on the Source Data tab. 200 means nothing to fix; 204 means the check did not apply to your environment; 207 means it ran and found a compliance gap you need to act on. See Understanding test results.
Usually not. On an integration-powered check, Failed means DSALTA was blocked and could not evaluate it — result code 403 (a missing permission) or 428 (a setting DSALTA still needs from you). Code 500 means the run failed on DSALTA’s side.A genuine compliance gap does not turn the list red — it runs to completion and shows 207.
Deactivate it: open the test from Data Library → Tests, then use the ⋮ menu at the top right of the panel and choose Deactivate Test. It applies immediately, with no confirmation step.Write your justification in the Comments tab before you deactivate. Once deactivated, every other tab is grayed out, so Comments is the only place an auditor can read why — see Test detail.
No. DSALTA only reads. It never creates, modifies, or deletes resources, and every remediation step is performed by your team directly in the third-party product.