NIST 800-171 Controls · Identification & Authentication
IA.2.078 — Use multifactor authentication for local and network access
Use multifactor authentication for local and network access to privileged accounts and for network access to non-privileged accounts.
What IA.2.078 means in plain English
A password alone is not enough anymore — attackers can steal passwords. MFA adds a second check (like a code on your phone) so even if your password is stolen, the attacker still cannot get in. For your team: every person must use MFA to log into Microsoft 365 email, and any admin account must use MFA even for local Windows logins. Microsoft Authenticator is free, takes 10 minutes to set up per person, and is the single highest-return security investment you can make. This one control blocks over 99% of automated credential-stuffing attacks.
The assessment question
“Is MFA enforced on all privileged accounts for both local and network access, AND on all non-privileged accounts for network access — with no exemptions or bypass methods in place?”
How to implement IA.2.078
- Enable Azure AD MFA for all users in Microsoft 365 Admin Center: go to Azure Active Directory > Security > MFA and enable per-user MFA or use Conditional Access (included in Microsoft 365 Business Premium).
- Deploy Microsoft Authenticator app on every employee smartphone — walk each person through enrollment in a 15-minute setup session.
- Create a Conditional Access policy (Business Premium) or enforce Security Defaults (free) that blocks any login without MFA regardless of location.
- For privileged/admin accounts, enforce MFA via Windows Hello for Business or require FIDO2 security keys for local machine access.
- Document MFA enrollment for each user and test a simulated login from outside the office to confirm MFA challenge fires.
Evidence your assessor will ask for
- Azure AD MFA status report showing 100% of users enrolled
- Conditional Access policy screenshot showing MFA required for all apps
- Authentication log showing MFA challenges being triggered on logins
- Signed user enrollment records confirming each employee completed MFA setup
Does AI prompt monitoring help with this control? Honestly, no.
IA.2.078 is met through the remediation steps above, not through AI traffic controls — an AI prompt firewall neither satisfies nor substitutes for it. We map AI monitoring only to the controls it genuinely evidences (flow control, boundary protection, audit, and incident support); for the full picture of where it does help, see the mapping guide linked below.
Full mapping: which 800-171 controls AI prompt monitoring evidences →
More Identification & Authentication controls
Identify system users, processes, and devices
IA.1.077Authenticate identities of users, processes, and devices
IA.2.079Employ replay-resistant authentication mechanisms
IA.2.080Prevent reuse of identifiers
IA.2.081Disable identifiers after defined period of inactivity
IA.2.082Enforce minimum password complexity and change of characters
Score yourself against all 110 controls
The free ShieldReady assessment walks every NIST 800-171 requirement, computes your SPRS score, and shows exactly which gaps cost the most points.