Defense and defense contractors
- Confirm which reporting rows apply; record in T1 who decided each clock started.Legal advisor
- Record the discovery time in T1 KEY TIMES; the 72 hours run from there.Planning
- Open T17 for DIBNet, the Defense Counterintelligence and Security Agency (DCSA) and any Federal Acquisition Regulation (FAR) 52.204-23 or 52.204-25 report.Planning
- Confirm a named certificate holder can sign in to DIBNet now.Liaison
- Image every known affected system and preserve monitoring and packet capture data before any rebuild.Intelligence/Investigations
- Report suspected classified information to the facility security officer (FSO) at once and stop all copying.Liaison
Then work the page: Reporting obligations, Terms, Roles, What changes in each phase, Records, Who you work with.
This page is for responders at defense industrial base (DIB) companies: prime contractors and subcontractors that handle covered defense information or provide operationally critical support under a Department of Defense (DoD) contract. DoD components are covered at the level of public policy. Civilian agencies use Federal civilian agencies. The department also publishes as the Department of War (DoW); the regulations cited here say DoD.
For a contractor, the contract sets the rules. Defense Federal Acquisition Regulation Supplement (DFARS) clause 252.204-7012 starts a 72-hour reporting clock at discovery, requires a DoD-approved certificate to file, and orders media kept for 90 days after the report. Cleared facilities add National Industrial Security Program Operating Manual (NISPOM) reporting to DCSA.
Supplier Performance Risk System (SPRS) scores and Cybersecurity Maturity Model Certification (CMMC) affirmations already told DoD how the controls work. The incident will test that claim.
This page adds to the phase playbooks for scope, contain, eradicate and recover. Incident Command seats for this sector are on Command by incident type.
This sector page is an addition to the book. Primary sources checked: DFARS 252.204-7012 and PGI 204.7303-3; DIBNet; 32 CFR Part 236; 32 CFR Part 117; 32 CFR Part 170; CJCSM 6510.01B. DFARS 252.204-7012, PGI 204.7303-3, 32 CFR 117.8 and 117.18, FAR 52.204-23 and 52.204-25, CMMC status, the class deviation and NIST SP 800-171 status were checked October 2026. DC3's reporting page was checked November 2026. The rest were checked September 2026.
Reporting obligations
Counsel confirms which rows apply; the last row is for DoD components, the rest for contractors. Record in T1 who decided that each clock started, and when. The notification deadlines table lists other regimes.
| Obligation | Who reports to whom | Clock | Starts when | What the report contains |
|---|---|---|---|---|
| DFARS 252.204-7012(c), cyber incident report | Contractor or subcontractor to DoD at dibnet.dod.mil, signed in with a DoD-approved medium assurance certificate under (c)(3). That address now opens DC3's reporting page, which takes reports through the Incident Collection Format (ICF) portal at icf.dcise.cert.org | 72 hours ("rapidly report") | Discovery of a cyber incident that affects a covered contractor information system, the covered defense information on it, or the ability to perform operationally critical support | As much of DC3's list as can be obtained within the 72 hours: company name and point of contact, unique entity identifier (UEI), facility CAGE code and clearance level, contract numbers and their clearance level, contracting officer and program manager contacts, impact to CDI and to operationally critical support, date discovered, locations of compromise and the incident location CAGE code, DoD programs, platforms or systems involved, type of compromise, technique or method, outcome, a narrative and any additional information. Later findings go in a follow-on report |
| 7012(m)(2), subcontractor report number | Subcontractor to the prime, or the next higher-tier subcontractor | As soon as practicable | The subcontractor's own report to DoD | The incident report number DoD assigns |
| 7012(d), malicious software | Contractor to the DoD Cyber Crime Center (DC3) | With the incident, per instructions from DC3 or the contracting officer | Malicious software discovered and isolated in connection with a reported incident | The sample. PGI 204.7303-3 says the contracting officer should never receive malicious software directly |
| 7012(e), media preservation | Contractor keeps for DoD | At least 90 days | Submission of the cyber incident report | Images of all known affected information systems identified under (c)(1)(i), and all relevant monitoring and packet capture data |
| 7012(f) and (g), forensics and damage assessment | Contractor to DoD, on request through the contracting officer | When DoD asks | DoD's request, or its decision to run a damage assessment | Access to further information or equipment for forensic analysis, and the damage assessment information gathered under (e) |
| 32 CFR 117.8(f)(1), NISPOM cyber incident | Cleared defense contractor to DCSA, DoD's cognizant security office | Immediately | A cyber incident on a classified covered information system that DCSA approved to process classified information | The technique or method, a malware sample if isolated, and a summary of DoD program information potentially compromised |
| 32 CFR 117.8(d) and (b), classified loss or compromise | Contractor to DCSA. Espionage, sabotage, terrorism or subversion to the nearest FBI field office, with DCSA told | Preliminary inquiry immediately, initial report promptly, final report after the investigation. FBI report promptly, in writing | Loss, compromise or suspected compromise of classified information, including a data spill | Circumstances, the classified information involved, and at the end corrective and disciplinary actions |
| FAR 52.204-25(d) and 52.204-23(c) | Contractor to DoD at dibnet.dod.mil | 52.204-25: 1 business day, then 10 business days. 52.204-23: 3 business days, then 10 business days | Identifying covered telecommunications or video surveillance equipment, or a Kaspersky Lab covered article, in contract performance | Contract number, supplier, brand, model and description, then mitigation and prevention steps |
| CJCSM 6510.01B (DoD components) | DoD component through its aligned cybersecurity service provider (CSSP) and the reporting chain in the manual, with USCYBERCOM at Tier I | Set by category in the manual's reporting timelines (Appendix A to Enclosure C) | Detection of a reportable event or incident | The category (CAT 0 to 9) and the manual's report format |
CMMC adds no incident clock. The DFARS CMMC rule dropped the proposed requirement to notify the contracting officer of security lapses. A FAR clause for CUI across civilian contracts remains proposed. The June 23, 2026 proposal would add FAR 52.240-7 with a 72-hour report, filed at dibnet.dod.mil for DoD contracts and with CISA for other agencies. It had not become final as of October 1, 2026.
CMMC status as of October 10, 2026: 32 CFR Part 170 took effect December 16, 2024. The DFARS rule adding 252.204-7021 took effect November 10, 2025 and started Phase 1 (Level 1 and Level 2 self-assessments). On July 13, 2026, the department suspended Phase 2, which was to start November 10, 2026, so Phase 2 does not start on that date. Phase 1 self-assessments, 7012 and NIST SP 800-171 Rev 2 remain in force. A CMMC Reform Task Force review ended September 11, 2026, and no date to resume Phase 2 had been announced as of October 1, 2026.
Class Deviation 2026-O0025, effective February 1, 2026, moved the CMMC and assessment prescriptions into DFARS Part 240 under the FAR overhaul. It replaces 252.204-7020 with 252.240-7997, NIST SP 800-171 DoD Assessment Requirements, and drops 252.204-7019. Clauses 252.204-7012 and 252.204-7021 keep their numbers. Revision 2 (July 16, 2026) superseded the original deviation. Revision 3 (September 3, 2026) implements the Phase 2 suspension and directs contracting officers to remove or revise CMMC requirements in new and existing solicitations and contracts (confirm against the deviation text and the clauses in each contract).
Sources: DFARS 252.204-7012 (May 2024); PGI 204.7303-3; DC3's Mandatory and Voluntary Cyber Incident Reporting page, which dibnet.dod.mil now opens, for the report elements and the ICF portal (checked November 2026); 32 CFR 117.8 and 117.18; FAR 52.204-25 (November 2021) and 52.204-23 (December 2023, 88 FR 69503, October 5, 2023, effective December 4, 2023); CJCSM 6510.01B, July 10, 2012, current as of December 18, 2014; DFARS CMMC final rule, September 10, 2025; FAR proposed rule, June 23, 2026, which Secureframe reports as not final as of October 1, 2026.
Terms
| Term | Meaning | PIVTR-D equivalent |
|---|---|---|
| DIB | Defense industrial base: the companies that supply DoD, primes and subcontractors | none |
| CUI | Controlled unclassified information: information the government creates or possesses, or an entity creates or possesses for it, that law, regulation or government-wide policy requires or permits to be safeguarded (32 CFR 2002.4). DoD marks and handles it under DoDI 5200.48 | Restricted data scenario |
| CDI | Covered defense information: unclassified controlled technical information or other CUI in the CUI Registry. It is either marked or identified in the contract and provided by or for DoD, or collected, developed, received, transmitted, used or stored by the contractor in performing the contract | Restricted data |
| CTI | Controlled technical information: technical information with military or space application under controls on access, use, reproduction and release | Restricted data |
| FCI | Federal contract information, protected by FAR 52.204-21 and CMMC Level 1 | none |
| Operationally critical support | Supplies or services the government designates as critical for airlift, sealift, intermodal transportation or logistical support essential to mobilizing, deploying or sustaining the armed forces in a contingency operation | Critical system in the containment triggers |
| Cyber incident | In 7012, actions through computer networks that compromise a system or its information, or have an actual or potential adverse effect on them | Incident |
| DFARS 7012 | Clause 252.204-7012, the safeguarding and 72-hour reporting clause | none |
| DIBNet | The DoD address in 7012, dibnet.dod.mil, for mandatory and voluntary cyber incident reports. In November 2026 it opens DC3's Mandatory and Voluntary Cyber Incident Reporting page, and reports go in through the Incident Collection Format (ICF) portal at icf.dcise.cert.org | none |
| Medium assurance certificate | A DoD-approved public key certificate required to sign in to DIBNet and file a report | none |
| Incident report number | The number DoD assigns to a DIBNet report. Subcontractors pass it up the chain | External reference in T17 |
| DC3 | DoD Cyber Crime Center: receives DIBNet reports and malware, runs forensics and DCISE | none |
| DCISE | DoD-DIB Collaborative Information Sharing Environment, run by DC3, which shares threat information with DIB CS participants | none |
| DIB CS Program | DoD's voluntary cybersecurity information sharing program for contractors, under 32 CFR 236.5 and a framework agreement | none |
| NIST SP 800-171 | The 110 security requirements for CUI on contractor systems. 7012 and CMMC Level 2 use Revision 2. Incident response is 3.6.1 (handling capability), 3.6.2 (track, document and report) and 3.6.3 (test) | Preparation |
| SSP | System security plan: how each requirement is met in the assessed system | none |
| POA&M | Plan of action and milestones for requirements not yet met. Under CMMC, open items close within 180 days | T14 Improvement register |
| SPRS | Supplier Performance Risk System, where DoD stores assessment scores and CMMC affirmations | none |
| CMMC levels | Level 1 (15 FAR 52.204-21 requirements, self-assessed), Level 2 (110 NIST SP 800-171 Rev 2 requirements, self or C3PAO), Level 3 (24 requirements from NIST SP 800-172, assessed by DCMA DIBCAC). Since July 13, 2026, new contract requirements are limited to Level 1 and Level 2 self-assessments | none |
| C3PAO | CMMC third-party assessment organization, accredited to run Level 2 certification assessments. The July 13, 2026 suspension directs contracting officers to remove C3PAO requirements from solicitations and contracts. Voluntary assessments remain available | none |
| Affirming official | The senior person who affirms CMMC compliance in SPRS, after each assessment and annually | none |
| FedRAMP Moderate equivalent | 7012(b)(2)(ii)(D) requires a cloud service that stores CDI to meet requirements equivalent to the FedRAMP Moderate baseline. The DoD CIO memorandum of December 21, 2023 accepts FedRAMP Moderate authorization, or a FedRAMP-recognized 3PAO assessment showing every Moderate control met with no open POA&M items | none |
| Flowdown | The prime puts 7012 into subcontracts, unaltered, when the subcontract involves CDI or operationally critical support | none |
| CAGE code | Commercial and Government Entity code, the identifier for a contractor facility. DIBNet asks for it | none |
| NISPOM | National Industrial Security Program Operating Manual, 32 CFR Part 117, the rules for contractors cleared for classified work | none |
| DCSA | Defense Counterintelligence and Security Agency, DoD's cognizant security office for cleared contractors | none |
| FSO | Facility security officer: supervises the cleared facility's security program and reports to DCSA | none |
| ISSM | Information system security manager: runs security for the contractor's classified information systems | none |
| Spillage | Classified information on a system not approved for it. NISPOM treats it as a data spill and requires plans to assess, report, isolate and contain it | none. Hand to the FSO |
| CSSP | Cybersecurity service provider that monitors and defends DoD systems aligned to it | Operations for DoD components |
| JFHQ-DODIN | Joint Force Headquarters-DoD Information Network, under USCYBERCOM, directs DODIN operations and defense | none |
| USCYBERCOM | US Cyber Command, Tier I in CJCSM 6510.01B | none |
| CAT 0 to CAT 9 | CJCSM 6510.01B categories. Incidents: 1 root level intrusion, 2 user level intrusion, 4 denial of service, 7 malicious logic. Events: 3 unsuccessful activity attempt, 5 non-compliance activity, 6 reconnaissance, 8 investigating, 9 explained anomaly. 0 is training and exercises | Classification in T1 |
Roles
| Sector role | What they do in an incident | PIVTR-D or Incident Command seat |
|---|---|---|
| Certificate holder | Files the DIBNet report and records the incident report number | Liaison |
| Contracts manager | Names affected contracts, contracting officers and program managers; receives DoD requests under 7012(f) and (g) | Liaison |
| Government contracts counsel | Decides which clauses apply, approves reports, and owns False Claims Act exposure | Legal advisor |
| Affirming official | Owns the CMMC affirmation and decides, with counsel, whether it still stands | CISO |
| Facility security officer | Reports classified loss, compromise and cyber incidents to DCSA, and espionage indicators to the FBI | Liaison, beside the Legal advisor |
| ISSM | Isolates and contains spills on classified systems under the approved plan | Operations, classified systems branch |
| Cloud service provider | Meets 7012(c) to (g) for CDI it stores and preserves its evidence | Assisting organization through Liaison |
| Contracting officer | Receives DC3's copy of the report and relays DoD requests | External, through Liaison |
| CSSP (DoD components) | Detects, reports and responds for aligned systems | Operations |
| Authorizing official (DoD components) | Accepts residual risk before an affected system returns to service | CISO |
What changes in each phase
Preparation
| # | Item | Owner |
|---|---|---|
| 1 | Get current DoD-approved medium assurance certificates for two or more named people, have each sign in to DIBNet, and track expiry dates | Liaison |
| 2 | Keep a contract register listing 7012, 7021, 252.240-7997, 52.204-21, 52.204-23, 52.204-25 and NISPOM duties, with contracting officers, program managers and CAGE codes | Legal advisor |
| 3 | Map where CDI lives, with each cloud provider's FedRAMP evidence and incident notice terms | Planning |
| 4 | Set log, endpoint detection and response (EDR) and packet capture retention to last 90 days past a report, and provide storage for full disk images | Logistics |
| 5 | List the subcontracts that carry 7012, with each subcontractor's incident contact | Liaison |
| 6 | Write up the incident response plan and its annual test against 3.6.1 to 3.6.3 in the SSP | CISO |
| 7 | At a cleared facility, put the FSO and ISSM on the call list and rehearse the data spill plan from 117.18(b)(2) | CISO |
| 8 | For a DoD component, write CSSP alignment and the reporting chain into the plan, with CJCSM 6510.01B categories in the classification matrix | CISO |
Identification and verification
| # | Item | Owner |
|---|---|---|
| 1 | Record the discovery time in T1 KEY TIMES. The 72 hours run from discovery of an incident affecting a covered contractor information system, whether or not CDI compromise is confirmed | Planning |
| 2 | Review for evidence of CDI compromise under 7012(c)(1)(i): computers, servers, specific data and user accounts | Intelligence/Investigations |
| 3 | Check operationally critical support for impact | Operations |
| 4 | Report suspected classified information on an unclassified system to the FSO at once, and stop further copying | Liaison |
| 5 | Route signs of espionage or foreign targeting to counsel and the FSO for the FBI report | Legal advisor |
| 6 | Ask cloud providers that store CDI for their incident status in writing | Liaison |
| 7 | For a DoD component, assign the CAT and report it through the CSSP | Intelligence/Investigations |
Response loop
| # | Item | Owner |
|---|---|---|
| 1 | Preserve images of every known affected system and the relevant monitoring and packet capture data before any rebuild | Intelligence/Investigations |
| 2 | File the DIBNet report within 72 hours with the facts known and unknowns marked, and record counsel's approval | Liaison |
| 3 | If you are a subcontractor, send the incident report number to the prime or the next higher tier | Liaison |
| 4 | Send malware to DC3 under instructions from DC3 or the contracting officer | Intelligence/Investigations |
| 5 | Log every DoD request for media, access or damage assessment information with its answer | Planning |
| 6 | Extend scope to CDI in cloud services and at subcontractors that received it | Intelligence/Investigations |
| 7 | Decide containment on classified systems with the ISSM and FSO, following DCSA direction | Incident Commander |
| 8 | For a DoD component, coordinate containment with the CSSP and follow the directions it relays | Operations |
Debrief
| # | Item | Owner |
|---|---|---|
| 1 | Update the SSP and POA&M for each control the incident showed missing or failed | CISO |
| 2 | Have counsel review whether findings contradict the SPRS score or a CMMC affirmation, before the next affirmation | Legal advisor |
| 3 | Release preserved media after the 90 days only with counsel's written approval and no open DoD request | Legal advisor |
| 4 | Build the findings into the next 3.6.3 incident response test | Planning |
| 5 | Fix flowdown and cloud gaps in the contracts | Liaison |
Records
| Record | What changes |
|---|---|
| T1 Incident record | Add the affected contracts, CAGE codes, whether CDI or operationally critical support is involved, whether classified systems are involved, and the DIBNet incident report number |
| T2 Triage brief | State the CDI answer, the classified answer and the time left on the 72-hour clock |
| T13 Law enforcement and insurer contact | Log FBI and DCIS contacts, and the FSO's reports to DCSA |
| T17 Regulator notification worksheet | One worksheet each for DIBNet, DCSA and any FAR 52.204-23 or 52.204-25 report. Attach the DIBNet confirmation and report number |
| T19 Vendor evidence and preservation request | Ask cloud providers that store CDI for their images, logs and packet capture under 7012(c) to (g), preserved for 90 days from the report date |
| DIBNet report form | Supplements T15 Incident report for DoD. Keep the submitted copy with the report number |
| Media preservation log | Each image and capture, its hash, storage location and the release date 90 days after submission |
Who you work with
| Body | What they do for you | How to reach them |
|---|---|---|
| DC3 | Receives mandatory reports and malware, sends the report to contracting officers, and offers analysis | dibnet.dod.mil, which opens DC3's reporting page and its link to the ICF portal. A medium assurance certificate is required. Without one, DC3 says to contact DCISE at DC3.DCISE@us.af.mil or 410-981-0104 |
| DCISE and the DIB CS Program | Voluntary threat sharing, mitigation advice and analyst exchanges | Join through a framework agreement with DoD, described at dibnet.dod.mil |
| Contracting officer | Relays DoD requests for media, access and damage assessment, and coordinates across contracts | Named in each contract |
| DCSA | Receives NISPOM reports and directs handling of classified systems and spills | Through the FSO and the facility's assigned DCSA representative |
| FBI | Criminal and counterintelligence investigation | Nearest field office, directly or through the FSO |
| DCIS | The DoD Inspector General's criminal investigators, who investigate intrusions and data theft affecting DoD and the DIB | DoD Office of Inspector General |
| DoD CIO and DCMA DIBCAC | Set CMMC and NIST SP 800-171 assessment policy. DIBCAC runs government assessments | Through the contracting officer |
| CSSP and JFHQ-DODIN | DoD components: monitoring, response and directions for DODIN defense | Through the component's aligned CSSP |
Sources: 32 CFR 2002.4; 32 CFR 170, 89 FR 83092, October 15, 2024; DoD, CMMC Phase II suspension, July 13, 2026, which keeps 7012 in force and enforces NIST SP 800-171 Rev 2 through self-assessments and select government-led assessments; DoD RFO deviation, DFARS Part 240 (Class Deviation 2026-O0025, effective February 1, 2026); Summit 7 on 7019 and 7020; Wiley's DFARS Overhaul Class Deviations summary (updated September 18, 2026), Serabrynn, Pivot Point Security and Secureframe on Revisions 2 and 3, because the revision memos would not open for the October check; ISI (reviewed October 1, 2026) and DLA Piper on the task force and the self-assessment limit; Wiley on Class Deviation 2024-O0013 (May 2, 2024), which keeps 7012 at NIST SP 800-171 Rev 2; Crowell & Moring on the DoD CIO FedRAMP Moderate equivalency memorandum (December 21, 2023); NIST SP 800-171 Rev 2; DoDI 8530.01, March 7, 2016; DCIS Cyber Field Office; DOJ, Civil Cyber-Fraud Initiative, October 6, 2021, and settlements with MORSECORP (March 26, 2025) and Georgia Tech Research Corporation (September 30, 2025) and Honeywell Aerospace (September 1, 2026), checked October 2026.
- A certificate ordered after discovery may arrive after the 72 hours end. Obtain certificates before an incident.
- Rebuilding a host before imaging it breaks 7012(e). Image first, then rebuild.
- DOJ's Civil Cyber-Fraud Initiative targets knowing failures to report cyber incidents and misstated security practices. MORSECORP paid $4.6 million in 2025 to resolve allegations over a score of 104 that a consultant later put at -142. Georgia Tech Research Corporation paid $875,000 in 2025 to resolve allegations over a score of 98 for a campus-wide system that, the government said, did not exist. Honeywell Aerospace paid $2,042,518 on September 1, 2026 to resolve allegations that one of its networks did not meet NIST SP 800-171. Counsel approves every report and affirmation.
- Spilled classified information copied into tickets, chat or a vendor's tools spreads the spill. Stop copying and call the FSO.