Defense Federal Acquisition Regulation Supplement
DFARS 252.204-7012 has required 110 NIST SP 800-171 controls since 2017, and it is unchanged by everything CMMC has done since. What has changed is how the Department verifies your work — and what happens when your posted score turns out to be wrong.
Where DFARS compliance stands in September 2026
DFARS 252.204-7012 is unchanged. If you store, process, or transmit Controlled Unclassified Information under a DoD contract, you owe all 110 requirements in NIST SP 800-171 Revision 2 today, plus 72-hour cyber incident reporting and FedRAMP Moderate equivalency for any cloud service touching CUI.
The clause numbers around it have moved. A February 2026 class deviation reorganized the cybersecurity clauses into FAR Part 40 and DFARS Part 240. DFARS 252.204-7019 is no longer prescribed, and 252.204-7020 now appears as 252.240-7997. See our DFARS clause crosswalk for where each requirement went.
CMMC third-party assessments are suspended; self-assessment is not. DoD suspended the transition to CMMC Phase 2 in July 2026, but Phase 1 self-assessment requirements, SPRS score posting, and annual affirmation all remain conditions of award. Full detail in our CMMC compliance guide.
What DFARS 252.204-7012 requires
DFARS 252.204-7012, Safeguarding Covered Defense Information and Cyber Incident Reporting, was published in 2015 and became fully effective at the end of 2017. If the clause is in your contract, accepting the contract means certifying you can meet it. It imposes three obligations.
The three obligations under 7012
-
Adequate security
The bulk of the work
- Implement all 110 requirements of NIST SP 800-171 Revision 2
- Applies to every system that stores, processes, or transmits covered defense information
- Not a one-time project — controls must remain in operation
-
Incident reporting
72 hours, no exceptions
- Report cyber incidents to DoD within 72 hours of discovery
- Preserve and provide access to affected media for 90 days
- Submit malicious software to DoD when isolated
-
Flow-down and cloud
Often missed entirely
- Flow the clause to subcontractors handling covered defense information
- Any cloud service touching CUI must meet FedRAMP Moderate equivalency
- External service providers come into your assessment scope
“Adequate security” is the phrase that does the most work in the clause. In practice it means the NIST SP 800-171 baseline, in full, evidenced.
FCI or CUI — which do you handle?
The distinction sets your obligation. Federal Contract Information is information not intended for public release that you receive or generate under a government contract, and it triggers the 15 basic safeguarding requirements in FAR 52.204-21. Controlled Unclassified Information is the marked or markable category covering defense technical data, drawings, specifications, and export-controlled information, and it triggers 7012 and the full 110. Most contractors who think they only handle FCI turn out to hold CUI somewhere — usually in an email attachment or a shared drive nobody scoped.
The 110 requirements behind the clause
DFARS 252.204-7012 does not contain security controls itself — it points to NIST SP 800-171 Revision 2, which organizes 110 security requirements into 14 families. Assessment is performed against the 320 objectives in NIST SP 800-171A, which is why partial implementation of a requirement scores as zero rather than as partial credit.
One point of confusion worth clearing up: NIST withdrew Revision 2 from its own catalog in May 2024 when Revision 3 was published, so NIST’s page for it now shows as superseded. Revision 2 is still what DoD enforces — a NIST publication only stops being your obligation when the regulation naming it is amended, and it has not been. For the family-by-family breakdown, the revision question in full, and the controls that cause contractors the most trouble, see our NIST SP 800-171 compliance guide.
| Family | Requirements | What it covers |
|---|---|---|
| Access Control | 22 | Who can reach CUI, from where, and with what privileges |
| Awareness and Training | 3 | Security training, role-specific training, insider threat awareness |
| Audit and Accountability | 9 | Logging, log review, and traceability of user actions |
| Configuration Management | 9 | Baselines, change control, least functionality, software allowlisting |
| Identification and Authentication | 11 | Identity, multifactor authentication, password and credential management |
| Incident Response | 3 | Response capability, tracking and reporting, testing |
| Maintenance | 6 | System maintenance controls, remote maintenance, media sanitization before service |
| Media Protection | 9 | Marking, storage, transport, sanitization, and removable media limits |
| Personnel Security | 2 | Screening before access, and protecting CUI during transfers and terminations |
| Physical Protection | 6 | Facility access, visitor logs, alternate work sites |
| Risk Assessment | 3 | Periodic risk assessment, vulnerability scanning, remediation |
| Security Assessment | 4 | Control assessment, system security plan, plan of action, continuous monitoring |
| System and Communications Protection | 16 | Boundary protection, encryption in transit, session control, subnetworks |
| System and Information Integrity | 7 | Flaw remediation, malicious code protection, monitoring and alerts |
Your SPRS score and how it is calculated
Implementing the controls is only half of DFARS compliance. The other half is reporting where you stand, in the Supplier Performance Risk System, on a scale DoD defined so that contractors can be compared against each other.
Scoring starts at 110 and subtracts a weighted value for every requirement you have not implemented — 1, 3, or 5 points, depending on how much risk that gap carries. The floor is negative 203. A first honest assessment landing below zero is far more common than contractors expect.
A company with 90 of 110 requirements implemented does not score 90. It scores 110 minus the weighted value of the 20 it is missing — which can put it under zero.
That weighting is the piece most self-estimates get wrong. Multifactor authentication and FIPS-validated cryptography are the two requirements that carry partial credit in the methodology, and both are heavily weighted. Miss a handful of the 5-point requirements and a posture that feels close to complete produces a score that looks nothing like it.
What a SPRS submission includes
- The name of your System Security Plan
- The CAGE code or codes the plan covers
- A brief description of the plan architecture
- The date the assessment was completed
- Your total score
- The date you expect to reach a score of 110
Give that last field real thought. It is a commitment on the record, and your later progress can be measured against it.
Reporting a cyber incident
Even in well-secured environments, incidents happen. Under 7012 you have 72 hours from discovery to report a cyber incident affecting covered defense information, submitted through DIBNet. Reporting requires a medium assurance certificate, which takes time to obtain — getting one before you need it is the difference between reporting on time and explaining why you didn’t.
You must also preserve and protect images of affected systems and relevant monitoring data for at least 90 days from the report, and provide DoD access on request. Contractors who reimage a compromised machine before capturing it are the most common version of this failure.
How DFARS relates to CMMC
DFARS creates the obligation. CMMC checks the work.
Your DFARS position determines your CMMC level, not the other way round. A contractor already implementing all 110 requirements under 7012 is substantially aligned to CMMC Level 2 by definition.
When 7012 was published, compliance was self-attested and unverified. Adoption was poor, DoD had no way to detect a false claim, and CMMC was created as the verification layer on top. That is the entire relationship: the security requirement lives in DFARS and NIST SP 800-171; CMMC is the mechanism for confirming you met it.
| If you handle | Your standard | CMMC level |
|---|---|---|
| FCI only | 15 basic safeguarding requirements, FAR 52.204-21 | Level 1, self-assessed |
| CUI | 110 requirements, NIST SP 800-171 Rev. 2, under DFARS 7012 | Level 2 — currently self-assessed while third-party designations are suspended |
| CUI on a highest-priority program | Level 2 in full, plus 24 enhanced requirements from NIST SP 800-172 | Level 3, government-assessed by DIBCAC |
One correction worth stating plainly, because older guidance across the web still gets it wrong: under the current model, CUI means Level 2. Guidance telling CUI handlers they need Level 3 is using CMMC 1.0 numbering, where Level 3 was the CUI tier. Today’s Level 3 is a much narrower category, and pursuing it unnecessarily is one of the most expensive mistakes available here.
Penalties for non-compliance
There is no single DFARS penalties clause. Consequences arrive through contract mechanisms and through the False Claims Act, and the second of those has become the sharper end.
| Consequence | How it happens |
|---|---|
| Ineligibility for award | Where a solicitation requires a current assessment or a CMMC level, no status in SPRS means no award. |
| Stop-work order | A DoD assessment finding you materially non-compliant can suspend work until you remediate. |
| Breach of contract and damages | 7012 is a contract term. Failing it is a breach, with the ordinary remedies attached. |
| False Claims Act liability | Under DOJ’s Civil Cyber-Fraud Initiative, submitting a score you cannot substantiate is a false claim. In June 2026 an Alabama defense contractor agreed to pay $507,144 after a DoD audit found its near-perfect self-assessment substantially inaccurate. |
| Termination, suspension, debarment | In the worst case, contracts are terminated and the contractor is excluded from future DoD work. |
| Loss of supply chain position | Primes remove non-compliant subcontractors from approved vendor lists on commercial timelines, with no regulatory trigger required. |
Note what the Logzone case did not involve: a third-party assessor. It was a self-assessment, audited by the government. That is the clearest available answer to whether self-attestation is a low-risk path while CMMC third-party assessments are suspended.
How to become DFARS compliant
Six steps, in order
-
1
Scope
Find where FCI and CUI actually enter, move, and rest. Scoping decisions set the cost of everything that follows, and over-scoping is the most expensive avoidable error.
-
2
Gap analysis
Assess the in-scope environment against all 320 objectives in NIST SP 800-171A. This is where you learn your real score rather than your assumed one.
-
3
SSP and POA&M
Document the system as it is and the plan to close what is open. Both are required, and both are the first artifacts any assessor asks to see.
-
4
Remediate
Close the gaps. MFA, FIPS-validated encryption, audit logging and review, and CUI marking and handling consume most of the effort and most of the budget.
-
5
Score and post
Calculate your score under the DoD methodology, post it in SPRS, and affirm it through a senior company official who understands what they are signing.
-
6
Monitor
Controls drift and staff turn over. Continuous monitoring, log review, and evidence collection keep the score you posted true a year later.
The gap analysis is the step contractors most often skip and most often regret skipping. Without it, there is no way to know what changes are needed — or to defend the score you posted.
What a gap analysis surfaces
A thorough gap analysis typically exposes problems in how system access is controlled and reviewed, how administrators and privileged users are trained, where CUI is stored and whether it is marked, which controls are genuinely operating rather than merely documented, and whether an incident response plan would survive an actual incident. Findings become the remediation plan, and the remediation plan becomes your POA&M.
What remediation looks like
Remediation ranges from configuration changes and policy work to rebuilding identity, endpoint, logging, and email infrastructure. Where CUI is confined to a subset of the business, a segmented enclave — often on Microsoft 365 GCC High — shrinks the assessment boundary along with the cost. Where CUI is genuinely everywhere, an enterprise-wide approach is the honest answer.
Ongoing monitoring and evidence
Compliance is a state, not a milestone. Once remediation is done, the work becomes detection, log review, vulnerability management, and keeping evidence current enough that an assessment on short notice is uneventful. This is also where an MSSP earns its place: monitoring, alerting, and incident reporting are continuous obligations that most contractors cannot staff around the clock internally.
In-house or with a consultant
Meeting the requirements in-house
Contractors with a capable internal security team can do this themselves. NIST’s Self-Assessment Handbook 162 remains a reasonable orientation, with one caveat that matters: it covers Revision 1, and it has never been updated for the Revision 2 baseline that DFARS and CMMC actually enforce. Use it for structure, not as your control list.
The real constraint is rarely knowledge. It is bandwidth and objectivity — assessing 320 objectives, remediating what you find, and maintaining evidence is a sustained workload on top of running IT for a business that has other priorities.
Working with a DFARS consultant or MSSP
Outsourcing to a provider that specializes in DFARS consulting or IT risk management and compliance gives you people who assess these environments continuously, templates and tooling that already exist, and monitoring capacity you would otherwise have to build.
Two things to understand before you sign. First, you remain responsible — outsourcing the work does not outsource the liability, and your senior official still signs the affirmation. Second, an external service provider that stores, processes, or transmits your CUI, or provides security protection for your in-scope environment, comes into your assessment scope. You need a shared responsibility matrix documenting which controls they implement and which remain yours. A provider who cannot produce one has not done this before.
Where CMMC certification is the eventual goal, look for a Cyber AB Registered Provider Organization. RPOs employ trained practitioners, undergo background screening, and agree to a code of professional conduct.
Frequently asked questions
What is DFARS compliance?
It means meeting DFARS 252.204-7012: implementing all 110 requirements of NIST SP 800-171 Revision 2 on systems that handle covered defense information, reporting cyber incidents to DoD within 72 hours, flowing the clause to subcontractors, and using only cloud services that meet FedRAMP Moderate equivalency. It also means posting an assessment score in SPRS.
Is DFARS compliance still required now that CMMC Phase 2 is suspended?
Yes, and this is the most common misconception right now. The suspension paused third-party certification assessments. DFARS 252.204-7012 is untouched, NIST SP 800-171 Rev. 2 remains the enforced standard, and SPRS scores and annual affirmations are still required. If anything, the suspension concentrates risk on self-attestation, which the government is auditing directly.
How many controls are in DFARS?
DFARS itself does not contain controls — it points to NIST SP 800-171, which has 110 security requirements across 14 families. Assessment is performed against the 320 objectives in NIST SP 800-171A.
What is a DFARS SPRS score, and can it be negative?
It is your NIST SP 800-171 implementation expressed on DoD’s scale. Scoring begins at 110 and deducts 1, 3, or 5 points per unimplemented requirement based on risk weighting, with a floor of negative 203. Negative scores are common on a first honest assessment.
Which NIST 800-171 revision applies?
Revision 2. Revision 3 exists, but a NIST publication only becomes an enforceable requirement when DoD writes it into the rule, and that has not happened. Building to Rev. 3 today means implementing controls you do not owe while possibly missing ones you do.
Do subcontractors have to be DFARS compliant?
Yes. DFARS 252.204-7012 flows down to subcontractors handling covered defense information, at every tier. In practice, primes have been enforcing this ahead of the government’s own schedule, using documented implementation and SPRS scores as a condition of remaining on approved vendor lists.
What is the difference between DFARS and NIST 800-171?
DFARS is the contractual requirement; NIST SP 800-171 is the technical standard it points to. DFARS makes 800-171 enforceable through your contract. You cannot comply with one without the other.
Does my MSP make me DFARS compliant?
Not on its own. If a provider handles your CUI or protects your in-scope environment, that provider enters your assessment scope and you need a shared responsibility matrix showing who implements what. A capable provider reduces your workload substantially and improves your evidence, but the obligation and the affirmation stay with you.
How long does DFARS compliance take?
For a contractor starting from a modern, well-managed environment with CUI confined to a defined boundary, several months. For a contractor with CUI spread across shared drives, legacy on-premises systems, and no logging, 12 to 18 months is realistic. Scope and starting posture drive the timeline far more than company size does.
What happened to DFARS 252.204-7019 and 7020?
The February 2026 class deviation stopped prescribing 7019 and relocated 7020 to 252.240-7997. The underlying self-assessment and government-assessment requirements survive through other clauses. Our clause crosswalk maps each one to its current status.
Sources and references
- NIST SP 800-171 Revision 2 — the 110 security requirements enforced under DFARS 252.204-7012.
- FAR 52.204-21 — the 15 basic safeguarding requirements for Federal Contract Information.
- 32 CFR Part 170 — the CMMC Program rule, including level definitions and affirmation requirements.
- DoD class deviations — current FAR and DFARS deviation memos, including the clause reorganization and the CMMC Phase 2 suspension.
- Supplier Performance Risk System — where assessment scores are submitted and maintained.
- DIBNet — the portal for 72-hour cyber incident reporting.
- DCMA DIBCAC — the DoD organization that conducts Medium and High assessments.
Want to know your real SPRS score before DoD does?
SysArc is a Cyber AB Registered Provider Organization and has guided more than 1,000 DoD contractors through DFARS, NIST SP 800-171, and CMMC. We scope the environment, assess against all 320 objectives, and give you a defensible score with a remediation plan behind it.
If your posted score was estimated rather than assessed, that is worth resolving before someone else checks it.



