By Dave Chapman, President
A useful CMMC readiness checklist covers the required level and assessment route, the FCI or CUI boundary, security controls, documentation and evidence, employee training, and supplier responsibilities. Each item needs an owner, a requirement reference, and evidence of completion. Record unmet requirements accurately rather than treating a planned purchase or future fix as completed work.
Confirm the CMMC Level You Need
Before you start checking controls, confirm the standard you are trying to meet.
Review active contracts, anticipated bids, and customer flow-down requirements. Determine whether your company handles FCI, CUI, or both.
- Level 1 requires 15 basic safeguarding practices for organizations that handle FCI.
- Level 2 covers all 110 security requirements in NIST SP 800-171 Rev. 2 for organizations that handle CUI.
Record the contract and amendment supporting the required level and assessment route. Current suspension guidance limits new procurement requirements to Level 1 or Level 2 self-assessments. A readiness checklist should reflect the actual requirement, not an outdated assumption about mandatory third-party certification.
Define the Assessment Boundary
Identify the people, systems, facilities, and service providers that handle protected information or provide security to the assessment scope.
In manufacturing, the review extends beyond the office network.
- Engineering and CAD workstations
- File servers and email systems
- CNC controllers, PLCs, and HMIs
- Quality and test equipment
- Remote access and maintenance tools
- Cloud platforms and backup systems
- Portable media, printers, and physical records
Assign asset categories and document why each asset belongs there. For Level 2, a security system may remain in scope without holding CUI. The inventory, diagram, and SSP should show the same boundary and explain how excluded systems are separated.
Review the Technical Controls
Your checklist should translate security requirements into actions that fit the production environment.
Review these technical areas against the requirements that apply.
- Network segmentation between operational technology and corporate IT
- MFA covering the account and access types required by Level 2 requirement 3.5.3
- Separate administrative and routine user accounts
- Endpoint protection or application whitelisting for fixed-function devices
- Central logging and monitoring
- Secure configuration and change management
- Media protection and sanitization
- Incident response and recovery procedures
Do not mark a control complete because a product was purchased. Confirm that it is configured, monitored, used consistently, and supported by evidence.
Build the Documentation and Evidence Set
Written policies describe what should happen. Assessors need evidence showing what actually happens.
Your System Security Plan should explain how each requirement works in your environment, including the technologies used, the people responsible, the procedure followed, and the location of supporting evidence.
Collect records that demonstrate the work your policies describe.
- Configuration screenshots
- Log and alert samples
- User-access reviews
- Training records
- Change and support tickets
- Network diagrams and asset inventories
- Incident-response exercises
- Vendor compliance records
Use the checklist to connect each requirement to its SSP narrative and evidence location. That makes the assessment easier to manage and exposes missing proof before an assessor does.
Track Gaps With a POA&M
Record each deficiency with its corrective action, owner, resources, due date, and supporting evidence. Check the POA&M eligibility rules before relying on conditional status. Level 1 does not permit a POA&M. Conditional Level 2 requires at least 88 points and allows only the specified unmet requirements.
Prioritize gaps by contractual deadline and risk severity. A vulnerable system that stores CUI deserves attention before a low-impact documentation cleanup.
Track progress regularly. The closeout assessment for a conditional Level 2 POA&M must be completed within 180 days of the conditional status date. An internal schedule change does not extend that deadline.
Include People and Vendors
Technical controls fail when employees do not understand the process or when a vendor introduces an unmanaged connection.
Your readiness checklist should confirm that role-specific training is complete, phishing simulations or tabletop exercises are being performed, and policy violations receive follow-up.
Identify vendors by the services and information involved. Retain relevant status or authorization evidence, shared-responsibility records, and access agreements. Set a review schedule for critical providers and update it after significant service or contract changes.
Use the Checklist as a Working Project Plan
A readiness checklist is most useful when it shows more than yes or no.
Use these fields to make each checklist entry actionable.
|
Checklist field |
What to record |
|---|---|
|
Requirement |
The control and assessment-objective reference |
|
Owner |
The role responsible for the work |
|
Status |
Implemented, incomplete, or not applicable with its basis |
|
Evidence |
The current record and its protected storage location |
|
Remediation |
The action, due date, and applicable POA&M status |
|
Review date |
The next scheduled review and change triggers |
Update it when infrastructure, staffing, contracts, or production processes change. CMMC readiness is a sustained practice, not a document assembled once before an assessment.
One Up Solutions Northwest's Perspective
I want a checklist to show what information is protected, which systems are in scope, how the controls work, and where the evidence is stored. A list of completed purchases does not answer those questions.
One Up Solutions Northwest helps Oregon manufacturers connect security requirements to real infrastructure, monitoring, support, and planning. The goal is a program your team can operate every day, not a stack of policies that only comes out during an assessment.
CMMC Compliance Checklist for the Manufacturing Industry
FAQs About CMMC Readiness Checklists
Should a CMMC checklist include all 110 NIST controls?
For Level 2, map the checklist to all 110 requirements and their applicable assessment objectives. Document the reason for any not-applicable finding. A requirement is not excluded simply because it is difficult to implement.
Who should own the CMMC readiness checklist?
Ownership can be shared across leadership, IT, security, operations, and compliance, but one person should coordinate status, evidence, deadlines, and follow-up so gaps do not fall between teams.
How often should the checklist be updated?
Update it whenever contracts, systems, staff, vendors, or data flows change, and review it on a regular schedule. Monthly review often aligns well with POA&M tracking.
Can a template replace a readiness assessment?
No. A template can organize the work, but the answers must reflect your actual environment. Generic descriptions and copied control language do not prove implementation.
Next Step
Schedule a readiness review to confirm the required level, map the environment, and organize the remaining work. Bring the contracts, asset list, SSP, and available evidence so the discussion starts with the systems your team actually uses.
Also, be sure to review the CMMC Compliance Checklist for Defense Manufacturers