Understanding CIRCIA: Compliance Timelines and Covered Entity Status
The Cyber Incident Reporting for Critical Infrastructure Act (CIRCIA), signed into law to bolster national cybersecurity, fundamentally changes how critical infrastructure companies interact with federal regulatory bodies following a breach. Run by the Cybersecurity and Infrastructure Security Agency (CISA), CIRCIA mandates streamlined, urgent updates to help prevent cascading cyber failures across key sectors.
The Reporting Deadlines: 72 vs. 24 Hours
CIRCIA compliance is governed by two clear-cut timelines depending on the type of threat vector:
- Substantial Cyber Incidents (72-Hour Rule): Covered organizations must report any significant incident within 72 hours of "reasonable belief" that the event occurred. This applies to incidents that severely impact operations, cause unauthorized system access, or compromise third-party provider systems.
- Ransomware Payments (24-Hour Rule): If an organization decides to pay a ransom demand resulting from a ransomware attack, they have a strict 24-hour reporting window starting from the minute the payment transaction is initiated.
Who Counts as a "Covered Entity"?
The scope of CIRCIA covers 16 critical infrastructure sectors defined by Presidential Policy Directive 21 (PPD-21). However, CISA distinguishes between small businesses and larger critical systems. Typically, organizations are covered if they meet the SBA size standards for their sector, operate active community water systems, manage critical bulk power lines, administer regional hospitals, or run critical IT managed services.
Why "Strict Calendar Hours" Matter
Unlike many other compliance obligations, CIRCIA does not acknowledge "business days" or standard bank holidays. A breach discovered on Friday afternoon at 5:00 PM must be filed by Monday afternoon at 5:00 PM. Organizations must maintain an active, 24/7 Incident Response Plan (IRP) that incorporates direct communication lines to CISA. Using this calculator, security officers can determine their target timestamps in UTC, avoiding potential legal recourse and severe regulatory penalties.