The 15 basic cybersecurity rules in almost every federal contract (FAR 52.204-21)

Updated Oct 25, 2026 · 7 min read

In this guide

  1. What federal contract information is
  2. When the clause is in your contract
  3. The 15 rules in plain English
  4. How this relates to CMMC Level 1
  5. A one-afternoon checklist for a 5-person company
  6. Key terms
  7. Common questions

Sources

What is FAR 52.204-21?

FAR 52.204-21 is a clause from the Federal Acquisition Regulation (FAR) that asks contractors to protect federal contract information on their computers. It lists 15 basic security steps, such as limiting access to your own people, using passwords, installing updates, running antivirus, and controlling who can reach your equipment. It also flows down to subcontractors that may hold that information.

Read the clause list in almost any federal contract and you’ll find “52.204-21, Basic Safeguarding of Covered Contractor Information Systems.” It sounds technical, but it’s mostly 15 short rules that a careful small business may already follow. You can write down how you meet them in one afternoon.

The 15 basic safeguarding rules

The 15 basic safeguarding rules fall into three groups; write one line on how you meet each.

  1. Who can get in

    • Only your people and devices (i)
    • Only what each person needs (ii)
    • Control outside systems (iii)
    • Know who’s who (v)
    • Prove it before access (vi)

    Check: One account per person, a password on each.

  2. What’s on the machines

    • Watch what goes public (iv)
    • Guard the edges (x)
    • Keep public parts separate (xi)
    • Fix flaws on time (xii)
    • Use malware protection (xiii)
    • Keep it updated (xiv)
    • Scan (xv)

    Check: Updates and malware protection on, everywhere.

  3. The building and the media

    • Wipe or destroy old media (vii)
    • Lock up the equipment (viii)
    • Manage visitors and keys (ix)

    Check: Doors lock; visitors signed in; old drives wiped.

Write one line per rule on how you meet it. Same 15 rules as CMMC Level 1.

Sources: FAR 52.204-21 · 32 CFR 170.14. Checked Oct 25, 2026. The solicitation decides the details.

What federal contract information is

The clause protects federal contract information (FCI). FAR defines it 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.”

Two things are left out:

  • Public information, like a solicitation posted on SAM.gov or anything on an agency’s public website.
  • Simple transactional information, like what’s needed to process your invoices and payments.

So if an agency emails you a building layout, a staff schedule or a draft report for your contract, that’s likely FCI. The work you produce for the agency can be FCI too.

CUI is a step up. Controlled unclassified information is a narrower group of sensitive information, usually marked “CUI,” such as some technical drawings. The clause says it doesn’t replace other agency rules or the rules for CUI. If you handle CUI on a defense contract, more rules usually apply. One is a clause in the Defense Federal Acquisition Regulation Supplement (DFARS 252.204-7012). Another is a security standard from the National Institute of Standards and Technology (NIST SP 800-171), a Special Publication. Those ask for much more. This guide covers the basic level only.

When the clause is in your contract

FAR 4.1903 tells the contracting officer to include 52.204-21 when “the contractor or a subcontractor at any tier may have Federal contract information residing in or transiting through its information system.” That covers commercial products and services too. The main exception is buying commercially available off-the-shelf (COTS) items.

Subcontractors get it too. The prime must put the clause in subcontracts where the subcontractor may have FCI on its systems. If a prime sends you a subcontract with 52.204-21 in it, the 15 rules apply to you. See how flow-down clauses work.

The number may change. The FAR overhaul is moving this clause into a new Part 40. In the model deviation text, the same clause is 52.240-93, with the same 15 rules. Agencies are switching at different times, so a solicitation may use either number. See How to read a government solicitation for where to find the clause list.

The 15 rules in plain English

The clause says you must apply these “at a minimum.” The wording below is a plain-language summary. The last column is the clause paragraph, (b)(1)(i) to (xv).

Who can get in
RuleWhat it meansParagraph
1. Only your people and devices get inLimit access to authorized users, programs acting for them, and devices.(i)
2. People get only what they needLimit each user to the tasks and functions they’re allowed to do. Not everyone needs admin rights.(ii)
3. Control outside systemsCheck and limit connections to systems you don’t control, like personal laptops or someone else’s cloud account.(iii)
4. Know who’s whoIdentify every user, program acting for a user, and device.(v)
5. Prove it before accessVerify each user or device, for example with a password, before letting them in.(vi)
What’s on the machines
RuleWhat it meansParagraph
6. Watch what goes publicControl what’s posted or processed on systems the public can reach, like your website.(iv)
7. Guard the edgesMonitor, control and protect communications at the edges of your network, for example with a firewall.(x)
8. Keep public parts separatePut anything the public can reach on a separate network from your internal one.(xi)
9. Fix flaws on timeFind, report and fix security flaws “in a timely manner.” Install updates.(xii)
10. Use malware protectionProtect against malicious code in the right places.(xiii)
11. Keep it updatedUpdate that protection when new releases come out.(xiv)
12. ScanRun periodic scans, plus real-time scans of files from outside as they’re downloaded, opened or run.(xv)
The building and the media
RuleWhat it meansParagraph
13. Wipe or destroy old mediaClean or destroy drives and devices that held FCI before you throw them out or reuse them.(vii)
14. Lock up the equipmentLimit physical access to your computers, equipment and the rooms they’re in to authorized people.(viii)
15. Manage visitors and keysEscort visitors and watch what they do, keep a record of who gets in, and control keys, badges and codes.(ix)

How this relates to CMMC Level 1

If you work with the Department of War (formerly the Department of Defense), you may hear about CMMC. CMMC Level 1 uses these same 15 rules. The CMMC rule says Level 1’s requirements “are those set forth in 48 CFR 52.204-21(b)(1)(i) through (xv).”

When a contract requires CMMC Level 1:

  • You check yourself, every year, and enter the result in SPRS.
  • Every rule must be met. You can’t list some as “fix later.”
  • A senior person in your company affirms the result in SPRS.
  • You keep your evidence for six years.

Some guides say Level 1 has 17 practices. Older CMMC material split the visitor rule (number 15 above) into three. The rules themselves didn’t change.

CMMC’s next phase, which would have added outside assessments, is paused. The self-assessments still apply. See CMMC is still paused for where things stand.

A one-afternoon checklist for a 5-person company

The FAR clause doesn’t say you must write anything down. But a written record shows what you do, helps you keep it up, and is what a prime or a CMMC self-assessment will ask about.

  1. List what holds FCI. Five laptops, one shared cloud drive, email, two phones. Write down where contract files live.
  2. List who has access. One account per person. No shared logins. Only the owner has admin rights.
  3. Turn on sign-in protection. Passwords on every device and account. Many firms also add a second step, like a code on a phone.
  4. Turn on automatic updates for every laptop, phone and browser.
  5. Check malware protection is on, updating, and scanning downloads on every laptop.
  6. Check the router. Firewall on. Guests use a separate guest Wi-Fi.
  7. Check the website. No contract files or non-public details posted.
  8. Set an office rule. Visitors are walked in and signed in. Doors lock. Keep a list of who has keys.
  9. Set a disposal rule. Old laptops and drives are wiped or destroyed, and you note the date.
  10. Write one line for each of the 15 rules saying how you meet it. Date it. Set a reminder to review it in a year.

If an item is unclear, an APEX Accelerator can help for free.

This guide explains the rules in plain language. It isn’t legal or security-certification advice.

Key terms

Federal contract information (FCI)
Information that isn’t meant for the public, given to you by the government or created for it under a contract. It doesn’t include information the government makes public or simple payment details.
Controlled unclassified information (CUI)
A narrower kind of sensitive government information, usually marked as CUI. It has stricter rules.
Covered contractor information system
Any computer system your company owns or runs that stores, processes or sends FCI.
Flow down
Passing a contract clause on to your subcontractors.
Cybersecurity Maturity Model Certification (CMMC) Level 1
The Department of War’s check that a contractor meets these same 15 rules, done as a yearly self-assessment.
SPRS
The Supplier Performance Risk System, the Department of Defense website where CMMC self-assessment results are entered.

Do this in FedPath

Add the clause to your compliance matrix. When you build a compliance matrix for a request for proposals (RFP), add a row for 52.204-21 (or 52.240-93). Link it to your one-line-per-rule record.

Free RFP compliance matrix generator

Free. FedPath is independent. It is not affiliated with, endorsed by, or part of the U.S. government, the Small Business Administration (SBA), SAM.gov, or any federal agency.

Common questions

Do I need a certification to meet 52.204-21?

No. The FAR clause has no certification. For some defense contracts, CMMC Level 1 asks for a yearly self-assessment of the same 15 rules.

Does it apply if I only get paid through the government’s payment system?

Simple transactional information, like what’s needed to process payments, isn’t FCI. If that’s all you hold, the clause has little to protect. Ask the contracting officer if you’re unsure.

Is this the same as NIST SP 800-171?

No. NIST SP 800-171 is a longer standard for CUI. The 15 basic rules are a small starting set.

I’m a subcontractor. Who checks?

Your prime may ask how you meet the clause. Keep your one-line-per-rule record ready.

Can I say I comply if I’m still working on it?

Be honest. Saying you meet a cybersecurity requirement when you don’t can lead to penalties under the False Claims Act.