CMMC Checklist for Small Defense Suppliers
A step-by-step CMMC checklist for small defense suppliers: what data you handle, how to shrink scope, Level 1 and 2 basics, SPRS, and where Phase 2 stands.
The email usually shows up on a Tuesday afternoon. A prime contractor you've supplied parts to for years wants your SPRS score, your CMMC level, and a contact for "cybersecurity compliance." You forward it to whoever handles IT, and the question comes back: where do we even start? If you're looking for a practical CMMC checklist for small business owners and IT managers, this is it.
I wrote this for small defense suppliers: machine shops, fabricators, electronics assemblers and service firms with somewhere between 10 and 500 people. You probably don't have a compliance department. You have a few people who wear a lot of hats, and you need to know what to do in what order.
My partner Mukesh has spent 25 years in cybersecurity, and I've spent 15 years building and running networks. The checklist below is the order we'd work through it ourselves. It's practical guidance, not legal advice, so confirm the details for your contracts with your attorney or a certified assessor.
In this guide
- Where CMMC stands right now
- Step 1: Find out what data you actually handle
- Step 2: Draw a tight boundary around it
- Step 3: Work the Level 1 checklist
- Step 4: Work the Level 2 checklist
- Step 5: Get the paperwork and SPRS right
- Step 6: Check your vendors, cloud and MSP
- Frequently asked questions
Where CMMC stands right now
CMMC has had a bumpy year, so here's the short version as of early November 2026. The CMMC program rule (32 CFR Part 170) is in effect, and Phase 1 began in November 2025. Phase 1 means CMMC self-assessments can show up as a requirement in DoD contracts.
Phase 2 was scheduled for November 10, 2026. That's when third-party (C3PAO) Level 2 certification would have started becoming a condition of award for many contracts involving Controlled Unclassified Information (CUI). On July 13, 2026, the Department of War suspended Phase 2 and set up a CMMC Reform Task Force to review the program. As I write this, no new Phase 2 date has been announced.
Here's the part people miss: the pause did not remove your obligations. If your contracts include DFARS 252.204-7012, you still have to protect CUI using NIST SP 800-171. If they include FAR 52.204-21, the basic safeguarding rules still apply. Self-assessments and SPRS postings are still expected where your contracts call for them, and the Department of Justice has kept pursuing False Claims Act cases over cybersecurity gaps. The program can change quickly, so check the current status with your attorney or assessor before you make big decisions.
My practical advice: treat the pause as extra time, not a reprieve. The work below is the same whether a C3PAO checks it next year or you self-assess it this year.
Step 1: Find out what data you actually handle
Everything in CMMC hangs on one question: what kind of government information touches your systems? Get this wrong and you'll either overspend or under-protect.
FCI vs. CUI in plain terms
- Federal Contract Information (FCI) is information provided by or generated for the government under a contract that isn't meant for public release. Think purchase orders, delivery schedules and contract details. If you have a DoD contract, you almost certainly have FCI.
- Controlled Unclassified Information (CUI) is information that a law, regulation or government policy says must be safeguarded. For manufacturers, it's often technical drawings, specifications or export-controlled data. It's frequently marked, but not always cleanly.
FCI points you to Level 1. CUI points you to Level 2. I walk through this decision in more detail in CMMC Level 1 vs. Level 2: Which One Does Your Manufacturing Shop Need?
Your Step 1 checklist
- Pull your active DoD contracts and subcontracts and search them for "252.204-7012", "252.204-7019", "252.204-7021" and "52.204-21".
- Ask your prime directly: "Will you be sending us CUI, and what CMMC level will you flow down?" Get the answer in writing.
- Look at the drawings and files you've received in the last year. Note any CUI markings, distribution statements or export-control notices.
- Write down every place that information lands: email inboxes, a shared drive, the CAM workstation, a USB stick on the shop floor, someone's phone.
That last item is the one that surprises people. CUI rarely stays in one folder.
Step 2: Draw a tight boundary around it
Once you know where the data goes, the smartest move most small shops can make is to shrink the area that has to meet the rules. CMMC assesses the systems that store, process or transmit the covered data, plus the systems that protect them. The smaller that footprint, the cheaper and easier compliance becomes.
Ways small suppliers commonly reduce scope
- Create an enclave. Put CUI work on a separate set of machines, user accounts and storage, often a dedicated cloud environment, so the rest of the business stays out of scope.
- Limit who touches it. If only engineering and quality need the drawings, the front office and shipping shouldn't have access.
- Segment the network. Keep CUI systems on their own network segment, away from guest Wi-Fi and general office traffic.
- Handle shop-floor machines carefully. CNC controllers and other equipment that receive CUI files need a plan too. Our post on securing shop-floor (OT) networks without stopping production covers how to do that without breaking anything.
Your Step 2 checklist
- Draw a simple network diagram showing where CUI (or FCI) lives and how it moves.
- List every in-scope asset: servers, laptops, cloud services, firewalls, printers and machines.
- Decide whether an enclave makes sense before you start fixing controls everywhere.
- Document the boundary. An assessor will ask how you decided what's in and out.
Step 3: Work the Level 1 checklist
If you only handle FCI, Level 1 is your target. It covers 15 basic safeguarding requirements from FAR 52.204-21, and you self-assess every year. It's a manageable project for most small shops, but every requirement must be fully met. Level 1 doesn't allow a plan to finish things later.
Here's what those requirements look like in practice:
- Access control: only authorized people and devices get in, and people only reach what their job needs. Control and verify any connections to outside systems, and keep nonpublic information off your public website.
- Identification and authentication: every user has a unique login, and you verify identities before granting access. No shared "shop" or "frontdesk" accounts.
- Media protection: wipe or destroy drives, laptops and USB sticks that held FCI before you dispose of or reuse them.
- Physical protection: limit physical access to systems, escort visitors, keep visitor logs and control keys, badges and codes.
- System and communications protection: use a firewall to monitor and control traffic at your network edge, and separate publicly accessible systems from your internal network.
- System and information integrity: patch promptly, run up-to-date malware protection, and scan files and systems regularly.
Your Step 3 checklist
- Walk through each of the 15 requirements and mark it met or not met, with evidence.
- Fix gaps first: shared accounts, missing patches and old firewalls are the usual suspects.
- Have a senior official review the results and affirm them in SPRS.
- Put the next annual self-assessment on the calendar now.
Many of these basics overlap with good security for any business. Our 10 steps to protect your company is a useful companion if you're starting from scratch.
Step 4: Work the Level 2 checklist
If you handle CUI, you're looking at Level 2, which maps to the 110 security requirements in NIST SP 800-171 Revision 2. This is a real program, not a weekend project. For a small shop starting from a typical setup, it often takes many months.
Don't try to fix all 110 at once. Start with the controls that carry the most weight in the scoring and the most risk in real life.
High-priority items we look at first
- Multi-factor authentication (MFA) for remote access, privileged accounts and network access to in-scope systems.
- Encryption of CUI on laptops, in email and in the cloud, using FIPS-validated cryptography where required.
- Logging and monitoring: collect audit logs, keep them, and actually review them.
- Endpoint protection on every in-scope device. An EDR tool with someone watching the alerts is a common way to cover several requirements.
- Incident response: a written plan, a tested process, and the ability to report incidents to DoD within 72 hours, as DFARS 252.204-7012 requires.
- Configuration management: a documented baseline for each system type and control over changes.
- Security awareness training for everyone with access, including insider-threat awareness.
- Vulnerability scanning on a regular schedule, with a process for fixing what you find.
Your Step 4 checklist
- Score yourself against all 110 requirements using the DoD Assessment Methodology.
- Rank the gaps by score value and risk, then build a realistic project plan.
- Budget for tools, people time and outside help. Costs vary widely with scope, which is why Step 2 matters so much.
- Retest each control after you fix it and save the evidence.
Step 5: Get the paperwork and SPRS right
A lot of small suppliers do decent security work and still fall short because the documentation is thin. Assessors and primes look for proof, not good intentions.
The documents you need
- System Security Plan (SSP): describes your boundary, your systems and how you meet each requirement. Required for Level 2, and a good idea at Level 1.
- Plan of Action and Milestones (POA&M): lists the gaps you haven't closed yet, who owns each one and when it'll be done.
- Policies and procedures: written, approved and actually followed. A policy nobody follows is worse than none, because it's evidence you knew.
- Evidence: screenshots, configuration exports, training records, visitor logs and scan reports, organized by requirement.
SPRS basics
SPRS (Supplier Performance Risk System) is where your score and affirmations live. A NIST SP 800-171 score runs from -203 to 110. Your score must be honest. Inflating it to win work is exactly the kind of thing that leads to False Claims Act exposure.
Under the CMMC rule, Level 2 can be achieved with a POA&M if you score at least 88 and close the remaining items within 180 days. Some requirements can't be left open on a POA&M at all. Ask your assessor which ones apply to your situation.
Your Step 5 checklist
- Write or update your SSP so it matches how things actually work today.
- Build a POA&M with owners and dates for every open gap.
- Calculate your score, have it reviewed internally, and post it in SPRS.
- Set a recurring reminder for the annual affirmation.
Step 6: Check your vendors, cloud and MSP
Your compliance only stretches as far as your weakest outside connection. This step gets skipped more than any other.
What to check
- Cloud services: under DFARS 252.204-7012, a cloud provider that stores or processes CUI for you generally needs to meet the FedRAMP Moderate baseline or its equivalent. Commercial versions of popular email and file-sharing tools don't always qualify, so check the specific product and plan.
- Your MSP or IT provider: if an outside firm manages in-scope systems, their tools and access are part of your assessment. Ask how they protect admin accounts, how they log their access, and whether they understand CMMC.
- Your own subcontractors: if you send CUI or FCI to a coating shop, heat treater or machinist down the road, the requirements flow down to them.
- Shared accounts with primes: portals and file-transfer sites set up by customers should be on your asset list too.
Your Step 6 checklist
- List every vendor that touches in-scope data or systems.
- Get written confirmation of their security responsibilities, ideally in a responsibility matrix.
- Confirm which of your cloud services are approved for CUI.
- Flow the right clauses down to your own subcontractors.
Frequently asked questions
Is CMMC still required if Phase 2 is paused?
Yes, in the sense that the program is still in Phase 1 and the underlying contract clauses still apply. If your contracts include DFARS 252.204-7012 or FAR 52.204-21, you must meet those safeguarding requirements now. What was paused is the third-party certification step that was set to start on November 10, 2026.
How long does it take a small business to get CMMC ready?
Level 1 often takes a few weeks to a few months for a small shop, depending on how much cleanup is needed. Level 2 commonly takes many months, sometimes a year or more if you're starting from scratch. Shrinking your scope early is the biggest lever you have on timeline.
How much does CMMC compliance cost for a small business?
It depends heavily on how much of your business is in scope, what tools you already have and how much help you need. Level 1 is usually a modest project. Level 2 costs commonly include new tools, documentation work, outside consulting and, eventually, a C3PAO assessment fee. Get quotes based on your actual scope rather than trusting a single published number.
Can we do a CMMC self-assessment ourselves?
Yes. Level 1 is always a self-assessment, and while Phase 2 is paused, contracts can only require Level 2 as a self-assessment. The catch is that a senior official has to affirm the results, and an inaccurate score carries real legal risk. Many small suppliers do the work internally and bring in outside help for a gap review before they post a score.
What is the difference between NIST 800-171 and CMMC?
NIST SP 800-171 is the set of security requirements for protecting CUI. CMMC is the DoD program that checks whether contractors actually meet those requirements, and how that checking happens. Level 2 of CMMC is built directly on the 110 requirements in NIST SP 800-171 Revision 2.
Get a clear starting point
The hardest part of CMMC for most small suppliers is knowing where they stand today. Once you know your data, your scope and your biggest gaps, the rest becomes a project plan instead of a worry.
That's what our free cybersecurity assessment is for. Mukesh and I will look at your environment, help you sort out FCI vs. CUI, and give you a plain-English list of what to fix first. There's no obligation, and if you're further along than you thought, we'll tell you that too. Request your free cybersecurity assessment and we'll set up a time to talk.
Related reading
- CMMC Level 1 vs. Level 2: Which One Does Your Manufacturing Shop Need?
- How to Secure Shop-Floor (OT) Networks Without Stopping Production
- Cybersecurity for Roanoke Small Businesses: 10 Steps to Protect Your Company
Harsha is a co-founder of SoftwarePac Technologies in Roanoke, VA, and a network engineer with 15 years of experience.




