# Checklist: the fifteen basic safeguarding requirements in FAR 52.204-21

Thirteen steps for federal contractors and subcontractors whose systems hold Federal contract information: finding the clause, drawing the system boundary, putting the fifteen controls in place and flowing the clause down.

Checklist · Government · Platforms & Architecture. Published November 14, 2026. Last reviewed November 14, 2026.

## A short clause with a wide reach

FAR subpart 4.19 tells contracting officers to insert the clause at 52.204-21, Basic Safeguarding of Covered Contractor Information Systems, in solicitations and contracts when the contractor or a subcontractor at any tier may have Federal contract information residing in or transiting through its information system [1]. It applies to all acquisitions, including commercial products and commercial services, other than commercially available off-the-shelf items, when a contractor’s information system may contain Federal contract information [1]. The clause, dated November 2021, lists fifteen security controls as the minimum and requires the substance of the clause in qualifying subcontracts [2]. It also says it does not relieve the contractor of other agency safeguarding requirements or of the separate requirements for controlled unclassified information [2].

The text below follows the eCFR current to November 12, 2026 [1] [2]. As checked on November 14, 2026, the FAR Council’s proposed rule under the Revolutionary FAR Overhaul for FAR parts 1, 2, 4, 33, 39, 40, 52 and 53 (FAR Case 2026-001, 91 FR 37550, published June 23, 2026) was still a proposal; its comment period closed on July 23, 2026 [3]. Until a final rule changes it, the current clause is the one in contracts.

## Using the steps

The first three steps decide where the clause applies; the next eight group the fifteen controls by what they protect; the last two cover subcontracts and evidence. Each step cites the paragraph of the clause or of subpart 4.19 it rests on. Where a step is our suggestion, it says so. The owner under each step is a typical role, not one the rule names, unless the step says the rule names it. The clause names no owner for any control. This page explains the rule; it is not legal advice.

Moraph’s teams help organizations with work like this. [See our solutions](https://www.moraph.com/solutions).

## The checklist

1. **List every solicitation and contract that carries 52.204-21, and record which ones may put Federal contract information on company systems.** (Contracts manager) Section 4.1903 requires the contracting officer to insert the clause when the contractor or a subcontractor at any tier may have Federal contract information residing in or transiting through its information system, and section 4.1902 applies the subpart to all acquisitions other than commercially available off-the-shelf items when a contractor’s information system may contain Federal contract information [1]. Keeping a register of contracts with the clause is our suggestion.
2. **Write down what counts as Federal contract information on each contract, and what does not.** (Contracts manager, with the program manager) Paragraph (a) 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, and excludes information the Government provides to the public and simple transactional information, such as that needed to process payments [2]. Recording the call for each contract is our suggestion.
3. **Draw the boundary of the covered contractor information systems: every system owned or operated by the company that processes, stores or transmits that information.** (IT director) Paragraph (a) defines a covered contractor information system as an information system owned or operated by a contractor that processes, stores or transmits Federal contract information, and an information system as a discrete set of information resources organized for the collection, processing, maintenance, use, sharing, dissemination or disposition of information [2]. Keeping the boundary as a diagram or inventory is our suggestion.
4. **Limit access to authorized users, processes acting for them and devices, and limit each user to the transactions and functions they are permitted to run.** (Identity and access lead) Paragraph (b)(1)(i) and (ii) require these two access controls [2]. Reviewing access lists on a fixed schedule is our suggestion.
5. **Identify every user, process and device, and authenticate each one before it gets access.** (Identity and access lead) Paragraph (b)(1)(v) requires identifying information system users, processes acting on behalf of users, or devices, and (b)(1)(vi) requires authenticating or verifying those identities as a prerequisite to allowing access [2]. The clause does not name a method; choosing multifactor authentication is our suggestion.
6. **Verify and control connections to external systems and control what staff post or process on public-facing systems.** (Network and security engineer, with communications) Paragraph (b)(1)(iii) requires verifying and controlling or limiting connections to and use of external information systems, and (b)(1)(iv) requires controlling information posted or processed on publicly accessible information systems [2]. A review step before anything is published to a public site is our suggestion.
7. **Monitor, control and protect communications at the external boundary and key internal boundaries, and put publicly accessible components on separate subnetworks.** (Network and security engineer) Paragraph (b)(1)(x) requires monitoring, controlling and protecting organizational communications at the external boundaries and key internal boundaries, and (b)(1)(xi) requires subnetworks for publicly accessible system components that are physically or logically separated from internal networks [2].
8. **Limit physical access to systems, equipment and the rooms they are in; escort and monitor visitors; keep physical access logs; and manage badges and keys.** (Facilities manager) Paragraph (b)(1)(viii) requires limiting physical access to authorized individuals, and (b)(1)(ix) requires escorting visitors and monitoring visitor activity, maintaining audit logs of physical access, and controlling and managing physical access devices [2].
9. **Sanitize or destroy any media holding Federal contract information before disposal or reuse, and keep a record of it.** (IT operations) Paragraph (b)(1)(vii) requires sanitizing or destroying information system media containing Federal contract information before disposal or release for reuse [2]. Keeping a disposal record is our suggestion.
10. **Run a process to identify, report and correct flaws in a timely manner, with a patching target the company writes down.** (IT operations) Paragraph (b)(1)(xii) requires identifying, reporting and correcting information and information system flaws in a timely manner [2]. The clause does not define timely; setting and recording a target is our suggestion.
11. **Run malicious code protection at the right points, keep it updated as new releases come out, scan systems periodically and scan files from outside sources in real time as they are downloaded, opened or executed.** (Security operations) Paragraph (b)(1)(xiii), (xiv) and (xv) require protection from malicious code at appropriate locations, updating it when new releases are available, and periodic scans of the system plus real-time scans of files from external sources [2].
12. **Put the substance of the clause, including the flowdown paragraph, in every subcontract where the subcontractor may have Federal contract information in or passing through its systems.** (Subcontracts manager) Paragraph (c) requires this flowdown, including in subcontracts for commercial products or commercial services, other than commercially available off-the-shelf items [2]. Asking subcontractors to confirm in writing that they meet the fifteen controls is our suggestion.
13. **Keep a short record for each control showing how it is met, and check where other safeguarding rules apply on top of the clause.** (Compliance lead) The clause asks for the controls, not for a written plan; the record is our suggestion. Paragraph (b)(2) says the clause does not relieve the contractor of other specific safeguarding requirements set by agencies or of the federal requirements for controlled unclassified information established by Executive Order 13556 [2].

## Sources

1. Electronic Code of Federal Regulations. 48 CFR subpart 4.19, Basic Safeguarding of Covered Contractor Information Systems (eCFR current to November 12, 2026; checked November 14, 2026). <https://www.ecfr.gov/current/title-48/chapter-1/subchapter-A/part-4/subpart-4.19> Checked November 14, 2026.
2. Electronic Code of Federal Regulations. 48 CFR 52.204-21, Basic Safeguarding of Covered Contractor Information Systems (NOV 2021) (eCFR current to November 12, 2026; checked November 14, 2026). <https://www.ecfr.gov/current/title-48/chapter-1/subchapter-H/part-52/subpart-52.2/section-52.204-21> Checked November 14, 2026.
3. FAR Council, Federal Register. Federal Acquisition Regulation: Revolutionary Federal Acquisition Regulation Overhaul Parts 1, 2, 4, 33, 39, 40, and 53 (proposed rule, FAR Case 2026-001, 91 FR 37550, June 23, 2026; API record checked November 14, 2026). <https://www.federalregister.gov/api/v1/documents/2026-12559.json> Checked November 14, 2026.

Published: November 14, 2026
Canonical URL: <https://insights.moraph.com/checklist-far-52-204-21-basic-safeguarding-fifteen-requirements>
Publisher: Moraph Insights
