# DFARS 252.204-7012 safeguarding and 72-hour cyber incident reporting, explained

The DoD clause that protects covered defense information on contractor systems and requires cyber incidents to be reported within 72 hours of discovery. Class Deviation 2026-O0025, Revision 3, signed September 3, 2026 (digital signature), carries a revised text that names NIST SP 800-171 Revision 2.

Explainer · Government · Security & Resilience. Published November 14, 2026. Last reviewed November 14, 2026.

## At a glance

- DFARS 252.204-7012 requires defense contractors to provide adequate security on covered contractor information systems and to report cyber incidents to DoD at dibnet.dod.mil within 72 hours of discovery.
- Systems not operated on the Government’s behalf follow NIST SP 800-171; a contractor that stores, processes or transmits covered defense information with an external cloud provider must ensure the provider meets requirements equivalent to the FedRAMP Moderate baseline.
- After an incident: review for compromise, report within 72 hours with a DoD-approved medium assurance certificate, send malware to DC3, preserve and protect images of known affected systems and relevant monitoring and packet capture data for at least 90 days from submission of the report, give DoD access on request for forensic analysis, and provide damage assessment information if DoD asks.
- Two texts as checked on November 14, 2026: the codified MAY 2024 clause in the eCFR, and the JUN 2026 deviation text in Class Deviation 2026-O0025, Revision 3, signed September 3, 2026 (digital signature), which names NIST SP 800-171 Revision 2.
- The clause flows down to subcontracts that involve covered defense information or operationally critical support; subcontractors report directly to DoD and pass the incident report number up the chain.

DFARS 252.204-7012 is the Department of Defense (DoD) contract clause that tells defense contractors how to protect covered defense information on their own systems and how fast to report a cyber incident: within 72 hours of discovery [1]. This explainer covers the two texts of the clause now in circulation, what it protects, the security baseline, the duties that start when an incident is discovered, what DoD does with a report, and how the clause reaches subcontractors. It describes the clause and is not legal advice; which text governs a given contract is a question for counsel and the contracting officer.

## Two texts of one clause

The codified clause in the eCFR is dated MAY 2024 and is prescribed at DFARS 204.7304(c) [1]. Its source note lists amendments from 80 FR 51745 (August 26, 2015) through 89 FR 46821 (May 30, 2024) [1]. As checked on November 14, 2026, the eCFR showed title 48 up to date as of November 12, 2026, and no version of the section newer than May 30, 2024 [1].

A second text comes from the Revolutionary FAR Overhaul. Class Deviation 2026-O0025, Revision 3, signed September 3, 2026 (digital signature), supersedes an earlier revision [2]. It tells contracting officers to use an attached revised DFARS part 240, Information Security and Supply Chain Security, in lieu of the text codified at 48 CFR chapter 2 [2]. In that attachment the clause is dated JUN 2026 (DEVIATION 2026-O0025) and is prescribed at 240.370-5(c) [2]. The deviation stays in effect until rescinded or incorporated into the FAR, DFARS and DFARS PGI [2]. DoD’s page of DFARS overhaul class deviations lists Revision 3, dated September 3, 2026, as the posted version [3].

The two texts differ on the security standard. The codified clause points to NIST SP 800-171 “in effect at the time the solicitation is issued or as authorized by the Contracting Officer” [1]. The deviation text names NIST SP 800-171 Revision 2, with the same qualifier [2]. NIST published Revision 3 in May 2024, superseding Revision 2 of January 28, 2021 [4]. Read on its own, the codified wording could point to a later revision, while the deviation text fixes Revision 2; we state this as a difference between the texts and do not resolve it. The deviation’s separate instruction on CMMC requirements also refers to NIST SP 800-171 Rev 2 under 252.204-7012 [2]; our [CMMC explainer](https://insights.moraph.com/cmmc-levels-and-dfars-phase-in-explained) covers that instruction. A smaller change: the deviation’s definition of technical information refers to the clause at 252.227-7989, where the codified clause refers to 252.227-7013 [1] [2].

## What the clause protects and where it goes

Covered defense information is unclassified controlled technical information or other information described in the CUI Registry that needs safeguarding or dissemination controls, and that is either marked or identified in the contract and provided by or for DoD, or collected, developed, received, transmitted, used or stored by or for the contractor in support of the contract [1]. A covered contractor information system is an unclassified system owned, or operated by or for, a contractor that processes, stores or transmits that information [1]. The clause also reaches incidents that affect a contractor’s ability to provide operationally critical support, meaning supplies or services the Government designates as critical for airlift, sealift, intermodal transportation or logistical support in a contingency operation [1].

Under the deviation’s prescription, contracting officers insert the clause in solicitations and contracts, including those for commercial products and commercial services, except those solely for commercially available off-the-shelf (COTS) items [2].

## The security baseline

The contractor must provide adequate security on all covered contractor information systems [1]. Systems that are part of an IT service or system operated on behalf of the Government follow the cloud clause 252.239-7010 or other security terms in the contract [1]. Other covered systems follow NIST SP 800-171 [1].

Requests to vary from a NIST SP 800-171 requirement go in writing to the contracting officer for the DoD CIO to consider, and a requirement the DoD CIO adjudicates as not applicable, or as met by an equally effective alternative, need not be implemented [1]. A contractor that uses an external cloud service provider for covered defense information must require and ensure that the provider meets security requirements equivalent to the FedRAMP Moderate baseline and complies with the clause’s incident reporting, malware, media, forensic access and damage assessment paragraphs [1]. The contractor also applies other measures it reasonably determines are needed, which may be addressed in a system security plan [1].

## Five duties once an incident is discovered

A cyber incident is defined as actions taken through computer networks that result in a compromise or an actual or potentially adverse effect on an information system or the information on it [1]. Once one is discovered, the clause sets these duties [1]:

- **Review.** Look for evidence of compromise of covered defense information, including compromised computers, servers, data and user accounts, and analyze other systems on the network that may have been accessed [1].
- **Report within 72 hours.** “Rapidly report” means within 72 hours of discovery, and reports go to DoD at dibnet.dod.mil with at least the elements required there [1]. Reporting requires a DoD-approved medium assurance certificate [1].
- **Submit malware.** Malicious software discovered and isolated in connection with a reported incident goes to the DoD Cyber Crime Center (DC3), never to the contracting officer [1].
- **Preserve media.** Preserve and protect images of all known affected information systems identified in the review, and all relevant monitoring and packet capture data, for at least 90 days from submission of the report, so DoD can request the media or decline interest [1].
- **Give access.** On DoD’s request, the contractor provides access to additional information or equipment needed for forensic analysis; if DoD elects to conduct a damage assessment, the contracting officer will request all of the damage assessment information gathered under the preservation duty [1].

Because the 72 hours run from discovery [1], in our view the certificate and the preservation steps are better arranged before any incident; that is our view, not a requirement of the clause.

## What DoD does with a report

The report is treated as information created by or for DoD [1]. DoD must protect contractor attributional or proprietary information against unauthorized use or release, and the contractor is asked to identify and mark such information to the maximum extent practicable [1]. Because the report counts as created by or for DoD, the clause allows its use and release outside DoD for listed purposes, including to entities that may help diagnose or mitigate incidents, to counterintelligence and law enforcement, and for national security purposes, and for any other lawful Government purpose, subject to applicable restrictions [1]. Support contractors that receive such information work under 252.204-7009, which limits their use of it to supporting the Government’s activities under 252.204-7012 [2].

The deviation’s policy text states that a reported cyber incident must not, by itself, be read as evidence that the contractor failed to provide adequate security [2]. Before assessing compliance after a report, the contracting officer must consult the DoD component CIO or cyber security office [2]. Under the deviation’s PGI text, DC3 sends the report to the contracting officers identified on the incident collection format, and if the requiring activity asks for a compliance assessment, the contracting officer requests a description of how the contractor implemented NIST SP 800-171 to judge whether controls were inadequate or not in place at the time [2].

## Subcontractors and other duties

The prime contractor includes the clause, without alteration except to identify the parties, in subcontracts for operationally critical support or whose performance will involve covered defense information, including commercial subcontracts [1]. Subcontractors must tell the prime, or the next higher tier, when they ask to vary from a NIST SP 800-171 requirement, and must pass on the incident report number DoD assigns as soon as practicable after reporting [1]. Under the deviation’s policy text, contractors and subcontractors report incidents directly to DoD, and each tier passes the report number up until it reaches the prime [2].

The clause does not displace other safeguarding or incident reporting duties under other contract clauses or other federal statutes and regulations [1]. Which other reporting rules apply to a given contractor is a question for counsel; CIRCIA and CISA’s rulemaking under it are covered in our [CIRCIA explainer](https://insights.moraph.com/circia-cyber-incident-reporting-rule-status-explained).

Status as checked on November 14, 2026: the codified clause is the MAY 2024 text in the eCFR, and Class Deviation 2026-O0025, Revision 3, signed September 3, 2026 (digital signature), carries the JUN 2026 deviation text. The two texts carry different clause dates, MAY 2024 and JUN 2026 (DEVIATION 2026-O0025) [1] [2].

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

## Sources

1. Office of the Federal Register, National Archives (eCFR). 48 CFR 252.204-7012, Safeguarding Covered Defense Information and Cyber Incident Reporting (eCFR, up to date as of November 12, 2026). <https://www.ecfr.gov/current/title-48/chapter-2/subchapter-H/part-252/subpart-252.2/section-252.204-7012> Checked November 14, 2026.
2. Department of War, Defense Pricing, Contracting, and Acquisition Policy. Class Deviation 2026-O0025, Revision 3: Revolutionary FAR Overhaul Part 40, DFARS Part 240, with attachments, signed September 3, 2026 (digital signature). <https://www.acq.osd.mil/dpap/dars/classdev/DFARS_RFO/Part-240/2026-O0025_Rev3_TAB_A_Deviation_Memo.pdf> Checked November 14, 2026.
3. Defense Acquisition Regulations System, Defense Pricing, Contracting, and Acquisition Policy. DFARS Revolutionary FAR Overhaul Class Deviations. <https://www.acq.osd.mil/dpap/dars/dfars_far_overhaul_class_deviations.html> Checked November 14, 2026.
4. National Institute of Standards and Technology. NIST SP 800-171 Rev. 3, Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations. <https://csrc.nist.gov/pubs/sp/800/171/r3/final> Checked November 14, 2026.

Published: November 14, 2026
Canonical URL: <https://insights.moraph.com/dfars-252-204-7012-72-hour-cyber-incident-reporting-explained>
Publisher: Moraph Insights
