Skip to content
Menu

MFA Coverage

The share of client user accounts enforced to use multi-factor authentication, with admin accounts tracked separately.

Security Operations

Formula

Accounts with MFA enforced ÷ Active interactive accounts × 100

Why Track It

Stolen credentials are how most account takeovers start, and MFA stops most of them. Coverage by client tells the vCIO which clients to push and gives evidence for cyber insurance questionnaires.

How It Is Measured

From each client's identity provider (such as Microsoft Entra ID or Google Workspace), count interactive user accounts where MFA is enforced by policy and registered. Divide by all active interactive accounts. Report admin and privileged accounts as a separate line, and count legacy authentication paths that bypass MFA as gaps. Also report the MSP's own staff accounts.

Constraints

Service accounts and shared mailboxes need a written exception rule or the number is meaningless. It does not show whether the MFA method resists phishing.

Measurement Note

Umbrex sets targets of 100% for privileged identities with zero legacy bypass and 95% or more of interactive workforce users enforced and registered. Registered is not enforced: an account that can still sign in without MFA is a gap.

Referenced In

Glossary and Answers

More in Security Operations

Whether the basic controls an MSP runs for clients are actually in place and working. These numbers show how exposed the client base is to the breach that ends a client relationship.

All KPIs
Sources1
  1. Umbrex: Multi-Factor Authentication Coverageumbrex.com

Welcome Back

Sign in to your MSP Outpost account.