Skip to main content

All MFA Activity by Factor

MFA challenges by factor, with each factor’s share of the total.

The volume of MFA challenges broken down by factor type, with each factor’s share of total activity. This is the platform-wide view: it covers every factor type the system records, including the internal and administrative factors (kq, totp, qr, ibm_verify_push) and the email_otp factor used only to validate emails at sign-up. For usage restricted to the factors the public can sign in with, see Sign-in MFA Activity by Factor.

This metric shows which second factors are exercised across the whole platform. Historically the mix has been dominated by sms_otp and email_otp. Passkeys (fido2) became generally available to the public on 2026-07-06, so fido2 volume is expected to grow from that point, while factors such as totp, kq, qr, voice_otp, and ibm_verify_push continue to see little use.

Calculation

Sum count grouped by mfa_type, then divide each factor’s total by the overall total to get its share. As with MFA Challenges, de-duplicate before counting: OTP factor types (sms_otp, email_otp, voice_otp) record both a sent event and a subsequent success/failure event for the same challenge, so only the sent row is counted for these; non-OTP factor types (fido2, kq, totp, ibm_verify_push) have no sent event and are counted through their success/failure rows. Without this, OTP factors are roughly double-counted relative to non-OTP factors.

SELECT
    mfa_type,
    SUM(count) AS mfa_challenges,
    CAST(SUM(count) AS DOUBLE)
        / NULLIF(SUM(SUM(count)) OVER (), 0) AS factor_share
FROM ibm_verify_events_transformed.events_mfa_activity
-- set the reporting window; see the timespans note in cookbook/notes.qmd
WHERE CAST(from_date AS DATE) BETWEEN DATE '2026-01-01' AND DATE '2026-05-28'
  -- de-duplicate OTP challenges: count only "sent" for OTP types, and
  -- "success"/"failure" for non-OTP types (which have no "sent" event).
  AND (
    result = 'sent'
    OR (
      result IN ('success', 'failure')
      AND mfa_type NOT IN ('sms_otp', 'email_otp', 'voice_otp')
    )
  )
GROUP BY mfa_type
ORDER BY mfa_challenges DESC;
otp_types <- c("sms_otp", "email_otp", "voice_otp")

tbl(con, in_schema("ibm_verify_events_transformed", "events_mfa_activity")) |>
  # set the reporting window; see the timespans note in cookbook/notes.qmd
  filter(
    as.Date(from_date) >= as.Date("2026-01-01"),
    as.Date(from_date) <= as.Date("2026-05-28"),
    # de-duplicate OTP challenges: count only "sent" for OTP types, and
    # "success"/"failure" for non-OTP types (which have no "sent" event).
    result == "sent" |
      (result %in% c("success", "failure") & !mfa_type %in% otp_types)
  ) |>
  group_by(mfa_type) |>
  summarise(
    mfa_challenges = sum(count, na.rm = TRUE)
  ) |>
  mutate(
    factor_share =
      as.double(mfa_challenges) / sum(mfa_challenges, na.rm = TRUE)
  ) |>
  arrange(desc(mfa_challenges))

Interpretation notes

factor_share is a proportion between 0 and 1 and sums to 1 across all factors. Combine with the MFA success rate to spot factors that are both heavily used and failing often.

Alternative names

  • MFA factor mix
  • second-factor distribution
  • MFA usage by method
  • MFA factor share