PIVTR-D
SSector

Defense and defense contractors

First moves
  1. Confirm which reporting rows apply; record in T1 who decided each clock started.Legal advisor
  2. Record the discovery time in T1 KEY TIMES; the 72 hours run from there.Planning
  3. 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
  4. Confirm a named certificate holder can sign in to DIBNet now.Liaison
  5. Image every known affected system and preserve monitoring and packet capture data before any rebuild.Intelligence/Investigations
  6. 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.

ObligationWho reports to whomClockStarts whenWhat the report contains
DFARS 252.204-7012(c), cyber incident reportContractor 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.org72 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 supportAs 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 numberSubcontractor to the prime, or the next higher-tier subcontractorAs soon as practicableThe subcontractor's own report to DoDThe incident report number DoD assigns
7012(d), malicious softwareContractor to the DoD Cyber Crime Center (DC3)With the incident, per instructions from DC3 or the contracting officerMalicious software discovered and isolated in connection with a reported incidentThe sample. PGI 204.7303-3 says the contracting officer should never receive malicious software directly
7012(e), media preservationContractor keeps for DoDAt least 90 daysSubmission of the cyber incident reportImages 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 assessmentContractor to DoD, on request through the contracting officerWhen DoD asksDoD's request, or its decision to run a damage assessmentAccess to further information or equipment for forensic analysis, and the damage assessment information gathered under (e)
32 CFR 117.8(f)(1), NISPOM cyber incidentCleared defense contractor to DCSA, DoD's cognizant security officeImmediatelyA cyber incident on a classified covered information system that DCSA approved to process classified informationThe 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 compromiseContractor to DCSA. Espionage, sabotage, terrorism or subversion to the nearest FBI field office, with DCSA toldPreliminary inquiry immediately, initial report promptly, final report after the investigation. FBI report promptly, in writingLoss, compromise or suspected compromise of classified information, including a data spillCircumstances, 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.mil52.204-25: 1 business day, then 10 business days. 52.204-23: 3 business days, then 10 business daysIdentifying covered telecommunications or video surveillance equipment, or a Kaspersky Lab covered article, in contract performanceContract 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 ISet by category in the manual's reporting timelines (Appendix A to Enclosure C)Detection of a reportable event or incidentThe 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

TermMeaningPIVTR-D equivalent
DIBDefense industrial base: the companies that supply DoD, primes and subcontractorsnone
CUIControlled 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.48Restricted data scenario
CDICovered 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 contractRestricted data
CTIControlled technical information: technical information with military or space application under controls on access, use, reproduction and releaseRestricted data
FCIFederal contract information, protected by FAR 52.204-21 and CMMC Level 1none
Operationally critical supportSupplies 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 operationCritical system in the containment triggers
Cyber incidentIn 7012, actions through computer networks that compromise a system or its information, or have an actual or potential adverse effect on themIncident
DFARS 7012Clause 252.204-7012, the safeguarding and 72-hour reporting clausenone
DIBNetThe 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.orgnone
Medium assurance certificateA DoD-approved public key certificate required to sign in to DIBNet and file a reportnone
Incident report numberThe number DoD assigns to a DIBNet report. Subcontractors pass it up the chainExternal reference in T17
DC3DoD Cyber Crime Center: receives DIBNet reports and malware, runs forensics and DCISEnone
DCISEDoD-DIB Collaborative Information Sharing Environment, run by DC3, which shares threat information with DIB CS participantsnone
DIB CS ProgramDoD's voluntary cybersecurity information sharing program for contractors, under 32 CFR 236.5 and a framework agreementnone
NIST SP 800-171The 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
SSPSystem security plan: how each requirement is met in the assessed systemnone
POA&MPlan of action and milestones for requirements not yet met. Under CMMC, open items close within 180 daysT14 Improvement register
SPRSSupplier Performance Risk System, where DoD stores assessment scores and CMMC affirmationsnone
CMMC levelsLevel 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-assessmentsnone
C3PAOCMMC 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 availablenone
Affirming officialThe senior person who affirms CMMC compliance in SPRS, after each assessment and annuallynone
FedRAMP Moderate equivalent7012(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 itemsnone
FlowdownThe prime puts 7012 into subcontracts, unaltered, when the subcontract involves CDI or operationally critical supportnone
CAGE codeCommercial and Government Entity code, the identifier for a contractor facility. DIBNet asks for itnone
NISPOMNational Industrial Security Program Operating Manual, 32 CFR Part 117, the rules for contractors cleared for classified worknone
DCSADefense Counterintelligence and Security Agency, DoD's cognizant security office for cleared contractorsnone
FSOFacility security officer: supervises the cleared facility's security program and reports to DCSAnone
ISSMInformation system security manager: runs security for the contractor's classified information systemsnone
SpillageClassified information on a system not approved for it. NISPOM treats it as a data spill and requires plans to assess, report, isolate and contain itnone. Hand to the FSO
CSSPCybersecurity service provider that monitors and defends DoD systems aligned to itOperations for DoD components
JFHQ-DODINJoint Force Headquarters-DoD Information Network, under USCYBERCOM, directs DODIN operations and defensenone
USCYBERCOMUS Cyber Command, Tier I in CJCSM 6510.01Bnone
CAT 0 to CAT 9CJCSM 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 exercisesClassification in T1

Roles

Sector roleWhat they do in an incidentPIVTR-D or Incident Command seat
Certificate holderFiles the DIBNet report and records the incident report numberLiaison
Contracts managerNames affected contracts, contracting officers and program managers; receives DoD requests under 7012(f) and (g)Liaison
Government contracts counselDecides which clauses apply, approves reports, and owns False Claims Act exposureLegal advisor
Affirming officialOwns the CMMC affirmation and decides, with counsel, whether it still standsCISO
Facility security officerReports classified loss, compromise and cyber incidents to DCSA, and espionage indicators to the FBILiaison, beside the Legal advisor
ISSMIsolates and contains spills on classified systems under the approved planOperations, classified systems branch
Cloud service providerMeets 7012(c) to (g) for CDI it stores and preserves its evidenceAssisting organization through Liaison
Contracting officerReceives DC3's copy of the report and relays DoD requestsExternal, through Liaison
CSSP (DoD components)Detects, reports and responds for aligned systemsOperations
Authorizing official (DoD components)Accepts residual risk before an affected system returns to serviceCISO

What changes in each phase

Preparation

#ItemOwner
1Get current DoD-approved medium assurance certificates for two or more named people, have each sign in to DIBNet, and track expiry datesLiaison
2Keep 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 codesLegal advisor
3Map where CDI lives, with each cloud provider's FedRAMP evidence and incident notice termsPlanning
4Set log, endpoint detection and response (EDR) and packet capture retention to last 90 days past a report, and provide storage for full disk imagesLogistics
5List the subcontracts that carry 7012, with each subcontractor's incident contactLiaison
6Write up the incident response plan and its annual test against 3.6.1 to 3.6.3 in the SSPCISO
7At a cleared facility, put the FSO and ISSM on the call list and rehearse the data spill plan from 117.18(b)(2)CISO
8For a DoD component, write CSSP alignment and the reporting chain into the plan, with CJCSM 6510.01B categories in the classification matrixCISO

Identification and verification

#ItemOwner
1Record 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 confirmedPlanning
2Review for evidence of CDI compromise under 7012(c)(1)(i): computers, servers, specific data and user accountsIntelligence/Investigations
3Check operationally critical support for impactOperations
4Report suspected classified information on an unclassified system to the FSO at once, and stop further copyingLiaison
5Route signs of espionage or foreign targeting to counsel and the FSO for the FBI reportLegal advisor
6Ask cloud providers that store CDI for their incident status in writingLiaison
7For a DoD component, assign the CAT and report it through the CSSPIntelligence/Investigations

Response loop

#ItemOwner
1Preserve images of every known affected system and the relevant monitoring and packet capture data before any rebuildIntelligence/Investigations
2File the DIBNet report within 72 hours with the facts known and unknowns marked, and record counsel's approvalLiaison
3If you are a subcontractor, send the incident report number to the prime or the next higher tierLiaison
4Send malware to DC3 under instructions from DC3 or the contracting officerIntelligence/Investigations
5Log every DoD request for media, access or damage assessment information with its answerPlanning
6Extend scope to CDI in cloud services and at subcontractors that received itIntelligence/Investigations
7Decide containment on classified systems with the ISSM and FSO, following DCSA directionIncident Commander
8For a DoD component, coordinate containment with the CSSP and follow the directions it relaysOperations

Debrief

#ItemOwner
1Update the SSP and POA&M for each control the incident showed missing or failedCISO
2Have counsel review whether findings contradict the SPRS score or a CMMC affirmation, before the next affirmationLegal advisor
3Release preserved media after the 90 days only with counsel's written approval and no open DoD requestLegal advisor
4Build the findings into the next 3.6.3 incident response testPlanning
5Fix flowdown and cloud gaps in the contractsLiaison

Records

RecordWhat changes
T1 Incident recordAdd 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 briefState the CDI answer, the classified answer and the time left on the 72-hour clock
T13 Law enforcement and insurer contactLog FBI and DCIS contacts, and the FSO's reports to DCSA
T17 Regulator notification worksheetOne 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 requestAsk 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 formSupplements T15 Incident report for DoD. Keep the submitted copy with the report number
Media preservation logEach image and capture, its hash, storage location and the release date 90 days after submission

Who you work with

BodyWhat they do for youHow to reach them
DC3Receives mandatory reports and malware, sends the report to contracting officers, and offers analysisdibnet.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 ProgramVoluntary threat sharing, mitigation advice and analyst exchangesJoin through a framework agreement with DoD, described at dibnet.dod.mil
Contracting officerRelays DoD requests for media, access and damage assessment, and coordinates across contractsNamed in each contract
DCSAReceives NISPOM reports and directs handling of classified systems and spillsThrough the FSO and the facility's assigned DCSA representative
FBICriminal and counterintelligence investigationNearest field office, directly or through the FSO
DCISThe DoD Inspector General's criminal investigators, who investigate intrusions and data theft affecting DoD and the DIBDoD Office of Inspector General
DoD CIO and DCMA DIBCACSet CMMC and NIST SP 800-171 assessment policy. DIBCAC runs government assessmentsThrough the contracting officer
CSSP and JFHQ-DODINDoD components: monitoring, response and directions for DODIN defenseThrough 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.

Watch out
  • 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.
Adapts material from Dynamic Incident Response: A Framework for Security Teams by Joshua Wright, © 2026 The Escal Institute of Advanced Technologies, Inc. d/b/a SANS Institute, licensed under CC BY 4.0. Figures reproduced under that license. Changes were made. Not published by, endorsed by, or affiliated with the SANS Institute.