| Takeaway | Detail |
|---|---|
| CIRCIA's 24-hour ransomware payment report clock starts at payment awareness, not incident awareness. | Log the timestamp when any ransom payment is confirmed; report within 24 hours from that trigger, even if the 72-hour incident clock started earlier. |
| CIRCIA's 72-hour covered incident report clock starts at covered-incident awareness. | Log the timestamp when the incident is confirmed covered; report within 72 hours from that trigger, independent of any payment. |
| The EU Cyber Resilience Act reporting deadline is September 11, 2026. | Crowell & Moring noted that date was less than 100 days away; use it as the fixed external deadline in 2026 planning. |
| Automated compliance reminders cost roughly $25,000–$32,000 per year for a 1,000-employee organization. | The figure is at fully-loaded rates and excludes any incident-avoidance benefit. |
The guide separates CIRCIA's 24-hour ransom payment report from its 72-hour covered incident report and shows each clock's trigger.
The answer changes when payment awareness occurs after incident awareness, because the 24-hour clock then starts later than the 72-hour clock.

Two Clocks, Two Triggers: How CIRCIA Works
The working pair this guide uses — a covered cyber incident reported to CISA within 72 hours and a ransomware payment reported within 24 hours of payment — should be confirmed against CISA's CIRCIA page and the Federal Register final rule text before any workflow is built on it. The operative phrase is "of payment" for the second clock. The two obligations are independent: one is anchored to incident awareness, the other to payment awareness, and neither clock borrows its start time from the other.
The mechanism distinction is that the 24-hour payment clock starts at payment awareness, not incident detection. A payment made on day 5 starts a fresh 24-hour clock that day. The incident clock, by contrast, starts when the incident is confirmed covered. That mirrors the awareness-based pattern in the site's NIS2 and DORA material: Alev-B's calculator asks when you became aware, and Sightadel's asks when you learned of the incident, with stages running from awareness rather than from first detection.
| Clock | Trigger | Starts when |
|---|---|---|
| 72-hour covered incident report | Incident awareness | The incident is confirmed covered |
| 24-hour ransomware payment report | Payment awareness | Any ransom payment is confirmed |
This separation matters because the triggers answer different questions. Incident awareness asks when the organization knew it had a covered incident; payment awareness asks when it knew a ransom payment occurred or was confirmed. Treating those as one workflow risks using the earlier timestamp for both, which is the error this section isolates.
Before relying on either clock, confirm that your organization is in the covered-entity population for CIRCIA and that the incident meets the covered-incident definition. The mechanism here is the trigger distinction; scope and classification checks belong in the same intake record as the two awareness timestamps.

The Evidence: Deadline Figures by Source
Before building any reporting workflow, compliance teams should verify the core deadline figures against the primary sources themselves: the Federal Register text of the CIRCIA final rule and CISA's CIRCIA page. Secondary summaries and deadline calculators can illustrate the arithmetic, but the 72-hour and 24-hour figures should be treated as confirmed only once the rule text states them.
Because the available material describes the rule as still finalizing, sector-specific confirmation of the 72-hour and 24-hour figures should come from the final rule text, not from sector summaries. For covered entities translating regulatory text into internal playbooks, document the date the Federal Register text and CISA's page were checked, and treat that verification record — not a secondary guide — as the governing reference point.
CISA’s final-rule coverage serves as the primary regulatory confirmation. By stating the same pair in plain terms, it allows teams to cross-check sector guidance against the rulemaking source itself. When two sources aligned to the same rule agree on the figures, organizations can treat the deadline values as a dependable input for escalation matrices and evidence-retention procedures.
The Alev-B deadline calculator adds a methodological check rather than a CIRCIA-specific restatement. Using an awareness time of Saturday, 14 November 2026 09:10 CET, the tool computes sequential stages at Sunday, 15 November 2026 09:10 CET and Tuesday, 17 November 2026 09:10 CET, illustrating how fixed reporting windows roll forward from a single recorded moment. Teams can apply this arithmetic discipline to validate that their own tracking systems calculate due times consistently from the correct recorded inputs.

Options Compared: One Workflow vs Two
When a ransomware event unfolds under pressure, incident response teams often default to a single reporting workflow to reduce confusion. That shortcut creates avoidable compliance risk because the two CIRCIA reporting obligations do not share the same starting point. Comparing the available approaches makes the operational choice clear: the explicit winner is two independent clocks with separate timestamps.
| Option | Trigger Used | Operational Outcome |
|---|---|---|
| A. Single incident clock | Incident detection for both reports | Uses the wrong trigger for payment reporting; a payment made days later can leave only hours, not the full payment-report window, creating guaranteed breach risk. |
| B. Payment clock backdated to incident awareness | Incident awareness applied retroactively to payment | Manufactures urgency before a payment decision exists, burns triage capacity, and can still miss the deadline if payment occurs late in or after the incident-reporting window. |
| C. Two independent clocks (winner) | Separate awareness timestamp for each obligation | Aligns each report to its own trigger, preserves the full time allowed for each filing, and prevents one decision from distorting the other. |
Option A fails because it treats detection as a universal start. As reflected in CISA’s CIRCIA final rule coverage, the payment obligation is tied to when payment is confirmed, not when the intrusion is first discovered. If leadership authorizes a ransom payment several days into the response, a single clock compresses the available reporting time to whatever remains, turning a manageable requirement into an immediate scramble.
Option B swings too far in the other direction. Backdating the payment clock to incident awareness forces teams to prepare a filing for a decision that has not yet been made. That drains legal, forensic, and executive attention during containment, while offering no protection if the organization ultimately pays after the assumed window has already closed.
Option C resolves both failures with a simple control: record one timestamp when the incident is confirmed as covered and a second timestamp when any ransom payment is confirmed. Each report then runs on its own clock from its own trigger. This separation keeps evidence collection, executive approvals, and submission tasks aligned to the correct deadline without borrowing time or urgency from the other obligation.

The Arithmetic: Buffer Math That Matters
When a covered incident and a ransom payment are confirmed at the same moment, the payment report is due 48 hours sooner than the incident report: 72 hours minus 24 hours leaves a 48-hour remainder. That remainder is not extra time for the incident workflow; it is the payment workflow's entire margin. Treating the payment report as a rider on the incident report therefore compresses the shorter clock into the longer one.
Capacity math (method): assume triage needs 6 hours to confirm that a payment occurred and the incident team needs 12 hours to assemble the incident report. A same-day payment leaves 24 − 6 = 18 hours of payment buffer, while the incident report retains 72 − 12 = 60 hours of buffer. The binding constraint is the payment report, because 18 hours is far smaller than 60 hours.
| Clock | Deadline from shared start | Work estimate | Buffer |
|---|---|---|---|
| Payment report | 24 hours | 6 hours triage | 18 hours |
| Incident report | 72 hours | 12 hours assembly | 60 hours |
The practical reading is that the 48-hour gap can disappear before the incident report is drafted. If payment confirmation arrives late in the day, the payment clock may expire while the incident team is still collecting facts. Separate owners, separate checklists, and separate awareness timestamps keep the shorter clock visible.
The 48-hour remainder also sets a ceiling on overlap: even if payment awareness follows incident awareness, the payment clock runs from payment confirmation and can expire while incident work continues. Log the actual confirmation time for each event and do not backdate either clock to the earlier event.
A useful control is to calculate remaining payment hours at every handoff: deadline time minus current time. If that number falls below the 6-hour triage estimate, escalate immediately rather than waiting for the incident report's 60-hour buffer.

What the Evidence Does Not Establish
The cited material supports CIRCIA’s reporting pair as a deadline structure, but it does not establish the operational details that decide whether a particular organization is in scope, when compliance begins, or what consequences attach to a missed report. Treat the deadline lengths as the confirmed element and everything else as a verification item.
| Confirmed in cited sources | Not established; verify in final rule text |
|---|---|
| 72-hour covered cyber incident report; 24-hour ransomware payment report | Exact effective or compliance date |
| — | Covered-entity thresholds and scope tests |
| — | Whether an extortion-only demand with no payment is a covered cyber incident |
| — | Penalty, enforcement, or late-reporting provisions |
The available sources describes the rule as finalizing, so the exact effective or compliance date and any covered-entity thresholds should be taken from the Federal Register text and CISA’s CIRCIA page rather than from summaries. Until those sources are checked, an organization should not assume a start date, a size threshold, or a sector test.
Whether a specific incident type triggers the 72-hour clock is also not established by the cited material. An extortion-only demand with no payment is the stated example: check CISA’s definition of “covered cyber incident” in the final rule, not secondary summaries, before deciding that the report is or is not required.
Penalty and enforcement provisions are likewise not established here. The cited sources do not state whether late reporting carries a civil penalty, a criminal exposure, a contractual consequence, or no stated consequence at all. Verify the final rule text and any CISA guidance before building an escalation or budget assumption around enforcement.
A practical control is to keep a verification log: record the date the final rule text and CISA page were reviewed, the version or citation used, and the specific scope and date conclusions drawn from them. Recheck that log whenever a new incident occurs, because a summary that was accurate for one reporting cycle may not be accurate for the next. This keeps the boundary between confirmed deadlines and unverified details visible to anyone who later reviews the file.

Ransom Paid on Day 5
When a ransom payment lands days after a covered cyber incident, the two CIRCIA reporting obligations separate in practice. Consider a covered incident detected on Monday at 09:00, which sets the 72-hour covered incident report deadline at Thursday at 09:00. If treasury confirms a ransom payment on Saturday at 14:00 — hour 125 of the incident clock — that confirmation starts a new 24-hour clock, making the ransomware payment report due Sunday at 14:00, hour 149. In this scenario the payment deadline falls 77 hours after the incident deadline, so the incident report remains the earlier filing; the payment clock still runs independently and must be tracked to its own Sunday 14:00 target.
Checkpoint 1 (hour 0, Monday 09:00): the incident response lead logs the incident-awareness timestamp as soon as the event is confirmed covered, and compliance records a “no payment yet” status. This preserves a clean starting point for the incident report without assuming that a payment clock is already running. Maintaining that status explicitly prevents teams from backdating a future payment to the moment of detection.
Checkpoint 2 (hour 125, Saturday 14:00): treasury confirms the ransom payment and compliance logs a second, independent payment-awareness timestamp. A new 24-hour clock starts at that moment, with the payment report due Sunday at 14:00. Measured against the original incident timeline, this due time falls 77 hours after the Thursday 09:00 incident report deadline, so no crossover occurs in this scenario: because payment was confirmed after hour 48, the incident report stays the earlier filing, while the payment report is tracked separately to Sunday 14:00.
| Checkpoint | Timestamp | Action | Resulting deadline |
|---|---|---|---|
| Hour 0 | Mon 09:00 | Log incident-awareness; record “no payment yet” | Covered incident report due Thu 09:00 |
| Hour 125 | Sat 14:00 | Log payment-awareness; start separate payment clock | Ransom payment report due Sun 14:00 |
To operationalize this crossover, response playbooks should require two immutable log entries: one for confirmed incident awareness and one for confirmed payment. Each entry should name the owner, the source of confirmation, and the calculated due time derived from that specific trigger. Handoffs between incident response, legal, treasury, and compliance should pass both timestamps forward, not a single merged deadline.
Before filing, teams should run a final check: verify that the payment report is tracked to Sunday 14:00 and the incident report remains tracked to Thursday 09:00, even if both are drafted in parallel. Treating the clocks as independent ensures the earlier-arriving payment obligation is met without displacing or redefining the incident reporting timeline established at hour 0.
Decision Rules for the First 24 Hours
When a cyber event is confirmed as covered under CISA’s Cyber Incident Reporting for Critical Infrastructure Act (CIRCIA) final rule, the first operational step is to log an incident-awareness timestamp within the first hour of that confirmation. Compute the 72-hour incident reporting deadline as an absolute calendar date and time from that timestamp—never in “business days”—and record it in the incident record so every responder works from the same fixed target.
If any ransom payment is confirmed at any point, treat that confirmation as a separate triggering event. Immediately log a distinct payment-awareness timestamp and start a fresh 24-hour clock from that moment, regardless of where the incident clock stands. Maintaining two separate timestamps prevents teams from collapsing the obligations into a single timeline and ensures each report is tracked against its own trigger.
Use an hour-48 crossover check to set filing priority as soon as a payment is confirmed. Compare the payment-awareness timestamp to the elapsed time on the incident clock: if payment is confirmed at or before hour 48, the payment report deadline (payment time plus 24 hours) arrives before the 72-hour incident report deadline, and the payment report must be filed first. If payment is confirmed after hour 48, the incident report deadline remains the earlier of the two, but both clocks continue to run independently.
Build this ruleset into the first 24 hours of response: at each status update, verify whether incident coverage is confirmed, verify whether any payment has been made, and re-run the hour-48 crossover check when payment status changes. Document both timestamps, assigned owners, and the computed absolute deadlines in the same system of record so handoffs do not reset or reinterpret either clock.
What to do next
| Step | Action | Why it matters |
|---|---|---|
| 1 | Create two distinct logging fields in your incident response system: one for when an incident is confirmed covered under CIRCIA, and one for when any ransom payment is confirmed. | Separate timestamps ensure each CIRCIA reporting obligation is tracked from its own trigger, preventing the payment clock from being backdated to initial incident detection. |
| 2 | Define and document the internal criteria that constitute covered-incident awareness, and assign an owner to start CIRCIA’s covered incident report clock the moment those criteria are met. | Clear ownership and criteria reduce triage delays and keep the covered incident report on its required timeline from the correct awareness trigger. |
| 3 | Establish a dedicated escalation path for ransom payment decisions so that payment confirmation immediately starts CIRCIA’s ransom payment report clock, independent of the incident clock. | A separate payment workflow ensures the shorter ransom payment reporting window is met even if the covered incident was identified earlier. |
| 4 | Mark September 11, 2026—the EU Cyber Resilience Act reporting deadline noted by Crowell & Moring as less than 100 Days away—as a fixed milestone in your 2026 compliance roadmap. | Anchoring plans to this external deadline aligns CIRCIA reporting readiness with broader 2026 regulatory obligations. |
| 5 | Evaluate budgeting $25,000–$32,000 per year for automated compliance reminders for a 1,000-employee organization to track both CIRCIA clocks and the EU Cyber Resilience Act deadline. | Automated tracking reduces the risk of missed triggers and helps maintain consistent, auditable reporting across parallel regulatory timelines. |
Frequently Asked Questions
When does CIRCIA's ransom payment report clock start?
CIRCIA's 24-hour ransomware payment report clock starts at payment awareness, not incident awareness.
What timestamp should be logged for a ransom payment?
Log the timestamp when any ransom payment is confirmed.
When does CIRCIA's covered incident report clock start?
CIRCIA's 72-hour covered incident report clock starts at covered-incident awareness.
How does payment awareness timing affect the two clocks?
The answer changes when payment awareness occurs after incident awareness, because the 24-hour clock then starts later than the 72-hour clock.
What is the EU Cyber Resilience Act reporting deadline?
The EU Cyber Resilience Act reporting deadline is September 11, 2026.
What caveat applies to the automated compliance reminder cost figure?
The figure is at fully-loaded rates and excludes any incident-avoidance benefit.
Quick answers
| When does CIRCIA's ransom payment report clock start? | CIRCIA's ransom payment report clock starts at payment awareness, not incident awareness, and the timestamp should be logged when any ransom payment is confirmed. |
| When does CIRCIA's covered incident report clock start? | CIRCIA's covered incident report clock starts at covered-incident awareness, and the timestamp should be logged when the incident is confirmed covered, independent of any payment. |
| What is noted about the EU Cyber Resilience Act reporting deadline? | Crowell & Moring noted that the date was less than 100 days away and it should be used as the fixed external deadline in planning. |
| What is the estimated annual cost of automated compliance reminders for a 1,000-employee organization? | Automated compliance reminders cost roughly $25,000–$32,000 per year at fully-loaded rates, excluding any incident-avoidance benefit. |
| When can the ransom payment report clock start later than the covered incident report clock? | The ransom payment report clock can start later than the covered incident report clock when payment awareness occurs after incident awareness. |
Also worth reading: FTC Safeguards Rule Breach Notice: 30-Day Clock Starts at Triage, Not Legal Review: FTC Safeguards Rule Breach Notice: · 2026 Enterprise Triage: Balancing Speed And Rework In Routing: 2026 Enterprise Triage: Balancing Speed · 2026 Securities and Exchange Commission Cybersecurity Disclosure Deadline: 4-Day vs Escalate: 2026 Securities and Exchange Commission