DFARS 252.204-7012
DFARS 252.204-7012 — Safeguarding Covered Defense Information and Cyber Incident Reporting — US Department of Defense (DoD)
Also known as: DFARS 7012, 252.204-7012, DFARS cybersecurity clause, Safeguarding Covered Defense Information
Official site Official change log Subscribe to DFARS 252.204-7012 (RSS)
At a glance
- Status
- In force
- Next deadline
- None announced
- Who must comply
- DoD contractors and subcontractors with covered contractor information systems that hold covered defense information, or that provide operationally critical support. source
- How it is assessed
- The contractor implements NIST SP 800-171 itself; DoD checks it through separate assessment clauses and CMMC. source
- Authority
- The Department of Defense issues the clause in the Defense Federal Acquisition Regulation Supplement; contracting officers insert it in solicitations and contracts. source
- Enforced by
- DoD enforces the clause through the contract: rapid incident reporting, evidence preservation and assessment of compliance after incidents. source
- Last change
- None recorded yet
The contract clause that makes NIST SP 800-171 binding on defense suppliers and requires a cyber incident affecting covered defense information to be reported to DoD within 72 hours, with media preserved for 90 days. It long predates CMMC and continues to apply on its own terms alongside it.
Recent changes
No changes recorded yet — we are watching, and nothing has been published.
Key dates
No upcoming dates- DoD CIO memo suspending CMMC Phase 2 requires baseline compliance with NIST SP 800-171 Rev 2 under DFARS 252.204-7012
- DFARS rule putting CMMC assessment requirements into DoD contracts takes effect
- Deadline in the clause for contractors to implement NIST SP 800-171
- Original DFARS safeguarding clause takes effect
Amendments
-
DFARS 252.204-7012 (MAY 2024) ErrataCurrent text
Editorial update of two outdated hyperlinks in the clause. source
-
DFARS 252.204-7012 (JAN 2023) Revision
Replaced "commercial items" terminology with "commercial products or commercial services" and edited the definition of technical information. source
-
DFARS 252.204-7012 (DEC 2019) Errata
Technical amendment updating internet hyperlinks in the clause. source
-
DFARS 252.204-7012 (OCT 2016) Revision
Final rule adopting, with changes, the 2015 interim rules on network penetration reporting and contracting for cloud services. source
-
Second interim rule (December 2015) Amendment
Gave contractors until 31 December 2017 to implement NIST SP 800-171 and narrowed the subcontract flowdown. source
Show 2 older amendments
-
First interim rule (August 2015) Major version
Renamed the clause "Safeguarding Covered Defense Information and Cyber Incident Reporting" and expanded it to covered defense information, with NIST SP 800-171 as the security baseline. source
-
Original clause (November 2013) Major version
Created the clause for safeguarding unclassified controlled technical information, effective 18 November 2013. source
Who it applies to
The clause binds DoD contractors whose systems hold covered defense information to NIST SP 800-171 and DoD's incident reporting rules.
- Security baseline
- Covered contractor information systems must implement NIST SP 800-171, in the version in effect when the solicitation is issued or as authorized by the contracting officer. source
- Rev. 2 baseline
- Since July 2026 DoD requires baseline compliance with NIST SP 800-171 Rev 2 under this clause. source
- Cloud services
- An external cloud provider holding covered defense information must meet security requirements equivalent to the FedRAMP Moderate baseline and the clause's incident duties. source
- Subcontracts
- The clause flows down without alteration to subcontracts for operationally critical support or involving covered defense information, including commercial ones. source
- Prescription
- Under class deviation 2026-O0025 the clause is prescribed for solicitations and contracts, including commercial ones, except those solely for COTS items. source
How compliance is assessed
The contractor implements NIST SP 800-171 itself; DoD checks it through separate assessment clauses and CMMC.
- Variances
- Requests to vary from NIST SP 800-171 go in writing to the contracting officer for DoD CIO consideration. source
- DoD assessments
- Under class deviation 2026-O0025, clause 252.240-7997 covers NIST SP 800-171 DoD Assessments in contracts. source
- CMMC
- CMMC Level 2 checks the requirements of NIST SP 800-171 Rev. 2; since July 2026 DoD permits Level 1 and Level 2 self-assessments in procurement requests. source source
Enforcement and penalties
DoD enforces the clause through the contract: rapid incident reporting, evidence preservation and assessment of compliance after incidents.
- 72-hour reporting
- Cyber incidents affecting covered defense information or operationally critical support must be reported to DoD at dibnet.dod.mil within 72 hours of discovery. source
- Media preservation
- Images of affected systems and relevant monitoring data must be kept for at least 90 days after the report. source
- Medium assurance certificate
- Reporting requires a DoD-approved medium assurance certificate. source
- After an incident
- Contracting officers consider reported incidents in assessing whether the contractor has met the clause's requirements. source
Documents
- Law text DFARS 252.204-7012 Safeguarding Covered Defense Information and Cyber Incident Reporting
- Law text DFARS Class Deviation 2026-O0025 Rev. 3 (DFARS Part 240; CMMC Phase 2 suspension)
- Guidance DoD Cyber Incident Reporting portal (DIBNet)
- Law text Final rule on network penetration reporting and cloud services (21 October 2016)
Verified against official sources on 18 October 2026. We monitor the official sources for this framework. Watching since 20 September 2026. Subscribe to DFARS 252.204-7012 (RSS)