Cyber regulation: who is in scope, and what follows
Most guidance on this asks you to trust it. This does not: every rule we apply names the provision it comes from, and the tool shows you which rules fired on your answers.
The regulatory landscape
Every instrument below is one we track: who issued it, whether it binds you by law or is taken on by contract, which version is current, and a link to the official text rather than to somebody’s summary of it.
120 instruments from 42 jurisdictions and standards bodies.
Showing all 120 instruments
Nothing matches those filters. Try clearing one of them.
| Instrument | Origin | Type | Status | Version | Applies from | Official text |
|---|---|---|---|---|---|---|
| International | ||||||
| Trust Services Criteria for service organisation reportsAICPA Trust Services Criteria (2017, revised 2022)CybersecurityPrivacy & data protection | AICPA | Certification schemeMandatory in context | In force | TSC 2017 (2022 revision) | — | Official text — SOC 2 |
Who it bindsService organisations, especially SaaS vendors selling into North America. An attestation report by a licensed CPA firm, not a certificate — Type I is a point in time, Type II covers a period. | ||||||
| CIS Critical Security ControlsCybersecurity | Center for Internet Security | FrameworkVoluntary | In force | v8.1 | — | Official text — CIS Controls |
Who it bindsAny organisation. 18 controls in three implementation groups sized by organisational capability — the usual starting point for a company too small to carry ISO/IEC 27001. | ||||||
| Cloud Controls Matrix and the STAR registryCybersecurity | Cloud Security Alliance | FrameworkVoluntary | In force | CCM v4 | — | Official text — CSA CCM / STAR |
Who it bindsCloud providers and their customers. 197 control objectives across 17 domains, with a public registry of self-assessments and third-party attestations — often the fastest way to answer a cloud vendor security questionnaire. | ||||||
| Trusted Information Security Assessment ExchangeCybersecuritySector-specific | ENX Association | Certification schemeMandatory in context | In force | Based on VDA ISA | — | Official text — TISAX |
Who it bindsThe automotive supply chain. Effectively mandatory to supply German OEMs: an assessment against the VDA ISA catalogue, with results shared through a common exchange rather than re-audited by each customer. | ||||||
| Cyber security for consumer internet of thingsETSI EN 303 645Product & IoT security | ETSI | StandardMandatory in context | In force | V3.1.3 | — | Official text — ETSI EN 303 645 |
Who it bindsConsumer IoT manufacturers. Thirteen provisions, of which the first three — no universal default passwords, a vulnerability disclosure policy, and software updates — are what the UK PSTI Act turned into law. | ||||||
| HITRUST Common Security FrameworkCybersecurityPrivacy & data protectionSector-specific | HITRUST | Certification schemeMandatory in context | In force | CSF v11 | — | Official text — HITRUST CSF |
Who it bindsPredominantly US healthcare and its supply chain. A prescriptive, certifiable framework that maps onto HIPAA, ISO/IEC 27001, NIST and PCI DSS at once — its selling point being that one assessment answers several. | ||||||
| Security for industrial automation and control systemsIEC 62443 seriesProduct & IoT securitySector-specificCybersecurity | IEC | StandardMandatory in context | In force | Series, parts published 2009–2024 | — | Official text — IEC 62443 |
Who it bindsAsset owners, system integrators and product suppliers in OT environments. Organised around security levels SL1–SL4 and zones and conduits, and increasingly cited directly in energy and manufacturing regulation. | ||||||
| Framework for the governance and management of enterprise ITCybersecurityOperational resilience | ISACA | FrameworkVoluntary | In force | 2019 | — | Official text — COBIT 2019 |
Who it bindsEnterprise IT governance rather than security specifically. Its value here is as the layer that connects board-level objectives to the control frameworks below it — which is exactly what NIS2 management liability asks a board to demonstrate. | ||||||
| Evaluation criteria for IT securityISO/IEC 15408 series (CC:2022)Product & IoT security | ISO / IEC | StandardMandatory in context | In force | ISO/IEC 15408:2022 / CC:2022 | — | Official text — Common Criteria |
Who it bindsIT product vendors seeking assurance certification, graded EAL1 to EAL7. The basis of the EU’s EUCC scheme and of procurement requirements in defence and government markets. | ||||||
| Business continuity management systems — RequirementsISO 22301:2019Operational resilience | ISO / IEC | StandardMandatory in context | In force | 2019 | — | Official text — ISO 22301 |
Who it bindsAny organisation. The usual evidence for the business continuity and crisis management limb of NIS2 Article 21(2)(c), DORA and CPS 230. | ||||||
| Risk management — GuidelinesISO 31000:2018Operational resilience | ISO / IEC | StandardVoluntary | In force | 2018 | — | Official text — ISO 31000 |
Who it bindsEnterprise-wide risk management principles. Deliberately not certifiable — it is a set of guidelines, and any body offering ISO 31000 certification is selling something ISO does not recognise. | ||||||
| Information security management systems — RequirementsISO/IEC 27001:2022 + Amd 1:2024Cybersecurity | ISO / IEC | StandardMandatory in context | In force | 2022 (Amd 1:2024) | — | Official text — ISO/IEC 27001 |
Who it bindsAny organisation, voluntarily or under contract. The 2022 revision cut Annex A to 93 controls in four themes; Amendment 1:2024 added climate change considerations to the context clause. Worth knowingCertificates issued against the 2013 edition ceased to be valid after 31 October 2025. | ||||||
| Information security controlsISO/IEC 27002:2022Cybersecurity | ISO / IEC | StandardVoluntary | In force | 2022 | — | Official text — ISO/IEC 27002 |
Who it bindsImplementation guidance for the Annex A controls of ISO/IEC 27001. Not certifiable in itself — it is the explanation, not the requirement. | ||||||
| Guidance on managing information security risksISO/IEC 27005:2022Cybersecurity | ISO / IEC | StandardVoluntary | In force | 2022 | — | Official text — ISO/IEC 27005 |
Who it bindsOrganisations building the risk assessment process that ISO/IEC 27001 clause 6.1.2 requires but deliberately does not prescribe. | ||||||
| Information security controls for cloud servicesISO/IEC 27017:2015Cybersecurity | ISO / IEC | StandardVoluntary | In force | 2015 | — | Official text — ISO/IEC 27017 |
Who it bindsCloud service providers and customers, splitting responsibility for each control between them. Usually certified as an extension to an existing ISO/IEC 27001 scope. | ||||||
| Protection of personally identifiable information in public cloudsISO/IEC 27018:2019Privacy & data protection | ISO / IEC | StandardVoluntary | In force | 2019 | — | Official text — ISO/IEC 27018 |
Who it bindsPublic cloud providers acting as processors of personal data. Frequently cited in procurement as evidence of GDPR Article 28 processor commitments. | ||||||
| Privacy information management systemISO/IEC 27701Privacy & data protection | ISO / IEC | StandardMandatory in context | In force | 2025 revision | — | Official text — ISO/IEC 27701 |
Who it bindsControllers and processors wanting a certifiable privacy management system. The revision restructures it as a standalone PIMS rather than an extension that could only be certified alongside ISO/IEC 27001. | ||||||
| Artificial intelligence management systemISO/IEC 42001:2023Artificial intelligence | ISO / IEC | StandardMandatory in context | In force | 2023 | — | Official text — ISO/IEC 42001 |
Who it bindsOrganisations providing or using AI systems. The first certifiable AI management standard, and the most common answer to how an EU AI Act quality management system gets evidenced. | ||||||
| NIST Cybersecurity FrameworkNIST Cybersecurity Framework (CSF) 2.0Cybersecurity | NIST (US) | FrameworkVoluntary | In force | 2.0 | — | Official text — NIST CSF 2.0 |
Who it bindsAny organisation. Version 2.0 dropped the critical-infrastructure framing and added Govern as a sixth function alongside Identify, Protect, Detect, Respond and Recover. | ||||||
| Protecting controlled unclassified information in nonfederal systemsNIST SP 800-171 Rev. 3Cybersecurity | NIST (US) | FrameworkMandatory in context | In force | Revision 3 | — | Official text — NIST SP 800-171 |
Who it bindsNon-federal organisations holding US Controlled Unclassified Information — in practice, defence and federal supply chains worldwide. It is the control set CMMC Level 2 assesses against. | ||||||
| Zero Trust ArchitectureNIST SP 800-207Cybersecurity | NIST (US) | FrameworkVoluntary | In force | 2020 | — | Official text — NIST SP 800-207 |
Who it bindsArchitectural guidance rather than a control set. The reference definition that US executive orders and a growing number of procurement documents point at when they say "zero trust". | ||||||
| Security and privacy controls for information systems and organizationsNIST SP 800-53 Rev. 5CybersecurityPrivacy & data protection | NIST (US) | FrameworkMandatory in context | In force | Revision 5, with patch releases | — | Official text — NIST SP 800-53 |
Who it bindsMandatory for US federal systems under FISMA; voluntary elsewhere, but the source catalogue that FedRAMP, StateRAMP and many national baselines derive from. | ||||||
| Application Security Verification StandardProduct & IoT security | OWASP | StandardVoluntary | In force | v5.0 | — | Official text — OWASP ASVS |
Who it bindsSoftware teams and the people testing their work. Three verification levels, and the usual way a secure-development requirement in a contract or in the Cyber Resilience Act gets made concrete. | ||||||
| Payment Card Industry Data Security StandardPCI DSS v4.0.1CybersecuritySector-specific | PCI Security Standards Council | StandardMandatory in context | In force | v4.0.1 | Mar 31, 2025staged | Official text — PCI DSS |
Who it bindsAnyone storing, processing or transmitting cardholder data. Not law anywhere, but enforced through the card brands’ contracts, which is a sharper instrument than most statutes. Timetablev4.0.1 replaced v3.2.1 in March 2024; the 51 future-dated requirements became mandatory on 31 March 2025. | ||||||
| Customer Security Controls FrameworkCybersecuritySector-specific | SWIFT | FrameworkMandatory | In force | Published annually | — | Official text — SWIFT CSCF |
Who it bindsEvery institution connected to the SWIFT network. Annual self-attestation against the mandatory controls is a condition of continued access, with independent assessment required. | ||||||
| European Union | ||||||
| Czech Cybersecurity Act (NIS2)Zákon č. 264/2025 Sb., o kybernetické bezpečnostiCybersecurityIncident reporting | CzechiaCheck your scope | LawMandatory | In force | 264/2025 Sb. | Nov 1, 2025 | Official text — Zákon o kybernetické bezpečnosti |
Who it bindsRegulated services in Czechia, split into a higher and a lower obligation regime rather than NIS2’s essential/important wording — one of the clearer examples of a transposition renaming the tiers. Worth knowingImplementing decrees 334/2025, 408/2025, 409/2025 and 410/2025 Sb. carry the actual security measures. | ||||||
| Thresholds identifying German critical installationsBSI-Kritisverordnung (BSI-KritisV)CybersecuritySector-specific | GermanyCheck your scope | Subordinate actMandatory | In force | BSI-KritisV | — | Official text — BSI-KritisV |
Who it bindsSets the quantitative thresholds — 500 000 supplied persons is the recurring one — that turn a German operator into a KRITIS operator. | ||||||
| German NIS2 implementation actGesetz über das Bundesamt für Sicherheit in der Informationstechnik (BSIG)CybersecurityIncident reporting | GermanyCheck your scope | LawMandatory | In force | BSIG in the version of the NIS2UmsuCG | Jan 1, 2026 | Official text — BSIG 2025 |
Who it bindsAround 29 000 German entities: besonders wichtige and wichtige Einrichtungen by size and sector, plus operators of critical installations under the BSI-KritisV thresholds. ExposureUp to €10 000 000 or 2% of worldwide turnover, with explicit management liability for failure to approve and monitor risk measures. | ||||||
| German CER Directive transpositionKRITIS-Dachgesetz (KRITIS-DachG)Operational resilienceSector-specific | GermanyCheck your scope | LawMandatory | In force | KRITIS-DachG | — | Official text — KRITIS-Dachgesetz |
Who it bindsOperators of critical infrastructure, for physical resilience: risk assessments, resilience plans and background checks — the non-cyber half that the BSIG does not cover. | ||||||
| Estonian Cybersecurity ActKüberturvalisuse seadusCybersecurityIncident reporting | EstoniaCheck your scope | LawMandatory | In force | Consolidated text | — | Official text — KüTS |
Who it bindsProviders of vital services and other entities designated under the act, together with the state information system. | ||||||
| Cyber Solidarity Act and the European Cybersecurity Alert SystemRegulation (EU) 2025/38CybersecurityOperational resilience | European UnionCheck your scope | RegulationMandatory in context | In force | (EU) 2025/38 | Feb 4, 2025 | Official text — Cyber Solidarity Act |
Who it bindsPrimarily Member States and their CSIRTs, through the alert system and the EU Cybersecurity Reserve. Private entities meet it as recipients of incident response support rather than as duty-holders. | ||||||
| Harmonised rules on fair access to and use of dataRegulation (EU) 2023/2854Privacy & data protectionOperational resilience | European UnionCheck your scope | RegulationMandatory | In force | (EU) 2023/2854 | Sep 12, 2025 | Official text — Data Act |
Who it bindsManufacturers of connected products and providers of related services, and — through the cloud-switching chapter — every provider of data processing services offered in the EU. Worth knowingThe chapter people miss is switching: contractual, technical and (from January 2027) charge-free egress obligations on cloud providers. | ||||||
| European data governanceRegulation (EU) 2022/868Privacy & data protection | European UnionCheck your scope | RegulationMandatory | In force | (EU) 2022/868 | Sep 24, 2023 | Official text — Data Governance Act |
Who it bindsPublic sector bodies re-using protected data, data intermediation service providers, and recognised data altruism organisations. | ||||||
| Digital Operational Resilience ActRegulation (EU) 2022/2554 on digital operational resilience for the financial sectorOperational resilienceCybersecurityIncident reportingSector-specific | European UnionCheck your scope | RegulationMandatory | In force | (EU) 2022/2554 | Jan 17, 2025 | Official text — DORA |
Who it bindsAround 20 categories of financial entity — banks, insurers, investment firms, payment and e-money institutions, crypto-asset service providers, trading venues — and the critical ICT third-party providers serving them. Worth knowingWhere DORA and NIS2 both reach a financial entity, DORA prevails as lex specialis for ICT risk and incident reporting. | ||||||
| Privacy and electronic communicationsDirective 2002/58/EC as amended by Directive 2009/136/ECPrivacy & data protection | European UnionCheck your scope | DirectiveMandatory | In force | 2002/58/EC (consolidated) | Oct 31, 2003 | Official text — ePrivacy Directive |
Who it bindsProviders of electronic communications services, and anyone storing or reading information on a user’s device — which is what makes it, not the GDPR, the source of the cookie consent rule. Worth knowingThe ePrivacy Regulation intended to replace it was withdrawn in 2025. The 2002 directive remains the operative text. | ||||||
| ENISA mandate and the European cybersecurity certification frameworkRegulation (EU) 2019/881CybersecurityProduct & IoT security | European UnionCheck your scope | RegulationMandatory in context | In force | (EU) 2019/881 | Jun 27, 2019 | Official text — EU Cybersecurity Act |
Who it bindsGives ENISA a permanent mandate and creates the machinery for EU-wide certification schemes. Certification under it is voluntary unless another instrument makes a scheme mandatory. | ||||||
| European cybersecurity certification scheme on Common CriteriaCommission Implementing Regulation (EU) 2024/482Product & IoT securityCybersecurity | European UnionCheck your scope | Certification schemeVoluntary | In force | (EU) 2024/482 | Feb 27, 2025 | Official text — EUCC |
Who it bindsICT products certified against Common Criteria. The first scheme adopted under the Cybersecurity Act; it succeeds the SOG-IS mutual recognition arrangement. | ||||||
| General Data Protection RegulationRegulation (EU) 2016/679Privacy & data protectionIncident reporting | European UnionCheck your scope | RegulationMandatory | In force | (EU) 2016/679 | May 25, 2018 | Official text — GDPR |
Who it bindsAny controller or processor established in the EU, and any outside it that offers goods or services to, or monitors the behaviour of, people in the EU. ExposureUp to €20 000 000 or 4% of worldwide annual turnover, whichever is higher. | ||||||
| Technical and methodological requirements for digital infrastructure entitiesCommission Implementing Regulation (EU) 2024/2690CybersecurityIncident reporting | European UnionCheck your scope | RegulationMandatory | In force | (EU) 2024/2690 | Nov 7, 2024 | Official text — NIS2 Implementing Regulation |
Who it bindsDNS providers, TLD registries, cloud and data-centre providers, CDNs, managed service and managed security providers, online marketplaces, search engines, social networks and trust service providers. Worth knowingThis is the only place NIS2 states concrete technical requirements. For every other sector the measures stay at the level of Article 21 and are filled in nationally. | ||||||
| Payment services and strong customer authenticationDirective (EU) 2015/2366 and Commission Delegated Regulation (EU) 2018/389Sector-specificCybersecurity | European UnionCheck your scope | DirectiveMandatory | In force | Directive (EU) 2015/2366 + RTS (EU) 2018/389 | Sep 14, 2019 | Official text — PSD2 / SCA |
Who it bindsPayment service providers in the EU, including account information and payment initiation services. Worth knowingThe PSD3 directive and Payment Services Regulation proposals are still in the legislative process; PSD2 remains the law. | ||||||
| Cybersecurity essential requirements for radio equipmentCommission Delegated Regulation (EU) 2022/30Product & IoT security | European UnionCheck your scope | RegulationMandatory | In force | (EU) 2022/30 | Aug 1, 2025 | Official text — RED delegated regulation |
Who it bindsInternet-connected radio equipment, and equipment processing personal data, traffic data or location data — in practice most consumer IoT sold in the EU. Worth knowingPresumption of conformity comes from the harmonised standards EN 18031-1/-2/-3, cited with restrictions. | ||||||
| Threat intelligence-based ethical red teaming frameworkOperational resilienceSector-specific | European UnionCheck your scope | FrameworkMandatory in context | In force | 2025 revision | — | Official text — TIBER-EU |
Who it bindsFinancial market infrastructures and significant financial entities, as directed by their national authority. The 2025 revision aligns it with DORA’s threat-led penetration testing requirement. | ||||||
| Italian NIS2 transpositionDecreto legislativo 4 settembre 2024, n. 138CybersecurityIncident reporting | ItalyCheck your scope | LawMandatory | In force | D.lgs. 138/2024 | Oct 16, 2024 | Official text — D.lgs. 138/2024 |
Who it bindsItalian essential and important entities, which register annually with ACN through a portal window that opens each January. | ||||||
| Europe (non-EU) | ||||||
| Mandatory cyberattack reporting for critical infrastructureInformationssicherheitsgesetz (ISG), Art. 74a ff.Incident reportingCybersecurity | Switzerland | LawMandatory | In force | ISG as amended | Apr 1, 2025 | Official text — ISA reporting duty |
Who it bindsSwiss operators of critical infrastructure — energy, water, transport, healthcare, finance, public administration and more. Cyberattacks must be reported to BACS within 24 hours of discovery. | ||||||
| Revised Federal Act on Data ProtectionBundesgesetz über den Datenschutz (DSG)Privacy & data protection | Switzerland | LawMandatory | In force | DSG (total revision) | Sep 1, 2023 | Official text — revFADP |
Who it bindsProcessing of personal data with an effect in Switzerland. Broadly GDPR-aligned, but sanctions fall on responsible individuals rather than the company — up to CHF 250 000. | ||||||
| Norwegian Digital Security ActLov om digital sikkerhet (digitalsikkerhetsloven)CybersecurityIncident reporting | Norway | LawMandatory | In force | Digitalsikkerhetsloven | Jan 1, 2025 | Official text — Digitalsikkerhetsloven |
Who it bindsNorwegian providers of essential services and digital service providers. It implements NIS1; NIS2 has not yet been incorporated into the EEA Agreement, so Norway sits a directive behind the EU. | ||||||
| Turkish Cybersecurity LawSiber Güvenlik Kanunu (No. 7545)CybersecurityIncident reporting | Türkiye | LawMandatory | In force | No. 7545 | Mar 19, 2025 | Official text — Cybersecurity Law No. 7545 |
Who it bindsPublic bodies and operators of critical infrastructure in Türkiye, with certification requirements for cybersecurity products and services sold into them. | ||||||
| Law on the Protection of Personal DataKişisel Verilerin Korunması Kanunu (No. 6698)Privacy & data protection | Türkiye | LawMandatory | In force | No. 6698, as amended in 2024 | Apr 7, 2016 | Official text — KVKK |
Who it bindsData controllers processing personal data of people in Türkiye. The 2024 amendment reworked the rules on special categories and international transfers towards the GDPR model. | ||||||
| Sectors of critical infrastructure and criteria for identifying CII objectsПостанова Кабінету Міністрів України № 1109 від 09.10.2020Sector-specificCybersecurity | UkraineCheck your scope | Subordinate actMandatory | In force | № 1109 від 09.10.2020 | — | Official text — CMU Resolution 1109 |
Who it bindsLists 26 sectors of critical infrastructure and names the sectoral body responsible for each. If you are looking for the question "is my sector in scope in Ukraine", this is the document that answers it. | ||||||
| Procedure for responding to cyber incidents and cyber attacksПостанова Кабінету Міністрів України № 1533 від 26.11.2025Incident reporting | UkraineCheck your scope | Subordinate actMandatory | In force | № 1533 від 26.11.2025 | — | Official text — CMU Resolution 1533 |
Who it bindsUkrainian operators of critical infrastructure. The deadline is ONE HOUR from detection of a significant cyber incident — the shortest in this table, and 24 times shorter than the NIS2 early warning. | ||||||
| General cyber protection requirements for critical infrastructure objectsПостанова Кабінету Міністрів України № 518 від 19.06.2019 (у ред. постанови КМУ № 1470 від 13.11.2025)Cybersecurity | UkraineCheck your scope | Subordinate actMandatory | In force | № 518 (ред. № 1470 від 13.11.2025) | — | Official text — CMU Resolution 518 |
Who it bindsThe substantive control set for Ukrainian critical infrastructure operators — the closest counterpart to NIS2 Article 21. Substantially rewritten in November 2025. | ||||||
| Vulnerability detection and cyber incident response systemПостанова Кабінету Міністрів України № 943 від 23.10.2020CybersecurityIncident reporting | UkraineCheck your scope | Subordinate actMandatory | In force | № 943 від 23.10.2020 | — | Official text — CMU Resolution 943 |
Who it bindsState bodies and critical infrastructure operators connected to the national vulnerability detection and incident response system. | ||||||
| Law of Ukraine on Critical InfrastructureЗакон України «Про критичну інфраструктуру» № 1882-IXOperational resilienceCybersecuritySector-specific | UkraineCheck your scope | LawMandatory | In force | № 1882-IX (ред. 21.09.2024) | Jun 27, 2022 | Official text — Law 1882-IX |
Who it bindsObjects of critical infrastructure and their operators. Article 10 sets four criticality categories — not the two classes a NIS2 reader expects. Worth knowingUkraine’s regime is a critical-infrastructure regime, not a NIS2 transposition: a different legal theory, a different sector taxonomy and a much shorter reporting clock. | ||||||
| Law on the Basic Principles of Cybersecurity of UkraineЗакон України «Про основні засади забезпечення кібербезпеки України» № 2163-VIIICybersecurity | UkraineCheck your scope | LawMandatory | In force | № 2163-VIII | May 9, 2018 | Official text — Law 2163-VIII |
Who it bindsThe framework statute: it defines critical information infrastructure, the national cybersecurity system and who does what within it. | ||||||
| Law on Personal Data ProtectionЗакон України «Про захист персональних даних» № 2297-VIPrivacy & data protection | UkraineCheck your scope | LawMandatory | In force | № 2297-VI | Jan 1, 2011 | Official text — Law 2297-VI |
Who it bindsControllers and processors of personal data in Ukraine. It predates the GDPR and is materially weaker; a GDPR-style replacement has been in draft for several years. Worth knowingEU accession will require alignment with the GDPR. Companies serving EU customers are usually already bound by the GDPR directly under its Article 3(2). | ||||||
| Criteria for determining a significant cyber incidentНаказ Адміністрації Держспецзв’язку № 351 від 14.05.2026 (зареєстровано в Мін’юсті 22.06.2026 за № 900/46294)Incident reporting | UkraineCheck your scope | Subordinate actMandatory | In force | № 351 від 14.05.2026 | Jun 30, 2026 | Official text — SSSCIP Order 351 |
Who it bindsDefines the threshold that starts the one-hour clock. Without it the reporting duty had no measurable trigger; it took effect on 30 June 2026. | ||||||
| Cyber Essentials and Cyber Essentials PlusCybersecurity | United Kingdom | Certification schemeMandatory in context | In force | Montpellier question set | — | Official text — Cyber Essentials |
Who it bindsVoluntary in general, mandatory for suppliers bidding for UK government contracts that handle sensitive information. | ||||||
| Network and Information Systems Regulations 2018The Network and Information Systems Regulations 2018 (SI 2018/506)CybersecurityIncident reporting | United Kingdom | Subordinate actMandatory | In force | SI 2018/506 | May 10, 2018 | Official text — NIS Regulations 2018 |
Who it bindsUK operators of essential services in energy, transport, health, water and digital infrastructure, plus relevant digital service providers. ExposureUp to £17 000 000 for the most serious contraventions. Worth knowingDerived from NIS1, which the EU has repealed. The UK did not follow NIS2 — the divergence is now substantial. | ||||||
| Product Security and Telecommunications Infrastructure Act 2022Product Security and Telecommunications Infrastructure Act 2022Product & IoT security | United Kingdom | LawMandatory | In force | 2022 c. 46, with the 2023 security requirements regulations | Apr 29, 2024 | Official text — PSTI Act |
Who it bindsManufacturers, importers and distributors of consumer connectable products in the UK: no universal default passwords, a vulnerability disclosure policy, and a published support period. | ||||||
| Telecommunications (Security) Act 2021 and the Security Code of PracticeSector-specificCybersecurity | United Kingdom | LawMandatory | In force | 2021 c. 31, with SI 2022/933 | Oct 1, 2022 | Official text — Telecommunications (Security) Act |
Who it bindsUK public electronic communications networks and services, on a tiered timetable by provider size. | ||||||
| UK General Data Protection Regulation and Data Protection Act 2018Data Protection Act 2018 and the retained Regulation (EU) 2016/679Privacy & data protection | United Kingdom | LawMandatory | In force | DPA 2018, as amended by the Data (Use and Access) Act 2025 | May 25, 2018 | Official text — UK GDPR / DPA 2018 |
Who it bindsControllers and processors with a UK establishment, or targeting people in the UK. ExposureUp to £17 500 000 or 4% of worldwide annual turnover. | ||||||
| North America | ||||||
| Technology and cyber risk management guidelineCybersecurityOperational resilienceSector-specific | Canada | GuidanceMandatory in context | In force | Guideline B-13 | Jan 1, 2024 | Official text — OSFI B-13 |
Who it bindsFederally regulated financial institutions in Canada. Supervisory expectation rather than statute, enforced through the supervisory relationship. | ||||||
| Personal Information Protection and Electronic Documents ActPrivacy & data protectionIncident reporting | Canada | LawMandatory | In force | S.C. 2000, c. 5 | Jan 1, 2001 | Official text — PIPEDA |
Who it bindsPrivate-sector organisations handling personal information in the course of commercial activity. Breaches posing a real risk of significant harm must be reported to the Commissioner and to affected individuals. | ||||||
| Act to modernise legislative provisions on the protection of personal informationLoi 25 / Loi sur la protection des renseignements personnels dans le secteur privéPrivacy & data protection | Canada — Québec | LawMandatory | In force | Loi 25 | Sep 22, 2024 | Official text — Law 25 (Québec) |
Who it bindsAnyone handling personal information about people in Québec. The closest thing in North America to the GDPR, including data portability and a private right of action. ExposureAdministrative penalties up to CAD 10 000 000 or 2% of worldwide turnover; penal fines up to CAD 25 000 000 or 4%. | ||||||
| Executive orders on strengthening the nation’s cybersecurityCybersecurityProduct & IoT security | United States | GuidanceMandatory in context | In force | EO 14144 (2025), amended by EO 14306 (2025) | Jan 16, 2025 | Official text — EO 14144 / 14306 |
Who it bindsFederal agencies directly, and software vendors selling to them through the procurement conditions the orders create — secure development attestations, post-quantum planning and identity requirements. | ||||||
| Federal Risk and Authorization Management ProgramCybersecuritySector-specific | United States | Certification schemeMandatory in context | In force | Rev. 5 baselines | — | Official text — FedRAMP |
Who it bindsCloud service providers selling to US federal agencies. Authorization is effectively a precondition of the sale rather than a legal duty on the provider. | ||||||
| Federal Information Security Modernization ActFederal Information Security Modernization Act of 2014, 44 U.S.C. ch. 35CybersecuritySector-specific | United States | LawMandatory | In force | Pub. L. 113-283 | Dec 18, 2014 | Official text — FISMA |
Who it bindsUS federal agencies and, through contract flow-down, the contractors operating systems on their behalf. The control set it mandates is NIST SP 800-53. | ||||||
| Standards for safeguarding customer information16 CFR Part 314Privacy & data protectionSector-specificIncident reporting | United States | RegulationMandatory | In force | 16 CFR Part 314 (as amended 2023) | Jun 9, 2023 | Official text — GLBA Safeguards Rule |
Who it bindsNon-bank financial institutions under FTC jurisdiction — a wider set than it sounds, reaching mortgage brokers, tax preparers, car dealers and many fintechs. Worth knowingSince May 2024 a security event affecting 500 or more consumers must be notified to the FTC within 30 days. | ||||||
| Security standards for the protection of electronic protected health information45 CFR Part 164, Subpart CPrivacy & data protectionSector-specificCybersecurity | United States | RegulationMandatory | In force | 45 CFR §§ 164.302–164.318 | Apr 20, 2005 | Official text — HIPAA Security Rule |
Who it bindsCovered entities — health plans, clearinghouses and most providers — and their business associates, including non-US processors handling PHI under contract. ExposureCivil money penalties tiered by culpability, with an annual cap per violation category that is adjusted for inflation each year. Worth knowingA January 2025 proposed rule would remove the "addressable" category and make encryption, MFA and asset inventories mandatory. Still a proposal. | ||||||
| Critical Infrastructure Protection reliability standardsSector-specificCybersecurity | United States | StandardMandatory | In force | CIP-002 through CIP-015 | — | Official text — NERC CIP |
Who it bindsOwners and operators of the bulk electric system in the US, Canada and part of Mexico. Enforced by audit with penalties up to USD 1 million per violation per day. Worth knowingCIP-015, adding internal network security monitoring, is the most recent addition to the family. | ||||||
| Cybersecurity risk management, strategy, governance and incident disclosureSEC Release Nos. 33-11216; 34-97989Incident reportingCybersecurity | United States | RegulationMandatory | In force | Release 33-11216 | Dec 18, 2023 | Official text — SEC cyber disclosure rules |
Who it bindsSEC registrants, including foreign private issuers. A material cybersecurity incident goes on Form 8-K Item 1.05 within four business days of the materiality determination; Regulation S-K Item 106 requires annual disclosure of governance and risk management. Worth knowingThe clock runs from the materiality determination, not from discovery — but that determination must be made without unreasonable delay. | ||||||
| Management assessment of internal controlsSarbanes-Oxley Act of 2002, section 404Sector-specific | United States | LawMandatory | In force | Pub. L. 107-204 | Jul 30, 2002 | Official text — SOX §404 |
Who it bindsUS public companies. Reaches IT because the general IT controls over financial reporting systems — access, change management, operations — are in scope of the audit. | ||||||
| Data breach notification statutes of the 50 statesPrivacy & data protectionIncident reporting | United States | LawMandatory | In force | All 50 states, DC and territories | — | Official text — State breach notification laws |
Who it bindsAnyone holding personal information about residents of a given state. There is no federal breach notification law of general application, so a single incident routinely triggers dozens of statutes with different definitions and deadlines. | ||||||
| Pipeline and rail cybersecurity security directivesSector-specificCybersecurityIncident reporting | United States | Subordinate actMandatory | In force | Reissued annually | — | Official text — TSA Security Directives |
Who it bindsDesignated pipeline, freight rail, passenger rail and higher-risk airport and aircraft operators. Requires a cybersecurity implementation plan, an assessment programme and 24-hour incident reporting to CISA. | ||||||
| Cybersecurity requirements for financial services companies23 NYCRR Part 500CybersecuritySector-specificIncident reporting | United States — New York | RegulationMandatory | In force | Second Amendment | Nov 1, 2025staged | Official text — NYDFS Part 500 |
Who it bindsEntities licensed by NYDFS — banks, insurers, mortgage servicers, virtual currency businesses. Widely copied by other state regulators, so it functions as a de facto national baseline. TimetableThe Second Amendment phased in over two years, with the final tranche — MFA everywhere, asset inventories — from 1 November 2025. ExposureAnnual certification of compliance is signed by the CISO and highest-ranking executive; a false certification is itself an enforcement matter. | ||||||
| Asia-Pacific | ||||||
| Prudential Standard CPS 230 Operational Risk ManagementOperational resilienceSector-specific | Australia | RegulationMandatory | In force | CPS 230 | Jul 1, 2025 | Official text — APRA CPS 230 |
Who it bindsAPRA-regulated entities. Requires identification of critical operations, tolerance levels for disruption, and active management of material service provider risk — the Australian counterpart to DORA’s third-party chapter. | ||||||
| Prudential Standard CPS 234 Information SecurityCybersecuritySector-specific | Australia | RegulationMandatory | In force | CPS 234 (determination F2018L01745) | Jul 1, 2019 | Official text — APRA CPS 234 |
Who it bindsAPRA-regulated banks, insurers and superannuation funds. Requires board-level accountability, controls sized to the threat, testing, and notification to APRA within 72 hours of a material information security incident. | ||||||
| Essential Eight Maturity ModelCybersecurity | Australia | FrameworkMandatory in context | In force | Maturity Model, revised periodically | — | Official text — Essential Eight |
Who it bindsMandatory for Australian non-corporate Commonwealth entities at Maturity Level Two; voluntary elsewhere, but widely used as a contractual baseline. Eight mitigations, three maturity levels, and unusually specific about what each level means. | ||||||
| Australian Government Information Security ManualCybersecurity | Australia | FrameworkMandatory in context | In force | Updated quarterly | — | Official text — ISM |
Who it bindsAustralian government entities and their suppliers. A large control catalogue organised around a risk management framework, and the source the Essential Eight is drawn from. | ||||||
| Security of Critical Infrastructure Act 2018Security of Critical Infrastructure Act 2018 (Cth)CybersecurityOperational resilienceSector-specificIncident reporting | Australia | LawMandatory | In force | Act No. 29 of 2018, as amended through 2024 | Jul 11, 2018 | Official text — SOCI Act |
Who it bindsResponsible entities for critical infrastructure assets across 11 sectors. Obligations stack: an asset register, a critical infrastructure risk management programme, mandatory incident reporting (12 hours for significant, 72 for other), and government assistance powers that can direct an entity mid-incident. Worth knowingThe step-in powers are the part with no European equivalent: in a serious incident the government can issue directions, or intervene on the network itself. | ||||||
| Cybersecurity directions under section 70B(6) of the IT ActIncident reportingCybersecurity | India | Subordinate actMandatory | In force | Directions of 28 April 2022 | Jun 28, 2022 | Official text — CERT-In Directions |
Who it bindsService providers, intermediaries, data centres, body corporates and government organisations in India. Reportable incidents go to CERT-In within SIX HOURS of noticing them — the shortest general reporting deadline of any major jurisdiction. Worth knowingIt also mandates 180-day log retention within India and five-year KYC retention for VPN, cloud and VPS providers. | ||||||
| Cybersecurity and Cyber Resilience FrameworkCybersecurityOperational resilienceSector-specific | India | RegulationMandatory | In force | CSCRF, August 2024 | — | Official text — SEBI CSCRF |
Who it bindsSEBI-regulated entities, graded into five categories by size and systemic importance, each with a different depth of audit and testing. | ||||||
| Act on the Protection of Personal Information個人情報の保護に関する法律(平成15年法律第57号)Privacy & data protectionIncident reporting | Japan | LawMandatory | In force | Act No. 57 of 2003, as amended | Apr 1, 2005 | Official text — APPI |
Who it bindsBusinesses handling personal information about people in Japan, including foreign businesses supplying goods or services there. Leaks likely to harm individuals must be reported to the PPC — a preliminary report within about 3–5 days and a full report within 30. Worth knowingJapan holds an EU adequacy decision, which is why EU–Japan transfers do not need standard contractual clauses. | ||||||
| Basic Act on Cybersecurityサイバーセキュリティ基本法(平成26年法律第104号)Cybersecurity | Japan | LawMandatory | In force | Act No. 104 of 2014, as amended | Jan 9, 2015 | Official text — Basic Act on Cybersecurity |
Who it bindsSets national strategy and allocates responsibility across government, critical infrastructure operators and businesses. Duties on private entities are largely cooperative rather than penal. | ||||||
| Information Security Management System and personal information certificationCybersecurityPrivacy & data protection | South Korea | Certification schemeMandatory in context | In force | ISMS-P | — | Official text — ISMS-P |
Who it bindsMandatory for Korean telecoms, large ISPs, hospitals and universities above revenue or user thresholds; voluntary for everyone else. Certification is annual with a three-year cycle. | ||||||
| Personal Information Protection ActPrivacy & data protectionIncident reporting | South Korea | LawMandatory | In force | As amended in 2023 | Sep 30, 2011 | Official text — PIPA |
Who it bindsAny personal information controller handling data about people in Korea. Among the strictest regimes in Asia: breaches are notifiable within 72 hours, and penalties reach 3% of total turnover. | ||||||
| New Zealand Privacy ActPrivacy & data protectionIncident reporting | New Zealand | LawMandatory | In force | 2020 No. 31 | Dec 1, 2020 | Official text — Privacy Act 2020 |
Who it bindsAgencies handling personal information in New Zealand, including overseas businesses carrying on business there. Privacy breaches causing serious harm must be notified as soon as practicable. | ||||||
| Singapore Cybersecurity Act, as amended in 2024Cybersecurity Act 2018 (Act 9 of 2018)CybersecurityIncident reporting | Singapore | LawMandatory | In force | Act 9 of 2018, amended by Act 39 of 2024 | Aug 31, 2018 | Official text — Cybersecurity Act |
Who it bindsOwners of critical information infrastructure in 11 sectors, plus — since the 2024 amendment — foundational digital infrastructure providers, entities of special cybersecurity interest and major systems of national interest. Incidents are reportable within 2 hours. Worth knowingThe 2024 amendment extended the Act to CII physically located outside Singapore, and to systems owned by third parties on which a CII depends. | ||||||
| Technology Risk Management GuidelinesCybersecurityOperational resilienceSector-specific | Singapore | GuidanceMandatory in context | In force | January 2021 revision | — | Official text — MAS TRM Guidelines |
Who it bindsAll MAS-regulated financial institutions. Guidelines rather than law, but non-compliance weighs in MAS’s risk assessment; the binding counterpart is the Notice on Cyber Hygiene. | ||||||
| Personal Data Protection ActPrivacy & data protectionIncident reporting | Singapore | LawMandatory | In force | Act 26 of 2012, as amended in 2020 | Jul 2, 2014 | Official text — PDPA |
Who it bindsOrganisations collecting, using or disclosing personal data in Singapore. Notifiable breaches go to the Commission within 3 calendar days of assessment. ExposureUp to 10% of annual turnover in Singapore, or SGD 1 000 000, whichever is higher. | ||||||
| Middle East & Africa | ||||||
| UAE Information Assurance StandardsCybersecurity | United Arab Emirates | StandardMandatory | In force | IAS v1.1 | — | Official text — UAE IA Standards |
Who it bindsUAE government entities and designated critical information infrastructure operators. Structured as 4 security priorities across 188 controls, mapped closely to ISO/IEC 27001. | ||||||
| Federal Personal Data Protection LawFederal Decree-Law No. 45 of 2021 on the Protection of Personal DataPrivacy & data protection | United Arab Emirates | LawMandatory | In force | Federal Decree-Law No. 45 of 2021 | Jan 2, 2022 | Official text — UAE PDPL |
Who it bindsControllers and processors in the UAE, and those abroad processing data of people in the UAE. The financial free zones — DIFC and ADGM — run their own separate data protection laws, which is the usual trap. | ||||||
| Privacy Protection Law, as amended by Amendment 13Privacy & data protection | Israel | LawMandatory | In force | Amendment 13 | Aug 14, 2025 | Official text — Privacy Protection Law (Amendment 13) |
Who it bindsControllers and processors handling personal data in Israel. Amendment 13 brought in administrative fines, mandatory DPOs for large processors, and a substantially expanded enforcement power — a decisive move towards the GDPR model. Worth knowingIsrael holds an EU adequacy decision, which the reform was partly intended to protect. | ||||||
| Essential Cybersecurity ControlsEssential Cybersecurity Controls (ECC-2:2024)Cybersecurity | Saudi Arabia | StandardMandatory | In force | ECC-2:2024 | — | Official text — NCA ECC |
Who it bindsSaudi government bodies and their contractors, plus operators of critical national infrastructure. Compliance is assessed annually and reported to the NCA. | ||||||
| Cyber Security FrameworkCybersecuritySector-specific | Saudi Arabia | FrameworkMandatory | In force | Version 1.0 | — | Official text — SAMA CSF |
Who it bindsBanks, insurers, financing and credit bureau companies regulated by SAMA. Maturity-model based, assessed on a 0–5 scale with level 3 as the minimum expectation. | ||||||
| Personal Data Protection LawPrivacy & data protection | Saudi Arabia | LawMandatory | In force | Royal Decree M/19, as amended | Sep 14, 2023 | Official text — Saudi PDPL |
Who it bindsAny processing of personal data of people in Saudi Arabia, including by entities outside the Kingdom. Enforcement began after a one-year grace period in September 2024. | ||||||
| Cybercrimes Act 19 of 2020CybersecurityIncident reporting | South Africa | LawMandatory | In force | Act 19 of 2020 (Government Gazette No. 44651) | Dec 1, 2021 | Official text — Cybercrimes Act |
Who it bindsCreates cybercrime offences and, unusually for a criminal statute, puts a reporting duty on electronic communications service providers and financial institutions: 72 hours to report an offence they become aware of. | ||||||
| Protection of Personal Information ActProtection of Personal Information Act 4 of 2013Privacy & data protectionIncident reporting | South Africa | LawMandatory | In force | Act 4 of 2013 | Jul 1, 2021 | Official text — POPIA |
Who it bindsResponsible parties processing personal information in South Africa. Security compromises must be reported to the Regulator and to data subjects as soon as reasonably possible. ExposureAdministrative fines up to ZAR 10 000 000, and criminal liability for some offences. | ||||||
| Latin America | ||||||
| Cybersecurity policy for financial institutionsResolução CMN nº 4.893/2021CybersecuritySector-specific | Brazil | Subordinate actMandatory | In force | Resolução CMN nº 4.893/2021 | Jul 1, 2021 | Official text — CMN Resolution 4.893 |
Who it bindsBrazilian financial institutions: a documented cybersecurity policy, an incident response plan, and prior notice to the central bank before contracting relevant cloud or data processing services abroad. | ||||||
| General Personal Data Protection LawLei Geral de Proteção de Dados Pessoais, Lei nº 13.709/2018Privacy & data protectionIncident reporting | Brazil | LawMandatory | In force | Lei nº 13.709/2018 | Sep 18, 2020 | Official text — LGPD |
Who it bindsAny processing of personal data carried out in Brazil, aimed at people in Brazil, or of data collected there — regardless of where the controller sits. ExposureUp to 2% of Brazilian turnover, capped at BRL 50 000 000 per infraction. Worth knowingANPD Resolution 15/2024 sets the security incident notification procedure and a three-working-day deadline. | ||||||
| Resilience of critical entitiesDirective (EU) 2022/2557 on the resilience of critical entitiesOperational resilienceSector-specific | European UnionCheck your scope | DirectiveMandatory | Phasing in | Directive (EU) 2022/2557 | Oct 18, 2024staged | Official text — CER Directive |
Who it bindsEntities identified by Member States as critical in 11 sectors. This is the physical-resilience twin of NIS2 — same sectors, non-cyber threats. TimetableTransposition was due 17 October 2024; Member States were to identify their critical entities by 17 July 2026. Worth knowingAn entity identified under CER is automatically an essential entity under NIS2. The reverse does not hold. | ||||||
| Horizontal cybersecurity requirements for products with digital elementsRegulation (EU) 2024/2847Product & IoT securityCybersecurityIncident reporting | European UnionCheck your scope | RegulationMandatory | Phasing in | (EU) 2024/2847 | Dec 11, 2027staged | Official text — Cyber Resilience Act |
Who it bindsAnyone placing a product with digital elements on the EU market — hardware and software alike, including remote data processing solutions. Manufacturers carry the weight; importers and distributors carry checks. TimetableIn force since 10 December 2024. Reporting of actively exploited vulnerabilities applies from 11 September 2026; conformity assessment body provisions from 11 June 2026; the full regime from 11 December 2027. ExposureUp to €15 000 000 or 2.5% of worldwide annual turnover for breach of the essential requirements. Worth knowingThe obligation that surprises people is the support period: security updates for the expected product lifetime, presumed to be at least five years. | ||||||
| European Digital Identity FrameworkRegulation (EU) 2024/1183 amending Regulation (EU) No 910/2014Privacy & data protectionCybersecurity | European UnionCheck your scope | RegulationMandatory | Phasing in | (EU) 2024/1183 | May 20, 2024staged | Official text — eIDAS 2 |
Who it bindsTrust service providers, Member States issuing wallets, and — on the acceptance side — very large online platforms, banks, telecoms and other regulated relying parties. TimetableMember States must offer at least one EU Digital Identity Wallet by the end of 2026; large online platforms and regulated sectors must accept it thereafter. | ||||||
| Artificial Intelligence ActRegulation (EU) 2024/1689 laying down harmonised rules on artificial intelligenceArtificial intelligenceProduct & IoT security | European UnionCheck your scope | RegulationMandatory | Phasing in | (EU) 2024/1689 | Aug 2, 2026staged | Official text — EU AI Act |
Who it bindsProviders, deployers, importers and distributors of AI systems placed on or used in the EU market, including providers established outside it whose output is used in the Union. TimetableIn force since 1 August 2024. Prohibited practices and AI literacy applied from 2 February 2025; general-purpose AI obligations from 2 August 2025; most high-risk obligations from 2 August 2026; Annex I embedded high-risk from 2 August 2027. ExposureUp to €35 000 000 or 7% of worldwide annual turnover for prohibited practices; €15 000 000 or 3% for most other breaches. Worth knowingA Commission simplification package has proposed deferring parts of the high-risk timetable. Check the current position before planning to a 2026 date. | ||||||
| Measures for a high common level of cybersecurity across the UnionDirective (EU) 2022/2555 on measures for a high common level of cybersecurity across the UnionCybersecurityIncident reportingOperational resilience | European UnionCheck your scope | DirectiveMandatory | Phasing in | Directive (EU) 2022/2555 | Oct 18, 2024staged | Official text — NIS2 |
Who it bindsMedium and large entities in 18 sectors (Annexes I and II), plus named entities of any size — DNS providers, TLD registries, trust service providers, public administration and sole providers of an essential service. TimetableTransposition was due 17 October 2024. National laws are still landing — Germany applied its act from January 2026, Czechia from November 2025, Poland from 2026; France and Spain have none in force. ExposureEssential entities: up to €10 000 000 or 2% of worldwide annual turnover. Important entities: up to €7 000 000 or 1.4%. Management bodies can be held personally liable. | ||||||
| Polish national cybersecurity system act, as amended for NIS2Ustawa o krajowym systemie cyberbezpieczeństwaCybersecurityIncident reporting | PolandCheck your scope | LawMandatory | Phasing in | Dz.U. 2026 poz. 252 | —staged | Official text — KSC (NIS2 amendment) |
Who it bindsKey and important entities established in Poland, replacing the earlier operator-of-essential-services designation model with self-identification and registration. TimetablePublished in the Journal of Laws as Dz.U. 2026 poz. 252, with a vacatio legis before the substantive duties bite and separate transition periods for registration and for the security measures. Registration deadlines run from the date an entity meets the criteria, not from a single national cut-off. | ||||||
| Cybersecurity Maturity Model Certification32 CFR Part 170 and DFARS 252.204-7021CybersecuritySector-specific | United States | Certification schemeMandatory | Phasing in | CMMC 2.0 (32 CFR Part 170) | Dec 16, 2024staged | Official text — CMMC |
Who it bindsThe defence industrial base — any contractor or subcontractor handling Federal Contract Information or Controlled Unclassified Information, including non-US suppliers. TimetableThe programme rule took effect in December 2024; the acquisition rule that puts the requirement into contracts followed in November 2025, starting a three-year phase-in. | ||||||
| California Consumer Privacy Act, as amendedCalifornia Civil Code § 1798.100 et seq.Privacy & data protectionCybersecurity | United States — California | LawMandatory | Phasing in | CCPA as amended by CPRA, plus the 2025 CPPA regulations | Jan 1, 2023staged | Official text — CCPA / CPRA |
Who it bindsFor-profit businesses meeting revenue or data-volume thresholds that handle personal information of California residents — including businesses with no California presence. TimetableThe 2025 regulations add cybersecurity audits, risk assessments and rules for automated decision-making technology, phasing in from 2027 through 2030. Worth knowingAround twenty other US states now have comprehensive privacy laws of their own; California is the one that has added a security audit obligation. | ||||||
| Australian Cyber Security ActCyber Security Act 2024 (Cth)CybersecurityIncident reportingProduct & IoT security | Australia | LawMandatory | Phasing in | Act No. 106 of 2024 | May 30, 2025staged | Official text — Cyber Security Act 2024 |
Who it bindsBusinesses with annual turnover above AUD 3 million must report a ransomware or cyber extortion payment within 72 hours. Separately, manufacturers and suppliers of internet-connectable consumer products must meet mandatory security standards. TimetableRansomware payment reporting began on 30 May 2025. Mandatory security standards for smart devices commenced in March 2025 for newly supplied products. Worth knowingIt also creates a limited-use protection: information given to the National Cyber Security Coordinator during an incident is restricted in how it may be used against the reporting entity. | ||||||
| Privacy Act and the Notifiable Data Breaches schemePrivacy Act 1988 (Cth)Privacy & data protectionIncident reporting | Australia | LawMandatory | Phasing in | As amended by the Privacy and Other Legislation Amendment Act 2024 | Jan 1, 1989staged | Official text — Privacy Act 1988 |
Who it bindsAustralian government agencies and organisations with turnover above AUD 3 million, plus smaller entities in health and credit. Eligible data breaches must be assessed within 30 days and notified to the OAIC and affected individuals. TimetableThe 2024 amendments phase in through 2026, including a statutory tort for serious invasions of privacy and transparency duties for automated decisions. ExposureUp to AUD 50 000 000, three times the benefit obtained, or 30% of adjusted turnover for the relevant period. | ||||||
| Digital Personal Data Protection ActThe Digital Personal Data Protection Act, 2023Privacy & data protectionIncident reporting | India | LawMandatory | Phasing in | Act No. 22 of 2023, with the 2025 Rules | Aug 11, 2023staged | Official text — DPDP Act |
Who it bindsAnyone processing digital personal data in India, and processing outside India connected with offering goods or services to people in India. TimetableThe Act was passed in 2023 but only became operable with the DPDP Rules notified in November 2025; the substantive obligations phase in over the following 18 months. ExposureUp to INR 250 crore for failure to take reasonable security safeguards. | ||||||
| Act on Active Cyber DefenceCybersecurityIncident reporting | Japan | LawMandatory | Phasing in | Enacted 2025 | May 16, 2025staged | Official text — Active Cyber Defence Law |
Who it bindsDesignated critical infrastructure operators, who gain reporting duties; and, on the state side, powers to monitor certain communications and neutralise attacker infrastructure. TimetableEnacted in May 2025 with provisions commencing in stages through 2027, including incident reporting duties on designated critical infrastructure operators. | ||||||
| European Health Data SpaceRegulation (EU) 2025/327Privacy & data protectionSector-specific | European UnionCheck your scope | RegulationMandatory | Adopted, not yet applicable | (EU) 2025/327 | Mar 26, 2029staged | Official text — EHDS |
Who it bindsHealthcare providers, EHR system manufacturers and wellness app vendors, plus health data holders and users on the secondary-use side. TimetableIn force since 26 March 2025, with the primary-use and secondary-use chapters applying in stages from 2029 through 2031. | ||||||
| Machinery, including cybersecurity of safety functionsRegulation (EU) 2023/1230Product & IoT securitySector-specific | European UnionCheck your scope | RegulationMandatory | Adopted, not yet applicable | (EU) 2023/1230 | Jan 20, 2027 | Official text — Machinery Regulation |
Who it bindsManufacturers of machinery and related products for the EU market. It replaces the Machinery Directive 2006/42/EC and, for the first time, treats corruption of safety-related control software as a safety requirement. | ||||||
| Cyber Incident Reporting for Critical Infrastructure ActCyber Incident Reporting for Critical Infrastructure Act of 2022Incident reporting | United States | LawMandatory | Adopted, not yet applicable | Pub. L. 117-103, Div. Y | Mar 15, 2022staged | Official text — CIRCIA |
Who it bindsCovered entities in the 16 critical infrastructure sectors. As drafted: substantial cyber incidents reported within 72 hours, ransom payments within 24. TimetableThe statute is in force but creates no duty until CISA’s implementing rule takes effect. The proposed rule was published in April 2024; the final rule has slipped repeatedly. | ||||||
| Spanish cybersecurity coordination and governance billAnteproyecto de Ley de Coordinación y Gobernanza de la CiberseguridadCybersecurity | Spain | LawMandatory | Proposed | Draft bill | — | Official text — Anteproyecto de Ley de Ciberseguridad |
Who it bindsWould transpose NIS2 in Spain. Real Decreto-ley 12/2018 (the NIS1 transposition) remains the operative law meanwhile. | ||||||
| French NIS2, CER and DORA transposition billProjet de loi relatif à la résilience des infrastructures critiques et au renforcement de la cybersécuritéCybersecurityOperational resilience | France | LawMandatory | Proposed | Bill, not enacted | — | Official text — Projet de loi résilience |
Who it bindsWould cover French essential and important entities. Until it passes, France has no NIS2 law in force and the directive is not directly effective against private entities. Worth knowingThis is why the scope check assesses France against the EU baseline and says so, rather than inventing French rules. | ||||||
| UK Cyber Security and Resilience BillCybersecurityIncident reporting | United Kingdom | LawMandatory | Proposed | Bill before Parliament | — | Official text — Cyber Security and Resilience Bill |
Who it bindsWould extend the NIS Regulations to managed service providers, widen incident reporting and give regulators cost-recovery powers. | ||||||
| Critical Cyber Systems Protection ActCybersecurityIncident reporting | Canada | LawMandatory | Proposed | Bill before Parliament | — | Official text — CCSPA (Bill C-8) |
Who it bindsWould bind designated operators in federally regulated finance, telecommunications, energy and transport, with a 72-hour incident reporting duty to the Cyber Centre. Worth knowingA predecessor bill died when Parliament was prorogued in January 2025; this is the reintroduction. | ||||||
| Security of network and information systems (superseded)Directive (EU) 2016/1148Cybersecurity | European UnionCheck your scope | DirectiveMandatory | Repealed | Directive (EU) 2016/1148 | — | Official text — NIS Directive |
Who it bindsRepealed by NIS2 with effect from 18 October 2024. Listed because national laws made under it — and audit findings citing it — are still in circulation. | ||||||
This information may be out of date or inaccurate. Check the official text before relying on it in production use.
How this works
- 1A rules engine, not a score. Each rule is a condition over your answers, an effect, and a citation. Nothing is weighted invisibly.
- 2Missing data weakens a negative, never a positive. If we cannot tell, we say so rather than reporting that you are out of scope.
- 3Your answers stay in your browser. The assessment runs client-side; nothing is sent anywhere unless you choose to.
Jurisdictions
We publish a jurisdiction only once its primary instruments are identified. Countries below that bar are still selectable in the tool, but you are told plainly that you were assessed against the EU baseline.
- European Union (NIS2 baseline)ENISAModelled
- UkraineАдміністрація Держспецзв’язкуModelled
- GermanyBundesamt für Sicherheit in der Informationstechnik (BSI)Modelled
- ItalyAgenzia per la cybersicurezza nazionale (ACN)Modelled
- PolandMinisterstwo Cyfryzacji (rejestr); sektorowe organy właściwe (nadzór)Modelled
- CzechiaNárodní úřad pro kybernetickou a informační bezpečnost (NÚKIB)Modelled
- EstoniaRiigi Infosüsteemi Amet (RIA)Modelled
- FranceAgence nationale de la sécurité des systèmes d’information (ANSSI)EU baseline only
- SpainDepartamento de Seguridad Nacional (DSN) — punto de contacto único; autoridades sectoriales (RD 43/2021 art. 3)EU baseline only
- NorwayNasjonal sikkerhetsmyndighet (NSM) — nasjonalt kontaktpunkt; sektorvise tilsynsmyndigheterEU baseline only
On the legal content
Citations were retrieved from official sources — EUR-Lex for EU law, the Verkhovna Rada portal for Ukrainian acts — on the date shown with each one. The content has not yet been through legal review, and the tool says so wherever it matters.