Where the clause stands (checked November 15, 2026)
- As codified. The clause in the DFARS at acquisition.gov is dated May 2024 and is prescribed at DFARS 204.7304(c) for all DoD solicitations and contracts, commercial ones included, except those solely for commercially available off-the-shelf (COTS) items. The eCFR shows no amendment to it since May 30, 2024.
- Under DoD's class deviation. DoD is rewriting the DFARS alongside the FAR Overhaul. Class Deviation 2026-O0025, Revision 3 (September 3, 2026) tells DoD contracting officers to use a revised DFARS Part 240 in place of the codified text. The clause keeps its number, is dated "JUN 2026 (DEVIATION 2026-O0025)", and is prescribed at 240.370-5(c). We compared the two versions: apart from a renumbered cross-reference in one definition, the only change is that the deviation names NIST SP 800-171 Revision 2 where the codified clause names NIST SP 800-171 without a revision.
- CMMC sits on top of it, and doesn't replace it. DFARS 252.204-7021 adds an assessed CMMC status. When DoD suspended CMMC Phase 2 on July 13, 2026, the class deviation above recorded that the suspension memorandum still requires baseline compliance with NIST SP 800-171 Rev 2 under this clause.
- Nothing proposes to remove it. The FAR Overhaul proposed rule of June 23, 2026 would add a governmentwide CUI clause to the FAR (proposed 52.240-7) and cites this clause's 72-hour reporting as the standard it aligns with. That rule isn't final, and it doesn't amend the DFARS.
So a DoD contract may carry either version, depending on when and how it was awarded. The paragraph letters below are the same in both.
What the clause requires
The clause applies to covered defense information (CDI): unclassified controlled technical information, or other information described in the CUI Registry that requires safeguarding or dissemination controls, which is either marked or identified in the contract and provided by or for DoD, or collected, developed, received, transmitted, used or stored by the contractor in support of the contract. A covered contractor information system is an unclassified system, owned or operated by or for a contractor, that processes, stores or transmits CDI.
- Adequate security, paragraph (b). For a system that isn't operated on behalf of the government, the security requirements of NIST SP 800-171. A request to vary from one goes in writing to the contracting officer, for the DoD CIO to decide.
- Cloud, paragraph (b)(2)(ii)(D). An external cloud service that stores, processes or transmits CDI must meet requirements equivalent to the FedRAMP Moderate baseline and comply with the clause's incident paragraphs, (c) to (g).
- Incident reporting, paragraph (c). On discovering a cyber incident that affects a covered system, the CDI on it, or the contractor's ability to provide operationally critical support, review for evidence of compromise and report to DoD at dibnet.dod.mil within 72 hours of discovery. Reporting needs a DoD-approved medium assurance certificate.
- After a report, paragraphs (d) to (g). Send malicious software you isolate to the DoD Cyber Crime Center (not to the contracting officer), preserve images of affected systems and relevant monitoring and packet-capture data for at least 90 days from the report, and give DoD access for forensic analysis or a damage assessment if it asks.
DFARS 204.7302(d) adds that a reported incident is not, by itself, evidence that the contractor failed to provide adequate security.
How it flows down to subcontractors
Paragraph (m) is the flow-down, and it is stricter than most:
- Which subcontracts. Those for operationally critical support, and those whose performance will involve covered defense information. Subcontracts for commercial products and commercial services are included. There is no dollar threshold.
- The whole clause, unaltered. The clause goes in "without alteration, except to identify the parties", including paragraph (m) itself, so it carries on down the tiers. The other clauses in these guides ask only for their "substance".
- The prime decides whether it applies. The contractor determines whether the information the sub needs keeps its identity as CDI and needs protecting under the clause, and consults the contracting officer if necessary. If a sub gets no CDI and gives no operationally critical support, the clause doesn't flow to it.
- Two duties the sub owes you. The prime must require each sub to tell it (or the next tier up) when the sub asks the contracting officer for a variance from a NIST SP 800-171 requirement, and to give it the incident report number DoD assigns, as soon as practicable, when the sub reports an incident.
- Subs report to DoD themselves. Under DFARS 204.7302(b) a subcontractor reports its incident directly to DoD, and the report number travels up tier by tier until it reaches the prime. The incident report doesn't go through you.
What to keep for each sub that gets CDI
The clause tells a prime what to put in the subcontract. It doesn't list what to collect. In practice a file that answers a contracting officer's questions holds:
- Your own decision on whether the sub receives CDI or provides operationally critical support, with the date
- The subcontract with 252.204-7012 in it, in the version your prime contract carries
- The sub's statement that NIST SP 800-171 is implemented on the systems that will hold the CDI, which revision, and any variance it has asked for
- The cloud services it uses for CDI, and whether each meets the FedRAMP Moderate equivalent
- Whether it holds a medium assurance certificate, since it can't file an incident report without one
- A named contact for incidents, and its agreement to give you the DoD report number
The assessment side (the SPRS score and the CMMC status) is in the guide to 252.204-7019 and -7020 and the CMMC flow-down guide. None of it matters if the sub can't be awarded work at all, so start with the pre-award screening checklist.
How Watch helps
- The supplier portal sends a DFARS 252.204-7012 questionnaire that follows the clause: whether the sub will handle covered defense information, NIST SP 800-171 and which revision, the system security plan, variance requests, cloud services and FedRAMP Moderate equivalence, 72-hour reporting, the medium assurance certificate, the 90-day preservation, and giving you the incident report number. It is signed with the signer's name and title
- An answer that needs a look (for example, NIST SP 800-171 not yet implemented, or no medium assurance certificate) becomes a finding on that supplier
- The "DoD subcontract with CUI" requirement template holds each sub to an active SAM.gov registration, no exclusions or screening hits, a CMMC status, an SPRS score and the signed 7012 questionnaire, and shows what is missing
- Every answer is kept dated, next to the sub's public record, and comes out in the per-supplier evidence package
Watch doesn't assess anyone's network, doesn't read SPRS or any DoD system, and doesn't report incidents: it holds what your subs tell you. It isn't a CUI system, so don't upload covered defense information to it.