Skip to main content

​
What this check does

DSALTA lists active OneLogin users and verifies each has at least one enrolled MFA device (GET /api/2/mfa/users/{id}/devices).
This check also runs on 13 other integrations — see MFA should be enabled for all users for the full list.
Passes when: All active OneLogin users in scope have MFA enrolled.
Check parameters. This check evaluates against the following defaults:
  • maxUsersToCheck: 200

​
Why this matters

MFA reduces account-takeover risk for identity-provider accounts.

​
How to fix

Enforce MFA in OneLogin
  1. Sign in to the OneLogin admin portal and go to Security → Authentication Factors; enable the factors you want to allow (OneLogin Protect, WebAuthn, or another OTP method).
  2. Go to Security → Policies, open the User Policies tab, and select the policy that applies to your users (or click New User Policy).
  3. Open the policy’s MFA tab and switch OTP Auth Required to On.
  4. Under Allowed Authentication Factors, select the factors users may register, and set the policy to require MFA at every login rather than only on untrusted devices.
  5. Click Save.
  6. Go to Users → Users, open each user without a registered factor, and on their Authentication tab assign this policy so they are prompted to enroll at next sign-in.
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.