Crashcart Start your free trial

Federal contract rules

CMMC Level 1 requirements for small businesses

CMMC Level 1 applies to a small business that holds Federal Contract Information under a Defense Department contract or subcontract that requires it. It asks for the 15 basic safeguards in FAR 52.204-21, a self-assessment against all 15 every year with every one met, and a senior official's affirmation of the result in SPRS, the Defense Department's Supplier Performance Risk System, before award and each year after. A July 2026 suspension stopped the move to Phase 2, which would have brought third-party Level 2 certifications, but solicitations can still require a Level 1 self-assessment, and the FAR clause applies wherever it is in your contract.

CMMC is the Cybersecurity Maturity Model Certification program, set out in 32 CFR Part 170 and run by the Department of Defense, whose own pages now use the name Department of War. Level 1 adds no safeguards of its own. It checks the ones in FAR 52.204-21, Basic Safeguarding of Covered Contractor Information Systems. This guide covers who Level 1 reaches, the 15 requirements, the yearly self-assessment and affirmation, how the requirement reaches subcontractors, and what a company of 3 to 30 people does for each requirement.

Is CMMC suspended?

Part of it is. On July 13, 2026, the department's chief information officer suspended the move to Phase 2 of CMMC, which was set for November 10, 2026, and held "all pending and future CMMC implementation milestones" in abeyance until further notice (memo). The same memo set up a CMMC Reform Task Force for a 60-day review of the program.

Level 1 was not suspended. The memo says program managers "shall only include the need for CMMC Level 1 or Level 2 Self Assessments" in procurement requests, and the department's CMMC page says "All Phase I self-assessment requirements remain firmly in place." The implementing memo describes Level 1 as a self-assessment of the FAR 52.204-21 safeguards. Class Deviation 2026-O0025, Revision 3, dated September 3, 2026, tells contracting officers to work with requiring activities to remove or revise CMMC requirements in solicitations and contracts to match the memo, which permits only the two self-assessment levels.

What hasn't changed:

  • The regulation, 32 CFR Part 170, has not been amended. Its text still describes all four phases.
  • The contract clause that puts a CMMC level into a defense contract, DFARS 252.204-7021, is still in the class deviation's text, including its Level 1 option.
  • FAR 52.204-21 applies wherever it is in your contract, with or without CMMC.

When we checked on October 15, 2026, the department's CMMC page showed nothing newer than the July 13 announcement. The memo says further guidance will follow, and we'll update this page when it does.

Who CMMC Level 1 applies to

CMMC applies to defense contractors and subcontractors, at every tier, that will process, store or transmit Federal Contract Information (FCI) or Controlled Unclassified Information (CUI) on their own information systems while performing the contract (32 CFR 170.3(a) and 170.23). Level 1 is the level for companies that handle FCI and no CUI.

Phase 1 began on November 10, 2025, when the DFARS rule that adds CMMC to contracts took effect. In Phase 1 the department decides contract by contract whether to require a CMMC level (170.3(e)(1)). A solicitation that requires Level 1 names "CMMC Level 1 (Self)" and includes DFARS 252.204-7021.

CMMC does not reach:

  • contracts and subcontracts solely for commercially available off-the-shelf (COTS) items
  • contracts at or below the micro-purchase threshold
  • procurements the department waives in advance (170.3(c))
  • a company whose systems will never hold FCI or CUI for the contract

There is no exemption for size. A 4-person shop that receives FCI under a contract requiring Level 1 owes the same 15 requirements as a large prime.

FAR 52.204-21 reaches further than CMMC. Any federal agency, not only Defense, puts it in solicitations and contracts when the contractor or a subcontractor at any tier may have FCI in its information systems (FAR 4.1903). A company working for a civilian agency can owe the same 15 safeguards with no CMMC requirement and no SPRS entry.

What counts as federal contract information

The clause defines FCI as "information, not intended for public release, that is provided by or generated for the Government under a contract to develop or deliver a product or service to the Government," leaving out information the government makes public and "simple transactional information, such as necessary to process payments."

For a small manufacturer or engineering firm that usually means the statement of work, drawings and specifications from a prime, reports you produce for the contract, and email about the work. An invoice and payment details on their own are the transactional information the definition leaves out.

FCI or CUI

Controlled Unclassified Information is information that a law, regulation or government-wide policy requires or permits the government to protect with safeguarding or dissemination controls (32 CFR 2002.4(h)). Documents carrying a CUI marking are CUI. If a subcontractor will process, store or transmit CUI, the minimum is CMMC Level 2 (Self), which follows all of NIST SP 800-171 Rev. 2 (170.23(a)(2)), far more than Level 1's 15 requirements. Ask your prime which kind of information you will receive before you plan anything.

The 15 FAR 52.204-21 requirements

The Level 1 security requirements are those in FAR 52.204-21(b)(1)(i) through (xv) (32 CFR 170.14(c)(2)). CMMC gives each one an ID made of a two-letter domain, the level and the clause paragraph, so paragraph (b)(1)(xii) becomes SI.L1-b.1.xii. The last column is our count of the assessment objectives the Defense Department's Level 1 Assessment Guide lists for each requirement, explained in the next section.

FAR (b)(1) CMMC ID What the clause requires Objectives
(i) AC.L1-b.1.i Limit system access to authorized users, processes acting for them, and devices 6
(ii) AC.L1-b.1.ii Limit access to the transactions and functions authorized users may perform 2
(iii) AC.L1-b.1.iii Verify and control or limit connections to and use of external systems 6
(iv) AC.L1-b.1.iv Control information posted or processed on publicly accessible systems 5
(v) IA.L1-b.1.v Identify users, processes acting for users, and devices 3
(vi) IA.L1-b.1.vi Authenticate those users, processes and devices before allowing access 3
(vii) MP.L1-b.1.vii Sanitize or destroy media containing FCI before disposal or reuse 2
(viii) PE.L1-b.1.viii Limit physical access to systems, equipment and operating environments 4
(ix) PE.L1-b.1.ix Escort and monitor visitors, keep physical access logs, and manage keys, locks and badges 6
(x) SC.L1-b.1.x Monitor, control and protect communications at external and key internal boundaries 8
(xi) SC.L1-b.1.xi Put publicly accessible system components on subnetworks separate from internal networks 2
(xii) SI.L1-b.1.xii Identify, report and correct system flaws in a timely manner 6
(xiii) SI.L1-b.1.xiii Provide protection from malicious code at appropriate locations 2
(xiv) SI.L1-b.1.xiv Update malicious code protection when new releases are available 1
(xv) SI.L1-b.1.xv Run periodic scans, and real-time scans of files from outside as they are downloaded, opened or run 3

For the self-assessment, 32 CFR 170.15(c)(1) maps these 15 onto 17 requirements in NIST SP 800-171A, because requirement (ix) splits into three: escorting visitors, keeping physical access logs, and managing physical access devices.

None of the 15 mentions encryption, backups, staff training or multi-factor authentication. The cyber insurance applications we read ask about all four (Cyber insurance requirements for small businesses), and Level 2 requires multi-factor authentication, but Level 1 does not require any of them.

Under the government's FAR overhaul, some newer contracts cite the same clause as 52.240-93. We compared the two texts, and the 15 requirements are word for word the same. FAR 52.204-21 requirements for small contractors goes through the clause paragraph by paragraph.

What the Level 1 self-assessment checks

A Level 1 self-assessment scores each requirement against its assessment objectives, and a requirement is met only when every objective is met or does not apply (32 CFR 170.24). The objectives come from NIST SP 800-171A, and the department's CMMC Assessment Guide for Level 1 prints them under each requirement.

We wanted to know how much of Level 1 is a computer setting and how much is a decision the owner has to make. On October 15, 2026 we downloaded version 2.13 of the Level 1 Assessment Guide (September 2024, 54 pages) from the DoD CIO site, counted the lettered objectives under "Determine if" for each of the 15 requirements, and sorted each one by what it asks for.

What the objective asks for Objectives
Something identified, defined or specified, such as a list, a boundary or a time frame 21
Accounts, computers and the network working that way 25
Physical access to the building, visitors, keys and badges 8
What gets posted on public websites 3
Wiping or destroying media before disposal or reuse 2
Total 59

Twenty-one of the 59 objectives ask the company to decide something and write it down. Examples are who the authorized users are, which outside systems you use, where your network's boundaries sit, how quickly you will find, report and fix flaws, and how often antivirus scans run. An IT provider can suggest answers, but the company has to own them. Another 13 concern the building, the website and old media, and depend on what people do more than on any setting. The 25 about accounts, computers and the network are the part a tool can check every day. Requirement (x), boundary protection, has the most objectives at 8. Requirement (xiv), updating antivirus, has 1.

Each MET finding needs evidence, and 170.24(b)(1) says the evidence must be "in final form and not draft." Working papers and unofficial or unapproved policies don't count. Keep the evidence for six years from the CMMC status date (170.15(c)(2)).

What a small business does for each CMMC Level 1 requirement

The steps below are what the requirements mean for a company with a few computers, one office or shop, and nobody whose job is IT.

Access control (i) to (iv)

(i) Authorized users and devices. Write down who is authorized and which accounts each person has on the computers, in email and in any cloud storage that holds contract files. Then make the computers match. Every person signs in with their own account, guest and unused accounts are off, and a person who leaves loses access the day they leave (Employee offboarding IT checklist). Note the accounts programs use, such as a backup or scanning program, and list the devices allowed to connect.

(ii) What each user can do. Decide what each role needs and limit accounts to that. In a small office the main control is admin rights. Everyday accounts are standard users, and installing software or changing settings takes a separate admin account that only one or two people have. Shared folders follow the same rule, so only the people on a contract can open its folder.

(iii) External systems. An external system is one you don't control: personal email, a home computer, a personal phone, a USB drive, an outside file-sharing site. List the ones that touch contract information and decide which are allowed. The Assessment Guide's own example is a policy that staff use company laptops, not personal ones, when working on the contract from home. Turn off Remote Desktop and similar tools that the internet can reach, or protect them.

(iv) Public websites. Name who may post to your website and social media accounts, check posts for contract information before they go up, and have a way to take one down. Photos from the shop floor are an easy way to post contract information by accident, when a part, a drawing or a screen sits in the background.

Identification and authentication (v) and (vi)

(v) Identify users, processes and devices. Give each person a unique account. A shared "frontdesk" login used by three people fails this, because nothing shows who did what. Give each computer and network device its own name too.

(vi) Authenticate before access. Every account needs a password, and none can be blank. Change the default passwords on routers, printers and other network equipment.

Level 1 does not require multi-factor authentication. The CMMC scoring rule lists it as a Level 2 requirement, IA.L2-3.5.3 (170.24(a)). Turn it on for email anyway. Five of the eight cyber insurance applications we read on October 14, 2026 ask about it for email, and How to turn on MFA in Microsoft 365 walks through the setup.

Media disposal (vii)

Shred or destroy anything holding FCI before you throw it away, and wipe it before anyone reuses it. The Assessment Guide counts paper documents, disks, USB drives, CDs and mobile phones as media, and points to NIST's media sanitization guidelines, SP 800-88, for how to wipe them. Check whether a leased copier or multifunction printer has its own drive before it goes back. Write down what was wiped or destroyed, how and when.

Physical access (viii) and (ix)

(viii) Limit physical access. Write down who may enter the areas where computers and contract files are. Keep computers that hold FCI out of the lobby, and lock the room or cabinet where the network equipment sits.

(ix) Visitors, logs and keys. Escort visitors and keep an eye on what they do. Keep a record of who enters. The Assessment Guide accepts a written sign-in and sign-out sheet as that record, kept for a period the company sets. Keep a list of who holds which key, badge or door code, collect keys when someone leaves, and change codes they knew.

Network boundaries (x) and (xi)

(x) Boundary protection. Define your external boundary, usually the router or firewall where the internet line comes into the office, and any internal boundaries, such as between guest Wi-Fi and the work network. The Assessment Guide's example starts with a simple sketch of both. Then monitor, control and protect traffic at each. Keep the firewall on at the router and on every computer, and know what the internet can reach at your office's address.

(xi) Public systems kept separate. Anything the public uses, such as guest Wi-Fi or a server the public can reach, goes on a network separate from your work computers. If nothing in scope is publicly accessible, the requirement can be scored not applicable. The Assessment Guide gives this requirement as its example, and calls it best practice to write down why it doesn't apply.

Flaws and malicious code (xii) to (xv)

(xii) Flaw remediation. Set time frames for finding, reporting and fixing flaws, then meet them. The Assessment Guide's example checks vendor notices weekly, patches end-user computers weekly and servers monthly. Pick numbers you can keep. Turn on automatic updates for Windows, macOS and your programs, check that they install, and replace computers running a version that no longer gets security fixes (Windows 10 end of support for small businesses).

(xiii) to (xv) Malicious code protection. Run antivirus on every computer that handles FCI, and on email if your provider offers attachment scanning. Keep it updating itself. Set how often full scans run and write it down. Keep real-time scanning on, so files are checked as they are downloaded, opened or run, including files from USB drives.

Which computers are in scope

Before the assessment you set its scope. Level 1 covers the systems that process, store or transmit FCI, and the people, technology, facilities and outside service providers involved (32 CFR 170.19(b)). Systems that never touch FCI are out of scope and need no paperwork.

Specialized assets are not part of the Level 1 scope and are not assessed. They are Internet of Things and Industrial Internet of Things devices, operational technology, government-furnished equipment, restricted information systems and test equipment (170.19(b)(2)(ii)). For a machine shop, that can include the controllers on the machines themselves. The department's Level 1 Scoping Guide has more detail.

Scope follows the information. If drawings arrive by email, the email account is in scope, and so is every computer that opens them. Keeping contract files on fewer computers and in one shared location makes the assessment smaller.

The yearly self-assessment and SPRS affirmation

32 CFR 170.15 sets out the Level 1 self-assessment. In order:

  1. Set the scope as above.
  2. Assess each of the 15 requirements against its objectives. The Assessment Guide describes three methods: examine documents and settings, interview the people involved, and test that things work.
  3. Score each requirement MET, NOT MET or not applicable. All must be met or not applicable. A plan of action to finish later is not allowed at Level 1 (170.21(a)(1)).
  4. Enter the result in SPRS: the CMMC level, the status date, the assessment scope, the CAGE codes for the systems in scope, and the compliance result (170.15(a)(1)(i)). The contract clause points to SPRS through the PIEE portal at piee.eb.mil.
  5. Have your affirming official submit the affirmation in SPRS (170.22).
  6. Keep the evidence for six years.
  7. Repeat every year.

The affirming official is "the senior level representative from within" the company who is responsible for its CMMC compliance and has the authority to affirm it (170.22(a)(1)). In a small company that is usually the owner or president. The person has to come from within the company, so an outside IT provider or consultant cannot affirm for you. The affirmation gives the official's name, title and contact information and states that the company "has implemented and will maintain implementation of" all Level 1 requirements for the systems in scope (170.22(a)(2)).

A company must have its Level 1 status and affirmation in SPRS before award of any contract or subcontract that requires it (170.15(b)). Under the class deviation's DFARS text, the status counts as current for one year, and contracting officers check SPRS before award and before exercising an option. Level 1 has no conditional status. It requires a final status at award.

The Assessment Guide says a company can assess itself or bring in a third party to help. Either way, the official who affirms is the one vouching for the result.

How flow-down reaches small subcontractors

If you work for a prime contractor rather than for the government directly, two clauses carry these rules down to you.

FAR 52.204-21(c) requires the contractor to put the substance of the clause into subcontracts where the subcontractor may have FCI in its systems, other than subcontracts for COTS items only. Each tier passes it to the next.

For CMMC, primes must flow the requirement down to every tier that handles FCI or CUI. A subcontractor that will handle only FCI needs CMMC Level 1 (Self) (170.23(a)(1)). DFARS 252.204-7021 makes the prime ensure each subcontractor completes its affirmation before the subcontract is awarded and keeps it current every year.

When a prime asks you about CMMC, get these answers in writing:

  • Will we receive FCI, CUI or neither?
  • Which CMMC level does the subcontract require?
  • Does the subcontract include FAR 52.204-21, 52.240-93 or DFARS 252.204-7021?
  • When do you need our SPRS entry?

If the answer is CUI, you are looking at Level 2, and this guide is not enough.

A starting checklist for a small company

  1. Find out from your prime or the solicitation whether you will hold FCI, CUI or neither, and which CMMC level applies.
  2. List where contract information lives: computers, email, cloud storage, paper files.
  3. Set the assessment scope, and move contract files onto fewer systems if you can.
  4. Write down the authorized users, devices and outside systems, and close accounts for anyone who has left.
  5. Remove everyday admin rights and give each person their own account and password.
  6. Change default passwords on network equipment.
  7. Turn on firewalls, automatic updates and antivirus with real-time scanning on every computer in scope.
  8. Separate guest Wi-Fi and anything public from the work network.
  9. Write down your time frames for fixing flaws and your scan frequency.
  10. Set visitor escort and sign-in rules, and list who holds which key or code.
  11. Decide how you will wipe or destroy drives and shred paper, and keep a record.
  12. Name the affirming official, assess all 15 requirements, and keep the evidence.
  13. Enter the result and the affirmation in SPRS, and set a date to repeat it next year.

The CMMC Level 1 checklist breaks these into the individual checks to work through.

Keeping the affirmation true all year

The affirmation is a statement about the year ahead as well as the day you sign. Things drift: a new laptop arrives without antivirus, someone leaves and their account stays open, an update fails for a month, a new hire gets admin rights to install one program. Each one turns a MET into a NOT MET until it is fixed. A dated record of checks and fixes is what shows the safeguards held between assessments.

Crashcart, which runs IT for small offices, applies CMMC Level 1 when a company says at setup that it works on government contracts. Each morning it checks every computer for unused accounts, everyday accounts with admin rights, the firewall and antivirus, and fixes routine problems. It installs updates every week. Every check and fix goes into an evidence log with the date and the CMMC practice it meets. From a year of that record it drafts the yearly review, safeguard by safeguard, and your affirming official reads it, then enters the result and the affirmation in SPRS. Who should have access, visitor rules and what goes on your website stay your decisions. The page for federal subcontractors shows what it does for each of the 15 safeguards.

This is general information, not legal advice. For your situation, ask your attorney.

More in this topic

Crashcart runs IT and security for small offices for $35 a computer a month. Start a 14-day free trial.