What Is DFARS?
DFARS, the Defense Federal Acquisition Regulation Supplement, is the Department of Defense’s set of contracting rules that adds to the Federal Acquisition Regulation (FAR). For defense contractors, its cybersecurity clauses decide how you protect Controlled Unclassified Information, which security standard you follow, and how fast you report a cyber incident.
Updated November 2026
DFARS in Six Facts
- Full Name
- Defense Federal Acquisition Regulation Supplement
- Where It Lives
- Title 48, Chapter 2 of the Code of Federal Regulations
- Who It Applies To
- DoD prime contractors and the subcontractors those clauses flow down to
- Core Cyber Clause
- DFARS 252.204-7012
- Security Standard
- NIST SP 800-171 Revision 2, with 110 security requirements
- Incident Reporting
- Within 72 hours of discovery, through the DoD’s DIBNet portal
What to Know About DFARS
The FAR sets the baseline rules for every federal agency’s purchasing. DFARS adds the requirements specific to the Department of Defense, and those requirements reach your company through the clauses written into your contracts and subcontracts.
DFARS Clauses Every Defense Contractor Should Know
Five clauses carry most of the cybersecurity weight in DoD contracts. If any of them appear in your contract, they apply to the systems that handle the covered information, and most of them flow down to your subcontractors.
- 252.204-7012
Safeguarding Covered Defense Information
The foundation. It requires “adequate security” on any system that processes, stores or transmits covered defense information, which means implementing NIST SP 800-171. It also sets the rules for cyber incident reporting, evidence preservation and cloud services, and it must be flowed down to subcontractors who handle that information.
- 252.204-7019
Notice of Assessment Requirements
Before award, you need a current NIST SP 800-171 DoD Assessment, no more than three years old, with your score posted in the Supplier Performance Risk System (SPRS).
- 252.204-7020
NIST SP 800-171 DoD Assessments
Defines the Basic, Medium and High assessments, gives the government access to assess your systems, and requires you to confirm your subcontractors have current scores in SPRS.
- 252.204-7021
CMMC Requirements
Requires the CMMC level named in the contract, kept current for the life of the contract, along with annual affirmations of continuing compliance and flow-down to subcontractors that handle FCI or CUI.
- 252.204-7025
Notice of CMMC Level Requirements
The solicitation provision. It tells bidders which CMMC level a contract requires and makes having that status in SPRS a condition of award eligibility.
What DFARS 7012 Requires
DFARS 7012 has appeared in DoD contracts since 2016, and it stays in force no matter where CMMC timelines land. These are its core obligations.
Implement NIST SP 800-171
Apply the 110 security requirements of NIST SP 800-171 to every system that handles covered defense information. A DoD class deviation keeps contracts pinned to Revision 2, even though NIST has published Revision 3.
Report Incidents Within 72 Hours
Report a cyber incident affecting covered defense information to the DoD within 72 hours of discovery through DIBNet. Reporting requires a DoD-approved medium assurance certificate, so get one before you need it.
Preserve Evidence for 90 Days
Keep images of affected systems and the relevant monitoring and packet capture data for at least 90 days from your report, in case the DoD asks for a forensic review.
Submit Malicious Software
If you find malicious software tied to the incident, submit it to the DoD Cyber Crime Center (DC3) as the clause directs.
Use Equivalent Cloud Security
Any external cloud service that stores, processes or transmits covered defense information must meet security requirements equivalent to the FedRAMP Moderate baseline and support the clause’s incident reporting rules. This is a common reason contractors move to Microsoft GCC High.
Flow It Down
Include the clause in subcontracts where the subcontractor will handle covered defense information. Subcontractors report incidents to the DoD and to the prime.
How DFARS Connects to CMMC
DFARS 7012 tells you to protect covered defense information with NIST SP 800-171. The Cybersecurity Maturity Model Certification (CMMC) program checks that you did. CMMC Level 2 uses the same 110 requirements, and clauses 7021 and 7025 bring CMMC status into contracts and solicitations.
The DoD has paused the move to required third-party CMMC certification while it reviews the program. That pause leaves the underlying DFARS obligations in place, so the work of implementing NIST SP 800-171 and keeping an accurate score in SPRS carries forward under any outcome. Learn more about CMMC compliance requirements and how your SSP, POA&M and SPRS score fit together.
Still in Force Today
- DFARS 252.204-7012 safeguarding and 72-hour incident reporting
- NIST SP 800-171 Revision 2 as the required standard
- A current self-assessment score posted in SPRS
- CMMC Level 1 and Level 2 self-assessments and annual affirmations where a contract requires them
DFARS Questions, Answered
What does DFARS stand for?
DFARS stands for Defense Federal Acquisition Regulation Supplement. It is the Department of Defense’s supplement to the Federal Acquisition Regulation, and it appears in Title 48, Chapter 2 of the Code of Federal Regulations.
What is the difference between FAR and DFARS?
The FAR is the main rulebook for purchasing across all federal agencies. DFARS adds rules that apply only to Department of Defense contracts. A DoD contract usually includes clauses from both, such as FAR 52.204-21 for basic safeguarding of Federal Contract Information and DFARS 252.204-7012 for covered defense information.
Who has to comply with DFARS?
Any company holding a DoD contract or subcontract that includes DFARS clauses. The cybersecurity clauses apply when your systems handle covered defense information or Federal Contract Information, and primes are required to flow them down to subcontractors who handle that information.
What does DFARS compliance mean for cybersecurity?
In practice it means implementing the 110 requirements of NIST SP 800-171 Revision 2, documenting them in a System Security Plan, posting a current assessment score in SPRS, reporting cyber incidents within 72 hours, preserving evidence for 90 days, and making sure any cloud service holding covered defense information meets FedRAMP Moderate equivalent security.
Does DFARS require NIST SP 800-171 Revision 2 or Revision 3?
Revision 2. NIST published Revision 3 in May 2024, but a DoD class deviation directs contracting officers to require Revision 2 under DFARS 7012 until the DoD rescinds it. It makes sense to understand Revision 3 now, since the DoD has signaled it intends to move to it. See our guide to NIST SP 800-171 Revision 3.
How quickly do you have to report a cyber incident under DFARS?
Within 72 hours of discovering it. Reports go through the DoD’s DIBNet portal, which requires a DoD-approved medium assurance certificate. Subcontractors also report to their prime contractor.
Is DFARS the same as CMMC?
No. DFARS is the regulation that puts requirements into your contract. CMMC is the program that verifies you meet them. They overlap because CMMC Level 2 assesses the same NIST SP 800-171 requirements that DFARS 7012 already requires.
What happens if a contractor does not comply with DFARS?
Noncompliance can cost you contract eligibility and expose your company to breach of contract claims. Misstating your cybersecurity status, including an inaccurate SPRS score, can also create liability under the False Claims Act, which the Department of Justice has pursued through its Civil Cyber-Fraud Initiative.