All posts

CMMC Level 2 Challenges for Small and Mid-Sized Defense Contractors

Chris Wolski · · 3 min read

CMMC Level 2 asks contractors that handle Controlled Unclassified Information (CUI) to implement the 110 security requirements of NIST SP 800-171 and, for most programs, to prove it through a third-party assessment. Large primes have teams for this. Small and mid-sized suppliers usually have an IT generalist and a few hundred employees' worth of risk.

The program's rollout timeline has shifted more than once, so check current Department of War and DFARS guidance for your contract. What has not changed is what an assessor needs to see. These are the challenges we encounter most.

Scope is bigger than you think, and smaller than you fear

Many contractors either scope too broadly (the entire company is "in scope," which multiplies cost) or too narrowly (a CUI enclave that quietly leaks into email, laptops or a file share). The fix is to follow the data:

  • Where does CUI enter the company?
  • Where is it stored, processed and transmitted?
  • Which people, systems and external service providers touch it?

A well-bounded enclave can dramatically reduce the assessed environment, but only if the boundary is real, documented and enforced.

The cloud question

Cloud services that store or process CUI must meet requirements for the environment, including FedRAMP Moderate or an equivalent authorization for the cloud service provider. Commercial office suites and file-sharing tools are frequent sticking points. Resolve this early, because migrating a mailbox is a project, not a setting.

Documentation that describes a company you are not

The System Security Plan (SSP) is the artifact assessors read first. Common problems:

  1. Templates filled in with aspirational statements ("we review logs regularly") that nobody can evidence
  2. Policies that do not match the actual procedures
  3. Missing inheritance statements for controls provided by a cloud or managed service provider

Write the SSP from what you really do. If a practice is not in place, that is a finding you can fix; an inaccurate statement is a credibility problem.

Evidence, not intent

Assessors test each requirement using NIST SP 800-171A objectives through interviews, document review and technical examination. For every practice, ask: what artifact shows this working? A screenshot of an MFA policy, an access review with a date and a signature, a vulnerability scan with remediation tickets, a training roster.

Evidence has a shelf life. An access review from eighteen months ago is not evidence of a current control.

Do not rely on the plan of action to rescue you

The rule allows limited Plans of Action and Milestones (POA&Ms) for a conditional status, subject to minimum scoring thresholds and a short closeout window, and some requirements cannot be deferred at all. Planning to "finish later" is a risky strategy. Treat the POA&M as an exception process, not a project plan.

Budget for people, not only products

Tools are visible. The ongoing cost is operational: patching, log review, access recertification, incident handling, annual affirmation. A realistic budget includes the time to run those processes, and a named owner for each.

A sensible path forward

  1. Determine your required level and contracts that carry it
  2. Define the CUI boundary and assets in scope
  3. Run a gap assessment against all 110 requirements with 800-171A objectives
  4. Remediate, prioritizing the weighted and non-deferrable items
  5. Finalize the SSP and evidence package
  6. Engage a C3PAO only when a mock assessment says you are ready

Smaller contractors can absolutely get there. The ones that do treat CMMC as an operating discipline, not an audit event.

Share LinkedIn X Email
How CMMC Compliance Strengthens Defense Against Threats
CMMCComplianceCritical Infrastructure

How CMMC Compliance Strengthens Defense Against Threats

In today's rapidly evolving digital landscape, ensuring the security of sensitive information is paramount, especially for companies working with the…

· Chris Wolski · 4 min read