Four clauses, one obligation chain
Four DFARS clauses carry the cybersecurity burden for defense contractors. 7012 sets the security standard and incident duties. 7019 and 7020 require you to score yourself honestly and let the government check. 7021 turns the CMMC level into a condition of award and performance. All four flow down to subcontractors that handle covered defense information.
| Clause | What it requires | Status Nov 2026 |
|---|---|---|
| 252.204-7012 | Adequate security (NIST SP 800-171), FedRAMP Moderate equivalent cloud, 72-hour reporting, malware submission, 90-day preservation, flow-down | Enforced |
| 252.204-7019 | Current NIST SP 800-171 assessment (not older than 3 years) posted in SPRS before award | Enforced |
| 252.204-7020 | Government access for Medium and High assessments; flow-down and verification of subcontractor scores | Enforced |
| 252.204-7021 | Required CMMC level and status in SPRS; maintain for contract life; annual affirmation | Phase 1 active |
DFARS 252.204-7012: safeguarding and reporting
Paragraph (b) requires “adequate security” for covered contractor information systems, defined as implementing NIST SP 800-171. Any requirement you have not implemented must be documented and, for contracts awarded since 2017, your SSP and plans of action stand in for that implementation status. Paragraph (b)(2)(ii)(D) requires that any external cloud service provider storing, processing or transmitting covered defense information meet security requirements equivalent to the FedRAMP Moderate baseline and comply with paragraphs (c) through (g) for incident reporting, malware, media preservation, access and damage assessment.
Paragraph (m) requires flowing the clause to subcontractors whose performance involves covered defense information, without alteration except to identify the parties. Subcontractors report incidents directly to DC3 and to the prime.
The 72-hour cyber incident report
When you discover a cyber incident affecting a covered system or covered defense information, or your ability to perform operationally critical support, you must rapidly report within 72 hours of discovery to the DoD Cyber Crime Center (DC3).
- Report through DC3’s Incident Collection Format, the DCISE reporting portal at
icf.dcise.cert.org, which replaced the legacy DIBNet submission path. Have your CAGE code, contract numbers, contracting officer contacts and a description of affected systems and data ready. - Authenticate with a DoD-approved Medium Assurance certificate. The portal requires an External Certification Authority (ECA) Medium Assurance certificate, issued by providers such as IdenTrust or WidePoint.
- Submit malicious software you isolate to DC3 as instructed, not to the contracting officer.
- Preserve and protect images of all known affected systems and relevant monitoring and packet capture data for at least 90 days from the report, so DoD can request them for forensic analysis.
- Provide access to additional information or equipment if DoD elects to conduct a damage assessment.
An ECA Medium Assurance certificate requires identity proofing and can take one to several weeks to issue. Contractors who wait until a breach discover they cannot file inside 72 hours. Buy the certificate now, assign it to at least two people, and record the renewal date in your incident response plan (3.6.1).
DFARS 252.204-7019 and 7020: the SPRS score
7019 requires an offeror to have a current NIST SP 800-171 DoD Assessment in SPRS for each covered system relevant to the offer. A Basic Assessment is a self-assessment using the DoD Assessment Methodology, scored from 110 down to −203 (see the calculator). The entry includes the score, assessment date, system scope, SSP name and version, and the date you expect to reach 110.
7020 obliges you to give DCMA’s DIBCAC access to facilities, systems and personnel for Medium and High assessments, and to verify that subcontractors have a current score before awarding them covered work. Medium and High assessments are where inflated Basic scores surface. LOGZONE’s 110 became −170 in exactly this way.
DFARS 252.204-7021: CMMC in the contract
Since November 10, 2025, contracting officers can insert 7021 with a specified CMMC level. The contractor must have the required status in SPRS at award, maintain it for the period of performance, complete annual affirmations, and notify the contracting officer of changes to the system that affect status. Under Phase 1 the level is typically Level 1 (Self) or Level 2 (Self). The July 2026 pause suspended the move to C3PAO certification, not 7021 itself. See the Phase 2 pause breakdown.
DFARS readiness checklist
- Contracts inventoried for 7012 / 7019 / 7020 / 7021 and CUI flow-downs
- System Security Plan current, naming the boundary and version you report in SPRS
- Cloud services storing CUI verified FedRAMP Moderate (or equivalent) with 7012 (c)–(g) commitments
- ECA Medium Assurance certificate issued to two named responders
- Incident response plan with the 72-hour clock, DC3 reporting steps, and 90-day image preservation
- Subcontractor SPRS scores verified before flowing CUI
- Annual senior-official affirmation calendared; see SPRS filing guide