CMMC Level 2 applies to the vast majority of DoD prime contractors and subcontractors that process, store, or transmit Controlled Unclassified Information (CUI). Under the CMMC 2.0 final rule published in the Federal Register on October 15, 2024 (32 CFR Part 170, effective December 16, 2024), contractors on solicitations issued after the effective date are subject to mandatory third-party assessment requirements. According to the DoD Office of the Chief Information Officer (DODCIO), more than 80,000 Defense Industrial Base (DIB) companies will ultimately need CMMC Level 2 certification. If your organization handles CUI — even indirectly as a subcontractor receiving CUI from a prime — failing to certify means losing eligibility to bid on or perform that work.
This checklist maps to the evidence a Certified Third-Party Assessment Organization (C3PAO) will evaluate using NIST SP 800-171A assessment procedures. Use it to identify gaps before engaging a C3PAO, so your assessment budget goes toward certification rather than remediation discovery.
What CMMC Level 2 Actually Requires
CMMC Level 2 requires full implementation of all 110 security practices from NIST SP 800-171 Revision 2, organized across 14 domains. Unlike Level 1 (annual self-attestation), Level 2 requires a triennial assessment by an accredited C3PAO — there is no self-attestation path for contracts involving critical programs or technologies. The 110 practices are weighted in the DoD's SPRS (Supplier Performance Risk System) scoring model, and your score must be calculated and submitted before contract award.
- 14 NIST 800-171 domains covering all major cybersecurity functions
- 110 practices, each mapped to an SPRS point value (total maximum: 110 points)
- Triennial C3PAO assessment for most contracts — no self-attestation option for CUI
- System Security Plan (SSP) required as primary evidence artifact
- Plan of Action & Milestones (POA&M) required for any unimplemented practices
- SPRS score submission required prior to DoD contract award
- Continuous compliance monitoring expected between assessments
Pre-Assessment Readiness Checklist
1. Infrastructure & Network Architecture
- CUI data flows are fully mapped — you know exactly where CUI enters, lives, and exits your environment
- Your CUI Boundary (Assessment Scope) is formally defined and documented
- Network segmentation isolates CUI systems from general business systems
- External boundary protections (firewalls, IDS/IPS) are in place and monitored
- Remote access uses encrypted VPN with MFA; no direct RDP exposure to the internet
- Wireless access points within the CUI boundary use WPA3 or WPA2-Enterprise (802.1X)
- All network devices (routers, switches, firewalls) run current firmware with no known critical CVEs
2. Documentation & Policy Framework
- System Security Plan (SSP) is complete, current (updated within 12 months), and covers all 110 practices
- Acceptable Use Policy (AUP) signed by all users with CUI system access
- Information Security Policy approved by senior leadership
- Incident Response Plan documented, tested, and assigned to named personnel
- Business Continuity / Disaster Recovery Plan addresses CUI systems
- Data Classification Policy defines CUI handling procedures
- Vendor and third-party access agreements include CMMC flow-down requirements
3. Access Control (AC Domain — 22 Practices)
- Formal user account lifecycle process: provisioning, periodic review, and de-provisioning
- Least privilege enforced — no shared admin credentials, no standing admin rights for daily use
- Multi-factor authentication (MFA) required for ALL privileged access and remote access
- MFA required for all CUI system access (not just VPN)
- Session lock activates after 15 minutes of inactivity
- Failed login lockout policy configured (5 attempts or fewer before lockout)
- Separation of duties implemented for critical functions (e.g., no single user can approve and execute changes)
- External system connections reviewed and restricted to business-necessity
- Mobile device management (MDM) solution in place for any mobile devices accessing CUI
4. Incident Response (IR Domain — 3 Practices)
- Incident response capability established with defined roles (IR coordinator, technical lead, communications lead)
- IR plan tested at least annually via tabletop exercise — results documented
- Incident reporting procedure includes notification to prime contractor and/or DoD within required timeframes
- Contact list for US-CERT and DoD reporting maintained and current
- Post-incident analysis process defined to capture lessons learned
5. Media Protection (MP Domain — 9 Practices)
- CUI media (USB drives, hard drives, backups) is labeled, inventoried, and access-controlled
- Removable media policy restricts use to authorized, encrypted devices only
- Media sanitization procedures follow NIST SP 800-88 (Purge or Destroy — not just Delete)
- Physical media transport requires chain-of-custody documentation
- Portable storage devices are scanned for malware upon connection
6. Configuration Management (CM Domain — 9 Practices)
- Baseline configurations documented for all CUI system components (OS, applications, network devices)
- Change management process requires approval before any configuration change to CUI systems
- Vulnerability scanning performed at least monthly on CUI systems
- Patch management process with defined SLAs: Critical patches within 30 days, High within 60 days
- Default passwords changed on all devices; vendor default accounts disabled
- Software allowlisting or application control prevents unauthorized software execution on CUI endpoints
7. Audit & Accountability (AU Domain — 9 Practices)
- Audit logging enabled on all CUI systems: logins, logouts, privilege escalations, file access, policy changes
- Logs retained for minimum 90 days online; 1 year archived
- Log integrity protection prevents tampering (write-once storage or SIEM with integrity controls)
- Log review process — alerts configured for high-priority events reviewed within 24 hours
- User actions on CUI systems are individually attributable (no shared generic accounts)
8. Risk Assessment (RA Domain — 3 Practices)
- Formal risk assessment conducted within past 12 months and documented
- Risk assessment covers CUI systems and supporting infrastructure
- Vulnerability scan results are reviewed and remediation tracked to closure
- Threat intelligence sources monitored (e.g., CISA Known Exploited Vulnerabilities catalog)
9. System & Communications Protection (SC Domain — 16 Practices)
- CUI encrypted in transit using TLS 1.2 or higher (TLS 1.3 preferred)
- CUI encrypted at rest using AES-256 or equivalent FIPS 140-2 validated encryption
- Email containing CUI is encrypted (S/MIME or transport-level encryption)
- DNS filtering / web proxy blocks malicious domains
- Network monitoring (IDS/IPS or SIEM) covers CUI boundary traffic
- Supply chain risk management considerations documented for critical software and hardware
10. Identification & Authentication (IA Domain — 11 Practices)
- Unique identifiers assigned to every user and every device
- Password policy enforces minimum length of 15 characters (or complexity equivalent)
- Password history enforced (prohibit reuse of last 24 passwords)
- Authenticator management process: password resets verified through secure out-of-band method
- Service accounts use managed service account credentials, not user credentials
- Privileged Account Management (PAM) solution or equivalent controls for admin credentials
System Security Plan (SSP) Checklist
The SSP is the single most important document in your CMMC assessment. Assessors will use it as the baseline against which all evidence is measured. An incomplete or outdated SSP is the fastest path to a failed assessment.
- System name, unique identifier, and categorization (CUI system) documented
- System owner, authorizing official (AO), and ISSO/ISSM identified with contact information
- System purpose, mission, and business functions described
- System boundary clearly defined — what is in scope and what is explicitly out of scope
- Hardware and software inventory (all components within the boundary) current and accurate
- Network topology diagrams showing CUI data flows, boundary protections, and trust zones
- All 110 NIST 800-171 controls addressed — status: Implemented, Planned (with POA&M), or Not Applicable (justified)
- Implementation descriptions are specific — name the actual tools, configurations, and responsible parties
- Interconnections with external systems documented (cloud providers, MSPs, partner systems)
- SSP version history and approval signatures from senior leadership
- SSP reviewed and updated within the last 12 months (dated)
POA&M Requirements
A Plan of Action & Milestones (POA&M) is required for every NIST 800-171 practice that is not yet fully implemented. POA&Ms are not a sign of failure — they are evidence of awareness and a commitment to remediation. However, high-risk gaps without realistic remediation timelines will concern assessors.
- Each POA&M item references the specific NIST 800-171 practice number (e.g., 3.1.1)
- Weakness or gap described specifically — not just 'MFA not implemented' but the specific systems/users affected
- Scheduled completion date is realistic and within an acceptable risk tolerance (generally 180 days for high-risk items)
- Responsible party (name and title) assigned to each POA&M item
- Resources required (budget, personnel, tools) identified
- Interim mitigating controls documented for high-risk gaps (compensating controls)
- POA&M reviewed and updated monthly — stale POA&Ms signal poor program management
- POA&M approval by senior leadership (CISO, CIO, or equivalent)
C3PAO Selection Checklist
Selecting the right C3PAO significantly impacts your assessment experience and timeline. All C3PAOs must be accredited or authorized by the CMMC Accreditation Body (The Cyber AB), but quality, specialization, and availability vary considerably.
- Verify the C3PAO is listed as authorized on the official CMMC Marketplace (cyberab.org/Catalog)
- Confirm C3PAO has experience with your industry sector (defense manufacturing, IT services, aerospace, etc.)
- Request references from organizations of similar size and scope that the C3PAO has assessed
- Confirm who will lead your assessment and verify that assessor's CCA certification
- Review proposed assessment team composition — verify all members hold current CCP or CCA credentials
- Get a clear Statement of Work defining assessment scope, timeline, deliverables, and fees
- Clarify what constitutes the 'assessment scope' — is the C3PAO including cloud services, MSPs, or subsidiaries?
- Understand their findings process: How are preliminary findings communicated? Is there a review period before the final report?
- Confirm Cyber AB Marketplace listing shows no open complaints or disciplinary actions
- Confirm the C3PAO will submit the assessment results to CMMC eMASS (the DoD system) on completion
Day-of-Assessment Preparation
The week before and day of your C3PAO assessment can make or break the outcome. Assessors form impressions quickly, and disorganization or inability to quickly produce evidence creates doubt even when controls are technically implemented.
- Evidence library organized by NIST 800-171 practice number — assessors can quickly find artifacts for any control
- SSP, POA&M, and network diagrams printed and available in physical form as backup
- Technical staff available during assessment — system administrators and security team on standby
- Conference room or video conferencing setup tested and ready for kickoff meeting
- Demo environments or live system access ready for assessor walk-throughs
- Screenshots and configuration exports pre-generated for key controls (firewall rules, AD policies, MFA config)
- Log samples available showing audit trail for privileged access and CUI system events
- All relevant vendor documentation (cloud security certifications, MSP SOC 2 reports) gathered
- HR records ready for background check verification if requested
- Points of contact list given to assessors: who to ask about which systems
Complete 30-Item CMMC Level 2 Pre-Assessment Checklist
| # | Checklist Item | Domain | Priority | Status |
|---|---|---|---|---|
| 1 | CUI data flow map documented and current | AC | Critical | |
| 2 | CUI boundary (assessment scope) formally defined | AC | Critical | |
| 3 | MFA enforced for all CUI system access | IA | Critical | |
| 4 | MFA enforced for all privileged/admin accounts | IA | Critical | |
| 5 | SSP complete and covers all 110 practices | CA | Critical | |
| 6 | POA&M created for all unimplemented controls | CA | Critical | |
| 7 | SPRS score calculated and submitted to SPRS portal | CA | Critical | |
| 8 | Endpoint detection & response (EDR) deployed on CUI endpoints | SI | High | |
| 9 | Vulnerability scans run monthly; results tracked | RA | High | |
| 10 | Patch SLAs defined and current: no critical unpatched CVEs | CM | High | |
| 11 | CUI encrypted at rest (AES-256 / FIPS 140-2) | SC | High | |
| 12 | CUI encrypted in transit (TLS 1.2+) | SC | High | |
| 13 | Network segmentation isolates CUI from general-purpose network | SC | High | |
| 14 | Audit logging active on all CUI systems; logs retained 1 year | AU | High | |
| 15 | Incident response plan documented and tested in past 12 months | IR | High | |
| 16 | Baseline configurations documented for all CUI system components | CM | High | |
| 17 | Change management process enforced for CUI systems | CM | High | |
| 18 | Least privilege enforced; admin rights not used for daily tasks | AC | High | |
| 19 | Session lock (15 min) and screen lock enforced on CUI endpoints | AC | Medium | |
| 20 | Account lockout after 5 failed attempts configured | IA | Medium | |
| 21 | Password policy: 15+ characters, no reuse of last 24 | IA | Medium | |
| 22 | Media sanitization per NIST 800-88 (Purge/Destroy, not Delete) | MP | Medium | |
| 23 | Removable media policy: authorized encrypted devices only | MP | Medium | |
| 24 | Physical access controls for CUI server/workstation areas | PE | Medium | |
| 25 | Security awareness training completed by all staff with CUI access | AT | Medium | |
| 26 | Annual risk assessment documented and approved | RA | Medium | |
| 27 | Vendor/MSP agreements include CMMC flow-down and CUI handling clauses | SR | Medium | |
| 28 | Network topology diagrams current and included in SSP | CA | Medium | |
| 29 | Backup and recovery tested for CUI systems (tested recovery RTO) | CP | Medium | |
| 30 | C3PAO selected and assessment engagement letter signed | — | Pre-Assessment |
Next Steps: From Checklist to Certification
Working through this checklist systematically — ideally 6 to 12 months before your target contract award date — gives you the runway to remediate gaps without compromising business opportunities. Organizations that attempt CMMC assessments without adequate preparation face assessment costs of $50,000–$150,000+ only to receive a conditional or failed result, requiring re-assessment fees on top of remediation costs.
Working through this checklist 6–12 months before your target contract award date gives you the runway to remediate gaps without losing bidding opportunities. Organizations that enter C3PAO assessments underprepared often find assessment costs of $40,000–$120,000 yield conditional results, requiring additional remediation and re-assessment fees. A structured pre-assessment approach is the most cost-effective path to CMMC Level 2 certification.
Authoritative Sources
- DoD CMMC Program Office (DODCIO): dodcio.defense.gov/CMMC — official CMMC 2.0 program documentation, FAQs, and policy updates
- CMMC 2.0 Final Rule: Federal Register Vol. 89, No. 199 (October 15, 2024), 32 CFR Part 170 — the legally binding CMMC program requirements
- NIST SP 800-171 Rev. 2: csrc.nist.gov — 'Protecting Controlled Unclassified Information in Nonfederal Systems' — the 110-control baseline for CMMC Level 2
- NIST SP 800-171A: csrc.nist.gov — 'Assessing Security Requirements for CUI' — the assessment procedures C3PAOs use
- CMMC Accreditation Body (The Cyber AB): cyberab.org — accredits C3PAOs and hosts the CMMC Marketplace
- CISA CMMC Resources: cisa.gov/cmmc — cybersecurity resources for defense industrial base organizations
- DFARS 252.204-7012: acquisition.gov — the DFARS clause requiring NIST 800-171 compliance for CUI contracts
- DFARS 252.204-7019/7020/7021: acquisition.gov — SPRS score requirements, assessment obligations, and CMMC flow-down clauses