Cybersecurity

U.S. DFARS 252.204-70xx

DFARS 252.204-7012 framework badge
Summarize with
ClaudeChatGPTPerplexityGoogle AI Mode
In this article
At a Glance
DFARS 252.204-70XX
  • Classification
    Category
    Cybersecurity
    Domain
    Cybersecurity
    Framework Family
    CMMC
  • Regulatory Context
    Type
    Regulation
    Legal Instrument
    Regulation
    Sector
    Defense Sector
    Industry
    Aerospace & Defense
  • Region / Publisher
    Region
    North America
    Region Detail
    United States
    Publisher
    Defense Acquisition Regulations System (DARS), U.S. Department of Defense
  • Versioning
    Version
    Clause 252.204-7012 (MAY 2024); 252.204-7019 and -7020 (NOV 2023); 252.204-7021 and -7025 (NOV 2025)
    Effective Date
    October 21, 2016 (final rule); clause revision MAY 2024
    Issue Date
    May 2024 (current clause revision)
  • Adoption
    Adoption Model
    Regulatory Compliance
    Implementation Complexity
    High
  • Official Reference
License Information

License included / downloadable: Yes

The clauses are U.S. federal regulation published free by the Defense Acquisition Regulations System on acquisition.gov and are included with the platform for reference.

Framework text is licensed by its publisher and is included only where stated above.

Official Resources
DFARS 252.204-7008 Compliance Clause
Defines requirements for safeguarding covered defense information in nonfederal systems.
DFARS 252.204-7012 Safeguarding Clause
Outlines safeguarding requirements and incident reporting for defense contractors.
NIST SP 800-171
Defines the security requirements for protecting Controlled Unclassified Information (CUI) in non-federal systems.
Key takeaways
  • DFARS 252.204-7012 requires DoD contractors to protect covered defense information with NIST SP 800-171 and report cyber incidents within 72 hours.
  • The clause has applied since the final rule of October 21, 2016 and flows down to subcontractors.
  • Clauses 252.204-7019 and -7020 require a current NIST SP 800-171 assessment score in SPRS; 252.204-7021 and -7025 carry the CMMC level.
  • Contractors document each covered system in a system security plan, report through DIBNet, and preserve images for 90 days.
  • SmartSuite Compliance Management holds the requirements and system security plans, with Cyber & IT Risk for incident records and 72-hour report evidence.

Overview

DFARS 252.204-7012 is the contract clause that requires Department of Defense (DoD) contractors to protect covered defense information on their systems with NIST SP 800-171 and to report cyber incidents to DoD within 72 hours of discovery. It is written into solicitations and contracts under the Defense Federal Acquisition Regulation Supplement (DFARS), has applied since the final rule of October 21, 2016, and flows down to subcontractors.

The Defense Acquisition Regulations System, part of the DoD, issues the DFARS, and the contracting officer enforces the clause through the contract. Neighboring clauses build on it: 252.204-7019 and -7020 require a current NIST SP 800-171 assessment score in the Supplier Performance Risk System (SPRS), and 252.204-7021 and provision 252.204-7025 carry the Cybersecurity Maturity Model Certification (CMMC) level requirement.

Contractors implement NIST SP 800-171 for each covered contractor information system, document it in a system security plan, post an assessment score, and keep an incident procedure that can report through DIBNet with a DoD-approved medium assurance certificate, preserve images for 90 days and flow the clause down.

Why does it matter?

Contractors that handle covered defense information win and keep DoD work only if they can show the clause is met. The clause is specific: it names the control set, the reporting deadline, the evidence to preserve and the clause to flow down, so a contractor can test itself paragraph by paragraph.

Key benefits include:

  • A defined data scope

Covered defense information is unclassified controlled technical information or other CUI that is marked in the contract or handled in support of it (paragraph (a)).

  • A named control set

Covered systems must meet NIST SP 800-171 in effect when the solicitation is issued, or as the contracting officer authorizes (paragraph (b)(2)(i)).

  • A 72-hour clock

"Rapidly report" means within 72 hours of discovery of any cyber incident that affects a covered system or its data (paragraphs (a) and (c)).

  • Evidence that must be kept

The contractor preserves images of affected systems and packet capture data for at least 90 days from the incident report (paragraph (e)).

  • Cloud and subcontractor reach

External cloud providers must meet FedRAMP Moderate equivalent requirements, and the clause flows down to subcontractors that handle covered defense information (paragraphs (b)(2)(ii)(D) and (m)).

How does it work?

The clause sets duties in order. Paragraph (b) requires adequate security: for systems run on behalf of the Government, cloud services follow DFARS 252.239-7010; other contractor systems follow NIST SP 800-171, with a contractor-requested variance reviewed by the DoD Chief Information Officer (CIO) and other measures added where risk calls for them. Paragraph (c) requires a review for compromise and a report through DIBNet.

The contractor needs a DoD-approved medium assurance certificate to report (paragraph (c)(3)). Malicious software goes to the DoD Cyber Crime Center, not to the contracting officer (paragraph (d)). On request the contractor gives DoD access to information or equipment for forensic analysis (paragraph (f)) and supports a damage assessment (paragraph (g)).

Paragraph (m) requires the clause, unaltered except to name the parties, in subcontracts for operationally critical support or where covered defense information is involved. Subcontractors tell the prime when they seek a variance and pass on the DoD incident report number.

Key Elements

  • Covered defense information and covered systems (paragraph (a))

The scope is defined by the data and the systems that process, store or transmit it, not by the contractor's whole network.

  • Adequate security and NIST SP 800-171 (paragraph (b))

Contractors implement the NIST SP 800-171 requirements, record gaps in a system security plan and plan of action, and may ask for a variance through the contracting officer.

  • Cyber incident reporting (paragraph (c))

Review for compromise, report within 72 hours through DIBNet, and hold a medium assurance certificate.

  • Malware, media and forensics (paragraphs (d) to (g))

Submit malware to the DoD Cyber Crime Center, preserve images and packet capture for 90 days, give access for forensic analysis and support damage assessments.

  • Assessment scores and CMMC (252.204-7019, -7020, -7021, -7025)

A current assessment, not more than three years old, must be posted to SPRS. Basic assessments are self-assessments; Medium and High assessments are done by the Government. CMMC statuses are required where a solicitation says so.

  • Flow-down (paragraph (m))

The clause passes to subcontractors that handle covered defense information, including for commercial products and services.

What does it cover?

The clause applies to contractors and subcontractors on DoD contracts that include it, and to their covered contractor information systems: unclassified systems owned or operated by or for the contractor that process, store or transmit covered defense information. It does not apply to classified systems or to information that is lawfully public without restriction.

What are its objectives?

The clause protects covered defense information on contractor systems and gives DoD visibility of incidents that affect it.

Implement NIST SP 800-171 on every covered contractor information system.

Report cyber incidents to DoD within 72 hours of discovery.

Preserve images and monitoring data for 90 days and support forensic analysis.

Hold a current assessment score in SPRS, and the CMMC status the solicitation requires.

Flow the clause down to subcontractors that handle covered defense information.

Framework in Context

The clause is one of several DFARS cybersecurity requirements. NIST SP 800-171 supplies its control set, the FedRAMP Moderate baseline sets the cloud expectation, and CMMC under 32 CFR part 170 adds assessments through clause 252.204-7021. DFARS 252.204-7021 took effect through a final rule on November 10, 2025, and the CMMC program phases in year by year from that date.

Common Framework Mappings

DFARS 252.204-7012 is often mapped to other defense and federal frameworks to simplify compliance, demonstrate control effectiveness, and harmonize cybersecurity requirements across DoD contracting and supply chain programs.

Mapped frameworks include:

CMMC (Cybersecurity Maturity Model Certification)

FAR 52.204-21

FedRAMP

ISO/IEC 27001

NIST Cybersecurity Framework

NIST SP 800-171

NIST SP 800-53

PCI DSS

SOC 2

SMARTSUITE

How SmartSuite Supports DFARS 252.204-7012

SmartSuite provides the system for managing controls, evidence, mappings, assessments, and reporting.

Use Compliance Management to hold the NIST SP 800-171 requirements, the system security plan and plan of action for each covered system, Cyber & IT Risk for incident records and the 72-hour report evidence, and Third Party Risk Management to track subcontractor flow-down.

Covered Systems and CDI Register

List each covered contractor information system, the contracts it supports and the covered defense information it handles (paragraph (a)).

NIST SP 800-171 Requirement Library

Assign an owner, implementation status and evidence to each requirement and record variance requests to the contracting officer (paragraph (b)(2)).

Assessment Score Tracking

Record the Basic, Medium or High assessment date, score out of 110 and SPRS posting, and flag assessments approaching three years old (252.204-7019 and -7020).

Incident Reporting Workflow

Time each incident from discovery against the 72-hour clock, capture the DIBNet report number and medium assurance certificate holder (paragraph (c)).

Evidence Preservation Log

Track image and packet capture preservation for 90 days, malware submissions and forensic access requests (paragraphs (d) to (f)).

Subcontractor Flow-Down

Record which subcontracts carry the clause, each subcontractor's variance notices and incident numbers, and CMMC levels flowed down (paragraph (m) and 252.204-7021).

Related frameworks

CIS Controls v8.1

CIS Controls v8.1 is a prioritized set of 18 Controls and 153 Safeguards, in three Implementation Groups, with a new Govern function.

CMMC 2.0

CMMC is the DoD program, 32 CFR Part 170, that requires contractors handling FCI or CUI to hold a Level 1, 2 or 3 status. Phase 2 was suspended on July 13, 2026.

FedRAMP Rev. 5

FedRAMP Rev5 is the legacy FedRAMP certification type: NIST SP 800-53 Rev. 5 baselines, 3PAO assessment and agency authorization for cloud services used by U.S. agencies.

ISO 27001:2022

ISO/IEC 27001:2022 specifies requirements for an information security management system: Clauses 4 to 10, risk treatment, the Statement of Applicability and 93 Annex A controls.

ISO 27002:2022

ISO/IEC 27002:2022 is the reference set of 93 information security controls in four themes, with attributes and implementation guidance, that supports an ISO/IEC 27001 ISMS.

NIST CSF 2.0

NIST CSF 2.0 (CSWP 29, February 26, 2024) is the voluntary cybersecurity framework with six Functions including Govern, 22 Categories, 106 Subcategories, Profiles and Tiers.

NIST 800-171 Rev.2

NIST SP 800-171 Rev. 2: 110 CUI security requirements in 14 families, withdrawn by NIST on May 14, 2024 but still the edition DFARS 252.204-7012 and CMMC Level 2 cite.

NIST 800-53 Rev.5

NIST SP 800-53 Rev. 5 is the NIST catalog of security and privacy controls in 20 families, mandatory for federal systems under OMB A-130 and FISMA; Release 5.2.0 issued August 27, 2025.

FAQ

Frequently Asked Questions For U.S. DFARS 252.204-70xx (Cybersecurity Clauses)

It requires contractors to provide adequate security on covered contractor information systems, meeting NIST SP 800-171 in effect when the solicitation is issued (paragraph (b)(2)), and to report cyber incidents within 72 hours of discovery (paragraph (c)). It also requires preserving images for 90 days and flowing the clause down to subcontractors.

It is unclassified controlled technical information or other CUI that is marked or identified in the contract, or collected, developed, received, transmitted, used or stored by the contractor in support of the contract (paragraph (a)). Public information without restriction is excluded.

They report through the DoD DIBNet portal and need a DoD-approved medium assurance certificate (paragraph (c)). Any malicious software they isolate is submitted to the DoD Cyber Crime Center, not to the contracting officer (paragraph (d)).

They require a current NIST SP 800-171 assessment, not more than three years old, with the summary score posted in the Supplier Performance Risk System. A Basic Assessment is a contractor self-assessment, while Medium and High assessments are conducted by the Government.

DFARS 252.204-7021 and provision 252.204-7025 require a CMMC status at the level the solicitation names, under 32 CFR part 170. They sit beside 252.204-7012 rather than replace it, and the CMMC rule has applied in contracts since November 10, 2025 in phases.

Put this framework to work in SmartSuite

Manage controls, risks, evidence, and audits in one platform designed for modern governance, risk, and compliance.