CMMC 2.0 Assessment Outline

Your IT Provider Can’t Handle a CMMC Assessment. Here’s What to Do About It

Many construction firms manage their technology through a part-time IT resource, a break-fix vendor they call when something stops working, or a managed services provider that handles their servers and email. Those arrangements work for routine IT support. They do not work for a CMMC assessment, and conflating the two is an increasingly expensive mistake as enforcement tightens.

CMMC Level 2 compliance is a fundamentally different kind of undertaking than keeping your network running and your computers patched. It requires formal documentation of your environment, evidence that specific controls are implemented and operating, a System Security Plan that survives scrutiny from a Certified Third-Party Assessment Organization, and in many cases a remediation program that spans months. The IT resource who has been with your firm for years and knows your systems well is not disqualified from participating in that work, but they cannot lead it, and treating general IT competence as equivalent to CMMC readiness will produce an assessment failure that costs significantly more than the preparation would have.

This post explains what CMMC assessment actually involves, why it is a different discipline from routine IT management, and what the right division of responsibility looks like. If you are managing construction projects for the Department of Defense or managing a firm that pursues federal contracts, CMMC compliance is no longer optional, and the time to start preparation is before the clock is running.


What a CMMC Level 2 Assessment Actually Involves

A CMMC Level 2 assessment is a formal third-party audit conducted by a Certified Third-Party Assessment Organization (C3PAO) authorized by the Cyber AB. It is not a questionnaire you fill out and submit. It is an assessment in which an authorized team evaluates your environment against 110 security requirements across 14 practice domains, based on NIST SP 800-171 controls.

The assessors look for three things: documentation (do you have written policies, procedures, and a System Security Plan that describe how you implement each control?), evidence (do your logs, configurations, and records demonstrate that controls are operating as intended?), and consistency (is the actual state of your environment consistent with what your documentation describes?). A mismatch between what you claim in writing and what the assessors find when they examine your systems is a deficiency. Deficiencies pile up, and if you have enough of them, you fail the assessment.

The assessment produces a score. A perfect score is 110 points. Organizations that fall below the threshold defined in their contract or solicitation have a defined period to remediate and be reassessed. Failing an assessment does not automatically disqualify you from all DoD work, but it does create compliance exposure and affects your ability to bid on contracts that require demonstration of current compliance.

What CMMC Level 2 Assessment Requires
  • A complete System Security Plan (SSP) documenting your environment and all 110 security requirements
  • A Plan of Action and Milestones (POA&M) for any requirements not yet fully implemented
  • Evidence packages for each control, logs, screenshots, configuration exports, training records, policy documents
  • Assessment by a C3PAO authorized by the Cyber AB, not a self-assessment for most DoD prime contract requirements
  • Ongoing compliance maintenance. CMMC is not a one-time project

Why General IT Competence Is Not the Same as CMMC Readiness

A skilled IT generalist can implement many of the technical controls CMMC Level 2 requires: multi-factor authentication, endpoint protection, patch management, backup and recovery. What they typically cannot do is produce the documentation framework that an assessment requires, scope the CUI boundary correctly, build the System Security Plan in the format assessors expect, or lead the evidence collection and organizational preparation that a C3PAO audit demands.

CMMC compliance is as much a documentation and program management exercise as it is a technical one. The gap most firms have is not that their technology is bad. It is that their technology is not documented, their policies are not written, their procedures are not formalized, and their evidence does not exist in a form that survives audit. An assessor can walk into your environment, find that you have MFA implemented and your servers are patched, and still find you non-compliant if you cannot produce written policy that describes how MFA is enforced, logs that prove it is operating, and procedures that define your process for managing MFA across the organization.

General IT Management CMMC-Capable Managed Services
Scope Keep systems running and patched Implement and document controls against 110 requirements
Output Working infrastructure Working infrastructure plus SSP, POA&M, and evidence packages
Assessment Readiness Not addressed Ongoing assessment readiness maintenance
Policy and Procedure Work Not typically in scope Policy development and review included
CUI Scoping Not addressed Formal CUI boundary determination
Ongoing Compliance Not typically in scope Continuous monitoring and compliance maintenance

What a C3PAO Is and What the Assessment Looks Like

A C3PAO (Certified Third-Party Assessment Organization) is an organization authorized by the Cyber AB (the Cyber AB is the accreditation body responsible for CMMC oversight) to conduct official CMMC Level 2 assessments. Not every IT firm or cybersecurity company can conduct CMMC assessments. Only C3PAOs listed in the official Cyber AB marketplace are authorized to conduct assessments that satisfy DoD contract requirements.

The assessment process typically unfolds over several weeks. It begins with a kickoff meeting to establish scope, logistics, and expectations. The C3PAO team then reviews your documentation (your System Security Plan, policies, procedures, and POA&M) to understand your claimed control posture. Next comes technical testing: the assessors examine system configurations, review logs, run vulnerability scans in some cases, and verify that technical controls are actually operating as documented. The assessment also includes interviews with key personnel (IT staff, managers responsible for specific controls, executives). Finally, the assessors produce a report that scores your environment against all 110 requirements and identifies any deficiencies.

The role of your managed IT or cybersecurity provider is to prepare you for the assessment, not to conduct it. A compliance-capable MSP implements the technical controls, builds the documentation, collects evidence, and coordinates the organizational preparation. The C3PAO then comes in as an independent third party to assess and validate.

The C3PAO assesses your environment. Your IT provider prepares it. Confusing those two roles is one of the most common reasons firms enter assessment under-prepared.


What CMMC Readiness Work Actually Looks Like

CMMC readiness is not a single project. It is a structured program with distinct phases. Here is what the work actually entails:

  • Phase 1. Scoping: Determine what systems, people, and locations process, store, or transmit Controlled Unclassified Information (CUI). This is harder than it sounds, email, file shares, project management platforms, laptops that travel to job sites, collaboration tools, and cloud services all need to be evaluated for CUI exposure.
  • Phase 2. Gap assessment: Score your current environment against all 110 NIST SP 800-171 requirements. Identify what is in place, what is partially in place, and what is missing. The gap assessment drives the remediation plan and helps you understand the work ahead.
  • Phase 3. Remediation: Implement missing technical controls, write missing policies, build the SSP, develop the POA&M for any items that require longer timelines, and systematically collect evidence for every control that is in place.
  • Phase 4. Pre-assessment review: A mock or readiness review conducted before the official C3PAO assessment to identify any remaining gaps, verify the evidence packages are complete and organized, and ensure your organization is ready for the formal audit.
  • Phase 5. C3PAO assessment: The official third-party assessment. Your role is to provide evidence and answer questions. Your IT provider’s role is to have prepared you so thoroughly that the assessment confirms what your documentation already says.
What a Compliance-Capable MSP Delivers Throughout This Process
  • CUI boundary scoping and documentation
  • System Security Plan (SSP) development and maintenance
  • Gap assessment against all 110 NIST SP 800-171 requirements
  • Technical control implementation (MFA, EDR, logging, patch management, backup)
  • Policy and procedure development
  • Evidence collection and organization
  • POA&M management and remediation tracking
  • Pre-assessment readiness review
  • Ongoing compliance maintenance between assessments

The Timing Question

The contractors in the best position for CMMC compliance are the ones who started the work before a contract required it. The contractors in the most difficult position are the ones who won a DoD contract, discovered they need to demonstrate compliance within 180 days, and are now attempting to complete 6-12 months of preparation work in compressed time, during the busiest periods of the year on their active projects.

Starting CMMC readiness work before you have an active requirement gives you time to make decisions carefully, address gaps in the right order, and build documentation that reflects how your environment actually works, not documentation that was assembled in a hurry to satisfy an audit. It also means you are not under pressure to skip steps, cut corners, or pay premium rates for accelerated services.

VQIS works with Sacramento-area construction firms on CMMC readiness before they need it and alongside them when they do. The work is the same either way; the timeline and the pressure are very different. The firms that succeed are the ones that start early, not the ones that wait until compliance becomes a contract requirement.


What This Means for Sacramento-Area Contractors Pursuing Federal Work

The question is not whether your IT is good enough for CMMC. It is whether your environment is documented, your controls are evidenced, and your organization has the program management infrastructure to sustain compliance over time. Those are different questions with different answers, and a general IT provider who has kept your network running well for years is not the right resource to answer them on their own.

The division of responsibility that works: a compliance-capable managed IT provider handles implementation, documentation, and preparation. A C3PAO conducts the independent assessment. Neither one does the other’s job.

If you are pursuing DoD contracts or working on a federal project that involves CUI, the time to start this work is before the contract requires it, not after.

Start Your CMMC Readiness Work Before the Clock Is Running

We help Sacramento-area construction firms scope their CUI environment, close the gaps in their NIST SP 800-171 controls, and build the documentation that CMMC assessment requires.

Contact Us
Scroll to Top