Cybersecurity

Three different questions get filed under this heading and they have different answers: who must secure a system, who must report an incident, and who may be prosecuted for causing one. This page grades jurisdictions by what the law actually compels, not by whether it has a cybersecurity statute.

The distinction that matters most: a criminal prohibition is not a security obligation. The CFAA punishes the intruder and asks nothing of the defender. CIRCIA, NIS2 and the Cyber Resilience Act compel the defender to act, on a clock, before anyone has been charged with anything. Treating an anti-hacking statute as evidence of a security regime is the most common error in this area.

No US state map here, and for the same reason as trademark and copyright: these duties attach through sectors, not geography. The genuinely state-level layer, written security programmes and breach notification, is on the privacy map, where it already lives, rather than being counted twice.

Reporting clocks, shortest first

What separates these is not only the length but what starts them. A clock running from “awareness” behaves very differently from one running from a materiality determination, and the 24-hour ransom clocks run from the payment itself rather than from discovery of the incident.

RuleWhoClockRuns from
CIRCIA (ransom payment)US critical infrastructure24 hoursthe payment being made
EU Cyber Resilience ActMakers of products with digital elements24 hoursawareness of active exploitation
NIS2 (early warning)EU essential & important entities24 hoursawareness of a significant incident
NYDFS Part 500 (extortion)NY-licensed financial services24 hoursan extortion payment
CIRCIA (incident)US critical infrastructure72 hoursreasonable belief an incident occurred
NIS2 (notification)EU essential & important entities72 hoursawareness
NYDFS Part 500 (event)NY-licensed financial services72 hoursdetermining an event is reportable
UK NIS RegulationsOperators of essential services72 hoursawareness
SEC Item 1.05SEC-registered public companies4 business daysdetermining the incident is material
FISMA (major incident)US federal agencies7 daysidentification

United States (federal)

Sectoral duties only

No general federal security statute for the private sector. Duties attach by sector, critical infrastructure under CIRCIA, listed companies under the SEC rules, health under HIPAA, finance under the GLBA, while the CFAA punishes intrusion without requiring anyone to defend against it.

Regulators
CISASECFTCNIST

CIRCIA

6 U.S.C. §§ 681–681g

Cyber Incident Reporting for Critical Infrastructure Act of 2022

In force since March 15, 2022

Read the full record0 rights · 2 primary sources

SEC cyber disclosure

17 C.F.R. §§ 229.106, 249.308; Form 8-K Item 1.05

SEC rules on cybersecurity risk management, strategy, governance and incident disclosure

In force since December 18, 2023

Read the full record0 rights · 2 primary sources

FISMA

44 U.S.C. §§ 3551–3558

Federal Information Security Modernization Act of 2014

In force since December 18, 2014

Read the full record0 rights · 2 primary sources

CFAA

18 U.S.C. § 1030

Computer Fraud and Abuse Act

In force since October 16, 1986

Read the full record1 right · 1 primary source

United States (federal) guidance

US states

Written security programme required

US security duties come from sector regulation rather than from a general statute, and NYDFS Part 500 is the most detailed of them. The broader state layer, written security programmes and breach notification, sits on the privacy map rather than being duplicated here.

Regulators
NYDFS

NYDFS Part 500

23 NYCRR Part 500

New York State Department of Financial Services Cybersecurity Requirements for Financial Services Companies

In force since March 1, 2017

Read the full record0 rights · 1 primary source

European Union

Mandatory incident reporting, on a clock

The most demanding regime in force. NIS2 compels risk management and 24-hour early warning across eighteen sectors, DORA extends it to finance and directly supervises critical ICT providers, and the Cyber Resilience Act is the first law anywhere to regulate the security of software as a product.

Regulators
ENISA

NIS2

Directive (EU) 2022/2555

Directive on measures for a high common level of cybersecurity across the Union

In force since October 18, 2024

Read the full record0 rights · 1 primary source

DORA

Regulation (EU) 2022/2554

Regulation on digital operational resilience for the financial sector

In force since January 17, 2025

Read the full record0 rights · 1 primary source

Cyber Resilience Act

Regulation (EU) 2024/2847

Regulation on horizontal cybersecurity requirements for products with digital elements

In force since December 10, 2024

Read the full record0 rights · 1 primary source

European Union guidance

United Kingdom

Mandatory incident reporting, on a clock

Retained the NIS Regulations after Brexit and is diverging from NIS2 rather than tracking it. Supervision is split across sector-specific competent authorities rather than held by one regulator.

Regulators
NCSCICO

UK NIS Regulations

S.I. 2018/506

Network and Information Systems Regulations 2018

In force since May 10, 2018

Read the full record0 rights · 1 primary source

United Kingdom guidance