Checklist: getting ready for CIRCIA reporting before CISA’s final rule

Eleven steps for critical infrastructure organizations. No CIRCIA report is required until CISA’s final rule takes effect; these steps use the statute and the 2024 proposal to prepare, and every one of them is our suggestion.

Where the rule stands

The Cyber Incident Reporting for Critical Infrastructure Act of 2022 requires a covered entity to report a covered cyber incident to CISA no later than 72 hours after it reasonably believes the incident occurred, and a ransom payment no later than 24 hours after making it. CISA may not require the incident report any sooner than 72 hours. Both duties, and the duties to supplement reports and preserve data, take effect only on the dates set in CISA’s final rule [1]. The statute asked for that final rule within 18 months of the proposed rule [1]. CISA published its proposed rule on April 4, 2024, with comments open until July 3 [2] [3].

As checked on November 14, 2026, CISA’s page says it held four town hall meetings between June 15 and June 18, 2026, that multiple funding lapses affected its ability to carry out the rulemaking, and that it continues to work on the final rule. It says reporting will not be required until the final rule goes into effect, and encourages organizations to share information about cyber incidents voluntarily in the meantime [2].

Using the steps

Nothing on this list is required today. Each step is our suggestion for preparing, and each names the part of the statute [1] or the proposed rule [3] it prepares for. The proposed rule may change before it is final. The owner under each step is a typical role. This page explains the statute and the proposal; it is not legal advice.

Moraph’s teams help organizations with work like this. See our solutions.

The checklist

Tick the steps as you go. The ticks are kept in this browser only; nothing is sent to us.

  1. Legal, with enterprise risk

    Our suggestion. Section 681b(c)(1) requires the final rule to describe covered entities based on the consequences of disruption, the likelihood of being targeted and the potential to enable disruption of critical infrastructure [1]. Proposed section 226.2 would cover entities in a critical infrastructure sector that exceed the small business size standard for their industry or meet a sector-based criterion [3].

  2. Incident response lead

    Our suggestion. Section 681b(c)(2)(A) requires the final rule to cover, at a minimum, substantial loss of confidentiality, integrity or availability or a serious impact on operational systems; disruption of business or industrial operations, including from denial of service, ransomware or a zero-day exploit; and unauthorized access or disruption caused through a cloud service provider, managed service provider, other third-party data host or supply chain compromise. Section 681b(c)(2)(C) excludes testing done in good faith at the owner’s request and a threat of disruption used as extortion [1].

  3. CISO

    Our suggestion. Section 681b(a)(1) would run the 72 hours from that reasonable belief [1].

  4. General counsel, with the CFO and incident response lead

    Our suggestion. Section 681b(a)(2) would require a ransom payment report within 24 hours of payment even if the attack is not a covered cyber incident. Under section 681b(d)(2) and (4), a third party that pays on a covered entity’s behalf does not report for itself but must advise the entity of its reporting duties [1].

  5. Incident response lead

    Our suggestion. Section 681b(c)(4) lists the contents of an incident report, from the affected systems and the impact on operations to the vulnerabilities, tactics and actors involved, and section 681b(c)(5) lists the contents of a ransom payment report, including the demand, the payment instructions and the amount [1].

  6. Security engineering, with records management

    Our suggestion. Section 681b(a)(4) requires covered entities to preserve data relevant to an incident or ransom payment as the final rule sets out [1]. The proposed rule would require preservation for at least two years from the latest report submitted [3].

  7. Incident response lead

    Our suggestion. Section 681b(a)(3) would require prompt updates when substantial new or different information becomes available or a ransom is paid after the first report [1].

  8. Regulatory compliance

    Our suggestion. Section 681b(a)(5)(B) excuses a covered entity that must report substantially similar information to another federal agency in a substantially similar timeframe, but only once CISA and that agency have an agreement and sharing mechanism in place [1]. The proposed rule calls these CIRCIA Agreements [3]. The NCUA, for example, set its own 72-hour credit union report in 2023 and said it intends to coordinate with CISA to avoid duplicate reporting [4].

  9. Procurement, with legal

    Our suggestion. Section 681b(d)(1) allows a covered entity to use such a third party to submit its reports, and section 681b(d)(3) says doing so does not relieve the entity of its duty [1].

  10. CISO

    Our suggestion, following CISA’s own: its CIRCIA page encourages all entities to share information about cyber incidents voluntarily before the final rule takes effect [2].

  11. Regulatory affairs

    Our suggestion. CISA says it will communicate updates on the rulemaking and its timeline through CISA.gov/CIRCIA, and public comments are in docket CISA-2022-0010 [2].

Spotted an error? Tell us and we will check it and correct the checklist where needed.

  • CIRCIA
  • CISA
  • 6 U.S.C. 681b
  • cyber incident reporting
  • ransom payments
  • critical infrastructure