> ## Documentation Index
> Fetch the complete documentation index at: https://help.dsalta.com/llms.txt
> Use this file to discover all available pages before exploring further.

# MFA should be enabled for all users

> Checks that every Neo4j Aura organization member has enrolled in multi-factor authentication.

## 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`.

<Note>
  This check also runs on 13 other integrations — see [MFA should be enabled for all users](/tests/mfa-should-be-enabled-for-all-users) for the full list.
</Note>

|               |                                                      |
| ------------- | ---------------------------------------------------- |
| **Severity**  | High                                                 |
| **Category**  | `access`                                             |
| **Data used** | Neo4j Aura organization member MFA enrollment status |

**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

**Enrol Neo4j Aura members in MFA**

1. Open **Neo4j Aura Console**.
2. Go to **Account settings**.
3. Enable multi-factor authentication for each listed member.
4. Alternatively, move those members onto an identity provider that enforces MFA for Aura 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

<AccordionGroup>
  <Accordion title="How often does this check run?">
    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.
  </Accordion>

  <Accordion title="What does the status actually tell me?">
    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](/guides/data-library/test-results).
  </Accordion>

  <Accordion title="The check shows Failed. Does that mean I am non-compliant?">
    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**.
  </Accordion>

  <Accordion title="What if this check does not apply to us?">
    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](/guides/data-library/test-detail).
  </Accordion>

  <Accordion title="Does DSALTA change my configuration?">
    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.
  </Accordion>
</AccordionGroup>