Back to blog

Product and Engineering

Enforcing the security that matters most with granular MFA

Enforcing the security that matters most with granular MFA

Enforcing the security that matters most with granular MFA

Vinny Mullin

·

1 min read

Today, we're introducing granular Multi-Factor Authentication (MFA), giving developers the ability to define which wallet actions require additional verification through Privy's policy engine, while allowing other actions to proceed without interruption.

Security often comes with a tradeoff: require additional verification for every action and introduce unnecessary friction; or remove those checks and leave sensitive operations less protected. 

The better approach is to apply additional verification where the risk is greatest. 

Anyone who shops online has seen this security model with credit cards. A small purchase at a familiar store usually goes through with no extra step, but a large or unusual purchase can trigger a second check, like a 3D Secure prompt or a one-time code sent to your phone. Cardholders pay attention when this step appears because of its rarity.

Use policies to decide when MFA is required

Granular MFA is built into Privy's policy engine, as part of the same rules your team would use to control what a wallet can do. 

A policy can allow an action, deny it, or require MFA before it proceeds. Common configurations include:

  • Wallet export: Require MFA before a user exports a private key or seed phrase

  • Large transfers: Require MFA above an amount your team sets, and let smaller transfers through

  • Withdrawals: Require MFA to withdraw funds to external, unrecognized addresses

  • Every action: Require MFA for all wallet activity, and require every user to enroll

These rules let teams enforce the controls defined by their risk and compliance requirements, including transfer thresholds and additional verification for sensitive operations.

Enforced inside the secure enclave

Privy checks every request against the wallet's policies inside the Trusted Execution Environment (TEE), the isolated enclave where wallet keys are used.

Requests that require MFA can only proceed with both a valid user session and recent MFA verification. A  compromised session is not enough to authorize a protected action. 

When you assign a policy to a user, updating or deleting that policy requires the user's MFA. A hostile actor can’t simply remove an MFA requirement to force a transaction through.

Users who have not set up MFA are asked to enroll before their first protected action.

Verify once, continue securely

Once a user completes verification, their MFA session lasts for 15 minutes by default. Developers can configure this window to fit their application's security requirements.

During that window, users can complete multiple protected actions without repeated prompts, while routine actions remain uninterrupted.

Fits to your existing stack

Granular MFA works whether users sign in with Privy or with your own authentication, in both client-side and server-side integrations. 

Automated systems using your app's authorization keys, such as scheduled payouts or treasury operations, continue running without MFA prompts. MFA applies to user-authorized actions, not backend-controlled keys.

Privy wallet infrastructure powers 200M+ accounts across 3,000+ teams. With granular MFA, teams with the strictest requirements can add strong controls without adding friction everywhere else.

To enable granular MFA, read the docs and talk to our team.