Skip to main content

​
What this check does

DSALTA lists the members of your Neon organization (GET /api/v2/organizations/{id}/members) and reads each member’s MFA flag. Any member whose flag is not set fails the check, and members for whom Neon reports no value count as not enabled rather than being skipped. The result also records whether the organization itself has Require 2FA switched on, for context.
This check also runs on 19 other integrations — see MFA should be enabled for all users for the full list.
Passes when: Every Neon organization member has MFA (multi-factor authentication) enabled.
This check reads the live member list on every run, not the Access page. If Neon returns no members at all, the run ends in an error rather than a pass, so a broken key is never mistaken for full MFA coverage.

​
Why this matters

Every account on the organization’s database platform must be protected with multi-factor authentication. A Neon member can open project connection details, so a password alone on any member is a direct path to production data.

​
How to fix

Require two-factor authentication in Neon
  1. Sign in to the Neon Console as an organization Admin who already has 2FA or a passkey enabled — Neon will not let you enforce it otherwise.
  2. Open the organization, go to Settings, and switch on the two-factor requirement. Members who do not yet meet it are prompted to enrol the next time they open the organization; either 2FA or a passkey satisfies it.
  3. Ask each flagged member to enrol now rather than waiting for their next visit, from their own Account settings.
  4. Open the organization’s People page and confirm no member is still reported without MFA.
  5. Remove any member who will not enrol and no longer needs Neon 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.