# DFARS 252.204-7012: Safeguarding Covered Defense Information and Cyber Incident Reporting

**In short:** The clause requires defense contractors to provide adequate security on covered contractor information systems, which for systems not operated on the government's behalf means the security requirements of NIST SP 800-171, and to report cyber incidents to the Defense Department within 72 hours of discovery. After an incident, contractors must preserve images of affected systems and relevant monitoring data for at least 90 days from the report, and a cloud service used for covered defense information must meet security requirements equivalent to the FedRAMP Moderate baseline. The current codified clause is dated May 2024 and set December 31, 2017 as the latest date to implement NIST SP 800-171.

48 CFR 252.204-7012 (DFARS clause; prescribed at DFARS 204.7304(c)) · Government · Security & Resilience. Published November 14, 2026. Last reviewed November 14, 2026.

## At a glance

- Citation: 48 CFR 252.204-7012 (DFARS clause; prescribed at DFARS 204.7304(c))
- Issued by: Department of Defense
- Type: Final rule
- Status: Effective (as of November 14, 2026) [1] Class Deviation 2026-O0025, Revision 3 tells contracting officers to use an attached revised DFARS part 240 in place of the codified text; it keeps this clause, prescribed at 240.370-5(c) and dated JUN 2026 (DEVIATION 2026-O0025). The deviation also implements the Department of War Chief Information Officer's memorandum of July 13, 2026, which requires baseline compliance with NIST SP 800-171 Rev 2 under this clause and suspends the November 2026 CMMC Phase 2 transition. [5]
- Applies to: Defense Department solicitations and contracts, including those for commercial products and commercial services, except those solely for commercially available off-the-shelf (COTS) items; the contractor must flow the clause down to subcontracts for operationally critical support or whose performance will involve covered defense information.
- Jurisdiction: United States (federal)

## Key dates

Each date ends with the number of its source in "Sources". Dates were checked on November 14, 2026 unless the row gives another date.

| Date | Kind | What | Source |
|---|---|---|---|
| August 26, 2015 | Published | Interim rule (DFARS Case 2013-D018) published in the Federal Register (80 FR 51739) | [2] |
| August 26, 2015 | Effective | Interim rule takes effect | [2] |
| December 30, 2015 | Published | Second interim rule published (80 FR 81472), giving contractors more time to implement NIST SP 800-171 | [3] |
| December 30, 2015 | Effective | Second interim rule takes effect | [3] |
| October 21, 2016 | Published | Final rule published in the Federal Register (81 FR 72986) | [4] |
| October 21, 2016 | Effective | Final rule takes effect | [4] |
| December 31, 2017 | Deadline | Latest date for contractors to implement NIST SP 800-171 on covered contractor information systems. Paragraph (b)(2)(ii)(A) of the clause: as soon as practical, but not later than this date. | [1] |

## What it changed

The clause comes from DFARS Case 2013-D018, an interim rule of August 26, 2015 that implemented contractor reporting on network penetrations required by the National Defense Authorization Acts for fiscal years 2013 and 2015 and set Defense Department policy on buying cloud computing services. A second interim rule of December 30, 2015 gave contractors more time to implement NIST SP 800-171, and the final rule of October 21, 2016 adopted the interim rule with changes.

## Not listed

- For contracts awarded before October 1, 2017, the clause required notice to the DoD CIO of any NIST SP 800-171 requirement not implemented, within 30 days of contract award. That is a period from each award, not a calendar date, so it is not listed. [1]
- The Revision 3 memorandum says it is effective immediately and supersedes Revision 2, issued July 16, 2026, but its text does not state its own issue date: it was signed September 3, 2026 (digital signature), the only date the memorandum shows for itself. A signature date is not an issue, publication or effective date, so no date is listed for it. [5]

## Sources

1. Electronic Code of Federal Regulations (Office of the Federal Register). 48 CFR 252.204-7012, Safeguarding Covered Defense Information and Cyber Incident Reporting (current text, clause dated MAY 2024, up to date as of November 12, 2026). <https://www.ecfr.gov/current/title-48/section-252.204-7012> Checked November 14, 2026.
2. Office of the Federal Register (Federal Register API). Defense Federal Acquisition Regulation Supplement: Network Penetration Reporting and Contracting for Cloud Services (DFARS Case 2013-D018), interim rule, FR Doc. 2015-20870. <https://www.federalregister.gov/api/v1/documents/2015-20870.json> Checked November 14, 2026.
3. Office of the Federal Register (Federal Register API). Defense Federal Acquisition Regulation Supplement: Network Penetration Reporting and Contracting for Cloud Services (DFARS Case 2013-D018), second interim rule, FR Doc. 2015-32869. <https://www.federalregister.gov/api/v1/documents/2015-32869.json> Checked November 14, 2026.
4. Office of the Federal Register (Federal Register API). Defense Federal Acquisition Regulation Supplement: Network Penetration Reporting and Contracting for Cloud Services (DFARS Case 2013-D018), final rule, FR Doc. 2016-25315. <https://www.federalregister.gov/api/v1/documents/2016-25315.json> Checked November 14, 2026.
5. Office of the Assistant Secretary of War for Acquisition and Sustainment, Defense Pricing, Contracting, and Acquisition Policy. Class Deviation 2026-O0025, Revision 3: Revolutionary FAR Overhaul Part 40, DFARS Part 240. <https://www.acq.osd.mil/dpap/dars/classdev/DFARS_RFO/Part-240/2026-O0025_Rev3_TAB_A_Deviation_Memo.pdf> Checked November 14, 2026.

Last reviewed: November 14, 2026
Canonical URL: <https://insights.moraph.com/rules/dfars-252-204-7012>
Publisher: Moraph Insights
