Checklist for Achieving CMMC Certification and Meeting Cybersecurity Standards for Defense Contractors
The CMMC compliance checklist at SpendLogic is a structured guide that outlines the necessary steps to achieve certification. A key component is confirming the CMMC level required for your contract, which can be Level 1 for Federal Contract Information (FCI) or Level 2 for Controlled Unclassified Information (CUI). Additionally, the checklist provides CMMC requirements that include conducting a gap analysis to assess your current environment against relevant standards, such as NIST SP 800-171 for Level 2, ensuring adherence to CMMC requirements throughout the process.

Cmmc Compliance Checklist
A CMMC compliance checklist generally involves the following steps to prepare for and achieve certification:
- Confirm the CMMC Level: Determine the required level (Level 1 for Federal Contract Information (FCI) or Level 2 for Controlled Unclassified Information (CUI)) based on your contract or solicitation.
- Scope the Assessment: Identify and document the systems, people, and facilities that process, store, or transmit FCI or CUI. Defining a smaller “enclave” or assessment boundary can often simplify the process.
- Conduct a Gap Analysis: Assess your current environment against the relevant requirements (e.g., NIST SP 800-171 for Level 2) to identify missing controls.
- Develop Documentation: Create and maintain a System Security Plan (SSP) that describes how each requirement is met.
- Create a Plan of Action and Milestones (POA&M): Document any identified gaps and the steps you will take to remediate them. Note that for Level 1, all requirements must be met (no POA&M allowed), while Level 2 has specific rules regarding POA&M eligibility.
- Implement Controls: Address the gaps identified in your assessment, starting with the controls that assessors focus on most.
- Self-Assessment and Affirmation: Conduct a final self-assessment against the objectives (e.g., NIST SP 800-171A for Level 2). Once compliant, enter your results, CAGE codes, and score into the Supplier Performance Risk System (SPRS) and have a senior official affirm your compliance.
- Third-Party Assessment (if required): For contracts requiring a C3PAO assessment, select an accredited organization to perform the formal audit.
Documenting Security Controls in a System Security Plan for Meeting CMMC Requirements
To document security controls in a System Security Plan (SSP) for CMMC compliance, you must create a formal document that serves as the foundation for your cybersecurity posture and demonstrates how your organization meets all applicable requirements. Key steps and requirements for documenting these controls include:
- Define Scope and Boundaries: Clearly identify the system boundaries and all assets that process, store, or transmit Controlled Unclassified Information (CUI), as well as security protection assets (e.g., firewalls, endpoint protection) and Contractor Risk Managed Assets (CRMAs).
- Map Controls to Implementation: Document how each required security control (such as the 110 controls in NIST SP 800-171 for Level 2) is implemented and maintained within your defined environment.
- Integrate Policies and Procedures: Rather than maintaining separate documents, many contractors embed security policies and procedures directly into the SSP for review by assessors.
- Reflect Current State: The SSP must accurately reflect your current, not future, security state. It should be consistent with other compliance artifacts, such as your Supplier Performance Risk System (SPRS) score and any Plans of Action and Milestones (POA&Ms).
- Incorporate Shared Responsibility: If using cloud service providers (e.g., AWS, Azure, Google Cloud) or managed service providers, include or reference a Customer Responsibility Matrix (CRM) to clarify which controls are managed by the provider versus your organization.
- Align with Evidence: Ensure the documentation is supported by a “proof package” of evidence—such as screenshots, logs, training records, and scan reports—that demonstrates the controls are functioning as described.
Pro-Tip: The most effective way to prevent scope creep when scoping and isolating CUI is to establish a clear, enforceable boundary from the outset and rigorously document every decision. Start by mapping every workflow and data touchpoint involving CUI, engaging both IT and frontline staff to uncover informal or overlooked data flows. Once you have a complete picture, design a dedicated enclave—physically or logically separated from the rest of your network—where all CUI activity is confined. Use technical controls like firewalls, access controls, and separate authentication to enforce this boundary, and avoid relying solely on network segmentation methods that can be bypassed or misunderstood. Categorize every asset according to its relationship with CUI, and explicitly exclude non-essential systems from your scope. Finally, keep your documentation—network diagrams, asset inventories, and policies—up to date and aligned with your actual environment, reviewing and updating it regularly as part of your change management process. This disciplined approach not only minimizes your compliance burden but also makes your CUI environment easier to secure and defend.
How many primary obligations must organizations fulfill for CMMC Level 1 compliance?
To implement foundational security practices for CMMC Level 1 compliance, organizations must fulfill three primary obligations centered on protecting Federal Contract Information (FCI):
- Implement 15 Security Practices: Organizations must fully implement all 15 security practices derived from Federal Acquisition Regulation (FAR) 52.204-21. These practices encompass six domains: access control, identification and authentication, media protection, physical security, communications protection, and system integrity. There are no Plans of Action and Milestones (POA&Ms) allowed at Level 1; all 15 practices must be fully implemented to be considered compliant.
- Conduct an Annual Self-Assessment: Compliance is verified through an annual self-assessment using the “examine, interview, and test” methodology. This involves reviewing documentation and configurations (examine), confirming that personnel understand and follow procedures (interview), and verifying that controls function as intended (test). Contractors may perform this internally or engage a third party to assist, though the latter is still considered a self-assessment.
- Submit an Annual Affirmation: A senior company official (such as the CEO, president, or owner) must formally attest to the organization’s compliance by submitting an annual affirmation in the Supplier Performance Risk System (SPRS). This serves as a legal declaration to the U.S. government that all 15 practices are fully implemented.
Compliance can be achieved for an entire enterprise network or for specific enclaves where FCI is processed, stored, or transmitted.
Checklist for CMMC Compliance: Determining the Required Level
To effectively determine your required CMMC compliance level, follow these essential steps:
- Review Contractual Obligations: Examine your specific Department of Defense (DoD) solicitations or contracts (DFARS 252.204-7021) to identify the required CMMC level and assessment type.
- Identify Information Types: Determine the nature of the information your organization processes, stores, or transmits:
- Level 1 (Foundational): Applies to organizations that handle only Federal Contract Information (FCI).
- Level 2 (Advanced): Applies to organizations that handle Controlled Unclassified Information (CUI).
- Level 3 (Expert): Applies to organizations that handle CUI and are subject to Advanced Persistent Threats (APTs).
- Check Flow-Down Requirements: Consult with your prime contractors to understand their requirements, as CMMC clauses often “flow down” to subcontractors handling the same types of information.
Checklist for CMMC Compliance: Identifying and Scoping Federal Contract Information or Controlled Unclassified Information
To identify and scope Federal Contract Information (FCI) and Controlled Unclassified Information (CUI) for CMMC compliance, organizations should follow a structured process to define the assessment boundary. This involves understanding the data types, identifying in-scope assets, using official resources, documenting the scope, and isolating data flows. FCI includes information created for or provided by the government under a contract that is not intended for public release, while CUI encompasses sensitive information requiring safeguarding or dissemination controls. Properly scoping these data types is crucial for meeting the certification criteria outlined in the CMMC.
| Approach | Factors | Scope | Timeline | Costs | Risks |
|---|---|---|---|---|---|
| Understand Data Types | FCI and CUI definitions | All relevant data | Initial phase | Low | Misidentification of data |
| Identify In-Scope Assets | Systems, applications, teams | Assets processing FCI/CUI | 1-2 weeks | Moderate | Exclusion of critical assets |
| Use Official Resources | DoD CUI Registry, contract clauses | Specific data categories | Ongoing | Minimal | Outdated information |
| Document the Scope | System Security Plan (SSP) | Documented assets | 1 week | Low | Inaccurate documentation |
| Isolate Data Flows | Data movement tracking | Systems handling FCI/CUI | 1-2 weeks | Moderate | Complexity in compliance |
Inventorying and Defining In-Scope Assets That Handle FCI or CUI for Compliance With CMMC
To inventory and define in-scope assets for CMMC compliance, organizations must identify all systems, people, and facilities that process, store, or transmit Federal Contract Information (FCI) or Controlled Unclassified Information (CUI). This process, known as scoping, is a foundational step that determines the assessment boundary and significantly impacts compliance costs.
- Map Data Flows: Before creating an inventory, map the paths that FCI and CUI take through your organization. Every path CUI travels pulls the systems on that path into the assessment scope.
- Create an Asset Inventory: Document every in-scope device, user, and cloud service. This includes obvious systems like file servers and databases, as well as commonly overlooked items such as email, file-sharing platforms, managed file transfers, web forms, and AI tools.
- Categorize Assets: For CMMC Level 2, assets must be sorted into specific categories:
- CUI Assets: Assets that process, store, or transmit CUI.
- Security Protection Assets (SPA): Systems that provide security controls for CUI assets, even if they do not directly handle CUI.
- Contractor Risk Managed Assets (CRMA): Assets capable of handling CUI but controlled to avoid doing so.
- Specialized Assets (SA): Unique systems such as IoT devices or government-provided equipment.
- Out-of-Scope Assets: Assets that cannot process, store, or transmit CUI and do not provide security protections for CUI assets. These require documented justification for their exclusion.
- Define the Boundary: Use network segmentation, isolation techniques, or CUI enclaves to limit the scope to only those systems necessary for compliance.
- Document in the System Security Plan (SSP): Record the asset inventory and the treatment of these assets within your SSP. While there is no requirement to embed every asset directly into the SSP, it must serve as a record of the scoping process, including data flows and security measures.
Checklist for CMMC Compliance: Covering 14 Security Domains Including Access Control and Incident Response
The CMMC framework organizes its security requirements into 14 distinct domains, which are essential for structuring compliance checklists and assessments. These domains encompass 110 security controls derived from NIST SP 800-171, ensuring a comprehensive approach to cybersecurity.
- Access Control (AC): Focuses on limiting system access to authorized users, processes, and devices, including managing remote access and session timeouts.
- Audit and Accountability (AU): Involves tracking and logging system activities to ensure accountability.
- Awareness and Training (AT): Ensures personnel are trained to recognize threats and understand their security responsibilities.
- Configuration Management (CM): Relates to establishing and maintaining baseline configurations for systems.
- Identification and Authentication (IA): Requires verifying the identities of users, processes, and devices before granting access.
- Incident Response (IR): Covers the detection, analysis, and response to security incidents, including maintaining an incident response plan.
- Maintenance (MA): Focuses on secure practices for system maintenance and repairs.
- Media Protection (MP): Involves protecting sensitive data stored on physical or digital media.
- Personnel Security (PS): Ensures that individuals are screened and managed appropriately regarding their access to sensitive information.
- Physical Protection (PE): Requires controlling physical access to facilities and systems.
- Risk Assessment (RA): Involves identifying and managing cybersecurity risks to organizational operations.
- Security Assessment (CA): Focuses on evaluating and improving the effectiveness of security controls.
- System and Communications Protection (SC): Safeguards data in transit and at rest within the system.
- System and Information Integrity (SI): Involves detecting and correcting system security weaknesses and protecting against malicious code.
Understanding these domains is crucial for meeting the assessment criteria of the CMMC compliance checklist, ensuring that organizations can effectively protect sensitive information and maintain compliance with federal regulations.
Tracking Remediation With a Plan of Action and Milestones for Meeting CMMC Requirements
A Plan of Action and Milestones (POA&M) serves as a centralized, living management tool used to track security gaps, document remediation steps, assign ownership, and establish timelines for achieving CMMC compliance. It is essential for organizations to understand that a POA&M is not a substitute for required security controls and cannot be used to defer foundational or critical requirements that must be fully implemented at the time of assessment.
Key aspects of tracking remediation via a POA&M include:
- Purpose and Scope: The POA&M documents known deficiencies and provides a structured roadmap for fixing them. It signals to assessors that an organization is actively managing its security posture and working toward compliance.
- Required Elements: An effective POA&M must include:
- Identification of the unmet security requirement or deficiency.
- Specific corrective actions or mitigation strategies.
- Assignment of a responsible party (owner).
- Realistic target completion dates and milestones.
- Resources required for remediation.
- Methods for verifying that the work is completed.
- CMMC Level Restrictions:
- Level 1: POA&Ms are not permitted; all 15 basic safeguarding requirements must be fully implemented before self-assessment.
- Level 2: Organizations may achieve a “conditional” status by meeting at least 80% of the 110 NIST SP 800-171 controls and placing remaining eligible “NOT MET” requirements into a POA&M. These gaps must be remediated within 180 days.
- Management Best Practices: The POA&M should be treated as a “living, breathing document” that is updated regularly to reflect progress. It is distinct from the System Security Plan (SSP), which documents how controls are currently implemented, though the POA&M tracks the path to closing gaps identified within that system.