Multi-factor authentication (MFA) is a keystone control for NIST SP 800-171 Rev.2 / CMMC 2.0 Level 2 IA.L2-3.5.3: it prevents credential-only access to Controlled Unclassified Information (CUI) by requiring additional proof of identity for both local and network logons — this post gives a practical, small-business-focused playbook for integrating MFA across on-prem Active Directory (AD), Azure AD, and VPNs to satisfy the Compliance Framework requirements.
Mapping IA.L2-3.5.3 to your environment (Compliance Framework)
IA.L2-3.5.3 in the Compliance Framework requires multifactor authentication for local and network access to privileged and non‑privileged accounts where CUI is accessible. Practically this means: inventory which accounts can access CUI (admins, developers, executives, remote users), ensure MFA is enforced for those accounts for interactive local sign-on and network/remote access (VPN, RDP, cloud apps), and log proof of enforcement. Implementation notes for Compliance Framework: document your scope, the MFA methods allowed, exceptions and compensating controls (e.g., dedicated privileged access workstations — PAWs), and evidence of enforcement (Conditional Access reports, VPN logs, and AD authentication events) for audits.
Active Directory (on‑prem) integration
Options and concrete steps
For traditional AD, you have three common approaches: 1) federate to Azure AD / ADFS and apply cloud MFA policies; 2) install an on‑prem MFA gateway/solution (Duo, Okta MFA, RSA) that integrates with AD via RADIUS or LDAP; 3) deploy Windows Hello for Business / smart card for passwordless MFA. Implementation steps for a small business using AD + VPN: (a) inventory domain controllers and RADIUS clients, (b) decide on MFA vendor (Azure MFA via ADFS/NPS extension or Duo), (c) if using Azure, install the NPS role on a hardened Windows Server, register it in Azure AD via the Azure MFA NPS extension, and configure your VPN to forward RADIUS to that NPS server. Example: Cisco ASA or SonicWall -> RADIUS -> NPS server with Azure MFA extension; configure RADIUS shared secret, test with an admin account, then roll out to all remote users.
Azure AD integration
Conditional Access, Security Defaults and passwordless
Azure AD offers the most flexible enforcement: Conditional Access policies allow you to require MFA for selected users, groups, and applications, and can be made risk‑based (require MFA when logging in from new locations or devices). Actionable steps: enable Azure AD Connect to sync your on‑prem users, assign Azure AD Premium P1 licenses if you need Conditional Access (required for targeted policies), create CA policies that require MFA for: administrative roles, any sign‑in to Microsoft 365 apps that access CUI, and all remote access from untrusted networks. For small businesses with Microsoft 365 Business Premium, Security Defaults provide an all-or-nothing MFA baseline (protects admin accounts immediately). Consider passwordless FIDO2 security keys or Windows Hello for Business for privileged accounts to reduce phishing and MFA fatigue.
VPN integration and common architectures
RADIUS/NPS extension vs SAML/OIDC
VPNs commonly integrate with MFA via RADIUS to an on‑prem NPS server (with Azure MFA NPS extension or third‑party MFA) or by using SAML/OIDC with Azure AD as an identity provider (works well with modern VPNs like Palo Alto GlobalProtect, Fortinet, and some Cisco appliances). Implementation notes: for RADIUS flow, ensure the NPS server is highly available (pair in HA or use load balancer), use secure shared secrets, and require TLS where supported; for SAML flow, create an Enterprise Application in Azure AD, configure the VPN as an SP with correct assertion/relay URLs, and then enforce Conditional Access on that application to mandate MFA. Real-world small-business example: a 30‑user firm with Palo Alto GlobalProtect configures Azure AD SAML SSO, assigns users to the app, and applies a Conditional Access policy requiring MFA for all users — this removes RADIUS complexity and centralizes MFA auditing in Azure AD sign-in logs.
Rollout plan and small-business scenario
A practical rollout: 1) pilot with break‑glass and admin accounts (test MFA flows, recovery methods); 2) enforce MFA for VPN and admin groups; 3) expand to remote workers and then to all employees. For a 25‑person contractor handling CUI: start by enabling Security Defaults or Conditional Access for admins, integrate VPN to use Azure AD SAML or NPS extension, issue FIDO2 keys to executives and privileged users, and enroll smartphones for push/TOTP as secondary methods. Train users on enrollment, phishing-resistant choices (hardware keys), and build a helpdesk runbook for lost devices and account recovery. Document each step, capture screenshots and logs as evidence for the Compliance Framework assessment.
Risks of non‑implementation and compliance tips
Failing to implement MFA exposes your organization to credential stuffing, password spraying, and phishing — attackers can obtain domain credentials and move laterally to exfiltrate CUI or deploy ransomware. From a compliance standpoint, lack of MFA will lead to failing IA.L2-3.5.3 during assessments and increases contractual and regulatory risk when handling DoD/CUI. Best practices: enforce MFA for all accounts with CUI access, disable legacy authentication protocols (SMTP/IMAP/EWS that bypass MFA), separate admin accounts from user accounts, use Privileged Access Workstations for admins, maintain break‑glass accounts with offline tokens stored in a vault, and instrument logging to a SIEM for continuous evidence (Azure AD sign-in logs, VPN auth logs, Windows Security logs). Ensure you have licensing aligned (Conditional Access requires Azure AD P1) and include compensating controls and exception documentation if immediate full coverage isn’t possible.
Summary
To meet Compliance Framework IA.L2-3.5.3, implement MFA across on‑prem AD, Azure AD, and VPNs by scoping accounts that access CUI, choosing a technical integration approach (NPS/Azure MFA extension, SAML/OIDC with Azure AD, or third‑party MFA), piloting on privileged accounts, and rolling out with monitoring and documented evidence. Prioritize phishing-resistant methods for high‑risk users, harden your VPN integration, disable legacy authentication, and maintain an auditable trail — doing so significantly reduces risk and provides the evidence required for NIST SP 800-171 Rev.2 / CMMC 2.0 Level 2 compliance.
