Skip to main content

​
What this check does

DSALTA lists Heroku members and verifies each has two_factor_authentication enabled. Passes when: All Heroku members have two-factor authentication enabled.

​
Why this matters

Two-factor authentication reduces account-takeover risk for Heroku members.

​
How to fix

Register multi-factor authentication for every Heroku member
  1. Sign in to the Heroku Dashboard, open the avatar menu in the top-right, and choose Account settings.
  2. Find Multi-Factor Authentication and click Setup Multi-Factor Authentication, then click Add.
  3. Register a verification method — Salesforce Authenticator, a third-party authenticator app such as Google Authenticator, or a security key such as a YubiKey — and follow the prompts to confirm it.
  4. Click Add again to register a backup method, and store the recovery codes somewhere your team can reach them.
  5. Have every member the test flagged repeat steps 1-4 on their own account; enrollment is per user and an admin cannot complete it for someone else.
  6. On a Heroku Enterprise Team, open the team’s Access page to see who still has no MFA, and configure Single Sign-On for the team so your identity provider enforces it at every login.
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.