Skip to main content

​
What this check does

DSALTA reads the Terraform organization’s collaborator-auth-policy setting (GET /api/v2/organizations/{org}). Terraform’s API does not expose per-user 2FA status, so this is an organization-wide enforcement check: it passes only when the policy is set to require two-factor authentication for all collaborators, not a per-user enrollment check.
This check also runs on 13 other integrations — see MFA should be enabled for all users for the full list.
Passes when: The organization’s collaborator authentication policy is set to require two-factor authentication (“two_factor_mandatory”).

​
Why this matters

The organization’s infrastructure-as-code platform — capable of provisioning and destroying real infrastructure — must require multi-factor authentication for every collaborator.

​
How to fix

Enforce two-factor authentication in Terraform
  1. Open Terraform Cloud.
  2. Go to Organization Settings.
  3. Go to General.
  4. Set the collaborator authentication policy to require two-factor authentication.
  5. Have every member without 2FA enabled complete enrollment before the policy takes effect.
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.