Crashcart Start your free trial

Federal contract rules

FAR 52.204-21 requirements for small contractors

FAR 52.204-21 requires any federal contractor or subcontractor whose systems hold federal contract information to apply 15 basic safeguards: limit who and what can get in, identify and authenticate users, wipe media before disposal, control physical access and visitors, protect the network edge, keep public systems separate, fix flaws promptly, and run antivirus that stays current and scans. It can come from any federal agency at any contract value, and primes must pass it down to subcontractors that may hold that information, except suppliers of commercially available off-the-shelf items. The clause itself asks for no written plan, assessment or report. The Defense Department's CMMC Level 1 adds a yearly self-assessment and a senior official's affirmation of the same 15 safeguards.

These 15 requirements are the whole of CMMC Level 1, which the full guide to CMMC Level 1 covers. CMMC's schedule is under review. On July 13, 2026, the Defense Department suspended CMMC Phase II, which was due to start November 10, 2026, and began a review of the program. Its CMMC page said on October 15, 2026 that all Phase I self-assessment requirements remain in place. None of that changes FAR 52.204-21, which applies wherever it is in your contract.

Who FAR 52.204-21 applies to

FAR 4.1903 tells contracting officers to use the clause "when the contractor or a subcontractor at any tier may have Federal contract information residing in or transiting through its information system." FAR 4.1902 says it applies to "all acquisitions, including acquisitions of commercial products or commercial services other than commercially available off-the-shelf items." Neither section sets a dollar threshold. Because the FAR covers purchasing across federal executive agencies, the clause can come from a civilian agency as easily as from the Defense Department.

Subcontractors get it through paragraph (c) of the clause, which makes the prime include its substance in any subcontract where the subcontractor may have federal contract information in its systems, commercial subcontracts included. Off-the-shelf items are the only carve-out. If you are a subcontractor, look for 52.204-21 among the flowdown clauses in your subcontract or purchase order terms.

What counts as federal contract information

The clause defines federal contract information 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." It excludes information the government gives the public, such as on its websites, and "simple transactional information, such as necessary to process payments."

For a small manufacturer or engineering firm, that can include the drawings, specifications and statements of work a prime or agency sends you, and the reports and data you produce for the contract, unless they are marked for public release.

Which systems the clause covers

A "covered contractor information system" is one "owned or operated by a contractor that processes, stores, or transmits Federal contract information." That is every computer, server, phone and account the information passes through, including the email account where the drawings arrive. Keeping contract files on fewer computers and accounts shrinks the job.

The 15 FAR 52.204-21 requirements and what they mean

Paragraph (b)(1) lists the 15 requirements, numbered (i) to (xv), quoted below. The Defense Department's CMMC Assessment Guide for Level 1 explains each one with examples, and we quote it where it settles a question.

Who can get in, (i) to (iv)

(i) "Limit information system access to authorized users, processes acting on behalf of authorized users, or devices (including other information systems)." Know who has an account on each computer and in your email, and which devices may join your network. When someone leaves, their accounts close.

(ii) "Limit information system access to the types of transactions and functions that authorized users are permitted to execute." People get the access their job needs and no more. In a small office that usually means staff work in standard Windows accounts, and only the people who need it get administrator rights or the contract folder.

(iii) "Verify and control/limit connections to and use of external information systems." The guide counts the public internet, outside companies' networks and "personally owned devices such as laptops, tablets, and phones." Decide whether personal phones and home computers may open contract files, and control remote access tools.

(iv) "Control information posted or processed on publicly accessible information systems." The guide says "Only government officials can be authorized to publicly release FCI." Know who can post to your website and social media, and check posts and photos before they go up.

Who someone is, (v) and (vi)

(v) "Identify information system users, processes acting on behalf of users, or devices."

(vi) "Authenticate (or verify) the identities of those users, processes, or devices, as a prerequisite to allowing access to organizational information systems."

Together these mean one account per person, no shared logins, and a password before anyone gets in. The guide also says to change default usernames and passwords on devices such as routers and printers. The clause doesn't require multi-factor authentication, and the guide says the most common way to authenticate is "a username and a hard-to-guess password." A code from a phone on top of the password does far more for email, and turning on MFA in Microsoft 365 is free.

Old drives and paper, (vii)

(vii) "Sanitize or destroy information system media containing Federal Contract Information before disposal or release for reuse." The guide counts paper, disks, USB drives and phones as media. Shred or destroy it, or wipe it if you will reuse it. The guide points to NIST SP 800-88 for wiping methods.

The building, (viii) and (ix)

(viii) "Limit physical access to organizational information systems, equipment, and the respective operating environments to authorized individuals."

(ix) "Escort visitors and monitor visitor activity; maintain audit logs of physical access; and control and manage physical access devices."

Lock the rooms where contract computers sit, know who has keys, escort visitors and keep a sign-in log. Requirement (ix) packs three requirements into one sentence. The CMMC rule at 32 CFR 170.15 maps it to three separate NIST SP 800-171 requirements, which is why some lists count 17 Level 1 practices instead of 15.

The network edge, (x) and (xi)

(x) "Monitor, control, and protect organizational communications (i.e., information transmitted or received by organizational information systems) at the external boundaries and key internal boundaries of the information systems."

(xi) "Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks."

For most small offices, (x) is a firewall at the internet connection that blocks incoming traffic you didn't ask for, plus the firewall on each computer. Requirement (xi) is about anything the public can reach, such as a web server in your office or guest Wi-Fi, which belongs on its own network. The guide says (xi) "might be N/A if there are no publicly accessible systems" in scope.

Flaws and malware, (xii) to (xv)

(xii) "Identify, report, and correct information and information system flaws in a timely manner." The clause doesn't define timely, so you set your own time frames and keep to them. In practice this is installing security updates and replacing computers that no longer get them, such as PCs still on Windows 10 without paid extended updates (see Windows 10 end of support for small businesses).

(xiii) "Provide protection from malicious code at appropriate locations within organizational information systems."

(xiv) "Update malicious code protection mechanisms when new releases are available."

(xv) "Perform periodic scans of the information system and real-time scans of files from external sources as files are downloaded, opened, or executed."

Antivirus on every computer, set to update itself, to scan on a schedule and to scan files as they are downloaded or opened, covers all three.

If your contract cites FAR 52.240-93

Under the Revolutionary FAR Overhaul, the FAR Council issues rewritten FAR parts as model text, and agencies adopt them through their own class deviations. The model text for Part 40, issued August 14, 2025, moves this subject to section 40.303 and renumbers the clause 52.240-93, with the same title. A newer contract may cite either number.

On October 15, 2026 we compared paragraph (b)(1) of 52.204-21 on acquisition.gov with the same paragraph of 52.240-93 in the Part 52 model text, requirement by requirement, using a short script that ignored spacing. All 15 requirements are word for word the same. Only the wording around them changed: the lead-in sentence, the definition of federal contract information, and the word order in the subcontract paragraph. By our count the whole clause runs about 570 words, and the 15 requirements are 243 of them.

What the clause doesn't ask for

FAR 52.204-21 has no assessment, score, certification, written plan or reporting step. It tells you to apply the safeguards and says nothing about how to prove it.

Paragraph (b)(2) adds that the clause doesn't replace other safeguarding rules, including those for controlled unclassified information (CUI) under Executive Order 13556. CUI is a larger job. On defense contracts it brings NIST SP 800-171 and CMMC Level 2, which the Defense Department's July 2026 memo describes as aligned with NIST SP 800-171 Rev 2.

How CMMC Level 1 adds to the clause

CMMC Level 1 asks for the same 15 safeguards. The Assessment Guide says "Level 1 aligns with FAR Clause 52.204-21." What it adds is proof.

The Defense Department's clause DFARS 252.204-7021 puts the requirement into contracts. It comes from a rule effective November 10, 2025 (90 FR 43560). When a solicitation calls for CMMC Level 1 (Self), DFARS 204.7502 says the contracting officer can't award to an offeror without a current status at that level.

Under 32 CFR 170.15, that status takes a yearly self-assessment against the NIST SP 800-171A objectives for the 15 requirements, with every one met and no plan of action allowed. The result goes into the Supplier Performance Risk System (SPRS), a senior official at your company affirms it there (32 CFR 170.22), and you keep the evidence for six years. The CMMC Level 1 checklist is the working list, with the evidence to keep for each requirement.

During the Phase II suspension, the July 2026 memo lets Defense Department program managers designate only CMMC Level 1 (Self) or Level 2 (Self) in new requirements.

Keeping the 15 safeguards in place all year

Most of the 15 are ongoing work. Accounts change when people join and leave, updates arrive every month, and a visitor log only counts if someone fills it in. Under CMMC, the yearly affirmation states that your company "has implemented and will maintain implementation of all applicable CMMC security requirements."

Crashcart does the computer side of that upkeep for small subcontractors. It installs Windows, Mac and app updates every week and flags computers on versions that no longer get security fixes. It keeps antivirus on, checks each morning for unused accounts and everyday accounts with admin rights, and logs every check and fix with the date and the CMMC practice it meets. Once a year it asks you to confirm the physical access and website items. Your company still decides who gets access and controls the building, and your affirming official signs. The page for federal subcontractors shows what it does for each safeguard.

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.