Family Sentinel
Scam Watch · November 12, 2026 · 5 min read

The phone call that walks past your organization's MFA

Most churches and nonprofits have turned on two-factor authentication by now — that is the right instinct. But security research published this quarter found that in 79 percent of business email compromises where multi-factor authentication was actually enabled, attackers bypassed it anyway. The primary method was a phone call.

The technique is called "device enrollment vishing." It does not require stolen passwords, malware, or anything technically sophisticated on the attacker's part. It requires one person on your staff to approve a request from a caller who sounds like IT support.

Understanding how it works — and writing down one rule before it happens — is the most valuable thing a small organization can do with twenty minutes this week.

What "trusted devices" are and why attackers have targeted them

When your organization uses Microsoft 365 or Google Workspace, your account administrator can configure the system so that email and shared files are only accessible from devices the organization has approved. Your staff laptop is enrolled. A work phone is enrolled. When you log in from one of those devices, the system recognizes it, and you are not asked for a second verification code every time — because the device itself counts as proof.

That approved status is called a trusted or enrolled device. And it is enormously valuable to an attacker, because once a device is enrolled, it bypasses the multi-factor authentication prompt entirely. To your email platform, an enrolled device is already verified.

Attackers have learned to target this. Rather than racing to intercept a one-time code before it expires, they simply persuade someone on your staff to enroll the attacker's own phone or laptop as a trusted organizational device. After that, they have persistent access to email, shared drives, and anything connected to that account — and no MFA challenge ever appears, because the system treats their device as legitimate.

What the call sounds like

These calls are designed to feel like routine IT work. A few patterns that appear repeatedly:

What gives these callers away is not their tone or their knowledge of your organization — it is the request itself. No legitimate IT team, Microsoft representative, or Google support agent will call you unexpectedly and ask you to approve a device enrollment or click an account link during the call. That is simply not how those companies do business.

The rule that stops this: No legitimate IT team, Microsoft, or Google will call you out of the blue to enroll or update devices. If a caller asks you to click a link or approve anything on a login screen during an unsolicited call, hang up. Then call your IT contact back on a number you already have. The rule applies even when the caller sounds like they know your organization well.

Why this matters for churches and nonprofits right now

Business email compromise — which often begins with account access gained exactly this way — was the leading type of cyber incident in the most recent quarter, accounting for nearly a third of all reported cases. The same research found that in 83 percent of those intrusions, attackers focused on quietly copying and removing data rather than triggering ransomware or visible disruption. Many organizations do not discover what happened until a donor list surfaces somewhere it should not, a payroll file is accessed during a pay cycle, or a financial account shows withdrawals that look like normal vendor payments.

For a church, that might mean a compromised giving database or a year-end donation campaign derailed. For a nonprofit, it might mean donor records, grant applications in progress, or payroll credentials. The entry point, in a growing share of these incidents, was a single phone call that a staff member had no reason to recognize as an attack.

The Q4 giving season runs through December. It is the period when churches and nonprofits process the highest volume of financial transactions, and when attackers who have already gained access through a device enrollment call are most likely to act on it.

What to do

  1. Write down the rule and share it at your next staff meeting. "We will never approve a device enrollment or click an account link during an unsolicited phone call." Read it aloud. It takes thirty seconds and applies to everyone — the finance volunteer, the administrative assistant, and the senior pastor's office. The person most likely to receive this call is not the most technical person on your team.
  2. Know how to check what devices are enrolled in your account. In Microsoft 365, an administrator can see all registered devices in the Entra admin center under Devices, then All devices. In Google Workspace, the same list is under Admin console, then Devices. If you do not have an IT person, ask your provider to show you this list at least once a quarter.
  3. Remove any device you do not recognize. If you see an enrolled device you cannot account for — a phone registered at an unusual hour, a laptop from an unfamiliar location — treat it as a potential compromise. Remove it immediately and change the password for the account it was enrolled under. Then review that account's sent mail and recently accessed files for the period since the enrollment date.
  4. Ask your IT provider how device enrollment is configured. Some Microsoft 365 configurations allow staff to self-enroll any device without administrator approval. If that is your current setup, ask your provider to require IT approval before any new device is added. This is a one-time configuration change and the single most effective technical control against this attack.
  5. Apply the hang-up-and-call-back rule to every unsolicited security call. If you receive a call about anything account-related — devices, MFA, a security alert, a compliance deadline — hang up. Then call your IT contact or vendor using the number you already have on file. If the call was genuine, they will confirm it in sixty seconds. If it was not, you just stopped an attack that bypasses most of what organizations spend on security.

Related reading

How secure is your organization's email environment right now?

Family Sentinel's free 20-minute checkup reviews your Microsoft 365 or Google Workspace configuration against the attack patterns we see weekly — including device enrollment policy, business email compromise controls, and email authentication. No commitment, no sales pitch, no charge.

Book a free 20-minute checkup →

Want the next threat before it reaches you?

Scam Watch goes out regularly — the newest scams and how to spot them, in plain English. Free.

Written by the Family Sentinel security desk — a working Security Architect and the team who watch family and organizational inboxes around the clock. Sources: LevelBlue Q3 2026 TTP Briefing (SpiderLabs / AT&T Cybersecurity, November 2026) — multi-factor authentication defeated in 79% of BEC incidents, primary method vishing to enroll attacker-controlled devices; exfiltration the leading attack outcome in 83% of intrusions; BEC the leading incident type at 32% of cases. Have a suspicious call, text, or email you'd like a verdict on? Forward it to security@familysentinel.org — no charge, no strings. Questions? Call (940) 281-6672.