CMMC gap assessment and mock assessment for defense contractors
A CMMC gap assessment is a valuable review of your environment against NIST SP 800-171, ending in a list of what falls short. You get an SPRS score. A mock assessment is also available to evaluate your readiness before the formal assessment.
Talk to a CMMC Advisor
Submit your details below to schedule your confidential 30-minute scoping review:
Who this is for
Defense contractors and subcontractors that handle CUI and need Level 2
Teams that submitted an SPRS score no one has independently checked
Companies whose policies and SSP came from several different sources
Contractors with an assessment date coming and no rehearsal yet
What you receive
110-Requirement Objective Findings
A finding for each of the 110 NIST SP 800-171 requirements, tied to the assessment objectives in NIST SP 800-171A
Official DoD SPRS Score
An SPRS score calculated with the DoD scoring method
Prioritized Remediation Fix List
A fix list ranked by point value, effort and owner
SSP & Evidence Reality Review
A review of your SSP and the evidence behind it
Advisory Walkthrough Debrief
A walkthrough call with the consultant who ran the assessment.
Sample findings
Complete visibility across every requirement.
| Requirement | What we found | Points at stake | Priority |
|---|---|---|---|
| 3.5.3 Multifactor authentication | Enforced for remote access, missing on local admin accounts | 5 | Fix first |
| 3.13.11 FIPS-validated cryptography | Encryption in use, module not FIPS-validated | 5 | Fix first |
| 3.11.2 Vulnerability scanning | Scans run, no record of remediation | 5 | Fix next |
| 3.6.3 Incident response testing | Plan written, never exercised | 1 | Schedule |
Why find gaps early
Know your real score
Your SPRS score is a self-reported number. A gap assessment tests against evidence, so what you submit holds up.
Fix what matters
Requirements carry 1, 3 or 5 points. The ranked list puts the heavy ones first, so each fix moves your score the furthest.
Rehearse before it counts.
A mock assessment introduces your team through the same interviews, and evidence requests an assessor will use. Nobody meets the format for the first time on the real day.
Plan the budget once.
You see the full scope of remediation up front, with owners and sequence, instead of finding it one by one.
How we assess
Four stages, one accountable team
Scope
We start with your contracts and the way CUI moves through the business. From that, we map the people, systems, and facilities in scope. A tight scope often removes whole sections of work, so this stage comes before any control review.
Review
We go through all 110 requirements using the three methods an assessor uses: examining documents and configurations, interviewing staff, and testing how systems behave. Each requirement is checked against its assessment objectives in NIST SP 800-171A, not just the headline text.
Score and rank
Every finding is scored with the DoD methodology, which gives your SPRS score. We then rank the fix list by points, effort, and dependency, so you can see what to do this month and what can wait
Walk through and rehearse
We take your team through the report thoroughly. If you choose the mock assessment, we run it the way a C3PAO would, with scheduled interviews, evidence requests and a closing readout of what held up and what didn't.
Pre-assessment and what comes after
CMMC pre assessment: Where this fits
A CMMC pre-assessment is the earliest checkpoint. It tells you whether your documents, scope, and score are close enough to justify remediation work, or whether the foundation needs to rebuild first. Many teams start here, then move to a full gap assessment once the scope is settled.
The mock assessment is the final stage in the preparation process. It comes after remediation, when you expect to pass, and it tests that expectation under assessor conditions. Used together, the two brackets for your preparation: one before you fix, one before you are assessed.
After the report
Once you have the fix list, remediation can run in three ways. Your own team can work through it; your IT provider can take the technical items, or Secure-Centric can manage the entire work. Whichever you choose, the report stays in your working document.
The final stage is crucial. Under the CMMC program rule, contractors can achieve Conditional Level 2 status with an assessment score of at least 88 out of 110. This is permitted when the remaining requirements are eligible for remediation under a Plan of Action and Milestones (POA&M).
Those items must be closed within 180 days, so the ranked list tells you which gaps can wait and which cannot (see the DoD’s published scoring guidance).
Gap assessment versus readiness assessment
| Gap assessment | Readiness assessment |
|---|---|
| Reviews every NIST SP 800-171 requirement | Judges how prepared you are for the official assessment |
| Ends in a ranked fix list and SPRS score | Ends in a verdict on whether to book the assessor |
| Best when you are starting remediation | Best when remediation is largely done |
| Can include a mock assessment as the final step | Often includes on-site interviews and evidence checks |
The two have more common than their names suggest, and the right approach depends on your specific requirements.
Not sure which applies to your business? Let’s discuss your scope and identify the right one for you.
Common gaps we find
Where NIST 800-171 compliance usually falls short
Most gaps fall into a few areas, and many carry the highest point values. Multifactor authentication is a frequent one: it is switched on for email and VPN, then missing on privileged and local accounts. Encryption comes next. Teams encrypt data in transit and at rest, but the cryptographic module isn’t FIPS-validated, which the requirement expects.
Documentation gaps can be just as damaging as technical deficiencies. An SSP must accurately reflect your actual operating environment, not an idealized version of it. Any inconsistency can quickly surface during assessor interviews. Incomplete scoping creates similar risks, especially when systems such as laptops, shared drives, or cloud applications that handle CUI are overlooked.
Then there are controls that exist on paper. Incident response plans that were never tested, audit logs that nobody reviews and vulnerability scans without tracked fixes all fit this pattern. An assessor asks for the evidence, and “we do this” isn’t enough without a record.
Finding these before an assessor does is the reason for a NIST 800-171 gap assessment, and it’s why we spend as much time with your team as with your configurations.
FAQs on CMMC gap assessment and mock assessment
Have specific questions regarding assessment timelines, SPRS formulas, or interview preparation? Speak with our accredited Registered Practitioners.
Identify compliance gaps early. Address them before your CMMC assessment.
Schedule a scoping call with an accredited Cyber AB Registered Provider Organization.