Skip to main content
Checks that MFA is enabled for all Clerk users.

​
About

When you connect Clerk to DSALTA, the platform lists your Clerk users using read-only API access and verifies that each active user has two-factor authentication enabled. Banned and locked accounts are out of scope because they cannot sign in. The check fails if any active user is missing MFA.

​
Why This Matters

Every account on the authentication platform must be protected with multi-factor authentication. A password alone is a single point of failure. If it is phished, guessed, or reused from a breached site, an attacker gains full access. Multi-factor authentication adds a second verification step that blocks the vast majority of account-takeover attempts and is a baseline requirement across most security frameworks.

​
How to Fix

Before you begin
  • Ensure you have access to the Clerk Dashboard with permission to manage authentication settings.
Enforce MFA in Clerk
  1. In the Clerk Dashboard, open User & Authentication → Multi-factor and require a second factor.
  2. In the Clerk Dashboard, open Users and confirm each active user has two-factor authentication enabled.
  3. Communicate the change to your team and set an enrollment deadline.
Once every active Clerk user has MFA enabled, DSALTA retrieves the change on the next sync and sets the check status to Passing.

​
Frequently Asked Questions

This check runs automatically every 24 hours while the Clerk integration is connected. You can also trigger a manual sync from Integrations in the sidebar.
A failing check appears in your Data Library → Tests dashboard. Work through the steps above; once the underlying configuration is fixed, the status updates automatically on the next sync.
Yes. If it does not apply to your environment, mark it as Not Applicable with a justification. The exclusion is documented for auditors.
No. DSALTA uses read-only API access and never modifies, creates, or deletes resources. All remediation is performed by your team directly in Clerk.