A CMMC compliance checklist for a small defense supplier starts by finding out whether you hold FCI or CUI and ends with a yearly affirmation in SPRS. The steps in between come from FAR and DFARS clauses.
Our guide to CMMC requirements for small business covers whether these rules reach your company at all. This page picks up from there. We wrote it for the rules in force since July 2026, when DoD suspended the move to CMMC Phase 2, and it’s easiest to use with one of your contracts open.
New to CMMC? Our post on where to start with CMMC gives the background. Keep in mind that a checklist is readiness work. It doesn’t certify a company, and the cluster doesn’t either.
The eight steps at a glance
- Find out, in writing, whether you hold FCI, CUI or both.
- List the cyber clauses in each contract and subcontract.
- Draw the scope: every system and person that touches that information.
- Meet the 15 basic safeguarding requirements.
- Holding CUI? Meet NIST SP 800-171’s 110 requirements as well.
- Write the system security plan, plus a plan of action for open gaps.
- Self-assess and post the results in SPRS.
- Have your affirming official affirm, then do it again every year.

Steps 1 to 3: the information, the clauses, the scope
In CMMC, scope means the information systems that process, store or transmit Federal Contract Information or Controlled Unclassified Information for a contract. DFARS 252.204-7021 applies the required CMMC status to those systems, so a short, written scope keeps the rest of the checklist manageable.
For step 1, ask whoever sent the work, usually the prime or the contracting officer, whether the work for this contract includes FCI, CUI or both. Get the answer in writing. If a document carries a marking, look the category up in the National Archives CUI Registry. Step 2 is reading each contract and subcontract for these clauses:
- FAR 52.204-21, the basic safeguarding clause behind Level 1
- DFARS 252.204-7012, for CUI and cyber incident reporting
- 252.204-7019 or 7020? Those ask for a NIST SP 800-171 assessment score.
- And 252.204-7021, which names the CMMC level itself.
Step 3 is a list of every laptop, server, cloud account and employee that handles that information. Anything left off the list stays away from FCI and CUI.
Steps 4 to 6: meet the requirements, then write them down
Level 1 is the shorter list. FAR 52.204-21 sets out 15 basic safeguarding requirements, starting with limiting system access to authorized users and ending with periodic scans of the system and real-time scans of files from outside sources. A company that only receives FCI finishes at step 4.
CUI brings in Level 2. It’s built on NIST SP 800-171 Rev. 2 and its 110 requirements in 14 families, and two of those requirements produce documents you’ll keep:
- Requirement 3.12.4, a system security plan: your boundary, your environment, how each requirement gets met.
- 3.12.2, plans of action for anything still deficient. Most people just say POA&M.
As of November 2026, buyers can only ask for Level 1 (Self) or Level 2 (Self). That limit comes from the July 13, 2026 memo, which DoD’s class deviation 2026-O0025, Revision 3 passes to contracting officers. The deviation also keeps the NIST SP 800-171 Rev 2 baseline under DFARS 252.204-7012. Our post on what is still required while Phase 2 is paused covers how that plays out for small suppliers.


Steps 7 and 8: post the results, then affirm every year
Step 7 happens in SPRS, the Supplier Performance Risk System. DFARS 252.204-7021 has you enter a current self-assessment there for each CMMC unique identifier. If your contract also includes DFARS 252.204-7019, SPRS also needs a NIST SP 800-171 Basic Assessment score that’s no more than 3 years old, unless the solicitation asks for a newer one. Check both entries.
Step 8 is the affirmation. The person your company names as its affirming official affirms continuous compliance once a year. It’s a formal statement to the government.
After you affirm
Two duties continue after that. DFARS 252.204-7012 requires you to report a cyber incident within 72 hours of discovering it. If you pass FCI or CUI to a subcontractor of your own, DFARS 252.204-7021 has you confirm that the subcontractor holds a current CMMC status at the right level before you award the subcontract.
The SoCal Defense Innovation Cluster helps with readiness. Members can get guidance, gap assessments and referrals to qualified assessors. Formal CMMC certification requires a third-party assessment organization, and when a referral involves outside fees, those fees are charged by that provider directly, not by the cluster.
The full CMMC compliance checklist, with the records to keep
You can print the table or keep it open next to your contracts. We checked every rule in the third column against its official source on November 18, 2026, which is the date to compare against if DoD issues a new deviation or amends one of these clauses later.
| Step | What to do | The rule behind it | Record to keep |
|---|---|---|---|
| 1 | Ask the prime or contracting officer whether you’ll receive FCI, CUI or both; check markings against the CUI Registry | The FCI and CUI definitions in DFARS 252.204-7021 | The written answer, filed with the contract |
| 2 | List the cyber clauses in every contract and subcontract | FAR 52.204-21; DFARS 252.204-7012, 7019, 7020 and 7021 | A clause list per contract, with the CMMC level it names |
| 3 | Name every system, account and person that touches FCI or CUI | DFARS 252.204-7021 | An asset list and a simple network diagram |
| 4 | Meet the basic safeguarding requirements | FAR 52.204-21(b)(1), 15 requirements | Evidence for each one: settings, access lists, scan logs |
| 5 | If you hold CUI, meet the security requirements | NIST SP 800-171 Rev 2, 110 requirements | A self-assessment worksheet, requirement by requirement |
| 6 | Write down how you meet them and how you’ll close the gaps | NIST SP 800-171 Rev 2, 3.12.4 and 3.12.2 | A system security plan and a POA&M |
| 7 | Self-assess and post the results | DFARS 252.204-7021 and 252.204-7019 | Your SPRS entries, with dates and the score |
| 8 | Affirm continuous compliance, every year | DFARS 252.204-7021 | The affirmation and the name of your affirming official |
Four clocks the checklist runs on
They run from shortest to longest. Each one is set by a clause.
3 years
Most a Basic Assessment score in SPRS may age, unless a solicitation sets less
Source: DFARS 252.204-7019
Sources checked November 18, 2026. Under 7021, a change in your compliance after the assessment date means the status is no longer current.
More CMMC guides from the cluster
CMMC requirements by situation
Which CMMC rules apply to you, sorted by the information you hold, in our CMMC requirements guide.
Where to start with CMMC
Background on what CMMC is, how the levels work and what to do first, in our CMMC starter post.
SPRS scores and affirmations
How your SPRS score and annual affirmation differ, and why each one needs to stay accurate.
CMMC & Compliance Readiness
Members get readiness guidance, a gap assessment and referrals to qualified CMMC assessors through this cluster service.
More from the resource library
- Reference documents library, with the DoD CMMC overview, NIST SP 800-171 and DFARS 7012
- Useful websites and tools for registration, contracting and compliance
What suppliers ask while working a CMMC compliance checklist
What should we keep on file for each step?
Keep the items in the table’s last column: the written FCI or CUI answer, your clause list, your asset list, evidence for each requirement, the SSP, the POA&M and your SPRS entries. Date each one.
Your affirming official relies on these records when signing.
Can we affirm if a few NIST requirements still aren’t met?
Short answer: be careful, because an affirmation states that you comply, while open gaps belong in your POA&M.
DFARS 252.204-7021 does define a Conditional Level 2 status that stays current for up to 180 days. Whether a contract accepts it depends on the solicitation and 32 CFR part 170. Check with the contracting officer first.
Is the SPRS score the same thing as the affirmation?
No, they’re separate entries. A Basic Assessment score shows how many NIST SP 800-171 requirements you’ve implemented, and the affirmation is a yearly statement that you still comply.
Our post on SPRS scores and affirmations during the pause explains both.
Does the checklist change for a subcontractor?
The steps are the same, but the requirement comes to you through your prime instead of directly from DoD.
Under DFARS 252.204-7021, the prime flows the CMMC level down and checks your status before awarding the subcontract. For step 2, read your subcontract. The prime’s own contract won’t show what applies to you. Ask for a copy.
How much does it cost to work through a CMMC compliance checklist?
There isn’t one figure we can honestly give. Cost depends on how many laptops, servers and cloud accounts are in scope, how many of the requirements you already meet today, and whether you handle CUI at all or only FCI.
Step 3 is where you have the most control. Start there. If a contract requires a third-party assessor, the assessor sets its own fees.
How often does the checklist have to be run again?
At least once a year, because the affirmation is annual. Under DFARS 252.204-7021, a Level 1 self-assessment stays current for 1 year and a Level 2 assessment for 3 years, as long as your compliance hasn’t changed.
Moving CUI to new laptops or a new cloud service is a reason to review the checklist. So is a new contract.
Work through the checklist with the cluster
Membership and cluster-funded services are provided at no cost to eligible participating businesses, subject to program requirements and available resources.
