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.

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.

The checklist

Tick the steps as you go. The ticks are kept in this browser only; nothing is sent to us.

  1. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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].

Spotted an error? Tell us and we will check it and correct the checklist where needed.

  • FAR 52.204-21
  • Federal contract information
  • federal contractors
  • access control
  • subcontract flowdown
  • FAR overhaul