HistoryKey Facts
December 2017DFARS 252.204-7012 became effective requiring DoD contractors to comply with NIST SP 800-171. Compliance with 800-171 was achieved via contractor self-certification.

Self-certification was determined to be insufficient.
January 2020DoD published CMMC version 1.0.
September 2020DoD published interim rule, which implemented timeline for rollout of CMMC version 1.0 to DoD contractors,

Contractors with Controlled Unclassified Information (CUI) were also required to begin self-reporting compliance with NIST SP 800-171 in the DoD’s Supplier Performance Risk System (SPRS)
November 2021DoD announced CMMC version 2.0, suspending the rollout of CMMC requirement until final rules are published. Estimated timeline for final rulemaking will take 9 to 24 months.
December 2023DoD published CMMC version 2.0
December 2024Title 32 Rule goes into effect. CMMC Assessment can begin to occur but will not appear in DoD solicitations until the Title 48 Rule goes into effect.
Key Facts
CMMC 2.0 has three maturity levels (ML-1, ML-2, ML-3). The CMMC maturity level a contractor must comply will be specified in the DoD solicitation or RFI.
Under CMMC 2.0, the large majority of DoD contractors will be able to continue with self-certification. For these contractors, a senior company official will have to provide an annual affirmation that the company is complying with its maturity level’s CMMC cybersecurity requirements.

The DoD contractors that will have access to information that is deemed to be critical to national security will be required to undergo third-party assessments.
CMMC 2.0 now allows for Plan of Action and Milestones (POAMs) in certain cases.
The DoD is considering providing incentives for contractors who voluntarily obtain a CMMC certification in the interim period.

The DoD is phasing in the implementation of the CMMC program:

PhaseTimingSolicitation/Contract Requirements
Phase 1Begins at Title 48 effective dateLevel 1 or 2 Self-Assessment
Phase 2Begins 12 months after Phase 1 startLevel 2 third-party certification
Phase 3begins 24 months after the phase 1 startLevel 3 third-party certification
Phase 4Begins 36 hours after the Phase 1 startAll solicitations/contracts have CMMC Level requirements

CMMC Maturity Levels
The CMMC framework has three maturity levels (ML). ML-1 is the least rigorous, ML-3 the most. The maturity level and assessment requirements are based on the sensitivity of the information shared with the contractor. Contractors who only have access to Federal Contract Information (FCI) will be ML-1. Contractors who have access to Controlled Unclassified Information (CUI) will be ML-2 or ML-3. Contracts that have CUI that the DoD deems not to be critical to national security will be ML-2 and might only require the contractor to annually self-certify compliance with CMMC 2.0.
Read more about FCI and CUI here

Maturity Level 1 | Foundational
17 practices
Requires contractor to annually perform self-assessment
Maturity Level 2 | Advanced
110+ practices aligned with NIST SP 800-171
For contracts with critical national security information, requires contractor obtain triennial third-party assessment
For contracts with CUI that is not deemed critical to national security, contractor to perform annual self-assessments
Maturity Level 3 | Expert
110+ practices based on NIST SP 800-172
Requires contractor to obtain triennial government-led assessments

 

DoD contractors need to ensure they are prepared to meet the cybersecurity requirements for their CMMC Maturity Level.

DoD contractors first need to determine the CMMC Maturity Level with which they need to comply. Contractors should review their current contracts and speak with their contracting officers, contracting officer’s technical representative (COTR), or other DoD representative to determine the sensitivity of the information (CUI vs FCI) the government considers the contractor to have.

Once the Maturity Level is determined, contractors should perform an assessment to determine if there are any CMMC requirements that it is not meeting for their specific Maturity Level. If gaps are identified, the contractor needs to implement corrective actions to resolve the gaps.

Additionally, if not already performed, DoD contractors with CUI need to perform a self-assessment against NIST SP 800-171 and self-report in the DoD Supplier Performance Risk System (SPRS).

Keiter is a Registered Practitioner Organization (RPO) in the CMMC Marketplace.

Many DoD contractors will need assistance in getting ready for their self- and/or third-party assessments, to include identifying controls, identifying gaps, and developing plan of action and milestones (POA&Ms). Keiter’s Risk Advisory Services team has been providing cybersecurity services and consulting on the major IT frameworks such as NIST SP 800-171, NIST SP 800-53, HIPAA, and others for close to 20 years. As CMMC RPO, our team can help DoD prime and subcontractors with the following:

  • Readiness Assessments and Gap Analyses against the CMMC Framework
  • Assistance with Remediating Gaps Identified during Readiness Assessment
  • Assistance with NIST SIP 800-171 Self-Assessment that is recorded in Supplier Performance Risk System

CMMC RPO

Below is our full collection of articles about the CMMC Level 1 Practices. In these articles we dive into the CMMC Practice Guides and provide our thoughts about the practices and what contractors should consider. The CMMC ecosystem is still developing, and as those developments occur, we will update these articles accordingly. As such, we hope that these articles represent an evergreen CMMC resource.

AC.L1

  • (AC.L1-3.1.1) Limit information system access to authorized users, processes acting on behalf of authorized users, or devices (including other information systems).
  • (AC.L1-3.1.2) Limit information system access to the types of transactions and functions that authorized users are permitted to execute.
  • (AC.L1-3.1.20) Verify and control/limit connections to and use of external information systems.
  • (AC.L1-3.1.22) Control information posted or processed on publicly accessible information systems.
  • (IA.L1-3.5.1) Identify information system users, processes acting on behalf of users, or devices.

IA.L1

  • (IA.L1-3.5.2) Authenticate (or verify) the identities of those users, processes, or devices, as a prerequisite to allowing access to organizational information systems.

MP.L1

  • (MP.L1-3.8.3) Sanitize or destroy information system media containing Federal Contract Information [or Controlled Unclassified Information] before disposal or release for reuse.

PE.L1

  • (PE.L1-3.10.1) Limit physical access to organizational information systems, equipment, and the respective operating environments to authorized individuals.
  • (PE.L1-3.10.3) Escort visitors and monitor visitor activity.
  • (PE.L1-3.10.4) Maintain audit logs of physical access.
  • (PE.L1-3.10.5) Control and manage physical access devices.

SC.L1

  • (SC.L1-3.13.1) Monitor, control, and protect organizational communications (i.e., information transmitted or received by organizational information systems) at the external boundaries and key internal boundaries of the information systems.
  • (SC.L1-3.13.5) Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks.

SI.L1

  • (SI.L1-3.14.1) Identify, report, and correct information and information system flaws in a timely manner.
  • (SI.L1-3.14.2) Provide protection from malicious code at appropriate locations within organizational information systems.
  • (SI.L1-3.14.4) Update malicious code protection mechanisms when new releases are available.
  • (SI.L1-3.14.5) Perform periodic scans of the information system and real-time scans of files from external sources as files are downloaded, opened, or executed.

Protect Your Small to Mid-size Business Safe From Cyber Attacks

CMMC Service Areas

Scoping

  • Assist with determining the CMMC level based on current contractual obligations.
  • Identify enclave boundaries and in-scope assets
  • Document asset applicability for each practice

Scoping is the first step. Get started with a with a scoping exercise.

Gap Analysis

  • Document practice implementations for each in-scope asset
  • Identify gaps
  • Gaps are unimplemented CMMC practice requirements or assessment objectives not implemented and/or with insufficient evidence
  • Document Plan of Action and Milestones (POA&Ms)

Documentation

  • For each practice and in-scope system, document CMMC practice owners, practice operators, evidence description, and evidence location.
  • Document your System Security Plan (SSP).
  • Calculate your CMMC and DFARS scoring.
  • As required, create or update policies, procedures, plans, diagrams, practice documentation templates and more.
Keiter Service Areas Infographic Scoping, Gap Analysis, Documentation, Assessment Prep, Assessment Support, Ongoing Project Support and Compliance Maintenance Activities Technology Implementation, Policy and Procedure Implementation, OSC C3PAO

Assessment Preparation

  • Review and organize initial body of evidence. Obtain final approvals on all documentation from management.
  • Ensure staff understand the overall CMMC regulatory landscape and the importance of compliance, are trained on critical organization policies and procedures, and understand expectations regarding the assessment process.

 

Assessment Support

  • Gather the body of evidence to support self-certifications and affirmations.
  • Coordinate with assessor regarding interview requests, gathering assessment documentation, participating in assessment interviews/walkthroughs, responding to and addressing assessor questions/concerns.

 

Ongoing Project Support and Compliance Maintenance Activities

  • Even the simplest organizations will have THOUSANDS of individual requirements.
  • Success requires a data driven approach during the readiness and throughout the process of maintaining compliance.
CMMC RPO Keiter

Test Drive Our CMMC Compliance Tool

All CMMC efforts should start with a scoping exercise.

Scoping has one key goal: to define your secure enclave. Your enclave defines your CMMC compliance footprint and is ultimately what is subject to assessment by a Certified Third-Party Assessor Organization (C3PAO).

The larger or more complex your enclave, the greater costs you will incur.
Accordingly, we approach scoping with an eye for compliance as well as opportunities to shrink your enclave.


en·​clave – än-klāv : A set of system resources that operate in the same security
domain and that share the protection of a single, common, continuous security perimeter. – NIST

Prior to scoping, organizations should already have a target CMMC Maturity Level. Most organizations will start at either:

  • Level 1 – You only handle Federal Contract Information (FCI)
  • Level 2 – You handle Controlled Unclassified Information (CUI) and FCI

Determining your target maturity level is a management decision based upon:

  • Contract Analysis: Whether existing contracts contain DFARS 252.204-7012 or flow down requirements.
  • Discussions: With contracting officers, contracting officer technical representatives, program managers, etc. to determine the type of data.
  • Corporate Strategic Goals: Whether you want to be able to bid on only Level 1 or Level 1 and Level 2 contracts in the future.

We can assist in this process upon request.

Meet with stakeholders, review documentation (network diagrams, data flow diagrams, architecture documents, and more) to identify the assets in your assessment scope.

The CMMC Level 1 and Level 2 Scoping Guides together identify six Asset Categories: FCI Assets, CUI Assets, Security Protection Assets (SPA), Contractor Risk Managed (CRM) Assets, Specialized Assets, and Out-of-Scope Assets.

However, there are other ‘things’ that fall within the assessment scope. Namely people and facilities. For example, CMMC Awareness and Training (AT) practices require security awareness training delivered to people, and Physical Protection (PE) requires security in facilities.

Additionally, some of your assets may involve third parties with their own compliance requirements, such as cloud service providers (CSP) or other external service providers (ESP), like managed IT services.

In this step, we work with your team to identify your in-scope assets and classify them into an appropriate asset type. This is the foundation of the remainder of your scoping exercise.

Work with stakeholders to identify opportunities to minimize your scope.

CMMC Assessment Scope Before and After

Document asset applicability for each CMMC Practice.

 

Based on what we’ve learned by working with your team, we will document asset applicability conclusions for each in-scope asset for each practice. For any practice that does not apply to a particular practice, we will document the rationale. For example, requirements to escort visitors does not apply to a CUI processing engineering system.

Powered by our CMMC Compliance Tool

All scoping documentation is entered into our internally developed CMMC Compliance Tool – which is yours forever as a benefit of retaining us for any CMMC related service.

Even the simplest organizations will have THOUSANDS of CMMC compliance data points. To attempt to comply in any other than a data driven manner invites waste and error.

The tool is easily maintained in your own environment. It is your security data, and we believe you should have the right to keep it in your environment, forever.

From scoping to the creation of your SSP, the CMMC Compliance Tool tracks thousands of requirements, scoping decisions, and internal assignment of responsibility, evidence location, related status, and more.

List of Practices:

Below is our full collection of articles about the CMMC Practices. In these articles we dive in to the CMMC Practice Guides and provide our thoughts about the practices and what contractors should consider. The CMMC ecosystem is still developing, and as those developments occur, we will update these articles accordingly. As such, we hope that these articles represent an evergreen CMMC resource.

AC.L1

  • (AC.L1-3.1.1) Limit information system access to authorized users, processes acting on behalf of authorized users, or devices (including other information systems).
  • (AC.L1-3.1.2) Limit information system access to the types of transactions and functions that authorized users are permitted to execute.
  • (AC.L1-3.1.20) Verify and control/limit connections to and use of external information systems.
  • (AC.L1-3.1.22) Control information posted or processed on publicly accessible information systems.
  • (IA.L1-3.5.1) Identify information system users, processes acting on behalf of users, or devices.

IA.L1

  • (IA.L1-3.5.2) Authenticate (or verify) the identities of those users, processes, or devices, as a prerequisite to allowing access to organizational information systems.

MP.L1

  • (MP.L1-3.8.3) Sanitize or destroy information system media containing Federal Contract Information [or Controlled Unclassified Information] before disposal or release for reuse.

PE.L1

  • (PE.L1-3.10.1) Limit physical access to organizational information systems, equipment, and the respective operating environments to authorized individuals.
  • (PE.L1-3.10.3) Escort visitors and monitor visitor activity.
  • (PE.L1-3.10.4) Maintain audit logs of physical access.
  • (PE.L1-3.10.5) Control and manage physical access devices.

SC.L1

  • (SC.L1-3.13.1) Monitor, control, and protect organizational communications (i.e., information transmitted or received by organizational information systems) at the external boundaries and key internal boundaries of the information systems.
  • (SC.L1-3.13.5) Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks.

SI.L1

  • (SI.L1-3.14.1) Identify, report, and correct information and information system flaws in a timely manner.
  • (SI.L1-3.14.2) Provide protection from malicious code at appropriate locations within organizational information systems.
  • (SI.L1-3.14.4) Update malicious code protection mechanisms when new releases are available.
  • (SI.L1-3.14.5) Perform periodic scans of the information system and real-time scans of files from external sources as files are downloaded, opened, or executed.

Protecting Your Business from Identity Theft This 2025–2026 Tax Season

Keiter Technologies: DoW Releases Revised CMMC FAQs

Mitigating Data Breach Risks: Insights for Business Leaders

View All CMMC Insights

Your Opportunity Advisors

Scott McAuliffe

Risk Advisory Services Partner

Chris Moschella

Risk Advisory Services Senior Manager

Contact Us