Skip to main content

​
What this check does

DSALTA reads each member’s mfa_enrollment_status from the Aura organization users endpoint (GET /v2beta1/organizations/{org}/users). Members who sign in through an external identity provider are reported separately and not counted for or against the result, because Aura cannot see whether that provider enforced MFA. The check flags any remaining member whose status is not_enrolled.
This check also runs on 13 other integrations — see MFA should be enabled for all users for the full list.
Passes when: Every member subject to Aura-managed sign-in has enrolled in multi-factor authentication.

​
Why this matters

The organization’s managed graph databases hold production application data, so every member who can sign in to the Aura Console must be protected by multi-factor authentication.

​
How to fix

Require multi-factor authentication for Aura members
  1. Sign in to the Neo4j Aura Console as an Organization Owner or Organization Admin, using email and password — MFA cannot be configured from an SSO or Google Sign-In session.
  2. Go to Organization Settings → Security & Networking → App MFA (Multi-Factor Authentication) and enable Multi-Factor Authentication (MFA), which makes setup mandatory for every member.
  3. Tell each member to sign in and follow the prompt, or to enroll directly from Account → Settings → Preferences → Security by enabling Multi-Factor Authentication (MFA), scanning the code with an authenticator app, and entering the verification code.
  4. Open the organization Users page from the console sidebar and confirm no member is still listed as not enrolled.
  5. Remove any member who will not enroll and no longer needs Aura 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.