Skip to main content
DFARS 252.204-7012

Your DFARS Cybersecurity Clauses,
IMPLEMENTED

For defense contractors and subcontractors handling CUI: ITS implements the NIST SP 800-171 controls DFARS 252.204-7012 requires, maintains your SPRS score under 252.204-7019, and gets your DIBNet reporting and medium assurance certificate in place in advance.

WHAT THE CLAUSE ASSUMES

The Clause Assumes You Already Did This

A DFARS clause does not teach you anything. It states an obligation and assumes the work behind it is finished, which is why the first real conversation usually happens after the contract is signed. This page sits inside our wider IT compliance services.

The gaps that turn a clause into a problem:

  • A contract signed without checking which clauses are in it
  • No list of the systems that hold covered defense information
  • A required NIST SP 800-171 assessment score in SPRS that is missing, outdated, or does not reflect the current environment
  • A System Security Plan written once, for a bid
  • A POA&M with no dates on it and no owner
  • No route to report an incident inside 72 hours
  • Clauses never flowed down to the subcontractors doing the work
WHY ITS

The Work the Clause Does Not Describe

The clause tells you the outcome it wants. It does not tell you which systems are in scope, who owns the plan, or what you do at 2am on the day something happens. That part is ours.

Clause by Clause Reading
We go through the clauses your contract actually names, and turn each one into work with an owner and a date.
Controls That Stay On
Controls That Stay On The NIST SP 800-171 security requirements behind the clause need to operate continuously, not only when an assessment is approaching.
Reporting You Can Do Fast
A reporting route agreed in advance, system images preserved, and the evidence collected while it still exists.

Two neighbors worth naming rather than blurring. The control set the clause points at is NIST 800-171 compliance, and the program that verifies you meet it is CMMC compliance. This page is about the clause that makes both of them contractual.

THE CLAUSES

Six Things the Clause Language Actually Says

DFARS is where defense cybersecurity stops being advice and becomes a term of your contract. These are the parts that land on IT, in the order they land.

Clause numbers, titles and requirements are taken from the DFARS clause text published by the Department of Defense at acquisition.gov. This page is not legal advice on the interpretation of your contract.

Covered Defense Information

The clause protects covered defense information, which includes controlled unclassified information given to you and information you generate performing the contract. Scoping it is the first decision, because every other requirement follows the boundary you draw.

What CUI actually is

Safeguarding and Reporting

DFARS 252.204-7012 requires adequate security on the systems that hold that information, and defines adequate security as implementing NIST SP 800-171. It also requires you to report a cyber incident to the Department of Defense within 72 hours of discovering it, preserve affected system images for at least 90 days, and submit malicious software when asked.

Your Score in SPRS

DFARS 252.204-7019 makes eligibility for award conditional on having a current NIST SP 800-171 Basic Assessment posted in the Supplier Performance Risk System. Current means not more than three years old, which makes the score a standing obligation rather than a bid task.

How to post your score

Assessments and Access

DFARS 252.204-7020 commits you to giving the Department of Defense access to conduct a Medium or High assessment of how you have implemented the controls, and to carrying the same requirement into your subcontracts.

The CMMC Requirement

DFARS 252.204-7021 brings CMMC requirements into applicable contracts. When the clause applies, the contractor must achieve and maintain the required CMMC status for the information systems covered by the contract and complete the required annual affirmation of continuous compliance.

Where the phase-in stands

Flow-Down to Your Suppliers

These clauses do not stop with you. Where a subcontractor handles the same information, the requirement goes into their agreement too, which means their gaps become your problem at award time.

HOW TO START

Three Steps to Put Your DFARS Requirements Into Practice

Start with these three steps to understand your requirements, assess your environment, and address the gaps.

STEP 1

Read the Clauses in Your Contract

A working session on the clauses your contract or solicitation actually names, and what each one obliges you to have. No preparation needed on your side.

Talk to a Compliance Expert
STEP 2

Scope the Information, Then Score It

We find where covered defense information lives, draw the boundary, and assess the 110 practices against it honestly. You get the gaps in writing, yours to keep.

Get My Free Assessment
STEP 3

Close the Gaps and Stay Reportable

Controls go in, the plan and the POA&M stay current, the score gets updated, and the reporting route is agreed before anybody needs it.

CLIENT RESULTS

What Clients Say About Working With Us

Hear from ITS clients about the security, compliance, and operational improvements they have experienced working with our team.

I think... to not adopt some form of advanced security these days would be incredibly foolish. The biggest benefit ITS provides is the weight off my shoulders knowing that they’re involved, and we’ve prepared ourselves as best as we could for any cyberthreats. That component is the most important to us.

JP Halverson Vice President, McQuarrie Associates
JP Halverson on working with ITS
FAQ

What Suppliers Ask Us After They Read the Clause

1. What is DFARS, and which clause applies to us?

What is DFARS, and which clause applies to us? DFARS is the Defense Federal Acquisition Regulation Supplement, which adds DoD-specific requirements to the federal acquisition rules. The cybersecurity provisions that apply depend on the language in your solicitation or contract. Common provisions include DFARS 252.204-7012, 252.204-7019, 252.204-7020, and 252.204-7021. Review the actual contract language to determine which requirements apply to your organization.

2. Is DFARS the same thing as NIST 800-171?

No. NIST SP 800-171 defines the security requirements for protecting CUI in nonfederal systems. DFARS 252.204-7012 is the contract clause that requires applicable contractor systems to provide adequate security, including implementation of NIST SP 800-171 requirements. One defines the security requirements; the other makes them a contractual obligation when the clause applies.

3. How does DFARS relate to CMMC?

CMMC is the DoD framework for assessing compliance with applicable information security requirements. DFARS 252.204-7021 brings CMMC requirements into applicable contracts and requires contractors to achieve and maintain the specified CMMC status, along with an annual affirmation of continuous compliance. The phase-in schedule has changed more than once, so the solicitation in front of you governs. DFARS 252.204-7012, the underlying safeguarding and incident-reporting clause, still binds every contractor and subcontractor regardless of where that phase-in stands.

4. How fast do we have to report a cyber incident?

DFARS 252.204-7012 requires you to rapidly report a cyber incident to the Department of Defense within 72 hours of discovering it. It also requires you to preserve images of the affected systems for at least 90 days so they can be reviewed, and to submit malicious software if it is found. Deciding who makes that report, and how, is work you do before you need it.

Source: DFARS 252.204-7012 clause text.

5. Do these clauses reach our subcontractors?

Do these clauses reach our subcontractors? They can. Applicable DFARS cybersecurity requirements must be flowed down when the subcontract meets the conditions defined in the relevant clause. For example, DFARS 252.204-7012 requires flow-down when subcontract performance involves covered defense information or operationally critical support, while CMMC flow-down depends on the information the subcontractor will process, store, or transmit.

6. Can ITS make us DFARS compliant?

We can do the work; we cannot sign it off. ITS scopes the information, implements and operates the controls, writes and maintains the System Security Plan and the POA&M, prepares evidence and helps you post an accurate score. What ITS is not is your assessor, your certifying body or your lawyer. Only a C3PAO certifies a CMMC level, only the Department of Defense conducts its own assessments, and only your contracting officer speaks for your contract.

Your Score Is Already Posted. Is It Accurate?

A working session on the clauses in your contract, what is actually in scope, and whether your SPRS score matches your systems. The gaps in writing, yours to keep.