DFARS 252.204-7012: What the Clause Requires

DFARS 252.204-7012 requires adequate security, including the NIST SP 800-171 requirements, on contractor information systems that handle covered defense information, and requires cyber incidents to be reported to DoD within 72 hours of discovery. The text DoD contracting officers use under class deviation 2026-O0025, revised September 3, 2026, dates it JUN 2026 and names NIST SP 800-171 Revision 2.

By Hemant Bundele

Last reviewed: November 17, 2026

Which version applies

The codified text of DFARS 252.204-7012 is dated MAY 2024 and is prescribed at DFARS 204.7304(c).

Since February 1, 2026, DoD contracting officers have used the version issued under class deviation 2026-O0025; its current text, in Revision 3 of September 3, 2026, names NIST SP 800-171 Revision 2 and its 110 requirements.

In the text DoD contracting officers use under class deviation 2026-O0025, the clause is headed “(JUN 2026) (DEVIATION 2026-O0025)” and prescribed at 240.370-5(c), for solicitations and contracts other than those solely for commercially available off-the-shelf items.

The deviation's original text, effective February 1, 2026, still dated the clause MAY 2024 and named no NIST SP 800-171 revision.

The codified text is unchanged, so read the clauses in your contract to see which version it carries.

What changed between the MAY 2024 and JUN 2026 texts

  • In paragraph (b)(2)(i), the JUN 2026 text adds “Revision 2” after the title of NIST SP 800-171 and links to the Revision 2 PDF, where the codified text names no revision and links to NIST's publications page.
  • Both texts keep the words “in effect at the time the solicitation is issued or as authorized by the Contracting Officer” after that title.
  • The definition of technical information points to DFARS 252.227-7989 in the JUN 2026 text and to 252.227-7013 in the codified text.
  • The prescription moves from DFARS 204.7304(c) to 240.370-5(c).
  • A word-by-word comparison found no other change of substance; the remaining differences are formatting, such as quotation marks around defined terms and a lowercased “information technology”.

Key definitions

Covered defense information is “unclassified controlled technical information or other information, as described in the Controlled Unclassified Information (CUI) Registry” that “requires safeguarding or dissemination controls pursuant to and consistent with law, regulations, and Governmentwide policies”.

It must also be either “[m]arked or otherwise identified in the contract, task order, or delivery order and provided to the contractor by or on behalf of DoD in support of the performance of the contract” or “[c]ollected, developed, received, transmitted, used, or stored by or on behalf of the contractor in support of the performance of the contract.”

A covered contractor information system is “an unclassified information system that is owned, or operated by or for, a contractor and that processes, stores, or transmits covered defense information.”

A cyber incident means “actions taken through the use of computer networks that result in a compromise or an actual or potentially adverse effect on an information system and/or the information residing therein.”

These definitions read the same in the codified text and in the JUN 2026 text.

Adequate security: paragraph (b)

Paragraph (b) requires the contractor to provide adequate security on all covered contractor information systems.

For a system that is part of an IT service or system operated on behalf of the Government, cloud computing services are subject to DFARS 252.239-7010, and any other such service or system to the security requirements specified elsewhere in the contract.

For every other covered contractor information system, paragraph (b)(2)(i) of the JUN 2026 text applies NIST SP 800-171 Revision 2 “in effect at the time the solicitation is issued or as authorized by the Contracting Officer.”

The security requirements in CMMC Level 2 are identical to the 110 requirements in NIST SP 800-171 Revision 2, even though NIST has withdrawn Revision 2 and replaced it with Revision 3.

The notice to the DoD CIO

Paragraph (b)(2)(ii)(A) has the contractor implement NIST SP 800-171 “as soon as practical, but not later than December 31, 2017.”

It also says that, for all contracts awarded prior to October 1, 2017, the contractor notifies the DoD CIO, within 30 days of contract award, of any NIST SP 800-171 security requirements not implemented at the time of award.

Variances

A contractor submits requests to vary from NIST SP 800-171 in writing to the Contracting Officer, for consideration by the DoD CIO.

It need not implement a requirement that an authorized representative of the DoD CIO adjudicates as nonapplicable, or as having an alternative but equally effective security measure.

If the DoD CIO has already adjudicated such a request, the contractor gives the Contracting Officer a copy of that approval when asking for it to be recognized under the contract.

Cloud service providers

If the contractor uses an external cloud service provider to store, process or transmit covered defense information, it must require and ensure that the provider meets security requirements equivalent to the FedRAMP Moderate baseline.

The provider must also comply with paragraphs (c) through (g), on cyber incident reporting, malicious software, media preservation and protection, access for forensic analysis, and damage assessment.

A cloud service provider that handles CUI must meet the FedRAMP requirements in DFARS 252.204-7012.

Other security measures and the system security plan

Paragraph (b)(3) has the contractor apply other security measures when it reasonably determines they may be required, and says “These measures may be addressed in a system security plan.”

The absence of a system security plan results in a finding that “an assessment could not be completed due to incomplete information and noncompliance with DFARS clause 252.204-7012.”

The system security plan guide covers what the plan has to describe.

Cyber incident reporting: paragraph (c)

Paragraph (c) applies when the contractor discovers a cyber incident that affects a covered contractor information system or the covered defense information on it, or that affects its ability to perform contract requirements designated as operationally critical support.

The contractor then reviews for evidence of compromise of covered defense information, including compromised computers, servers, specific data and user accounts.

The clause sets the deadline through its definition of “rapidly report”.

It requires cyber incidents to be reported to DoD within 72 hours of discovery.

Reports go to DoD at https://dibnet.dod.mil, and each report includes at least the required elements listed there.

To report, the contractor or subcontractor must have or acquire a DoD-approved medium assurance certificate.

Malicious software, media and forensic access: paragraphs (d) to (g)

  • Malicious software (d). Malicious software found and isolated in connection with a reported cyber incident goes to the DoD Cyber Crime Center (DC3), following the instructions of DC3 or the Contracting Officer, and not to the Contracting Officer.
  • Media preservation (e). The contractor preserves and protects images of all known affected information systems and all relevant monitoring and packet capture data for at least 90 days from submitting the cyber incident report, so DoD can request the media or decline interest.
  • Forensic access (f). On request by DoD, the contractor gives DoD access to additional information or equipment necessary to conduct a forensic analysis.
  • Damage assessment (g). If DoD elects to conduct a damage assessment, the Contracting Officer will request the damage assessment information gathered under paragraph (e).

Subcontracts: paragraph (m)

Paragraph (m) requires the contractor to include the clause, without alteration except to identify the parties, in subcontracts for operationally critical support or whose performance will involve covered defense information, including subcontracts for commercial products or commercial services.

The contractor determines whether the information a subcontractor needs keeps its identity as covered defense information, and consults the Contracting Officer if necessary.

Subcontractors must notify the prime contractor, or the next higher-tier subcontractor, when they submit a request to vary from a NIST SP 800-171 security requirement, and give it the incident report number DoD assigns when they report a cyber incident.

Since February 1, 2026, DoD contracting officers have used a revised DFARS Part 240, issued as class deviation 2026-O0025, in place of the codified text.

Neither the deviation's original text nor its Revision 3 of September 3, 2026, prescribes 252.204-7019 or 252.204-7020.

Instead it prescribes 252.240-7997, which defines only two kinds of assessment, Medium and High, both conducted by Government personnel.

Revision 3 prescribes 252.204-7021, dated NOV 2025, at 240.371-5(a).

The required level is written into the contract through DFARS 252.204-7021, which requires you to have and maintain a current status at that level for the duration of the contract.

The SPRS score guide covers how these clauses affect what goes into SPRS; the Level 2 self-assessment guide, the system security plan guide and the POA&M rules guide cover the NIST SP 800-171 work itself.

For where third-party assessment stands today, see the CMMC compliance overview.

How CMMCSync helps

The Maintain plan covers CMMC Level 2 readiness: SPRS score tracking, POA&M management and a Mock Assessment, with document exports that carry no draft watermark. The SSP Generator turns your organization profile and control statuses into a system security plan you can version and export. See what each plan includes on the pricing page.

Sources

  1. DoD class deviation 2026-O0025, Revision 3 (September 3, 2026), with DFARS 252.204-7012 (JUN 2026) (DEVIATION 2026-O0025) in Attachment 1
  2. DoD class deviation 2026-O0025, FAR Overhaul Part 40 and DFARS Part 240 (effective February 1, 2026)
  3. DoD class deviations for the FAR overhaul (index)
  4. DFARS 252.204-7012, Safeguarding Covered Defense Information and Cyber Incident Reporting (codified text, MAY 2024)
  5. DFARS 252.204-7021, Contractor Compliance with the CMMC Level Requirements
  6. NIST SP 800-171 DoD Assessment Methodology, Version 1.2.1 (June 24, 2020)
  7. NIST SP 800-171 Revision 2, Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations
  8. NIST SP 800-171 Revision 2 security requirements (CSV)
  9. 32 CFR 170.14, CMMC Model
  10. 32 CFR 170.19, CMMC scoping

General information, not legal advice.

Stay assessment-ready between assessments.

Start with Foundations (Free) for the Level 1 self-assessment, or talk to the founder about what your contract requires.

Free to start — no application, no quote call. Cancel paid plans anytime.