Key Takeaways
- CMMC compliance requires safeguarding Federal Contract Information (FCI) and Controlled Unclassified Information (CUI) under Department of Defense (DoD) cybersecurity regulations.
- Level 2 requirements mandate MFA for local and network privileged access plus network non-privileged access under practice 3.5.3.
- Certificate-based network authentication provides cryptographic identification but functions as only one factor type within the broader MFA framework.
CMMC compliance is a core requirement for defense contractors handling FCI and CUI, protecting data throughout its lifecycle on contractor information systems. As contracts shift toward higher security levels, organizations must integrate strong authentication methods like MFA into their network infrastructure to meet NIST SP 800-171 standards.
What Is CMMC Compliance and Why Does It Matter?
CMMC compliance is meeting the security requirements of the Department of Defense Cybersecurity Maturity Model Certification (CMMC) Program, which exists so defense contractors properly safeguard FCI and CUI that is processed, stored, or transmitted on contractor information systems. The program has three levels. The level a contractor needs depends on the type of information it handles.
Adherence to these frameworks reduces the risk of unauthorized access, data exfiltration and potential compromise of national interests. For network administrators tasked with implementing MFA requirements under specific NIST practices, understanding the baseline compliance expectations is the first step in audit preparation.
Who Needs CMMC Compliance?
CMMC applies to defense contractors whose information systems process, store or transmit FCI or CUI. That includes:
- Prime contractors that hold DoD contracts involving FCI or CUI.
- Subcontractors at any tier that receive FCI or CUI from a prime.
- Contractors managing only FCI generally require Level 1, while those handling CUI need Level 2 or higher, since Level 1 draws on 48 CFR 52.204-21 and Level 2 on NIST SP 800-171 R2.
The Defense Federal Acquisition Regulation Supplement (DFARS) CMMC acquisition rule took effect November 10, 2025, marking the start of Phase 1 when requirements appeared in solicitations.
Understanding CMMC Levels 1 Through 3 Requirements
The following comparison shows what each tier protects and where its rules originate.
|
Level |
Name |
Information Protected |
Requirement Source |
|---|---|---|---|
|
1 |
Foundational |
FCI |
48 CFR 52.204-21 basic safeguarding requirements |
|
2 |
Advanced |
CUI |
NIST SP 800-171 R2 |
|
3 |
Expert |
CUI |
Level 2 requirements plus selected NIST SP 800-172 (February 2021) requirements |
CMMC Level 1 requirements come from the basic safeguarding rules in 48 CFR 52.204-21. This entry-level tier is designed for contractors that handle FCI but not CUI.
CMMC Level 2 requirements, often referred to as Advanced, match the security requirements of NIST SP 800-171 Revision 2 (R2), including protection of CUI at rest and cryptographic protection in transit, continuous monitoring capabilities and comprehensive incident response planning. The key requirement for network-focused teams is practice 3.5.3, which mandates MFA for local and network access to privileged accounts and for network access to non-privileged accounts.
CMMC Level 3 requirements, categorized as Expert, add selected requirements from NIST SP 800-172. It expands upon Level 2 protocols, requiring contractors to identify and authenticate systems and their components, where possible, prior to establishing network connections using cryptographically-based, replay-resistant bidirectional authentication. This tier represents the highest operational burden of the three levels.
IA.L2-3.5.3: Implementing Network Access Authentication Standards
The requirement known as IA.L2-3.5.3 is central to achieving compliance at Level 2, specifically concerning authentication mechanisms used during local access attempts or network connections involving CUI systems.
Defining Multifactor Authentication in the NIST Context
According to the NIST glossary, multi-factor authentication involves using two or more different factors to verify user identity before granting system entry. These factors generally fall into three primary categories: something you know (like a password), something you have (such as hardware tokens), and something you are (biometric data). The NIST framework specifically emphasizes that relying on a single factor type like passwords is insufficient for protecting CUI environments.
Where Certificate-Based Network Authentication Fits
Extensible Authentication Protocol-Transport Layer Security (EAP-TLS) provides support for certificate-based mutual authentication and key derivation. While this protocol offers strong security through public-key cryptography, possessing a valid digital certificate alone constitutes only one factor in an MFA solution.
The Role of Hardware Authenticators and Smart Cards
MFA solutions utilizing “something you have” typically involve cryptographic identification devices, tokens, hardware authenticators providing time-based or challenge-response codes and smart cards, as the assessment guide describes. For contractors using network access control systems where EAP-TLS is used for wireless or wired connectivity, these hardware elements supply the something-you-have factor of an MFA strategy.
What Assessors Check for IA.L2-3.5.3
CMMC requirement IDs follow the format domain, level and NIST SP 800-171 R2 requirement number, which is why practice 3.5.3 becomes IA.L2-3.5.3; the CMMC Assessment Guide splits it into four assessment objectives, and an assessor looks for evidence of each one.
- Privileged accounts are identified.
- MFA is implemented for local access to privileged accounts.
- MFA is implemented for network access to privileged accounts.
- MFA is implemented for network access to non-privileged accounts.
The fourth objective is where network-layer controls such as Wi-Fi and VPN authentication come in.
The guide defines network access as access obtained through network connections, meaning nonlocal access, and states that if a mobile device is used to access a system or application containing CUI, multi-factor authentication is required.
Integrating Network Layer Security With CMMC Level 2 Goals
Achieving full compliance under IA.L2-3.5.3 involves more than simply turning on authentication protocols on network access gateways or Wi-Fi controllers. It requires aligning these technologies with the broader organizational MFA strategy mandated by NIST SP 800-171 R2. Network administrators need infrastructure that integrates user identity providers and device management platforms to meet both CMMC requirements and internal security policies.
Beyond traditional username/password combinations, modern compliance strategies use technologies such as managed public key infrastructure (PKI) for certificate lifecycle management or cloud-based RADIUS services with identity-lookup capabilities.
The Limitations of Certificate-Based Authentication Alone
MFA requires two or more different factor types. A digital certificate is just one type: something you have. EAP-TLS using a certificate alone supplies that single factor regardless of cryptographic strength because it lacks another category for verification.
A certificate becomes part of an MFA strategy when it is paired with a second factor type. For example, a private key bound to a smart card that requires a PIN or biometric before use. This mirrors the pattern used on Personal Identity Verification (PIV) cards and DoD Common Access Cards (CAC), where identity confirmation needs both possession of the device and proof of knowledge or presence from the user. Assessors still evaluate the whole design against the IA.L2-3.5.3 objectives.
Strategic Roadmap for Achieving CMMC Certification Readiness
Organizations preparing for Level 2 certification should adopt a phased approach to make systematic progress toward meeting all technical controls outlined in NIST SP 800-171 Revision 2. The first phase typically involves conducting an internal self-assessment against the current security posture and identifying gaps relative to CMMC requirements before engaging external assessors for formal audits.
Phase One: Internal Gap Analysis and Documentation Prep
The initial step requires a thorough review of existing network configurations, authentication policies, and user access logs mapped directly to the specific CMMC requirement IDs, such as IA.L2-3.5.3. This internal audit helps teams understand which elements already meet compliance standards versus those needing immediate remediation efforts focused on MFA implementation or encryption upgrades.
Phase Two: Deploying Technical Controls Across the Network
Once gaps are identified, security architects can design and deploy necessary controls, such as enforcing EAP-TLS for wireless networks or integrating a cloud-based RADIUS server with existing firewall appliances for centralized authentication management. This phase often involves coordinating between IT operations teams responsible for network infrastructure and those managing identity governance across the enterprise environment.
Phase Three: External Assessment and Remediation Planning
After deploying technical controls, once C3PAO assessments resume, contractors engage a CMMC Third-Party Assessment Organization (C3PAO) to conduct an independent audit verifying that all requirements have been met.
If any deficiencies emerge during this evaluation process, organizations must create Plan of Action and Milestones (POA&M) documents outlining corrective actions required within 180 days and need a minimum score of 80% for conditional status eligibility. Requirements worth more than 1 point, including the 5-point IA.L2-3.5.3, cannot go on a POA&M (the one exception is SC.L2-3.13.11 when encryption is used but not FIPS-validated).
Phase Four: Continuous Monitoring and Compliance Maintenance
Maintaining compliance is an ongoing commitment to continuous monitoring and adherence to evolving regulations post-certification. Regular updates check that new threats or policy changes do not compromise previously achieved security levels over time, necessitating periodic reassessment under the CMMC Program rule, which took effect December 16, 2024.
Common CMMC Compliance Pitfalls and Challenges
Many organizations attempting Level 2 certification struggle with misreading the scope of IA.L2-3.5.3, which covers local and network access to privileged accounts and network access to non-privileged accounts. This misunderstanding often leads to incomplete deployments where certain high-value targets remain unprotected against unauthorized intrusion attempts through compromised credentials alone.
Partial Credit Scoring for IA.L2-3.5.3
Contractors must be aware that partial credit exists within the scoring methodology when MFA covers only remote and privileged users. In that case, three points are deducted from the total score instead of the five deducted when MFA is not implemented at all.
The Impact of Suspended Phases on Timeline Expectations
The DoD suspended CMMC Phase 2 on July 13, 2026, pausing third-party assessments slated to commence November 10, 2026. Phase 1 self-assessments remain in effect, and DoD created a CMMC Reform Task Force for a 60-day review.
Strengthen CMMC Compliance With Certificate-Based Authentication
IA.L2-3.5.3 requires multifactor authentication, which uses two different factor types. EAP-TLS provides a phishing-resistant something-you-have element that organizations pair with a second factor type, such as a PIN or biometric.
JoinNow Dynamic PKI automates the certificate lifecycle and issues hardware-bound certificates for Wi-Fi and VPN access. JoinNow Cloud RADIUS validates each attempt against an identity provider, revoking access instantly when a user is disabled or a device becomes non-compliant. Neither tool meets MFA requirements on its own.
To discuss how these solutions fit your authentication strategy, schedule a demo.
Frequently Asked Questions
Does CMMC Level 2 require MFA for every login?
No. IA.L2-3.5.3 does not require MFA for local logins by non-privileged users; it covers local and network access to privileged accounts and network access to non-privileged accounts. Implementing broad policies across the entire user base may be prudent but is not strictly enforced under current guidelines.
Does a certificate count as a factor for CMMC MFA?
Yes, but only as one factor: something you have. Certificates do not independently satisfy multifactor requirements unless paired with a different factor type, such as a PIN or biometric. MFA requires two different categories to achieve valid identity confirmation before granting access privileges.
Is there a deadline for CMMC Level 2 certification?
No fixed deadline currently exists: Phase 2, Phase 3 and Phase 4 are suspended, and DoD relies on self-assessments and select government-led assessments in the interim. A replacement date has not yet been announced. Monitoring official announcements provides clarity on upcoming milestones or adjustments.
Do contractors need GCC High or FedRAMP for CMMC compliance?
CMMC does not mandate a specific cloud product name. DFARS 252.204-7012 requires that an external cloud service provider storing, processing or transmitting covered defense information meets security requirements equivalent to the FedRAMP Moderate baseline. Microsoft describes Office 365 GCC High as designed according to DoD Security Requirements Guidelines Level 4 controls and used by the Defense Industrial Base, while stating Azure Government supports these DFARS cloud service provider requirements. GCC High is one common way to meet that cloud requirement, not a CMMC mandate in itself. Contractors must still enforce MFA on their own accounts under IA.L2-3.5.3 regardless of the chosen cloud tier.
Does CMMC use the latest revision of NIST SP 800-171?
No. NIST published Revision 3 in May 2024 and withdrew Revision 2, but CMMC Level 2 assessments still use Revision 2. The CMMC rule pins the program to Revision 2, February 2020, with updates as of January 28, 2021.
Who performs CMMC assessments?
Contractors conduct Level 1 and Level 2 self-assessments under Phase 1. Although Level 2 assessments by a C3PAO were set to begin November 10, 2026, the DoD suspended those milestones on July 13, 2026. Consequently, organizations currently rely on self-assessments and select government-led assessments while awaiting further regulatory clarity from the CMMC Reform Task Force.