DFARS 252.204-7012: every control, and what you already have

14 controls 3 frameworks share controls with it United States (DoD) verified against its source document

Every control below is one this framework asks for. The right hand column counts how many other frameworks in our corpus carry the same control, which is the difference between doing this work once and doing it again for the next standard.

DFARS 252.204-7012 Safeguarding Covered Defense Information Evidence & Implementation Kit

14 controls is the documentation set somebody has to write. This is that set, already written: an adopt-ready artifact for every control in policy and procedure text you edit rather than draft, and the evidence checklist an auditor asks for against each.

See what is in it, $249

The same set every buyer of this kit receives. Nothing here is produced on request.

What you already have

Frameworks whose controls overlap this one, most first. If you run any of them, the count is roughly what you have already evidenced.

If you run	Shared controls
NIST Cybersecurity Framework 2.0	4	measure it →
CMMC 2.0	2	measure it →
NIST SP 800-53 Rev 5	2	measure it →

Every control

Code	Control	Also in
`7012(b)(1)`	Covered Defence Information Identification	0
`7012(b)(2)`	Scope of Protected Systems	0
`7012(b)(3)`	COTS Exclusion	0
`DFARS-7012-b`	Adequate security - implement NIST SP 800-171	1
`DFARS-7012-b-cloud`	Cloud and external service provider security	0
`DFARS-7012-b-var`	Variance requests and alternative measures	0
`DFARS-7012-c`	Cyber incident reporting (72-hour rapid report)	3
`DFARS-7012-d`	Malicious software submission to DC3	1
`DFARS-7012-e`	Media preservation and protection (90 days)	1
`DFARS-7012-f`	Access to additional information or equipment for forensic analysis	1
`DFARS-7012-g`	Cyber incident damage assessment activities	1
`DFARS-7012-hk`	DoD safeguarding and use of contractor attributional/proprietary information	0
`DFARS-7012-l`	Other safeguarding or reporting requirements	0
`DFARS-7012-m`	Subcontract flowdown	0

Tell me when DFARS 252.204-7012 files something new

One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

What an auditor will ask you to produce

The artefacts named on the failure modes this framework speaks to.

CTDPA applicability worksheet (100K consumer / 25K + 25% revenue thresholds)
Data inventory tagged with PA 23-56 consumer health data flags
Entity-level exemption memo (GLBA, HIPAA, nonprofit, higher ed)
Processor vs controller role determination log

How programmes fail on this

Failure modes named by this framework and others. Each opens the full record.

Pseudonymous data treated as out of scope without safeguards review named by 3 frameworks
Applicability re-run not triggered when revenue mix shifts named by 3 frameworks
Consumer health data not separated from general sensitive data named by 3 frameworks
B2B contact data assumed exempt past PA 23-56 effective date named by 3 frameworks

What this page is

A control-level reference for DFARS 252.204-7012, drawn from our framework corpus. Control codes and titles are references to the standard, not reproductions of it. The overlap counts and the auditor artefacts are our own work and are the part you will not find elsewhere.

Measure this against what you already run · All frameworks · Today's edition