If you handle Controlled Unclassified Information (CUI) for the Department of Defense, CMMC expects you to have a working incident response capability, not just a document. That means detecting an incident, containing it, reporting it, keeping the evidence and recovering. Where your contract includes the DFARS 252.204-7012 clause, the reporting deadline is 72 hours from discovery. A small business can meet all of this, but it needs named people, a written plan, tested backups and round-the-clock visibility into its systems. That last piece is what we provide for Oklahoma small businesses through managed IT support.
Key Takeaways
- CMMC Level 2 incident response comes down to three things: handle incidents, track and report them, and test your capability. The plan has to work in practice.
- If your contract carries DFARS 252.204-7012, you report qualifying cyber incidents to DoD within 72 hours of discovery. You also preserve affected system images and monitoring data for at least 90 days.
- As of mid-2026, parts of CMMC rollout are paused for review, but DFARS 7012 incident reporting is unchanged and still applies.
- A good plan names who decides, who reports, who contains and who restores. Test it at least once a year, and keep the records, because they are your evidence.
Table of Contents
- Who this applies to
- What CMMC actually requires for incident response
- The 72-hour rule under DFARS 252.204-7012
- What is the status of CMMC right now?
- What your incident response plan should include
- How to test the plan
- Where small contractors go wrong
- Getting the plan operational with local support
- FAQ
- Sources
Who this applies to
CMMC is the Department of Defense's program for verifying that contractors protect sensitive information. Two kinds of information matter. Federal Contract Information (FCI) is non-public information the government gives you or you create under a contract. CUI is a more sensitive category the government says needs safeguarding, such as technical drawings or export-controlled specifications.
Under the CMMC rule in 32 CFR Part 170, CMMC applies to contractor systems that process, store or transmit FCI or CUI. It also reaches systems that protect those systems, and systems that are not logically or physically separated from them. If your shop floor network, your Microsoft 365 tenant and your file server all touch CUI, they are all in scope for incident response.
The formal incident response controls belong to Level 2, the level for CUI. If you only handle FCI, your target is Level 1, which has 15 basic safeguarding requirements and no dedicated incident response domain. Our guide to the 15 CMMC Level 1 requirements covers that path. Even so, a Level 1 company that gets hit by ransomware still needs a plan, which is why much of what follows is worth doing at any level.
What CMMC actually requires for incident response
The Level 2 incident response practices come from NIST SP 800-171, the federal standard that CMMC Level 2 is built on. In plain terms there are three:
- Incident handling (3.6.1). You have an operational capability to prepare for, detect, analyze, contain, recover from and respond to incidents.
- Incident reporting (3.6.2). You track and document incidents, and report them to the right people inside the company and to outside authorities.
- Incident response testing (3.6.3). You test that capability.
The NDISAC supplier training for the defense industrial base describes the expectation the same way: establish an operational incident-handling capability, then track, document and report incidents to management and to authorities.
The word "operational" is the one that trips up small companies. An assessor does not want to see a template saved in a folder. They want to see that someone owns the process, that staff know whom to call, and that the process has been exercised. Your evidence is typically the plan itself, named roles, incident tickets or logs, training records and the results of your last test.
The 72-hour rule under DFARS 252.204-7012
CMMC is not the only rule that governs incidents. If your contract includes DFARS clause 252.204-7012, that clause sets a legal reporting trigger and deadline.
What triggers a report. A cyber incident that affects a covered contractor information system or the covered defense information on it. It also includes an incident that affects your ability to perform contract requirements designated as operationally critical support.
When and where. Under the clause, you report rapidly, within 72 hours of discovery, to DoD through DIBNet, the department's online reporting portal. DIBNet is run by the DoD Cyber Crime Center, known as DC3.
What you must preserve. The same clause requires you to keep images of known affected systems, plus relevant monitoring or packet-capture data, for at least 90 days from the date you submit the report. If you isolate malicious software, you submit it to DC3 as they instruct.
What you must look for. The clause requires a review for evidence of compromise of covered defense information. That includes identifying compromised computers, servers, specific data and user accounts, and analyzing the affected systems and other parts of your network that may have been reached.
Two practical points follow from this. First, "discovery" starts the clock, so you need monitoring that actually discovers things. A breach that sits unnoticed for weeks is a bad outcome, and it also makes your later 72-hour report harder to defend. Second, you can only preserve system images and monitoring data if you were collecting them before the incident. Wiping a laptop to "clean it up" before imaging it destroys evidence you are required to keep.
The NDISAC training adds two points. It advises that you notify the contacts your contract requires, commonly the buyer or subcontract administrator, in addition to reporting to DoD. It also recommends reporting suspected incidents promptly even when no mandatory threshold has clearly been met. That is guidance, separate from the legal trigger and deadline in the clause. If you are a subcontractor, check your agreement for a flow-down notice period to your prime, because it may be shorter than 72 hours.

What is the status of CMMC right now?
The rules have moved recently, so here is the picture as published.
The final CMMC acquisition rule took effect on November 10, 2025. It added DFARS 252.204-7025 and revised DFARS 252.204-7021. The Army's Small Business Office summary says contractors should keep reporting cyber incidents under DFARS 252.204-7012 within 72 hours through DC3's portal.
As of July 29, 2026, a published white paper reports that Phase 2 and pending CMMC implementation milestones were suspended during a review. Phase 1 self-assessments, SPRS scores, annual affirmations and DFARS 7012 incident reporting stayed in effect. During the suspension, contracting officials may require Level 1 (Self) or Level 2 (Self) in solicitations, but not a third-party Level 2 certification or a government-led Level 3 assessment.
What does that mean for you? A pause in third-party assessments does not pause the incident reporting clause or your obligation to attest to your security posture. Companies that build the incident response capability now are not wasting effort: the same plan supports your self-assessment, your SPRS score and your annual affirmation. Our walkthrough of the CMMC self-assessment and SPRS shows where incident response fits into the score. Because this program has changed several times, check the DoD CIO's CMMC page and your contract language for the current schedule before you plan around any date.
What your incident response plan should include
No single format is mandated, but a plan that satisfies an assessor and works at 2 a.m. has the same core parts. Keep it short enough that people will read it during an emergency, ideally under ten pages plus a contact sheet.
1. Scope and definitions
State which systems are in scope (anything touching FCI or CUI), and define "incident" in plain words: ransomware, a compromised email account, a lost laptop with CUI on it, an unauthorized person in a file share. Add a severity scale of three or four levels so staff know when to escalate.
2. Roles and contacts
Name a person, with a backup, for each job:
- Incident lead: makes the calls and keeps the timeline.
- Technical lead: isolates systems and collects evidence.
- Reporting contact: files the DIBNet report and notifies your prime or contracting officer.
- Leadership contact: an owner or executive who can approve shutting systems down.
- Outside help: your IT provider, your attorney and your cyber insurance carrier, with phone numbers that work after hours.
If you do not have a DIBNet account, getting one is a task for now, not for the middle of an incident. DoD requires a medium assurance certificate to submit reports, and getting one takes time, so plan for that in advance.
3. Detection and triage
Say how incidents are noticed: monitoring alerts, antivirus or endpoint detection, a user reporting a strange email, a vendor notice. Tell employees exactly how to report something suspicious, whom to call and that nobody will be blamed for reporting. Record who decides whether an event is a reportable cyber incident, and write down the time of discovery, because that starts the 72-hour clock.
4. Containment
List the first moves: disconnect affected machines from the network, disable compromised accounts, block malicious addresses and stop the spread. Specify what not to do, such as powering off a machine in a way that loses memory evidence or reimaging before capture.
5. Evidence preservation and investigation
Tie this to the DFARS clause. Specify how system images and logs are captured, where they are stored, who can access them and how long they are retained (at least 90 days from the report). Decide in advance who reviews for evidence of compromise of covered defense information, and how they will identify affected accounts, servers and data.
6. Reporting
Include a checklist: DIBNet report within 72 hours, notice to your prime or contract contacts, internal notice to management, and, if personal data of employees or customers is involved, a check with your attorney on state breach notification duties. Oklahoma businesses with customer data should ask counsel about state requirements rather than assume DFARS covers them.
7. Recovery
Describe how you restore systems from clean backups, in what order, and how you confirm they are free of the attacker's access before reconnecting. Write down two numbers for each key system: how much downtime you can tolerate (recovery time objective) and how much recent data you can afford to lose (recovery point objective). Backups that have never been restored are a guess, so record the date of your last successful restore test. This is where backup and recovery either makes the plan real or leaves it hollow.
8. After the incident
Hold a review within a couple of weeks. Record what happened, what worked, what failed and what you will change. Update the plan, your system security plan and, if your controls changed, your self-assessment records. For a general walk through the phases, see our guide to NIST and CISA aligned incident response steps.
How to test the plan
The third control, incident response testing, is the one most often skipped. You do not need an expensive simulation. A practical schedule for a small contractor:
- Tabletop exercise, at least annually. Gather your incident lead, technical lead, reporting contact and an owner for 60 to 90 minutes. Walk through a scenario, for example: an employee clicks a link, and by Monday morning the shared drive of CAD files is encrypted. Ask at each step who does what, and how you would know.
- Reporting drill. Have the reporting contact log in to the DIBNet portal and prepare, without submitting, the details a report requires. If the account or certificate is missing, you found a gap cheaply.
- Restore test. Restore a sample of files and one full system from backup, and time it against your recovery time objective.
- Contact check. Call every number on the contact sheet. Phone numbers go stale faster than anything else in the plan.
Keep the agenda, attendee list, scenario, findings and the follow-up actions you closed. Those records are the proof that the capability is operational, and an assessor or your own annual affirmation will rely on them.
Where small contractors go wrong
- Treating the plan as a download. A generic template with the blanks unfilled fails the first time someone asks "who is the reporting contact?"
- No monitoring outside business hours. Most intrusions are not polite enough to happen at 10 a.m. If nobody sees the alert until Monday, the discovery clock and the damage have both been running all weekend.
- Not knowing where CUI lives. You cannot scope an incident if you do not know which laptops, mailboxes and folders hold the data.
- Overwriting evidence. Rebuilding machines before imaging them can break the preservation requirement.
- Backups on the same network as everything else. Ransomware that reaches the backups removes your recovery option.
- Confusing a pause in assessments with a pause in obligations. DFARS 7012 reporting stayed in effect during the review.
Manufacturers face a particular version of this problem, because production systems, CAD files and the office network are often tangled together. Our article on protecting manufacturing data from cyberattacks covers the common weak points.
Getting the plan operational with local support
Great Plains Networking provides managed IT support for small businesses in Norman, Moore and Oklahoma City, including law firms, dental and medical practices, manufacturers and nonprofits. Our 24/7 monitoring is built to catch problems before they disrupt operations, which matters when the 72-hour reporting clock starts at discovery. We also offer cybersecurity, backup and recovery, and compliance guidance for frameworks such as HIPAA, IRS requirements and CMMC. Support is in plain language, with same-day response and no long-term contracts.

If you want to see where you stand first, take the 10-minute readiness audit, or look at how our managed IT support and cybersecurity services fit a contractor handling CUI. For the wider picture of what the program asks of you, start with our overview of CMMC IT requirements for DoD contractors.
FAQ
Does a CMMC Level 1 contractor need an incident response plan?
The formal incident response practices apply at Level 2, which covers CUI. A Level 1 company handling only FCI is not assessed on them. A written plan is still sensible, because any contractor can be hit by ransomware or a compromised email account, and your contract may carry its own reporting terms.
How soon must I report a cyber incident to DoD?
If your contract includes DFARS 252.204-7012, you must report a qualifying incident within 72 hours of discovery through DoD's DIBNet portal. The clause also requires you to keep images of affected systems and relevant monitoring data for at least 90 days from the report. Check your contract and any prime contractor flow-down for shorter notice periods.
Did the 2025 CMMC rule change incident reporting?
No. The CMMC acquisition rule took effect on November 10, 2025, but DFARS 252.204-7012 reporting continued to apply with its 72-hour requirement. A proposed separate 72-hour report for CMMC compliance lapses was not added to the final rule.
How often should I test my incident response plan?
CMMC requires that you test your capability but does not set a fixed interval in the practice itself. A yearly tabletop exercise plus a restore test is a reasonable baseline for a small contractor. Retest after major changes such as a new IT provider, a new cloud system or a change in who holds a response role.
Who should be my reporting contact?
Choose someone who can act without waiting for approval, usually an owner, operations manager or IT lead, and name a backup. They need a DIBNet account and the right certificate in place before an incident. Your IT provider can support the technical details, but the company remains responsible for the report.
Sources
- 32 CFR Part 170, Cybersecurity Maturity Model Certification Program (eCFR)
- 48 CFR 252.204-7012, Safeguarding Covered Defense Information and Cyber Incident Reporting (eCFR)
- Defense Industrial Base Supply Chain Cyber Training, CMMC (NDISAC, January 2026)
- Small Business Office (U.S. Army Contracting Command)
- The CMMC Phase 2 Suspension white paper (July 29, 2026)
