An MFA rollout checklist is not a list of tasks for the IT team. It is the control document that shows a manager, an auditor or an insurer that every account able to move money, expose customer data or change infrastructure is protected, and that a person who loses a phone can return to work without someone switching the protection off. That purpose changes what belongs on the list: each item needs an owner, a piece of evidence and a review date.
This checklist assumes the decision to adopt multi-factor authentication has been made. It does not revisit the business case or the cost model. It defines what "complete" means at each gate and what evidence should survive after the project team has moved on.
How to use the checklist
Work through the gates in order. A gate is not a meeting; it is a set of evidence that must exist before the next phase begins. For every item, record four fields: accountable owner, evidence artefact, review frequency and sign-off. If an item cannot produce evidence, treat it as open, even if everyone believes it is done.
| Gate | Question it answers | Sign-off |
|---|---|---|
| 1. Scope | Which accounts, applications and identities are covered? | IT lead and business owner |
| 2. Design | Which factors, policies and exceptions apply? | Security lead |
| 3. Pilot | Does enrolment work for real users and real devices? | Service owner |
| 4. Recovery | Can a locked-out user be verified and restored safely? | Helpdesk lead |
| 5. Enforcement | Is coverage complete, including legacy and privileged access? | Operations head |
| 6. Operation | Is the control reviewed, tested and improved? | Risk owner |
Gate 1: Scope and account inventory
- Human accounts: export every active directory, email and application account. Reconcile against HR or contractor records so departed staff cannot sit outside the rollout. Owner: identity administrator. Evidence: dated export with last-login date. Frequency: quarterly.
- Privileged accounts: list cloud administrators, domain administrators, finance approvers, database owners and anyone who can change payment details. Owner: security lead. Evidence: privileged role register signed by system owners. Frequency: quarterly and on role change.
- Service and shared accounts: identify automation, integrations, shared mailboxes and vendor access. Mark each as federated, vaulted or explicitly out of scope with a reason. Owner: application owners. Evidence: inventory tab with disposition. Frequency: each new integration.
- Applications: record the authentication protocol each system supports, such as SAML, OIDC, RADIUS or local passwords. Owner: application owners. Evidence: application register with protocol and integration route. Frequency: annually and at renewal.
Gate 2: Policy and design decisions
- Factor policy: state which factors are allowed for which user group. Push notifications and SMS codes are not equivalent to passkeys or hardware keys, so write the rule per risk tier rather than a single company-wide default. Owner: security lead. Evidence: one-page policy approved by management. Frequency: annually.
- Conditional access: document the conditions that trigger a second factor or block access, such as new devices, unusual locations, administrator roles or risky sign-ins. Owner: identity administrator. Evidence: policy export showing rule name and scope. Frequency: each change.
- Break-glass access: define at least one recovery route that does not depend on the identity provider, store it offline and test it. Owner: operations head. Evidence: sealed procedure, custody record and test date. Frequency: every six months.
- Exceptions: list every account exempted from MFA, with a business reason and an expiry date. Owner: risk owner. Evidence: exception register. Frequency: monthly.
Gate 3: Pilot and enrolment
- Pilot group: include administrators, finance, remote staff and at least one person with an older phone. A pilot that only covers office-based laptop users proves very little. Owner: service owner. Evidence: pilot list and feedback log. Frequency: per rollout wave.
- Enrolment instructions: provide a one-page guide in the languages staff actually read, with screenshots for the supported devices. Owner: IT communications. Evidence: published guide and intranet link. Frequency: each device or provider change.
- Enrolment completion: track who has registered at least two factors, not who has opened an invitation. Owner: identity administrator. Evidence: enrolment report by department. Frequency: weekly during rollout.
Gate 4: Recovery and helpdesk readiness
- Identity proofing: write how a user is verified before a factor is reset, and who may approve it. A reset over a personal phone call is a social-engineering path into the company. Owner: helpdesk lead. Evidence: written procedure and approval matrix. Frequency: annually and after any incident.
- Lost-device drill: run the full recovery path with a test user, including the wait time and the audit record. Owner: helpdesk lead. Evidence: drill record with timestamps. Frequency: before enforcement, then every quarter.
- Second factor: require a backup method or recovery code at enrolment, and report users who have only one registered factor. Owner: identity administrator. Evidence: coverage report. Frequency: monthly.
Gate 5: Enforcement and coverage
- Enforcement waves: publish the date for each department and the consequence of missing it. Owner: operations head. Evidence: communications calendar and enforcement report. Frequency: per wave.
- Legacy access: close or vault applications that cannot support MFA. Do not leave a local password as the permanent exception. Owner: application owners. Evidence: remediation list with dates. Frequency: quarterly.
- Vendor and partner access: apply the same standard to external users, or terminate the access. Owner: procurement and IT. Evidence: external account register. Frequency: at contract renewal.
- Coverage statement: produce a single figure and a list: percentage of in-scope human accounts with two factors, and every exception by name. Owner: identity administrator. Evidence: signed coverage statement. Frequency: monthly until stable, then quarterly.
Gate 6: Steady-state review
- Sign-in quality: review failed sign-ins, MFA fatigue reports and helpdesk resets. Owner: security lead. Evidence: monthly dashboard. Frequency: monthly.
- Access reviews: confirm that leavers lose access and that role changes update their factor requirements. Owner: system owners. Evidence: review attestation. Frequency: quarterly.
- Roadmap: move high-risk users from codes to passkeys or security keys, and retire weaker methods as devices are replaced. Owner: security lead. Evidence: method mix report and dated plan. Frequency: annually.
The sign-off record
Keep a one-page record for each rollout wave: scope, owner, enforcement date, coverage figure, open exceptions, recovery drill date and the name of the person who accepted the residual risk. If an account is compromised tomorrow, that record should show that protection was designed, applied and tested.
Common ways the checklist fails
- Counting invitations instead of enrolled factors.
- Leaving administrator accounts until the last wave because they are inconvenient to move.
- Writing a recovery process that exists only in the helpdesk manager's head.
- Treating service accounts as "not people" and therefore out of scope.
- Closing the project at enforcement and never reviewing coverage again.
If you need help turning this checklist into a rollout with a tested recovery path, start with Managed Technology & Cybersecurity. The pricing page explains how assessment, implementation and ongoing support are separated. For the cost drivers behind the work, read the MFA rollout cost model for Bangladesh.
Sources
- NIST SP 800-63B, Digital Identity Guidelines, accessed 17 November 2026.
- CISA, More Than a Password: MFA guidance, accessed 17 November 2026.
- CISA, Implementing Phishing-Resistant MFA fact sheet, accessed 17 November 2026.
- Microsoft Learn, How Microsoft Entra multifactor authentication works, accessed 17 November 2026.
- FIDO Alliance, Passkeys, accessed 17 November 2026.
Responses (0)
No comments yet. Add the first one below.
Leave a response
Your email address will not be published. Required fields are marked *.