Skip to main content

​
What this check does

DSALTA lists the members of your Turso organization (GET /v1/organizations/{slug}/members) and reads each member’s MFA flag. Any member whose flag is not set fails the check, and members for whom Turso reports no value count as not enabled rather than being skipped. The result also records whether the organization itself requires MFA, 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 Turso organization member has MFA (multi-factor authentication) enabled.
This check reads the live member list on every run, not the Access page. If Turso returns no members at all, the run ends in an error rather than a pass, so a broken token 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 Turso member can create database tokens and read data, so a password alone on any member is a direct path to production data.

​
How to fix

Require MFA in Turso
  1. Sign in to app.turso.tech as an organization owner or admin.
  2. Open the organization’s Settings and turn on the option that requires MFA for the organization, so members without it are made to enrol.
  3. Ask each flagged member to enrol now: in their own Settings, under Security, they enable multi-factor authentication.
  4. List the members again — in the dashboard, or with turso org members list in the Turso CLI — and confirm no one is still reported without MFA.
  5. Remove any member who will not enrol and no longer needs Turso 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.