Access Control
Set Up and Check Multi-Factor Authentication
Start with administrator accounts and remote access. Set up MFA, check that it is required at sign-in, and keep a safe way to recover access.
Content review: 2026-09-22 · Estimated effort: Medium
Priority and effort are suggestions, not risk scores or deadlines. Check business impact, vendor instructions, licenses and obligations before making changes. Test before wider rollout.
Before you start
Before starting: identify an administrator, supported methods, recovery procedures, and a protected emergency-access route. Never remove your only working administrator access.
Put it into practice
- Start with existing MFA capabilities in business email and important services. Record accounts, owners, licensing limits, and exceptions.
- Prefer phishing-resistant FIDO2/WebAuthn passkeys or security keys where supported. Ordinary approval prompts and one-time codes are not phishing-resistant; use available MFA while planning improvements.
- Pilot with a small group and test sign-in, lost-device recovery, and service dependencies. Prioritize administrators, email, and supported remote-access gateways, then expand on an agreed schedule.
- Review older authentication paths and exclusions that could bypass MFA. Test dependencies before blocking them and monitor emergency-account use.
- Verify: test a fresh sign-in on each important service and inspect enforcement rather than enrollment alone. Rehearse recovery without exposing recovery codes.
Use what you have
Tools and templates
“Included” tools require an eligible product or subscription. Options reviewed 2026-09-22; check current vendor terms.
Start without another software subscription
Microsoft Authenticator is free. For a Microsoft Entra tenant, review security defaults before buying advanced policies. A compatible free TOTP app is another option where the service and administrator allow it.
What to account for: An app generates or approves authentication; the service must enforce it. Conditional Access customization requires eligible licensing. TOTP codes are not phishing-resistant and do not replace Microsoft push or passwordless methods.
Allow for equipment, storage and staff time. Eligibility details are linked below.
Microsoft Entra security defaults
No additional premium license; requires a Microsoft Entra tenant
In Entra ID > Overview > Properties, review Manage security defaults. Inventory dependencies and protect emergency access before changing enforcement.
Limits: An on/off tenant-wide package, not a per-user pilot policy. Conditional Access customization requires at least Entra ID P1; do not disable existing protections to use this option.
Your information: Your existing Microsoft tenant processes identities, sign-ins and policy information. Never upload tenant exports to this website.
Official instructions: Microsoft Entra security defaults ↗Microsoft Authenticator
Free mobile app; no app subscription required
Use Microsoft’s official download links and register through your service’s approved security settings. Test sign-in and recovery before removing an existing method.
Limits: Installing the app does not enforce MFA. Available methods depend on the service and policy; a free app does not grant Conditional Access licensing.
Your information: The app handles authentication secrets and account information. Review device protection and backup settings; never share registration QR codes or recovery codes.
Official instructions: Microsoft Authenticator ↗Bitwarden Authenticator: standalone app
Free standalone TOTP app for iOS and Android; no Bitwarden account required
For a service that permits third-party TOTP codes, follow its registration flow and test a code. Keep an approved recovery route before switching apps.
Limits: Not Microsoft push approval or passwordless sign-in, and TOTP is not phishing-resistant. Confirm your tenant permits software OATH. The password manager’s integrated code generator is a different feature with different licensing.
Your information: Local codes are stored on the device; vendor documentation describes a local unencrypted database. Protect the device and review OS cloud backups. Optional vault copying or syncing changes where secrets are stored. Restrict exports and never upload them here.
Official instructions: Bitwarden Authenticator: standalone app ↗Microsoft 365 MFA setup guidance
Use included tenant capabilities first; methods and advanced policies vary by license
Use the official setup instructions to identify your current enforcement route. Test an authorized sign-in and lost-device recovery rather than checking enrollment alone.
Limits: Security defaults and Conditional Access are different routes. A free authenticator app does not by itself enforce MFA; hardware keys may have a purchase cost.
Your information: Authentication and registration information is handled by your identity provider. Keep recovery codes out of worksheets.
Official instructions: Microsoft 365 MFA setup guidance ↗Download a working template
Open the Excel or Word file using your existing Microsoft Office license. Replace fictional entries, fill in the blanks and save your own copy. These manual worksheets have no macros, scoring or automatic verification.
- Security change and verification record (Excel (.xlsx)) ↓
Plan one scoped change per row, including prerequisites, recovery, test expectations and actual results. An untested change is not a verified success.
Fictional worksheet preview: Security change and verification record Change ID Proposed change Actual test results EXAMPLE-CHANGE-01 Test an approved MFA policy in a limited scope Not tested Three columns shown. The full worksheet also records prerequisites, expected behavior and recovery steps. Confirm permissions and recovery access before making changes.
- Administrator access review (Excel (.xlsx)) ↓
Record roles, scope, justification, approval and the outcome of each review. Use identifiers appropriate for a restricted internal record.
Fictional worksheet preview: Administrator access review Account or group reference Role and scope Decision EXAMPLE-ADMIN-GROUP Administrator: tenant scope Pending review Three columns shown. The full worksheet also records justification, approval and verification. Record the owner’s approval before changing access.
Fictional worked example
Use these invented entries as a guide when filling in your worksheet. They are not a customer story or lab result. Record what you observe in your own checks.
A team wants to confirm that its existing MFA policy protects an authorized test account.
Use the Security change and verification record template.
What to enter before testing
- Change ID
- EXAMPLE-MFA-01
- Service and scoped recipients
- Microsoft 365: authorized test account
- Expected allowed and blocked behavior
- Authorized sign-in succeeds; access cannot bypass required MFA
- Actual test results
- Not tested
How to verify
Confirm the applicable enforcement policy, then perform an authorized fresh sign-in and inspect sign-in evidence. A missing prompt alone is inconclusive: an existing session or authentication method can satisfy MFA. Rehearse approved lost-device recovery.
If the result is unexpected
If access bypasses the intended policy or recovery fails, preserve working administrator access and investigate scope, exclusions and sessions. Do not disable tenant protections as a shortcut. Record the result and retest. Security defaults is tenant-wide, not a one-user rollout.
Keep completed worksheets private. Leave out passwords, recovery keys and confidential messages. This site does not receive your edits, but a cloud editor or synced folder may send them to its provider.
Sources and review approach
These guides use selected NIST CSF 2.0 alignments. They are not official crosswalks or complete framework implementations. We have not tested these steps in your environment.
- NIST CSF 2.0: PR.AA-03: authentication, not identity proofing
- https://www.nist.gov/publications/nist-cybersecurity-framework-csf-20 ↗
- https://csrc.nist.gov/pubs/sp/800/63/b/4/final ↗