Menu

Individual skill

mfa-rollout

0upvotes

Plan and execute organization-wide MFA adoption — phishing-resistant methods, enrollment, exceptions, and measurement.

skills/mfa-rollout/SKILL.md

Read pinned source

Source commit faf37c0859ebf627bfcb5225e8057d088691e0ae

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 8, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
54
Repository last updated
Oct 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

## Overview

Multi-factor authentication is the single most effective control against credential theft: it neutralizes password leaks, phishing (with phishing-resistant methods), and credential stuffing at the login step. Yet rollouts stall on user friction, legacy apps, and exception sprawl. A successful rollout is a change-management project with a technical core.

This skill covers the rollout end to end: method selection, phased enrollment, legacy-app handling, exception governance, and metrics that prove coverage.

MFA rollout is change management disguised as a security project: the technology decisions take weeks, the human adoption takes quarters. Success depends on executive air cover, empathetic support, and relentless measurement. Organizations that treat it as 'turn it on Friday' spend the next year fighting shadow exceptions and helpdesk fires.

## When to use

- Mandating MFA org-wide (or for privileged/remote access first).
- Upgrading from SMS/TOTP to phishing-resistant MFA (FIDO2/passkeys).
- Fixing stalled adoption or runaway exception lists.
- Meeting compliance, cyber-insurance, or customer requirements for MFA.
Back to top