BankingAuthentication

MFA Enforcement

Require stronger authentication for accounts whose emails appear in known breaches.

Start with 500 free creditsDocumentation

Email breaches · 1 credit per lookup · no monthly fee

sam@corp.comBreached
MFA now required
•••

The problem

Universal MFA is the right answer that users keep refusing. Blanket enforcement tanks signups; no enforcement leaves breached accounts one password from takeover.

With Encrata

Enforce MFA where the risk actually is. Accounts whose emails appear in breaches, especially recent ones with passwords exposed, get required MFA; clean accounts keep the frictionless path. Risk-based enforcement gets you most of the security at a fraction of the user complaints.

How it works

1

Send the address

Call the breach endpoint with an email address, one-off for a signup check, or on a schedule for monitoring.

2

We check known breaches

Encrata searches disclosed breach data and returns every breach the address appears in, when it happened, and what leaked.

3

Respond to exposure

Alert the user, raise a risk score, force a reset or require MFA, the full breach history is one credit away.

One call, structured answer

MFA Enforcement runs on the email breaches lookup at 1 credit per lookup. Same API key, same JSON shape as every other Encrata lookup.

  • Full breach history, names, dates and exposed data classes per breach
  • 1 credit per check, so continuous monitoring stays affordable
  • New-breach detection turns a public leak into a same-day security response
  • Works for one address or your whole domain
Terminal
curl -X POST "https://encrata.com/api/agent/breaches" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"email": "sam@corp.com"}'
response.json
{
  "email": "sam@corp.com",
  "breached": true,
  "breach_info": {
    "breach_count": 2,
    "services": [
      { "name": "LinkedIn", "breach_date": "2012-05-05",
        "data_types": ["Email addresses", "Passwords"] }
    ],
    "exposed_data": ["Email addresses", "Passwords"]
  },
  "credits": 1
}

Enforce where the risk is

Implement as a policy tier: accounts with recent password-exposed breaches require MFA at next login; clean accounts keep the optional path. Check at login time with cached results so the policy evaluates fresh without adding latency. Pair enforcement with the reason, 'your email appeared in a breach, so we're requiring extra protection', and resistance drops.

Security without the revolt

Risk-based enforcement gets most of universal MFA's security benefit at a fraction of the adoption pain, and it concentrates support load on exactly the users who most needed the protection. Track takeover attempts against the enforced cohort, the before/after on that segment is the clearest security ROI number you'll produce this year.

More email breaches use cases

View all

New breach: DataCo

Your email was exposed · just now

Secure account

Breach Alerts

Warn users the moment their email address shows up in a newly disclosed data breach

CybersecurityMonitoring

Identity risk

78/100
4 prior breaches · manual review

Risk Scoring

Raise risk scores for identities with prior breach exposure before approving transactions

FintechRisk
Breach affects 3 users
Password resets sent

Password Reset

Trigger targeted password resets when a breach relevant to your users becomes public

SaaSSecurity
Start with 500 free credits
$curl https://encrata.com/api/agent/lookup -H "Authorization: Bearer YOUR_API_KEY" -d '{"e": "satya@microsoft.com"}'