CIRCIA explained: who must report cyber incidents in 72 hours
CIRCIA explained: covered entities must report cyber incidents to CISA in 72 hours and ransom payments in 24 hours. Final rule status as of Oct 30, 2026.
CIRCIA is a US law that will require organizations in critical infrastructure to report serious cyber incidents to CISA within 72 hours and ransom payments within 24 hours. The law passed in 2022, but the reporting duty is not in force yet: as of October 30, 2026, CISA's own page says it applies only once the final rule takes effect, and that rule has not been issued.
CIRCIA is the Cyber Incident Reporting for Critical Infrastructure Act of 2022. The sections below cover what the statute fixes, what CISA proposed in 2024, where the final rule stands, and how it compares with the SEC's disclosure rule.
Is CIRCIA reporting mandatory today?
No. According to CISA's CIRCIA page, reporting under the act is not required until the final rule takes effect. CISA still encourages voluntary reports in the meantime.
When we checked it on October 30, 2026, the same page gave no date for the final rule and said CISA continues to work on it. It also says that multiple funding lapses affected its rulemaking work. The statute gave CISA 18 months after the proposal to finish, which would have been around October 2025, so the rule is late.
A final rule could be published at short notice, so check that CISA page before you act on anything here. Once it is out, its definitions and effective date override the proposal described below.
What the statute already fixes
Congress set the main deadlines in 6 U.S.C. 681b, so CISA's rulemaking cannot change them. The statute fixes these parts:
- 72 hours for covered cyber incidents. The clock starts when the entity reasonably believes a covered incident has occurred, not when the investigation ends.
- 24 hours for ransom payments. A covered entity that pays a ransom after a ransomware attack must report the payment within 24 hours. This applies even when the attack itself was not a covered incident.
- Supplemental reports. If substantial new information appears, or a ransom is paid after the first report, the entity must update CISA promptly until the incident is fully mitigated and closed.
- Data preservation. Entities must keep data relevant to the incident or payment, following rules set in the final regulation.
- Third-party filing. An incident response firm, insurer or other third party can submit a report for the entity, but the entity stays responsible for compliance.
The statute also excuses an entity that must report substantially similar information to another federal agency within a similar timeframe, but only once CISA has an information-sharing agreement with that agency in place.
What CISA proposed in the 2024 rule
The statute leaves two big questions to the regulation: who counts as a covered entity, and what counts as a covered incident. CISA's answer came in a proposed rule published in the Federal Register on April 4, 2024 (89 FR 23644). The comment period, originally set to close on June 3, 2024, was extended into July 2024. Everything in this section is a proposal, not current law.
Who would be covered
The proposal applied to entities in the 16 critical infrastructure sectors defined by federal policy, using two tests. An organization would be covered if it met either one:
- a size-based test, which captures entities in a critical infrastructure sector that exceed the Small Business Administration's size standard for their industry;
- a sector-based test, which captures certain entities regardless of size, such as particular categories of hospitals and other sector-specific operators that CISA listed.
CISA estimated that about 316,000 entities could be affected and that they would file roughly 210,000 reports over its 2023 to 2033 analysis period. The final text may differ from the proposal.
What would count as a covered incident
The proposal described four kinds of events. In summary, they were a substantial loss of confidentiality, integrity or availability of an information system; a serious impact on the safety and resilience of operational systems; disruption of business or industrial operations, including through denial of service or ransomware; and unauthorized access caused by a compromise of a cloud provider, managed service provider or other third party, or by a supply chain compromise.
The last category matters for infrastructure teams. A provider-side compromise could trigger a report from the customer even if the customer's own systems show little damage.
Harmonization with other regimes
CISA proposed that an entity could skip a CIRCIA report if it already sends substantially similar information to another federal agency in a similar timeframe, provided CISA has an agreement with that agency. The proposal also let an entity file one combined report when an incident and a ransom payment fall close together.
How CIRCIA differs from the SEC rule
Publicly traded companies already face a separate US deadline. Under the SEC's 2023 cybersecurity disclosure rules, a registrant files Form 8-K Item 1.05 within four business days after it determines an incident is material. A delay is possible only if the US Attorney General finds that immediate disclosure would create a substantial risk to national security or public safety.
- Audience. CIRCIA reports go confidentially to CISA. SEC filings are public disclosures to investors.
- Trigger. CIRCIA keys on a reasonable belief that a covered incident occurred. The SEC keys on a materiality determination by the company.
- Clock. CIRCIA uses 72 hours (24 for ransom payments). The SEC uses four business days.
- Who is covered. CIRCIA follows critical infrastructure status, public or private. The SEC rule follows public registration.
A listed company in a critical infrastructure sector could eventually owe both, so incident runbooks should name who decides each filing. This article covers US rules only.
What to do before the final rule lands
Nothing in CIRCIA is enforceable yet, but several steps are cheap and useful whatever the final text says:
- Work out which critical infrastructure sector you belong to, and whether you would pass the proposed size-based or sector-based test.
- Write down who can declare that a covered incident is reasonably believed to have occurred, since that decision starts the 72-hour clock.
- Add a ransom-payment step to the incident plan, with a named person responsible for the 24-hour report.
- Check contracts with cloud, managed service and incident response providers for notice terms that would let you meet a 72-hour deadline.
- Plan for log and artifact retention so evidence can be preserved on request.
For related reading, see our security coverage, the breaches section, and our explainer on CISA BOD 26-04 and KEV remediation timelines, which applies to federal agencies rather than private companies. Cloud-dependent teams may also follow infrastructure and cloud news.
Frequently asked questions
When does CIRCIA take effect?
The reporting duty begins only after CISA publishes a final rule and it takes effect. As of October 30, 2026, CISA had not published the final rule or announced an effective date.
What is the CIRCIA 72-hour rule?
A covered entity must report a covered cyber incident to CISA within 72 hours of reasonably believing it occurred. The deadline comes from the statute itself.
Do I have to report a ransom payment within 24 hours?
Once the rule is in force, yes: a covered entity that pays a ransom after a ransomware attack must report it within 24 hours. This applies even if the attack was not itself a covered incident.
Who are CIRCIA covered entities?
The final definition is still pending. The 2024 proposal would cover entities in the 16 critical infrastructure sectors that meet a size-based or sector-based test.
Can I report to CISA voluntarily now?
Yes. CISA encourages voluntary reporting through report@cisa.gov or 1-844-Say-CISA while the mandatory rule is pending.