From A GRC Perspective, What Is Defense Federal Acquisition Regulation Supplement (DFARS)?
The five main DFARS clauses collectively establish the cybersecurity baseline for defense suppliers, imposing prescriptive requirements for system security, incident reporting, assessment and third-party certification.
DFARS cybersecurity clauses, particularly 252.204-7012 and -7021, along with the assessment clauses -7019 and -7020 (reorganized by a DoD class deviation in 2026), are no longer dormant regulatory obligations. They now represent a current compliance regime, grounded in NIST SP 800-171 and enforced through contractual terms, government assessments and civil litigation.
These DFARS clauses marked the end of the self-certification era. Defense contractors must now invest in defensible documentation, technical rigor and third-party assurance. Organizations that treat these clauses as operational mandates and not legal formalities will be better positioned to retain contracts, protect national security information and navigate DoD’s evolving cybersecurity landscape.
As enforcement continues to expand, the ability to prove compliance at any point in time through validated controls, accurate scoring and robust documentation has become the cornerstone of doing business in the Defense Industrial Base (DIB).
GRC-Focused Overview of DFARS
In response to escalating threats to defense supply chains, the US Department of Defense (DoD) codified a robust cybersecurity framework through a series of Defense Federal Acquisition Regulation Supplement (DFARS) clauses. These clauses are designed to enforce cybersecurity standards on DoD contractors and subcontractors, particularly those who handle Controlled Unclassified Information (CUI).
The five main DFARS clauses, 252.204-7008, 252.204-7012, 252.204-7019, 252.204-7020 and 252.204-7021, collectively establish the cybersecurity baseline for defense suppliers. Together, they impose prescriptive requirements for system security, incident reporting, assessment and third-party certification. From mandatory implementation of NIST SP 800-171 to the Cybersecurity Maturity Model Certification (CMMC) program, these regulations fundamentally alter how defense contractors manage cybersecurity compliance. Since February 1, 2026, a DoD class deviation has removed -7019 from new solicitations and replaced -7020 with DFARS 252.240-7997, while -7012 and -7021 are unchanged.
This page provides a cybersecurity-focused summary of DFARS from a GRC practitioner’s perspective, including: the history of these laws; the consequences of non-compliance; practical compliance strategies; high-profile enforcement actions; and the role of high-quality documentation in audit readiness and breach resilience.
DFARS: Origins and Purpose
The DFARS cybersecurity clauses emerged from a decade of rising concern within the DoD over the theft of sensitive defense information. With adversaries exploiting cyber weaknesses in the DIB, the DoD sought to impose enforceable cybersecurity obligations on contractors.
Key milestones include:
2015
DFARS 252.204-7012 mandates implementation of NIST SP 800-171 controls for safeguarding CUI and reporting cyber incidents;
2017–2020
Contractors self-certify compliance through Supplier Performance Risk System (SPRS);
2020
Interim DFARS rule introduces DFARS 252.204-7019, -7020 and -7021, formalizing assessments and launching CMMC; and
2021–Present
The DoD refines CMMC 2.0, emphasizing third-party certification and harmonization with NIST requirements. In February 2026, a DoD class deviation removes -7019 from new solicitations and renumbers -7020 as DFARS 252.240-7997.
While each clause serves a distinct purpose, they function collectively to create a structured compliance pathway that links contractual eligibility with cybersecurity maturity.
Summary of Key DFARS Clauses
DFARS 252.204-7008
Compliance with Safeguarding Covered Defense Information Controls
This clause is a pre-award requirement asserting that contractors must represent their ability to comply with the security requirements of NIST SP 800-171, or list out variances via a System Security Plan (SSP) and Plan of Action and Milestones (POA&M): Requires contractor systems to comply with NIST SP 800-171 when handling CUI; acknowledges that not all 110 controls may be immediately met but demands documented remediation timelines; and precludes award unless the contractor affirms a valid implementation path.
Key compliance action: Maintain current and accurate SSP and POA&M documentation prior to contract award.
DFARS 252.204-7012
Safeguarding Covered Defense Information and Cyber Incident Reporting
The core DFARS cybersecurity clause, -7012 protects covered defense information: CUI that the DoD provides to the contractor, or that the contractor collects, develops, receives, transmits, uses or stores in support of the contract. It mandates both preventive and responsive controls: implement all 110 NIST SP 800-171 controls in covered contractor information systems; rapidly report cyber incidents, meaning within 72 hours of discovery, through the DoD's DIBNet portal using a DoD-approved medium assurance certificate; submit any malicious software found to the DoD Cyber Crime Center (DC3); preserve images of affected systems and relevant monitoring data for at least 90 days from the report so the DoD can request them; and use only cloud services that meet security requirements equivalent to the FedRAMP Moderate baseline for covered defense information.
The clause also flows down. Prime contractors must include -7012 in subcontracts that involve covered defense information, and subcontractors must report cyber incidents directly to the DoD and give the incident report number to their prime. Compliance with -7012 is not optional. It is enforceable under contract law and is often a focal point during audits and investigations.
DFARS 252.204-7019
Notice of NIST SP 800-171 DoD Assessment Requirements
Clause -7019 formalizes the requirement for contractors to perform and submit cybersecurity assessments to the DoD’s Supplier Performance Risk System (SPRS). Requirements include: submit a Basic, Medium, or High assessment based on NIST SP 800-171; basic assessments are self-generated, based on contractor SSPs; scores are calculated by subtracting unmet controls from 110; and assessments must be current (within 3 years) for contract eligibility.
SPRS scores are used by contracting officers during source selection and acquisition reviews, creating a direct link between cybersecurity posture and business opportunity. 2026 update: under DoD Class Deviation 2026-O0025, effective February 1, 2026, contracting officers no longer include -7019 in new solicitations. Older contracts and solicitations may still carry it, the codified DFARS still lists it until formal rulemaking, and SPRS remains in use.
DFARS 252.204-7020
NIST SP 800-171 DoD Assessment Requirements
Clause -7020 mandates that contractors: allow the DoD to conduct Medium or High assessments, including on-site reviews; flow down -7020 to all subcontractors that process, store, or transmit CUI; and provide documentation (SSPs, POA&Ms, evidence) upon DoD request.
This clause operationalizes enforcement by granting the DoD access to audit and validate contractor claims and is often triggered by risk-based criteria or anomalies in SPRS scoring. Medium and High assessments are performed by the government, ordinarily DCMA DIBCAC, and contractors have 14 business days after an assessment to provide additional information or rebut findings. 2026 update: under DoD Class Deviation 2026-O0025, effective February 1, 2026, new solicitations and contracts use DFARS 252.240-7997 in place of -7020. It keeps the government's right to conduct Medium and High assessments but removes the Basic self-assessment. Contracts awarded earlier still reference -7020.
DFARS 252.204-7021
Cybersecurity Maturity Model Certification (CMMC) Requirements
Clause -7021 codifies the requirement for contractors to meet the CMMC level specified in the solicitation before contract award: CMMC Level 1 aligns with FAR 52.204-21 (basic safeguarding of FCI); CMMC Level 2 aligns with NIST SP 800-171 Rev 2 and requires either a self-assessment or third-party certification by a CMMC Third-Party Assessment Organization (C3PAO), as the solicitation specifies; and CMMC Level 3 (for critical programs) adds 24 requirements selected from NIST SP 800-172 and is assessed by DCMA DIBCAC once the contractor holds Final Level 2 (C3PAO) status.
The required CMMC status, whether a self-assessment or a certification, must be in place before award and maintained throughout contract performance, including annual affirmations of continued compliance.
Ramifications of Non-Compliance with DFARS
Failure to comply with DFARS cybersecurity clauses carries serious consequences, both contractual and legal.
Loss of Contract Eligibility
Non-compliance with -7008, -7019, or -7021 can render a company ineligible to bid or win DoD contracts. Contracting officers are required to confirm compliance as part of source selection.
Breach of Contract
Failure to meet -7012 obligations (e.g., inadequate safeguarding, delayed incident reporting) can constitute breach of contract, potentially resulting in: termination for default; withheld payments; and suspension or debarment from future contracts.
False Claims Act (FCA) Liability
This adds a significant layer of legal risk, particularly for contractors who overstate their cyber maturity to win awards. False attestation of compliance, especially SPRS score inflation or fabricated SSPs, can trigger FCA investigations by the Department of Justice: penalties can include treble damages and civil penalties per false claim; and whistleblowers can initiate suits under qui tam provisions.
Public Examples of DFARS Enforcement Actions
While DoD has not widely publicized contract terminations under these clauses, recent legal activity suggests growing enforcement momentum.
Aerojet Rocketdyne (2022) – False Claims Act Settlement
Allegation: Misrepresentation of cybersecurity compliance with DFARS -7012 and NIST SP 800-171.
Outcome: Settled for $9 million.
Precedent: Marked the first known FCA case focused on cybersecurity misrepresentation tied to DoD compliance. This case confirmed that internal whistleblowers, even without a breach event, can bring FCA claims based on inadequate SSPs and security gaps.
DOJ Civil Cyber-Fraud Initiative (2021 – Present)
The Department of Justice has launched a targeted enforcement initiative to pursue government contractors that knowingly fail to meet cybersecurity obligations. Focuses on misrepresentations, failure to report breaches and poor internal controls. Cyber fraud is now treated as contract fraud and the DoD’s Inspector General has increased audit referrals.
These developments show that DFARS cybersecurity compliance is no longer a passive or symbolic requirement. It is a measurable legal duty.
Common Methods to Achieve and Maintain DFARS Compliance
DFARS compliance is not achieved with a policy document or one-time assessment. It requires a sustained operational program rooted in NIST SP 800-171.
Implement NIST SP 800-171
Contractors must fully implement the 110 controls from NIST SP 800-171. POA&Ms may exist, but must be realistic, resourced and time-bound.
Maintain a Current System Security Plan (SSP)
DoD assessors scrutinize SSPs for completeness and accuracy. The SSP is the foundational document for DFARS compliance. It must: describe how each of the 110 controls is implemented; map controls to responsible roles and evidence sources; and reflect actual, operational practices (not future intentions).
Submit Accurate SPRS Scores
Inflated scores without supporting evidence present legal risk. For contracts that still include -7019 and -7020: calculate a Basic Assessment score using DoD's scoring methodology; enter the score, date and system boundary into the SPRS portal; and retain all supporting documentation for review. CMMC Level 1 and Level 2 self-assessment results are also entered in SPRS, so accurate scoring matters under -7021 as well.
Prepare for DoD Assessments
High assessments can last multiple days and require on-site engagement. Contractors selected for Medium or High assessments must: undergo interviews, technical reviews and evidence-based audits; provide real-time system access or screenshots; and remediate deficiencies per DoD timelines.
Obtain CMMC Certification (if required)
CMMC Level 2 certification is valid for 3 years, but annual affirmation of compliance is still required. To meet -7021, contractors must: engage an authorized C3PAO listed on The Cyber AB Marketplace; conduct pre-assessments to validate readiness; and resolve any POA&Ms prior to certification.
Understanding The Value of Quality Cybersecurity Documentation in DFARS Success
Documentation is not a formality in DFARS compliance, but is the primary evidence used by DoD and legal authorities to assess security posture and contract eligibility. Failure to produce documentation upon request can be interpreted as failure to implement the control.
Key Documents Include
- System Security Plan (SSP): Master control document detailing implementation and responsibilities;
- Plan of Action and Milestones (POA&M): Active remediation tracker with realistic timelines and resource assignments;
- Security Assessment Reports (SAR): Results of internal or external control reviews;
- Incident Response Plan and Logs: Evidence of triage, containment and reporting timelines
- Access Control Logs and User Access Reviews: Proof of access enforcement, termination and review;
- Configuration and Patch Management Records: Documentation of baseline configurations and patch cadence;
- Third-Party Audit Reports or C3PAO Assessment Records: Third-Party Audit Reports or CMMC Assessments.
.png)
%20(white).png)