Skip to main content
DoD Contractors

DFARS 7012 Cyber Incident Reporting: The 72-Hour DIBNet Playbook

Ken Satkunam, CISM
Ken Satkunam, CISM

Published · 9 min read

DFARS 7012 Cyber Incident Reporting: The 72-Hour DIBNet Playbook

DFARS 7012 cyber incident reporting is the duty, under DFARS clause 252.204-7012, for defense contractors and subcontractors that handle covered defense information to report a cyber incident to DoD through DIBNet within 72 hours of discovery. To file, a company needs a DoD-approved medium assurance certificate. It must also preserve images of affected systems for at least 90 days after the report.

Key takeaways

  • The clause defines "rapidly report" as within 72 hours of discovery of a cyber incident, and the report goes to DoD at dibnet.dod.mil.
  • You need a DoD-approved medium assurance certificate to file, so get it before an incident, not during one.
  • Images of all known affected systems and relevant monitoring or packet capture data must be preserved for at least 90 days from the date you submit the report.
  • Isolated malicious software goes to the DoD Cyber Crime Center (DC3), never to the Contracting Officer.
  • Subcontractors report directly to DoD and give the DoD-assigned incident report number to the prime or next higher-tier subcontractor.

What does DFARS 252.204-7012 require when a cyber incident happens?

When you discover a cyber incident that affects a covered contractor information system or the covered defense information (CDI) on it, the clause requires two things: review for evidence of compromise, and rapidly report the incident to DoD. The same duty applies when an incident affects your ability to provide operationally critical support named in the contract.

Paragraph (c)(1)(i) says the review includes identifying compromised computers, servers, specific data and user accounts, plus other systems on your network that may have been accessed.

The incident duties sit in paragraphs (c) through (g) of the May 2024 clause, and the subcontract rules sit in paragraph (m). For the full clause, including NIST SP 800-171 and SPRS, see our DFARS 252.204-7012 compliance overview. This article focuses only on what to do after something goes wrong.

When does the 72-hour reporting clock start?

The clock starts at discovery. The clause defines "rapidly report" as "within 72 hours of discovery of any cyber incident," and it does not wait for you to confirm that CDI was actually taken.

A "cyber incident" is defined broadly: actions through computer networks that result in a compromise or "an actual or potentially adverse effect" on a system or its information. A suspicious login to a mailbox holding CUI drawings can qualify before anyone knows whether files left.

Your plan should say who can declare a reportable incident, who files the report, and who backs that person up on a weekend.

  • Name a primary and a backup reporter, each with a working certificate.
  • Write down the decision rule your team uses to call an event reportable.
  • Log the discovery time the moment an alert is confirmed as suspicious, not when the investigation ends.

What do you need before you can file on DIBNet?

You need a DoD-approved medium assurance certificate. Paragraph (c)(3) says the contractor or subcontractor "shall have or acquire" one to report cyber incidents, and it points to DoD's External Certification Authority (ECA) program at public.cyber.mil/eca.

DC3 says you do not have to join the voluntary DIB Cybersecurity Program to file. If you must report before you have a certificate, it says to email DC3.DCISE@us.af.mil or call the DCISE hotline at (410) 981-0104, which it lists as operating 24/7.

The DIB Cybersecurity rule at 32 CFR 236.4 adds that you need a Procurement Integrated Enterprise Environment (PIEE) account to access DIBNet, and that you may authorize your third-party security provider to report on your behalf. Put that authorization in writing ahead of time.

What information goes into a DIBNet cyber incident report?

The report uses DoD's Incident Collection Format (ICF), and DC3 lists 21 elements that contractors should provide, "as much of the following information as can be obtained," within 72 hours. You do not need every answer on day one, but you do need the business details on hand.

The elements fall into three groups:

  • Company and contract details: company name, Unique Entity Identifier (UEI), facility CAGE code, facility clearance level, contract number (PIID), affected contracts, and points of contact for your company, the government program manager and the Contracting Officer.
  • Impact: impact to CDI, ability to provide operationally critical support, the DoD programs, platforms or systems involved, and the contract clearance level.
  • The incident itself: date discovered, locations of compromise and their CAGE code, type of compromise, technique or method used, outcome, and a narrative covering the timeline, threat actor techniques, indicators of compromise and mitigation.

DC3 says new facts learned after the first report go in a follow-on ICF, which you open from your submission history. That is the practical answer to "we don't know enough yet": file what you know inside 72 hours, then update it.

What must you preserve, and for how long?

You must preserve and protect images of all known affected information systems, plus all relevant monitoring and packet capture data, for at least 90 days from the date you submit the report. Paragraph (e) of the clause says this is to allow DoD to request the media or decline interest.

Reimaging a laptop or rolling back a server is the fastest way to get people working again, and it can destroy the evidence the clause requires you to keep. The fix is sequencing:

  1. Isolate the affected systems from the network without powering them off when you can.
  2. Capture forensic images and export the relevant logs and packet captures before you wipe or restore anything.
  3. Store the images on protected media with a written chain of custody and a clear 90-day hold date.
  4. Only then rebuild or restore from clean backups.

Two more duties follow the preserved data. Under paragraph (f), DoD can ask for access to additional information or equipment needed for forensic analysis. Under paragraph (g), if DoD decides to do a damage assessment, the Contracting Officer will request the information you preserved.

Where does malicious software go?

Isolated malicious software goes to DC3. Paragraph (d) says to submit it "in accordance with instructions provided by DC3 or the Contracting Officer," and adds plainly: "Do not send the malicious software to the Contracting Officer."

DC3's FAQ describes two routes: an account on its Electronic Malware Submission portal (ems.dc3on.gov) for holders of a PKI certificate, or a DoD SAFE link requested by emailing DCISE with your ICF number in the subject line. Do not email the files themselves.

What do subcontractors owe the prime?

Subcontractors report the incident directly to DoD and then give the prime, or the next higher-tier subcontractor, the incident report number that DoD assigns automatically. Paragraph (m)(2)(ii) says to do that "as soon as practicable."

Primes must flow the clause down without alteration to subcontracts that involve CDI or operationally critical support, including commercial products and services.

One limit surprises people. DC3's FAQ says you cannot submit a mandatory report on behalf of a vendor or customer that suffered an attack, because the impacted company must report its own incident. If a supplier tells you it was breached, ask for its report number and assess your own exposure separately. Our guide to CUI handling for DoD contractors covers how to know which suppliers hold CUI in the first place.

How does this connect to NIST SP 800-171 and CMMC?

The incident response family in NIST SP 800-171 Revision 2 is where reporting readiness lives on paper. Requirement 3.6.1 calls for an operational incident-handling capability covering preparation, detection, analysis, containment, recovery and user response. Requirement 3.6.2 calls for tracking, documenting and reporting incidents to designated officials and authorities. Requirement 3.6.3 calls for testing the incident response capability.

A written plan that names DIBNet, the certificate holder, the 90-day hold and the DC3 malware route is concrete evidence for all three in a self-assessment or CMMC Level 2 assessment. For where your company sits in the CMMC rollout, see our CMMC compliance timeline and milestones.

How should a small defense contractor get ready this quarter?

Start with what takes longest to fix during a crisis: the certificate, the access accounts and the evidence process.

  1. Obtain a medium assurance certificate for at least two people and confirm both can reach DIBNet.
  2. Fill in a reference sheet with every ICF company and contract field, and store it off-network.
  3. Write an incident procedure that names the reportable-incident decision maker, the filer and the 72-hour timeline.
  4. Decide how you will capture images and packet data, where you will store them, and who tracks the 90-day hold.
  5. Add the subcontractor report-number step to your supplier agreements and your own procedure.
  6. Run a tabletop exercise against a realistic scenario, such as a compromised mailbox holding CUI, and record the result as 3.6.3 evidence.

NorthStar's incident response planning and escalation services help defense contractors put this plan in writing and rehearse it. Containment and documentation support is included with our higher service packages, and full forensic investigation runs through our forensics partner, which you contract with directly at added cost. If you are not sure where you stand, the free NorthStar security check is a quick first look, and our CMMC and DFARS compliance support for defense contractors covers the wider program. More articles for this audience are on the DoD contractor resources hub.

What else do defense contractors ask about DFARS incident reporting?

Do we have to report if we are not sure CUI was accessed?

The trigger is a cyber incident that affects a covered system or the CDI on it, and the definition includes potentially adverse effects. The clause also requires a review for evidence of compromise, so file within 72 hours with what you know and update it with a follow-on report.

Can our IT provider file the report for us?

32 CFR 236.4(f) allows a contractor to authorize its third-party security service provider to report on its behalf. The report is still about your incident, so document the authorization in advance and make sure the provider has the access it needs.

Should we report phishing attempts and scans?

Activity that does not compromise CDI or affect operationally critical support is not a mandatory report under the clause. DC3 encourages voluntary reports of things like phishing messages and scanning for situational awareness.

Sources

Industry Resources

DoD & CMMC Compliance Support

NorthStar helps defense contractors scope CUI, prepare for DFARS and CMMC requirements, and build an incident response plan that meets DoD reporting deadlines.

Learn More →
DFARS 7012incident reportingDIBNetCUIDoD contractors
Share this article

About the author

Ken Satkunam, CISM

Ken Satkunam, CISM

President & Founder, NorthStar Technology Group

Ken has spent over 25 years in IT leadership, serving in roles from technical support to CIO for organizations as large as 23,000 employees. He founded NorthStar Technology Group in 2000 to help regulated organizations build secure, compliant, and operationally resilient technology environments. Ken holds the Certified Information Security Manager (CISM) credential from ISACA and is the co-author of the Amazon best-seller "Cyber Attack Prevention." He has been quoted in industry publications including eWeek and DM News, and NorthStar has been recognized on the Inc. 5000 list in both 2024 and 2025.

CISMInc. 5000MSP 500Published Author25+ Years

Need Help With Your Technology Strategy?

Our experts can help you assess your current posture and build a roadmap for success.