CIRCIA Final Rule Under Review: How to Prepare for 72-Hour Cyber Incident Reporting
CISA sent its CIRCIA final rule to White House review on October 1, 2026. How to prepare for 72-hour incident and 24-hour ransom payment reports.
- Author
- Ackatec
- Published
- Reading time
- 7 min read
- CIRCIA
- Incident reporting
- Incident readiness
- Critical infrastructure
- Compliance readiness
- Ransomware
On October 1, 2026, CISA sent its final rule under the Cyber Incident Reporting for Critical Infrastructure Act of 2022 (CIRCIA) to the White House Office of Information and Regulatory Affairs (OIRA), according to the OIRA review record (opens in a new tab). Once the rule takes effect, a covered organization will have 72 hours to report a covered cyber incident to CISA after it reasonably believes one occurred, and 24 hours to report a ransom payment.
The short answer: do not wait for the final text. Decide now who can declare that an incident is reportable, practice getting a first report out within 72 hours, and make sure your logs, vendor contracts, and evidence handling would support it.
What is CIRCIA?
CIRCIA is a 2022 federal law that requires covered entities in critical infrastructure sectors to report covered cyber incidents to CISA within 72 hours and ransom payments within 24 hours. It left the details, including who is covered and what counts as reportable, to a CISA rulemaking. CIRCIA reporting is not required until the final rule takes effect, and CISA's CIRCIA page (opens in a new tab) encourages organizations to share incident information voluntarily in the meantime.
Where does the rulemaking stand in October 2026?
The final rule is under OIRA review, the last major step before publication in the Federal Register. The path here was slow:
- April 2024: CISA published the proposed rule (opens in a new tab). The statute called for a final rule within 18 months of that proposal.
- June 15 to 18, 2026: after funding lapses delayed the schedule, CISA held four town halls on the proposal.
- October 1, 2026: the final rule was received for OIRA review, after CISA missed a previously announced September 2026 publication target, as Steptoe noted (opens in a new tab).
Covington observes (opens in a new tab) that OIRA review can take up to 90 days, which could push publication into early 2027, and that the rule is unlikely to take effect sooner than 60 days after publication. The exact effective date will be in the final text.
Who would have to report?
Under the proposed rule, a covered entity is an organization in one of the 16 critical infrastructure sectors that either exceeds the U.S. Small Business Administration size standard for its industry or meets a sector-based criterion, such as being a defense contractor that must already report cyber incidents to the Department of Defense. CISA estimated that 316,244 entities could be covered, spanning sectors such as energy, financial services, healthcare, communications, transportation, and information technology.
Town hall participants pushed CISA to narrow these criteria, and the final rule may change them. A mid-sized hospital, regional bank, manufacturer, or software provider should not assume it is out of scope before reading the final definition.
What counts as a reportable incident?
The proposal defines a "substantial cyber incident" as one that leads to any of four impacts:
- A substantial loss of confidentiality, integrity, or availability of an information system or network.
- A serious impact on the safety and resiliency of operational systems and processes.
- A disruption of the ability to conduct business or industrial operations, or deliver goods or services.
- Unauthorized access facilitated by the compromise of a cloud service provider, managed service provider, other third-party data hosting provider, or the supply chain.
The fourth impact means an incident that starts at your provider can still trigger your reporting obligation.
When does the 72-hour clock start?
Under the proposal, the 72-hour clock starts when the covered entity reasonably believes a covered cyber incident has occurred, not when an investigation confirms it. In the proposal, CISA describes reasonable belief as "a much lower threshold than confirmation" and says the preliminary analysis to reach it should usually take "hours, not days" and generally happen at the subject matter expert level, not the executive level.
So the analysts who first see an incident need a clear escalation rule, and the people who approve a report must be reachable within hours, including on weekends.
What else does the proposed rule require?
- A detailed first report. It covers affected systems, key dates, operational impact, exploited vulnerabilities, defenses in place, attacker tactics, indicators of compromise, and the response so far, to the extent known.
- Supplemental reports. Covered entities must promptly update CISA when substantial new or different information becomes available, or when they pay a ransom after an initial report.
- A separate ransom payment report. Paying a ransom triggers a 24-hour report even if the underlying attack is not a covered cyber incident.
- Third-party filing. An authorized third party can file for you, but you remain responsible.
- Two years of preservation. Covered entities must preserve incident data, including threat actor communications, indicators of compromise, relevant logs, forensic artifacts, and ransom payment records, for at least two years from the most recent required report. The proposal does not require creating records you do not already have, which is why logging decisions made before an incident matter.
CIRCIA also has a "substantially similar reporting" exception for reports made to another federal agency under an agreement with CISA. Covington's summary of the town halls (opens in a new tab) notes that the proposal identified no existing requirement that would qualify. Plan to file with CISA in addition to your other reports unless the final rule or a CISA agreement says otherwise.
How should you prepare before the final rule is published?
Map every reporting clock you already carry
List each incident notification obligation you have today: sector regulators, SEC disclosure rules if you are public, state breach laws, contracts, and cyber insurance policies. Record each trigger, deadline, recipient, and owner, then add CIRCIA's 72-hour and 24-hour clocks. Connecting obligations to owners and evidence is the core of compliance readiness work.
Write the reportability decision into your incident plan
Define who makes the "reasonable belief" call, what evidence they need, and who approves and submits the report, with backups for each role. Keep the ransom payment decision and its 24-hour report as a separate workflow. A virtual CISO can own this decision structure and keep it current as the final rule lands.
Fix logging and vendor terms before you need them
Check that the logs the proposal lists, such as DNS, firewall, VPN, endpoint, and Active Directory events, are collected and kept long enough to reconstruct an incident, and that you could hold them for two years once preservation applies. Review contracts with managed service, cloud, and incident response providers so they notify you quickly, preserve evidence, and can support a report filed on your behalf.
Rehearse the first 72 hours
Run a tabletop in which a ransomware attack or provider compromise unfolds over a weekend and the team must produce a first CIRCIA report, timing each decision. Incident readiness work covers these exercises, and it pairs with preparing for ransomware. Ackatec prepares organizations and coordinates the response providers they already engage; emergency response and forensics stay with the firms contracted to deliver them. Legal questions about coverage belong with your counsel.
CIRCIA readiness checklist
- Have we identified whether we are likely to be a covered entity, and who will confirm it against the final rule?
- Who decides when we reasonably believe a covered cyber incident occurred, and who is their backup?
- Can we draft and submit a first report within 72 hours, including on a weekend?
- Is the ransom payment decision paired with a 24-hour reporting workflow?
- Do our providers' contracts require prompt notification and evidence preservation?
- Could we preserve the logs, forensic data, and communications the proposal lists for two years?
- When did we last exercise the plan with the people who would actually make these calls?
If several answers are unclear, start a conversation before the final rule is published.
References
- OIRA, Pending EO 12866 Regulatory Review: CIRCIA Reporting Requirements, RIN 1670-AA04 (opens in a new tab) (received October 1, 2026)
- CISA, Cyber Incident Reporting for Critical Infrastructure Act of 2022 (CIRCIA) (opens in a new tab)
- CISA, CIRCIA Reporting Requirements, Notice of Proposed Rulemaking (opens in a new tab), Federal Register (April 4, 2024)
- Covington, CISA Submits Final CIRCIA Rule for OMB Review (opens in a new tab) (October 8, 2026)
- Covington, CISA Town Halls Signal Key Cyber Rule Changes Ahead (opens in a new tab) (September 4, 2026)
- Steptoe, CIRCIA Rule Advances, Bringing New Cyber Reporting Requirements Closer (opens in a new tab) (October 9, 2026)
