Lessons on the Road to Complete Customer MFA
summary
Companywide mandate aims for 100% customer MFA but timeline shifts from a one‑year goal to phased rollouts, starting automated enables for tiny tenants in January while full enforcement waits about a year; program uses a writer, a data person, non‑SME rollout teams and V2MOM planning; allowed factors are Salesforce Authenticator, TOTP and WebAuthn while enforcing no SMS OTP; two outages (DNS and regional failover) prompt hardened controls; result: about 80% adoption for monthly active users and 14 million users added with a large drop in account takeover.
AI-written summary · about
chapters (15)
- 0:00Introduction and welcome
- 1:50Starting the MFA journey
- 3:16Building the program team
- 6:02Gaining stakeholder commitment
- 7:28Measuring progress with V2MOM
- 9:12Replanning and adjusting timelines
- 12:02Communicating the MFA rollout
- 13:48Handling customer feedback and wobblers
- 15:57Addressing hard use cases
- 17:23Dealing with infrastructure failures
- 18:25Current adoption and tenant differences
- 20:11Enabling MFA for lagging tenants
- 21:40Results and impact of MFA mandate
- 23:46Long-term benefits and community impact
- 25:31Q&A session
related talks
50mOne Does Not Simply Add MFA
17mImplementing Multi-factor Authentication
38mAnatomy of the Attack: The Rise and Fall of MFA
30mDeploying Two-Factor Authentication to Millions of Users
38mI Was Tasked With Enrolling Millions of Developers in 2FA - Here's What Happened
25mNavigating the implementation and roll out of passwordless authentication
45mMFA: Stories that make you go 'Huh?'
24m2FA in 2020 and Beyond