Home Guides CMMC 2.0 Level 2 Compliance Guide
📋

CMMC 2.0 Level 2 Compliance Guide

Framework: CMMC

Download Assessment PDF

Comprehensive Guide to Achieving CMMC 2.0 Level 2 Certification

The Cybersecurity Maturity Model Certification (CMMC) 2.0 is a framework developed by the U.S. Department of Defense (DoD) to enhance the protection of sensitive information within the Defense Industrial Base (DIB). This guide provides a step-by-step approach for contractors aiming to achieve Level 2 certification, ensuring compliance with DoD requirements and securing eligibility for defense contracts.

Understanding CMMC 2.0

CMMC 2.0 streamlines the original five-level model into three distinct levels:

  • Level 1: Foundational – Focuses on basic cybersecurity practices to protect Federal Contract Information (FCI). This level requires organizations to implement a set of 17 practices that align with FAR 52.204-21 standards. It's often self-assessed, ensuring baseline protections against threats to infrastructure.
  • Level 2: Advanced – Targets the protection of Controlled Unclassified Information (CUI) by implementing 110 security practices aligned with NIST SP 800-171. This level represents a substantial leap in complexity and requires a more rigorous assessment of practices that include establishing comprehensive security programs and incident response strategies.
  • Level 3: Expert – Aims to protect CUI from advanced persistent threats by incorporating additional practices from NIST SP 800-172. Level 3 emphasizes real-time threat detection and response mechanisms, necessitating highly sophisticated cybersecurity frameworks.

For a detailed overview, refer to the DoD's official CMMC page: DoD CIO - About CMMC.

Who Needs Level 2 Certification?

Organizations that handle CUI are required to achieve Level 2 certification. This requirement is outlined in the Defense Federal Acquisition Regulation Supplement (DFARS) clause 252.204-7012, which mandates the safeguarding of CUI. Understanding whether your organization processes, stores, or transmits CUI is crucial in determining the need for Level 2 certification. Level 2 certification is mandatory for contractors where handling sensitive defense information is a core part of their operations.

For more information on DFARS 252.204-7012, visit: DFARS Clause 252.204-7012.

Prerequisites for Level 2 Certification

Before pursuing Level 2 certification, organizations should complete the following:

  • NIST SP 800-171 Self-Assessment: Evaluate your current cybersecurity practices against the 110 controls specified in NIST SP 800-171. This comprehensive analysis helps identify potential weaknesses in processes such as access control, incident response, and system integrity.
  • System Security Plan (SSP): Document how each control is implemented within your organization. Your SSP should detail aspects like system boundaries, security architecture, and data flow diagrams to provide a complete overview of the implemented security measures.
  • Supplier Performance Risk System (SPRS) Score: Submit your self-assessment score to the SPRS as required by the DoD. This score is critical in providing the DoD with insights into a contractor's cybersecurity posture.

Guidance on conducting a self-assessment can be found here: DoD CIO - CMMC Resources & Documentation.

Step-by-Step Implementation Process

  1. Conduct a Gap Analysis: Identify discrepancies between your current practices and the requirements of NIST SP 800-171. This includes reviewing technical controls, policies, and procedures to spotlight deficiencies.
  2. Develop a Plan of Action and Milestones (POA&M): Outline strategies and timelines to address identified gaps. This document should include prioritization of tasks based on risk and potential impact.
  3. Implement Required Controls: Apply the necessary technical and administrative controls to meet NIST SP 800-171 requirements. This step could involve deploying advanced security solutions, such as intrusion detection systems and endpoint protection.
  4. Train Personnel: Provide cybersecurity training to employees, emphasizing the handling of CUI. Training should be role-specific and frequent, covering topics such as phishing prevention and secure communication methods.
  5. Document Policies and Procedures: Ensure all cybersecurity policies and procedures are well-documented and accessible. Incorporate regular updates to adapt to new threat landscapes and technological changes.
  6. Perform Internal Audits: Regularly assess the effectiveness of implemented controls and address any deficiencies. Internal audits should be impartial, providing insights into compliance and functionality of security measures.
  7. Engage a Certified Third-Party Assessment Organization (C3PAO): Schedule an official assessment to validate compliance. Choose a C3PAO with experience in your industry to ensure a thorough review aligned with your operational nuances.
  8. Maintain Continuous Monitoring: Establish ongoing monitoring to detect and respond to cybersecurity incidents promptly. This supports proactive identification of threats, allowing for quicker intervention.

The 14 Control Families and 110 Practices

NIST SP 800-171 organizes the 110 security practices into 14 control families, which offer a comprehensive approach to cybersecurity:

Control Family Description
Access Control (AC) Limit system access to authorized users and devices. Implement multi-factor authentication and robust access management systems to reduce unauthorized access risks.
Awareness and Training (AT) Ensure personnel are trained to recognize and respond to security threats. Training programs should include regular testing and simulations to assess awareness levels.
Audit and Accountability (AU) Track system activities to detect and respond to security incidents. Logging and monitoring tools should be deployed to provide traceable and timely data for audits.
Configuration Management (CM) Establish and maintain secure configurations for systems. Implement change control processes to ensure all configuration changes are documented and approved.
Identification and Authentication (IA) Verify the identities of users and devices before granting access. Encourage the use of biometrics and digital certificates for enhanced identity validation.
Incident Response (IR) Develop and implement procedures for responding to security incidents. Create detailed response plans that define roles, responsibilities, and communication paths.
Maintenance (MA) Perform regular maintenance on systems to ensure security. Utilize automated tools for patch management, ensuring timely updates to defenses.
Media Protection (MP) Safeguard media containing CUI from unauthorized access. Apply encryption to portable devices and implement stringent data handling policies.
Personnel Security (PS) Ensure personnel are trustworthy and understand their security responsibilities. Conduct background checks and provide ongoing security awareness programs.
Physical Protection (PE) Limit physical access to systems and facilities to authorized individuals. Secure facilities with access controls like key cards and surveillance systems.
Risk Assessment (RA) Identify and assess risks to organizational operations and assets. Regularly update risk assessments in response to new threats or organizational changes.
Security Assessment (CA) Regularly assess the effectiveness of security controls. Use third-party audits and penetration testing to validate security postures.
System and Communications Protection (SC) Protect the confidentiality and integrity of transmitted information. Implement secure communication protocols and data encryption methods.
System and Information Integrity (SI) Identify and correct system flaws in a timely manner. Establish regular scanning for vulnerabilities and corrective action workflows.

For a comprehensive list of practices within each control family, refer to NIST SP 800-171: NIST SP 800-171 Rev. 2.

Plans of Action and Milestones (POA&M)

POA&Ms are used to document planned remedial actions to correct deficiencies and reduce vulnerabilities. Under CMMC 2.0 Level 2, POA&Ms are permitted but must be closed out within 180 days. Certain critical requirements, such as the implementation of encryption technologies and incident response procedures, cannot be included in a POA&M and must be fully implemented at the time of assessment.

⚠️ Important: Failure to close out POA&Ms within the specified timeframe may result in the expiration of your Conditional CMMC Status.

Detailed POA&M requirements are outlined in 32 CFR § 170.21: DoD CIO - CMMC Resources & Documentation.

Assessment Process

The assessment process involves the following steps:

  1. Select a Certified Third-Party Assessment Organization (C3PAO): Choose an authorized C3PAO from the DoD's marketplace. Select a C3PAO that aligns with your industry and understands the specific challenges faced in your operational environment.
  2. Schedule the Assessment: Coordinate with the C3PAO to plan the assessment timeline. Proper scheduling is essential to allow sufficient preparation and reduce operational disruptions.
  3. Prepare Documentation: Ensure all required documentation, including the SSP and evidence of control implementation, is ready for review. Thorough preparation minimizes the risk of delays and non-compliance findings.
  4. Undergo the Assessment: The C3PAO will evaluate your organization's compliance with CMMC Level 2 requirements through interview sessions, document reviews, and system inspections.
  5. Receive Assessment Results: The C3PAO will provide findings and, if compliant, issue a certification valid for three years. Feedback from this process should also be used to enhance and refine cybersecurity practices continuously.

For more information on the assessment process, refer to the CMMC Assessment Guide: CMMC Assessment Guide - Level 2.

Common Pitfalls and How to Avoid Them

  • Inadequate Documentation: Ensure all policies, procedures, and evidence of control implementation are thoroughly documented. Use centralized repositories and version control to manage document updates efficiently.
  • Insufficient Training: Regularly train employees on cybersecurity practices and the importance of protecting CUI. Include scenarios relevant to your organizational structure and operations to foster engagement and understanding.
  • Overlooking Physical Security: Implement measures to control physical access to systems and facilities. Regular drills and audits can help identify lapses in physical security implementations.
  • Neglecting Continuous Monitoring: Establish processes for ongoing monitoring and timely response to security incidents. Utilize security information and event management (SIEM) tools for real-time analysis and actionable threat intelligence.

Timeline Estimates

The time required to achieve Level 2 certification varies based on organizational maturity and complexity:

  • Small Contractors: Approximately 6-12 months. Smaller organizations may benefit from shorter communication lines but must allocate resources effectively to meet technical challenges.
  • Medium Contractors: Approximately 9-15 months. Medium-sized organizations must balance resource allocation across multiple departments while adhering to security requirements.
  • Large Contractors: Approximately 12-18 months. Larger organizations face complex integration challenges due to diverse systems and extensive infrastructure.

These estimates include time for gap analysis, remediation, implementation, and assessment. Tailoring your timeline requires a detailed understanding of organizational capacity and resource availability.

Cost Estimates

Costs associated with achieving Level 2 certification can vary significantly based on the size and complexity of the organization:

  • Small Contractors: $50,000 - $150,000. Smaller companies often need to invest in initial setup and training expenditures but may face lower overhead costs.
  • Medium Contractors: $150,000 - $500,000. Costs for medium-sized firms may include more significant investments in technology and consultant services to handle complexities.
  • Large Contractors: $500,000 - $1,000,000+. Large organizations typically incur higher costs due to the need for comprehensive security solutions, extensive training, and the scale of CUI handling.

Costs include expenses for technology upgrades, personnel training, policy development, and assessment fees. Consider the costs as ongoing investments in organizational security posture and contract eligibility.

Maintaining Certification

To maintain Level 2 certification, organizations must implement a sustainable cybersecurity strategy:

  • Continuous Monitoring: Implement processes to detect and respond to security incidents promptly. Automation, artificial intelligence, and machine learning can enhance security operations centers (SOCs) for continuous threat identification.
  • Annual Affirmation: Submit an annual affirmation of compliance to the SPRS. Ensure timely and accurate documentation to reflect true compliance status and highlight enhancements in cybersecurity posture.
  • Triennial Assessments: Undergo assessments every three years to renew certification. Regular reviews reinforce compliance and enable organizations to adapt to emerging challenges effectively.

Failure to maintain these requirements may result in the lapse of certification status. Ongoing diligence and investment in cybersecurity practices secure both compliance and operational peace of mind.

References & Further Reading

Compliance Assessment Checklist

63 questions across 14 control domains

Download Printable PDF

Access Control

3.1
6 questions
Q1
Are access control policies established and documented?
3.1.1
Provide policies and procedures that outline access control measures.
Q2
Is access to systems and data limited to authorized users?
3.1.2
Evidence of user access lists and authorization procedures.
Q3
Are access control devices audited regularly?
3.1.5
Records of audits and reviews of access control devices.
Q4
Are remote access sessions restricted and managed?
3.1.6
Remote access logs and restrictions documentation.
Q5
Is separation of duties enforced through access restrictions?
3.1.8
Role-based access control lists and separation of duties policies.
Q6
Is external system access limited to authorized connections?
3.1.22
List of authorized external connections and monitoring reports.

Awareness and Training

3.2
4 questions
Q7
Is security awareness training provided regularly to personnel?
3.2.1
Records of training sessions and attendance logs.
Q8
Are personnel trained to recognize and report potential insider threats?
3.2.2
Training materials and incident reporting procedures.
Q9
Is role-based security training provided based on specific responsibilities?
3.2.3
Curriculum outlines and role-specific training documentation.
Q10
Is refresher training mandatory following significant updates?
3.2.1, 3.2.3
Training schedule and update logs.

Audit and Accountability

3.3
5 questions
Q11
Are audit logs maintained for all critical systems?
3.3.1
Audit logs and retention policies.
Q12
Are audit logs reviewed regularly for anomalous activity?
3.3.2
Review schedules and analysis reports.
Q13
Are audit logs protected from unauthorized access or modifications?
3.3.3
Access control policies for audit logs.
Q14
Are log changes detected and reported?
3.3.5
Log monitoring tools and alteration reports.
Q15
Are audit logging processes tested and verified?
3.3.9
Testing results and verification documentation.

Configuration Management

3.4
5 questions
Q16
Are configuration settings defined and documented for all systems?
3.4.1
Configuration setting documents and baselines.
Q17
Are changes to configuration settings tracked and approved?
3.4.2
Change management logs and approval records.
Q18
Are unauthorized changes to configurations detected and corrected?
3.4.3
Monitoring logs and incident reports on unauthorized changes.
Q19
Is software inventory maintained and regularly updated?
3.4.5
Software inventory records and update schedules.
Q20
Are system configurations periodically reviewed against the baseline?
3.4.6
Review schedules and baseline comparison reports.

Identification and Authentication

3.5
5 questions
Q21
Are unique identifiers assigned to all users and devices?
3.5.1
Identification policies and user/device ID records.
Q22
Is multifactor authentication implemented for access to sensitive systems?
3.5.2
Multifactor authentication setup and logs.
Q23
Are password policies enforced and regularly reviewed?
3.5.3
Documentation of password policies and review records.
Q24
Are inactive accounts disabled or removed after a defined period?
3.5.5
Account management procedures and deactivation logs.
Q25
Are authentication attempts monitored for unusual activity?
3.5.10
Logs and reports of authentication monitoring.

Incident Response

3.6
4 questions
Q26
Is there an established incident response plan?
3.6.1
Incident response plan documentation and approval records.
Q27
Are incidents reported and documented in accordance with procedures?
3.6.2
Incident reports and documentation procedures.
Q28
Are incident response activities regularly tested and updated?
3.6.3
Test results and update logs of incident response plans.
Q29
Is personnel trained in incident response roles and responsibilities?
3.6.1, 3.6.3
Training materials and personnel records.

Maintenance

3.7
4 questions
Q30
Are maintenance processes and schedules documented and reviewed?
3.7.1
Maintenance schedule and review records.
Q31
Is maintenance conducted by authorized personnel only?
3.7.2
Authorization records and maintenance logs.
Q32
Are maintenance tools inspected and secured?
3.7.4
Tool inspection records and security procedures.
Q33
Is remote maintenance of systems restricted and monitored?
3.7.6
Remote maintenance access logs and restriction policies.

Media Protection

3.8
4 questions
Q34
Are media containing sensitive information identified and protected?
3.8.1
Inventory and labeling records of sensitive media.
Q35
Is data destructed using approved methods when no longer needed?
3.8.3
Documentation of data destruction procedures and logs.
Q36
Is access to media restricted to authorized personnel?
3.8.5
Access control lists for storage areas.
Q37
Are media sanitization processes audited for effectiveness?
3.8.6
Audit reports and effectiveness evaluations.

Personnel Security

3.9
4 questions
Q38
Are personnel security policies defined and reviewed?
3.9.1
Policies and review documentation.
Q39
Are background checks conducted on personnel prior to granting access?
3.9.2
Records of background checks and access authorizations.
Q40
Are security policies communicated to all employees?
3.9.1, 3.9.2
Communication records and acknowledgment receipts.
Q41
Are personnel re-evaluated for security clearance periodically?
3.9.1
Re-evaluation schedules and clearance records.

Physical Protection

3.10
4 questions
Q42
Are physical access controls implemented at all entry points?
3.10.1
Documentation of access controls and security measures.
Q43
Is physical access to sensitive areas restricted and monitored?
3.10.2
Access logs and monitoring records.
Q44
Are physical security controls reviewed and tested regularly?
3.10.4
Review logs and test documentation.
Q45
Are visitor access records maintained and reviewed?
3.10.6
Visitor logs and review schedules.

Risk Assessment

3.11
4 questions
Q46
Is a risk assessment process defined and documented?
3.11.1
Risk assessment documents and processes.
Q47
Are risk assessments performed periodically?
3.11.2
Risk assessment schedules and result reports.
Q48
Are identified risks prioritized and mitigated effectively?
3.11.3
Risk mitigation plans and prioritization records.
Q49
Are risk assessments updated following significant changes?
3.11.1, 3.11.2
Change logs and updated risk assessments.

Security Assessment

3.12
4 questions
Q50
Is a security assessment policy defined and in practice?
3.12.1
Security assessment policies and implementation records.
Q51
Are system security assessments conducted to verify compliance?
3.12.2
Assessment schedules and compliance reports.
Q52
Are security control deficiencies documented and remediated promptly?
3.12.3
Deficiency reports and remediation plans.
Q53
Are periodic security assessments reviewed by management?
3.12.4
Review records and management feedback.

System and Communications Protection

3.13
5 questions
Q54
Are network boundaries controlled and monitored?
3.13.1
Network diagrams and monitoring logs.
Q55
Are communication protocols protected from unauthorized access?
3.13.2
Protocol security settings and protection records.
Q56
Are cryptographic mechanisms used to protect data integrity?
3.13.3
Encryption policies and implementation records.
Q57
Is information output from systems checked for accuracy?
3.13.5
Output validation procedures and logs.
Q58
Are system communications monitored for security violations?
3.13.16
Communication monitoring logs and violation reports.

System and Information Integrity

3.14
5 questions
Q59
Are systems regularly scanned to identify vulnerabilities?
3.14.1
Scan schedules and vulnerability reports.
Q60
Are anti-malware measures implemented and updated regularly?
3.14.2
Anti-malware policies and update logs.
Q61
Is unauthorized software installation prevented?
3.14.3
Software installation policies and enforcement records.
Q62
Are security alerts monitored and addressed promptly?
3.14.5
Alert monitoring systems and response records.
Q63
Are integrity verification applications in place to detect unauthorized changes?
3.14.7
Verification application logs and change reports.

Recommended Tools for CMMC