DFARS 252.204-7012 gives defense contractors 72 hours from discovery to report a cyber incident to DoD, and it requires more than a report: a medium assurance certificate, malware submission to DC3, at least 90 days of preserved images and monitoring data, and flowdown to subcontractors. Here is what the clause requires and a readiness checklist for Inland Empire aerospace and defense suppliers, based on the official regulation text and NIST and CISA guidance.
If your contract includes DFARS 252.204-7012, Safeguarding Covered Defense Information and Cyber Incident Reporting, a security incident is not only an IT problem. The clause requires you to "rapidly report" cyber incidents to DoD, and it defines rapidly report as within 72 hours of discovery. That clock starts when you discover the incident, not when you finish investigating it.
Seventy-two hours goes quickly when a server is encrypted on a Friday night or a project manager's mailbox starts sending strange messages. Inland Empire aerospace and defense suppliers that work through the reporting steps before anything goes wrong are in a much better position to meet the deadline, protect evidence, and keep their primes informed.
The clause defines a cyber incident as actions taken through the use of computer networks that result in a compromise or an actual or potentially adverse effect on an information system and/or the information residing therein. The reporting duty applies when an incident affects a covered contractor information system or the covered defense information on it, or affects your ability to perform contract requirements designated as operationally critical support.
Covered defense information includes unclassified controlled technical information and other Controlled Unclassified Information (CUI) that is marked or identified in the contract and provided by or for DoD, or that you collect, develop, receive, transmit, use, or store in support of the contract. For many machine shops, engineering firms, and component suppliers, that means drawings, specifications, and technical data. Note the word "potentially": the definition is not limited to confirmed data theft.
Paragraph (c)(1)(i) requires a review for evidence of compromise of covered defense information, including identifying compromised computers, servers, specific data, and user accounts. The review also covers other systems on your network that may have been accessed as a result of the incident.
Reports go to DoD at dibnet.dod.mil, and must include, at a minimum, the required elements listed there. The clause treats the report as information created by or for DoD.
To report, the contractor or subcontractor must have or acquire a DoD-approved medium assurance certificate. The clause points to the DoD External Certification Authority (ECA) program for how to obtain one. This is the step most likely to stall a small supplier in the middle of an incident, so do it before you need it.
If you discover and isolate malicious software in connection with a reported incident, paragraph (d) requires you to submit it to the DoD Cyber Crime Center (DC3) following instructions from DC3 or the Contracting Officer. The clause specifically says not to send the malicious software to the Contracting Officer.
Paragraph (e) requires you to preserve and protect images of all known affected information systems and all relevant monitoring and packet capture data for at least 90 days from the submission of the report, so DoD can request the media or decline interest. Reimaging every affected laptop on day one can destroy exactly what you are required to keep.
On request, you must give DoD access to additional information or equipment necessary for forensic analysis (paragraph (f)). If DoD elects to conduct a damage assessment, the Contracting Officer will request the information you preserved under paragraph (e) (paragraph (g)).
Paragraph (m) requires the clause to flow down, without alteration except to identify the parties, to subcontracts for operationally critical support or where subcontract performance will involve covered defense information, including subcontracts for commercial products or commercial services. Subcontractors report incidents to DoD themselves and must provide the incident report number, automatically assigned by DoD, to the prime contractor or next higher-tier subcontractor as soon as practicable.
If you are a second- or third-tier supplier, know which customer receives that report number and who on their side should hear from you.
If you use an external cloud service provider to store, process, or transmit covered defense information, paragraph (b)(2)(ii)(D) requires you to ensure that the provider meets security requirements equivalent to the FedRAMP Moderate baseline and complies with the clause's requirements for incident reporting, malicious software, media preservation, forensic access, and damage assessment. Review your agreements with email, file-sharing, and backup providers before an incident, so you know how they will notify you and what logs and images they can preserve.
For covered contractor information systems that are not operated on behalf of the Government, DFARS 252.204-7012 generally requires the security requirements in NIST SP 800-171. Its incident response family includes three requirements: 3.6.1, establish an operational incident-handling capability that includes preparation, detection, analysis, containment, recovery, and user response activities; 3.6.2, track, document, and report incidents to designated officials and/or authorities both internal and external to the organization; and 3.6.3, test the organizational incident response capability.
Under 32 CFR 170.14, the CMMC Level 2 security requirements are identical to the requirements in NIST SP 800-171 Revision 2. A documented, tested incident response capability is therefore something an assessor will expect to see evidence of, not just a policy on a shelf.
1. Confirm which contracts include DFARS 252.204-7012 and which systems store, process, or transmit covered defense information.
2. Obtain the DoD-approved medium assurance certificate needed to report, and document who holds it and who is the backup.
3. Write a short incident response plan that names decision-makers, an after-hours contact list, the DIBNet reporting step, and when to call outside help, legal counsel, and your insurer.
4. Make sure logging and endpoint monitoring are on and retained, so you have evidence to review and preserve.
5. Write down how to capture images of affected systems before rebuilding them, and where preserved media will be kept for at least 90 days.
6. List the primes and higher-tier subcontractors who must receive your DoD incident report number.
7. Confirm in writing how your cloud providers support incident reporting and preservation.
8. Run a tabletop exercise at least once a year and record what you learned. NIST's SP 800-61 Revision 3 and CISA's Incident Response Plan (IRP) Basics are useful free references.
DFARS 252.204-7012 applies to defense contracts, so its 72-hour DoD reporting rule is not the rule for a law firm, medical practice, or dental office. Those organizations have their own legal and regulatory notification obligations, which they should confirm with counsel. The preparation is similar, though: know where sensitive data lives, keep logs, name decision-makers, preserve evidence, and practice. Our industries page covers how we support each of these practices.
Integrity Security Defense Corp helps Inland Empire defense suppliers prepare for incidents before they happen, through CMMC readiness, managed cybersecurity monitoring and response, and managed IT. We are not a C3PAO, we are not an authorized CMMC assessor, and we do not certify companies. This article is general information, not legal advice; your contract and the current regulation control. To review your incident response readiness, contact us or call (909) 310-2022.
Integrity Security Defense Corp helps Inland Empire defense contractors with CMMC readiness and managed cybersecurity. We are not a C3PAO and do not perform official certification assessments.