CMMC/Level 2
Advanced — 110 Practices

CMMC Level 2:
Advanced Cybersecurity

CMMC Level 2 applies to DoD contractors that handle Controlled Unclassified Information (CUI). It encompasses all 110 security practices of NIST SP 800-171 r2 across 14 domains — and requires a formal third-party assessment by a Cyber-AB accredited C3PAO.

Galaxy Consulting has achieved CMMC Level 2 certification. This accomplishment gives us direct, first-hand insight into exactly what your organization will face.

Who Needs CMMC Level 2?

CMMC Level 2 is required for any DoD contractor or subcontractor that handles Controlled Unclassified Information (CUI) — a category of sensitive but unclassified federal data that requires protection under law, regulation, or government-wide policy.

CUI includes export-controlled technical data, defense technical information, personally identifiable information (PII), and other sensitive categories defined by the CUI Registry maintained by the National Archives and Records Administration (NARA).

If your DoD contract includes a DFARS 252.204-7012 clause or references NIST SP 800-171 compliance, you almost certainly need CMMC Level 2. As the DoD phases CMMC into solicitations, non-compliant companies will be ineligible to bid.

Defense contractors that receive, process, or store CUI
Subcontractors handling CUI passed down from primes
Companies with DFARS 252.204-7012 clauses in their contracts
Manufacturers producing defense-related products or components
IT service providers supporting organizations that process CUI

Key Facts About CMMC Level 2

110 Practices
Based on NIST SP 800-171 r2 — all 110 security requirements across 14 domains. Includes all 17 Level 1 practices.
C3PAO Assessment
Unlike Level 1, contracts which include requirements to access and process Controlled Unclassified Information (CUI), require CMMC Level 2 or Level 3 assessments. Contracts which are classified as "non-prioritized" acquisitions allow contractors to conduct CMMC Level 2 self-assessments. Acquisitions which include levels of CUI with higher sensitivity and risk require CMMC Level 2 or CMMC Level 3 formal third-party assessments led by a Cyber-AB an accredited Certified Third-Party Assessment Organization (C3PAO).
3-Year Validity
CMMC Level 2 certification is valid for 3 years. A full re-assessment by a C3PAO is required at the end of each 3-year cycle.
SSP & POA&M Required
A System Security Plan (SSP) and Plan of Action & Milestones (POA&M) are required documentation artifacts for Level 2 assessment.
DFARS 252.204-7012
Most companies that need Level 2 already have DFARS 252.204-7012 in their contracts. CMMC formalizes and verifies those existing obligations.
Annual Affirmation
In years 2 and 3, a senior company official must annually affirm continued compliance with all Level 2 practices in the CMMC portal.

Understanding the Difference

Level 1 vs. Level 2 — What Changes?

CMMC Level 1

  • 17 security practices across 6 domains
  • Protects Federal Contract Information (FCI)
  • Annual self-assessment — no third party required
  • Based on FAR 52.204-21
  • Required for all DoD contractors with FCI

CMMC Level 2

  • 110 security practices across 14 domains
  • Protects Controlled Unclassified Information (CUI)
  • Formal C3PAO third-party assessment required
  • Based on NIST SP 800-171 r2
  • Required for contractors that handle CUI

CMMC Level 2 is a superset of Level 1 — all 17 Level 1 practices are included within the 110 Level 2 practices.

The Requirements

The 14 CMMC Level 2 Domains

All 110 practices from NIST SP 800-171 r2 are organized into 14 security domains. Every organization seeking Level 2 must demonstrate compliance across all domains. Key representative practices are shown below.

AC

Access Control

22 practices
Limit System Access to Authorized Users

Limit information system access to authorized users, processes acting on behalf of authorized users, and devices (including other information systems).

AC.L2-3.1.1
Control CUI Flow

Control the flow of CUI in accordance with approved authorizations. Enforce information flow policies between interconnected systems.

AC.L2-3.1.3
Employ Least Privilege

Employ the principle of least privilege, including for specific security functions and privileged accounts.

AC.L2-3.1.5
Control Remote Access

Monitor and control remote access sessions. Employ cryptographic mechanisms to protect the confidentiality of remote access sessions.

AC.L2-3.1.12
Protect Wireless Access

Protect wireless access using authentication and encryption. Identify and authenticate wireless users prior to granting access.

AC.L2-3.1.17
Control Use of External Systems

Verify and control/limit connections to external information systems. Prohibit the use of portable storage devices on external systems without verifiable controls.

AC.L2-3.1.20

Showing representative practices — AC domain contains 22 total practices in NIST SP 800-171 r2.

AT

Awareness & Training

3 practices
Conduct Security Awareness Activities

Ensure personnel are aware of the security risks associated with their activities and of applicable policies, standards, and procedures related to CUI.

AT.L2-3.2.1
Role-Based Security Training

Ensure personnel are trained to carry out their assigned information security responsibilities. Provide role-based security training before authorizing access.

AT.L2-3.2.2
Insider Threat Awareness

Provide security awareness training on recognizing and reporting potential indicators of insider threat.

AT.L2-3.2.3

Showing representative practices — AT domain contains 3 total practices in NIST SP 800-171 r2.

AU

Audit & Accountability

9 practices
Create and Retain System Audit Logs

Create and retain system audit logs to enable monitoring, analysis, investigation, and reporting of unlawful or unauthorized activity.

AU.L2-3.3.1
Ensure Audit Accountability

Ensure the actions of individual users can be traced to those users so they can be held accountable for their actions.

AU.L2-3.3.2
Correlate Audit Records

Correlate audit record review, analysis, and reporting processes for investigation and response to indications of unlawful, unauthorized, suspicious activity.

AU.L2-3.3.5

Showing representative practices — AU domain contains 9 total practices in NIST SP 800-171 r2.

CM

Configuration Management

9 practices
Establish Baseline Configurations

Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation).

CM.L2-3.4.1
Establish Configuration Settings

Establish and enforce security configuration settings for information technology products used in organizational systems.

CM.L2-3.4.2
Employ Least Functionality

Configure systems to provide only essential capabilities, prohibiting or restricting functions, ports, protocols, and services not required.

CM.L2-3.4.6

Showing representative practices — CM domain contains 9 total practices in NIST SP 800-171 r2.

IA

Identification & Authentication

11 practices
Identify and Authenticate System Users

Identify and authenticate organizational users, processes acting on behalf of users, and devices before allowing access to organizational systems.

IA.L2-3.5.1
Use Multi-Factor Authentication (MFA)

Use multi-factor authentication for local and network access to privileged accounts and remote access to non-privileged accounts.

IA.L2-3.5.3
Enforce Password Complexity

Enforce minimum password complexity and change requirements. Prohibit password reuse for a specified number of generations.

IA.L2-3.5.7

Showing representative practices — IA domain contains 11 total practices in NIST SP 800-171 r2.

IR

Incident Response

3 practices
Establish Incident Handling Capability

Establish an operational incident-handling capability including preparation, detection, analysis, containment, recovery, and user response activities.

IR.L2-3.6.1
Track and Report Incidents

Track, document, and report incidents to designated officials and/or authorities both internal and external to the organization.

IR.L2-3.6.2
Incident Response Testing

Test the organizational incident response capability including testing of roles and responsibilities.

IR.L2-3.6.3

Showing representative practices — IR domain contains 3 total practices in NIST SP 800-171 r2.

MA

Maintenance

6 practices
Perform System Maintenance

Perform maintenance on organizational systems. Approve and monitor all maintenance activities, whether performed on site or remotely.

MA.L2-3.7.1
Control Maintenance Tools

Provide controls on the tools, techniques, mechanisms, and personnel that perform maintenance on organizational systems.

MA.L2-3.7.2
Require MFA for Remote Maintenance

Require multi-factor authentication to establish nonlocal maintenance sessions via external network connections, and terminate such connections when maintenance is complete.

MA.L2-3.7.5

Showing representative practices — MA domain contains 6 total practices in NIST SP 800-171 r2.

MP

Media Protection

9 practices
Protect System Media

Protect system media (both paper and digital) containing CUI, both paper and digital. Mark media with necessary CUI markings and distribution limitations.

MP.L2-3.8.1
Sanitize or Destroy Media

Sanitize or destroy system media before disposal or reuse. Use NIST SP 800-88 guidelines for media sanitization.

MP.L2-3.8.3
Control Use of Removable Media

Control the use of removable media on system components. Prohibit use of portable storage without an identifiable owner.

MP.L2-3.8.7

Showing representative practices — MP domain contains 9 total practices in NIST SP 800-171 r2.

PE

Physical Protection

6 practices
Limit Physical Access

Limit physical access to organizational systems, equipment, and operating environments to authorized individuals.

PE.L2-3.10.1
Protect and Monitor Physical Facility

Protect and monitor the physical facility and support infrastructure for organizational systems.

PE.L2-3.10.2
Enforce Access Control for Alternative Work Sites

Enforce safeguarding measures for CUI at alternate work sites. Apply appropriate protections for individuals working in telework environments.

PE.L2-3.10.6

Showing representative practices — PE domain contains 6 total practices in NIST SP 800-171 r2.

PS

Personnel Security

2 practices
Screen Personnel

Screen individuals prior to authorizing access to organizational systems containing CUI. Review and verify personnel security clearances and background investigations.

PS.L2-3.9.1
Protect CUI During Termination

Ensure that CUI and system access are properly terminated upon employee departure. Conduct exit interviews, retrieve all access media, and disable all accounts.

PS.L2-3.9.2

Showing representative practices — PS domain contains 2 total practices in NIST SP 800-171 r2.

RA

Risk Assessment

3 practices
Conduct Risk Assessments

Periodically assess the risk to organizational operations, assets, and individuals resulting from the operation of organizational systems and the associated processing of CUI.

RA.L2-3.11.1
Scan for Vulnerabilities

Scan for vulnerabilities in organizational systems and applications periodically. Remediate vulnerabilities in accordance with risk assessments.

RA.L2-3.11.2
Remediate Vulnerabilities

Remediate vulnerabilities in accordance with risk assessments. Develop and implement a plan for vulnerability remediation and tracking.

RA.L2-3.11.3

Showing representative practices — RA domain contains 3 total practices in NIST SP 800-171 r2.

CA

Security Assessment

4 practices
Periodically Assess Security Controls

Periodically assess the security controls in organizational systems to determine if the controls are effective in their application.

CA.L2-3.12.1
Develop and Implement Plans of Action

Develop and implement plans of action (POA&Ms) designed to correct deficiencies and reduce or eliminate vulnerabilities in organizational systems.

CA.L2-3.12.2
Develop System Security Plans

Develop, document, and periodically update system security plans that describe the system boundaries, system operating environments, and how security requirements are implemented.

CA.L2-3.12.4

Showing representative practices — CA domain contains 4 total practices in NIST SP 800-171 r2.

SC

System & Communications Protection

16 practices
Monitor and Control Communications

Monitor, control, and protect communications (transmissions of CUI) at the external boundaries and key internal boundaries of organizational systems.

SC.L2-3.13.1
Implement Cryptographic Mechanisms

Implement cryptographic mechanisms to prevent unauthorized disclosure of CUI during transmission, unless otherwise protected by alternative physical safeguards.

SC.L2-3.13.8
Establish Cryptographic Key Management

Establish and manage cryptographic keys for required cryptography employed in organizational systems. Protect against both disclosure and modification of cryptographic keys.

SC.L2-3.13.10
Protect at Rest

Protect the authenticity of communications sessions. Implement cryptographic mechanisms to protect the integrity of information during transmission and at rest.

SC.L2-3.13.15

Showing representative practices — SC domain contains 16 total practices in NIST SP 800-171 r2.

SI

System & Information Integrity

7 practices
Identify and Correct Flaws

Identify, report, and correct information and information system flaws in a timely manner.

SI.L2-3.14.1
Provide Protection from Malicious Code

Provide protection from malicious code at appropriate locations within organizational information systems.

SI.L2-3.14.2
Monitor Systems for Security Alerts

Monitor organizational systems, including inbound and outbound communications traffic, to detect attacks and indicators of potential attacks.

SI.L2-3.14.6

Showing representative practices — SI domain contains 7 total practices in NIST SP 800-171 r2.

The Process

The CMMC Level 2 Assessment Process

Unlike Level 1, contracts which include levels of CUI require CMMC Level 2 or CMMC Level 3 assessments. Acquisition with higher sensitivity and risk require CMMC Level 2 or CMMC Level 3 formal third-party assessments led by a Cyber-AB an accredited Certified Third-Party Assessment Organization (C3PAO). Preparation is everything — organizations that go into the assessment without proper readiness risk costly delays and remediation cycles.

1

Gap Assessment & Readiness Review

Galaxy's RPs evaluate your environment against all 110 NIST SP 800-171 r2 practices, identify gaps, and deliver a prioritized remediation roadmap.

2

Remediation & Control Implementation

Implement required technical and administrative controls to close gaps — from MFA and encryption to access control policies and incident response plans.

3

Documentation — SSP & POA&M

Develop your System Security Plan (SSP), Policies and Procedures, and a Plan of Action & Milestones (POA&M) for any residual gaps accepted by the DoD.

4

SPRS Score Submission

Contractors must calculate and submit NIST SP 800-171 self-assessment scores to the Supplier Performance Risk System (SPRS). Submissions made in support of acquisitions with high sensitivity and risk levels will require a follow-on C3PAO assessment.

5

C3PAO Assessment

A Cyber-AB accredited C3PAO (Third-Party Assessment Organization) conducts the official assessment of your environment against all 110 practices.

6

Certification & eMASS Entry

Upon successful completion, your certification is recorded in the DoD's Enterprise Mission Assurance Support Service (eMASS). Level 2 certification is valid for 3 years.

How Galaxy Consulting Helps

As a CMMC RPO that has undergone a CMMC Level 2 certification, Galaxy Consulting brings direct, current experience to your Level 2 journey. Our Registered Practitioners guide you through gap assessment, control implementation, SSP and POA&M development, SPRS submission, and C3PAO assessment coordination — so you walk into your assessment fully prepared.

See Our CMMC Services

Understanding CUI

What is Controlled Unclassified Information (CUI)?

CUI is information the U.S. Government creates or possesses that requires safeguarding or dissemination controls pursuant to law, regulation, or government-wide policy — but is not classified.

The DoD uses CUI designations for technical data, engineering drawings, export-controlled information, sensitive acquisition information, proprietary business information, and much more.

If your contract includes a DFARS 252.204-7012 clause — Safeguarding Covered Defense Information — you are already legally obligated to protect CUI. CMMC Level 2 formalizes and verifies that obligation.

Common CUI Categories in Defense Contracting

Technical Data
Engineering drawings, specifications, and design information related to defense systems.
Export Controlled (EAR/ITAR)
Technology or data subject to Export Administration Regulations or International Traffic in Arms Regulations.
Acquisition & Procurement
Sensitive contract terms, cost and pricing data, source selection information.
Privacy / PII
Personally Identifiable Information pertaining to DoD personnel, contractors, or veterans.
Critical Infrastructure
Information related to the security or operation of critical defense infrastructure.
CMMC Level 2 Preparation

Ready to Start Your Level 2 Journey?

Galaxy Consulting offers a free initial consultation to assess your current CMMC Level 2 posture, identify critical gaps, and give you a clear roadmap to C3PAO assessment.