# CIRCIA, explained: the 72-hour and 24-hour reports, and where CISA’s rule stands

The Cyber Incident Reporting for Critical Infrastructure Act of 2022 requires covered entities to report covered cyber incidents to CISA within 72 hours and ransom payments within 24 hours, but only once CISA’s final rule is in effect. As checked on November 14, 2026, CISA was still working on that rule.

Explainer · Cross-sector · Regulation & Compliance. Published November 14, 2026. Last reviewed November 14, 2026.

## At a glance

- Statute: 6 U.S.C. 681 to 681g, enacted in March 2022.
- Covered cyber incident: report to CISA no later than 72 hours after the covered entity reasonably believes it occurred. CISA may not require it any sooner.
- Ransom payment: report no later than 24 hours after the payment is made, even if the attack is not a covered cyber incident.
- Neither duty applies until the dates set in CISA’s final rule.
- CISA proposed the rule on April 4, 2024 (89 FR 23644; docket CISA-2022-0010). The statute asked for a final rule within 18 months of the proposal.
- As checked on November 14, 2026, CISA’s CIRCIA page says it continues to work on the final rule. It held town halls in June 2026, and says multiple funding lapses affected its ability to carry out the rulemaking.

## What the statute requires

The Cyber Incident Reporting for Critical Infrastructure Act of 2022 (CIRCIA), codified at 6 U.S.C. 681 to 681g, directs the Cybersecurity and Infrastructure Security Agency (CISA) to write regulations requiring covered entities to report covered cyber incidents and ransom payments to it [1] [2]. CISA says the reports are meant to let it send help to victims, spot trends across sectors and warn other potential victims quickly [2]. The statute sets four duties in section 681b(a) [1].

- **Covered cyber incident report, 72 hours.** A covered entity that experiences a covered cyber incident reports it to CISA no later than 72 hours after it reasonably believes the incident occurred. The Director may not require reporting any earlier than that.
- **Ransom payment report, 24 hours.** A covered entity that makes a ransom payment as the result of a ransomware attack reports the payment no later than 24 hours after making it. This applies even when the attack is not a covered cyber incident.
- **Supplemental reports.** The entity promptly updates its report when substantial new or different information becomes available, or when it pays a ransom after reporting, until it tells CISA the incident has concluded and been fully mitigated and resolved.
- **Preservation.** The entity preserves data relevant to the incident or payment, following procedures to be set in the final rule.

An entity that pays a ransom before its 72-hour deadline may file a single report covering both [1]. The statute also excuses an entity that must report substantially similar information to another federal agency within a substantially similar timeframe, but only once CISA and that agency have an information-sharing agreement in place [1].

## When the duties start

Section 681b(a)(7) says the reporting and preservation duties take effect on the dates set in the final rule [1]. CISA states the same: covered cyber incident and ransom payment reporting under CIRCIA will not be required until the final rule takes effect [2]. Until then, CISA encourages organizations to share information on incidents voluntarily [2].

The statute required a proposed rule within 24 months of March 15, 2022, and a final rule within 18 months of the proposal [1]. CISA published its proposed rule on April 4, 2024, at 89 FR 23644, proposing a new 6 CFR part 226 [3].

## Where the rulemaking stands

As checked on November 14, 2026, CISA’s CIRCIA page gives this account [2]:

- The proposed rule was open for comment until July 3, 2024. CISA published a correction on June 3, 2024, and the comments are on regulations.gov under docket CISA-2022-0010.
- CISA is reviewing and considering the comments.
- CISA held four town hall meetings between June 15 and June 18, 2026, announced in the Federal Register on February 13, 2026 (91 FR 6794) and May 26, 2026 (91 FR 30498). Transcripts are on the docket.
- Multiple funding lapses affected CISA’s ability to carry out the rulemaking. CISA continues to work on the final rule and says it will post updates on the process and timeline at CISA.gov/CIRCIA.

The February 2026 notice said CISA had received about 300 comments on the proposal, that it would not reopen the comment period at that time, and that it might do so later [4]. It asked for input on refining scope and burden, including:

- entities covered only because of the size test, and whether to keep a size-based criterion at all;
- the proposed sector-based criteria;
- whether to add specific criteria for managed service providers or cloud service providers using open-source software, or for reporting related to open-source code;
- the proposed examples of incidents that would or would not count as substantial [4].

Because these points were open, the scope of the final rule may differ from the proposal.

## Who would be covered: what the statute fixes and what the proposal suggested

The statute leaves the definition of covered entities to the final rule. It must base that description on the consequences that disruption of an entity could cause to national security, economic security or public health and safety; the likelihood that a malicious actor targets the entity; and how far compromising it would enable disruption of critical infrastructure [1].

The 2024 proposal would have applied to an entity in a critical infrastructure sector that either exceeds the Small Business Administration size standard for its industry code or meets one of a list of sector-based criteria [3]. Examples include owning a covered chemical facility, providing wire or radio communications service, and being a Defense contractor required to report cyber incidents under DFARS 252.204-7012 [3]. The proposal also would have required data to be preserved for at least two years from the latest report submitted [3]. These are proposals, not law.

## What a covered cyber incident is

The final rule must describe the substantial cyber incidents that count. At a minimum, they include incidents that cause a substantial loss of confidentiality, integrity or availability of a system or network, or a serious impact on the safety and resiliency of operational systems; disruptions of business or industrial operations, such as by denial of service, ransomware or a zero-day exploit; and unauthorized access or disruption caused by a compromise of a cloud service provider, managed service provider, other third-party data host, or the supply chain [1]. Good-faith activity done at the system owner’s request, and threats of disruption used as extortion, are excluded [1].

## What the reports contain, and who may file them

An incident report must include, where applicable and available: a description of the incident and the affected systems; the estimated date range and the impact on operations; vulnerabilities exploited, defenses in place and the tactics used; information on the actor; the categories of information accessed; and the entity’s identity and contact details [1]. A ransom payment report adds the date and amount of the payment, the demand, including the type of virtual currency or other commodity requested, and the payment instructions [1].

A covered entity may use a third party, such as an incident response firm, insurer, service provider, Information Sharing and Analysis Organization or law firm, to submit a report, but the duty stays with the entity [1]. A third party that knowingly pays a ransom for a covered entity must advise it of its reporting duties [1].

## Enforcement and protections

If CISA believes a covered entity failed to report, it may first ask for information. If there is no response, or an inadequate one, 72 hours after that request, CISA may issue a subpoena, and failure to comply with a subpoena can lead to a civil action [5]. Information in reports may be used by the federal government only for listed purposes, such as cybersecurity, identifying threats and vulnerabilities, and responding to specific serious threats [6].

## Reading the deadlines today

CISA says organizations are not required to submit CIRCIA reports until the final rule’s effective date, and the statute starts the 72-hour and 24-hour duties only on the dates the final rule sets [1] [2]. This page does not cover other incident reporting duties, from sector regulators, contracts or state law, that may already apply. The final rule will decide who is covered, and counsel can say whether it reaches a given organization. This page explains the statute and the rulemaking and is not legal advice.

Moraph’s teams help organizations with work like this; see [our solutions](https://www.moraph.com/solutions).

## Sources

1. U.S. Government Publishing Office (GovInfo). 6 U.S.C. 681b, Required reporting of certain cyber incidents (United States Code, 2024 edition). <https://www.govinfo.gov/content/pkg/USCODE-2024-title6/html/USCODE-2024-title6-chap1-subchapXVIII-partD-sec681b.htm> Checked November 14, 2026.
2. Cybersecurity and Infrastructure Security Agency. Cyber Incident Reporting for Critical Infrastructure Act of 2022 (CIRCIA). <https://www.cisa.gov/topics/cyber-threats-and-advisories/information-sharing/cyber-incident-reporting-critical-infrastructure-act-2022-circia> Checked November 14, 2026.
3. Cybersecurity and Infrastructure Security Agency, Federal Register (via GovInfo). Cyber Incident Reporting for Critical Infrastructure Act (CIRCIA) Reporting Requirements, proposed rule (89 FR 23644, April 4, 2024). <https://www.govinfo.gov/content/pkg/FR-2024-04-04/html/2024-06526.htm> Checked November 14, 2026.
4. Cybersecurity and Infrastructure Security Agency, Federal Register (via GovInfo). CIRCIA Rulemaking; Town Hall Meetings (91 FR 6794, February 13, 2026). <https://www.govinfo.gov/content/pkg/FR-2026-02-13/html/2026-02948.htm> Checked November 14, 2026.
5. U.S. Government Publishing Office (GovInfo). 6 U.S.C. 681d, Noncompliance with required reporting. <https://www.govinfo.gov/content/pkg/USCODE-2024-title6/html/USCODE-2024-title6-chap1-subchapXVIII-partD-sec681d.htm> Checked November 14, 2026.
6. U.S. Government Publishing Office (GovInfo). 6 U.S.C. 681e, Information shared with or provided to the Federal Government. <https://www.govinfo.gov/content/pkg/USCODE-2024-title6/html/USCODE-2024-title6-chap1-subchapXVIII-partD-sec681e.htm> Checked November 14, 2026.

Published: November 14, 2026
Canonical URL: <https://insights.moraph.com/circia-cyber-incident-reporting-rule-status-explained>
Publisher: Moraph Insights
