Cybersecurity risk-management measures
Compared across 6 jurisdictions
In European Union (NIS2 baseline)
Implement the ten cybersecurity risk-management measures
Appropriate and proportionate technical, operational and organisational measures on an all-hazards basis, including at least: risk analysis and information system security policies; incident handling; business continuity including backup management, disaster recovery and crisis management; supply chain security covering direct suppliers and service providers; security in acquisition, development and maintenance including vulnerability handling and disclosure; policies to assess the effectiveness of the measures; basic cyber hygiene and cybersecurity training; cryptography and, where appropriate, encryption; human resources security, access control and asset management; and multi-factor or continuous authentication, secured voice, video and text communications and secured emergency communications where appropriate.
When: Ongoing. Where an entity finds it does not comply, it must take corrective measures without undue delay. Proportionality is judged on exposure to risk, the entity size, and the likelihood and severity of incidents.
What evidence looks like
- An approved information security policy set covering all ten measures
- An incident response plan that has been exercised, with the exercise record
- Tested backups with a documented recovery time
- A supplier register with security assessments of direct suppliers
- Evidence of multi-factor authentication coverage
In Germany
Implement the ten cybersecurity risk-management measures
Appropriate and proportionate technical, operational and organisational measures on an all-hazards basis, including at least: risk analysis and information system security policies; incident handling; business continuity including backup management, disaster recovery and crisis management; supply chain security covering direct suppliers and service providers; security in acquisition, development and maintenance including vulnerability handling and disclosure; policies to assess the effectiveness of the measures; basic cyber hygiene and cybersecurity training; cryptography and, where appropriate, encryption; human resources security, access control and asset management; and multi-factor or continuous authentication, secured voice, video and text communications and secured emergency communications where appropriate.
When: Ongoing. Where an entity finds it does not comply, it must take corrective measures without undue delay. Proportionality is judged on exposure to risk, the entity size, and the likelihood and severity of incidents.
What evidence looks like
- An approved information security policy set covering all ten measures
- An incident response plan that has been exercised, with the exercise record
- Tested backups with a documented recovery time
- A supplier register with security assessments of direct suppliers
- Evidence of multi-factor authentication coverage
In Poland
Implement the ten cybersecurity risk-management measures
Appropriate and proportionate technical, operational and organisational measures on an all-hazards basis, including at least: risk analysis and information system security policies; incident handling; business continuity including backup management, disaster recovery and crisis management; supply chain security covering direct suppliers and service providers; security in acquisition, development and maintenance including vulnerability handling and disclosure; policies to assess the effectiveness of the measures; basic cyber hygiene and cybersecurity training; cryptography and, where appropriate, encryption; human resources security, access control and asset management; and multi-factor or continuous authentication, secured voice, video and text communications and secured emergency communications where appropriate.
When: Ongoing. Where an entity finds it does not comply, it must take corrective measures without undue delay. Proportionality is judged on exposure to risk, the entity size, and the likelihood and severity of incidents.
What evidence looks like
- An approved information security policy set covering all ten measures
- An incident response plan that has been exercised, with the exercise record
- Tested backups with a documented recovery time
- A supplier register with security assessments of direct suppliers
- Evidence of multi-factor authentication coverage
In Czechia
Implement the higher-regime measures and perform a risk analysis
Fourteen organisational measures — an ISMS; top-management duties; security roles; policy and documentation; asset management; risk management; supplier management; human resources security; change management; acquisition, development and maintenance; access control; handling cybersecurity events and incidents; business continuity; and a cybersecurity audit — and eleven technical measures: physical security; network security; identity administration and verification; access-rights management; detection; logging; evaluation of events; application security; cryptographic algorithms; availability assurance; and security of industrial and control assets. You must perform a risk analysis and map the measures to the risks. Where a measure cannot be implemented in time, justify it and produce a plan.
When: The duty begins at the latest one year from delivery of the registration decision.
What evidence looks like
- The risk analysis, with the mapping from measures to risks
- The ISMS documentation set covering all 14 organisational measures
- For any measure not yet implemented, the justification and the plan
- Logging and detection coverage across the stanovený rozsah
Implement the lower-regime measures — no risk analysis required
Thirteen combined measures. You need NOT perform a risk analysis; instead a fixed set of measures is non-derogable — vyhl. 410/2025 § 3(1)(b) names §§ 3(2) to (6), 4 to 6 and 10 — and the rest operate on a comply-or-explain basis recorded in the register of security measures. The lighter regime is a different structure, not a discount: what replaces the risk analysis is a documented, reasoned account of every measure you have not implemented.
When: The duty begins at the latest one year from delivery of the registration decision.
What evidence looks like
- Evidence of the non-derogable measures being in place
- The register of security measures with reasons for each omission
In Estonia
Implement the ten cybersecurity risk-management measures
Appropriate and proportionate technical, operational and organisational measures on an all-hazards basis, including at least: risk analysis and information system security policies; incident handling; business continuity including backup management, disaster recovery and crisis management; supply chain security covering direct suppliers and service providers; security in acquisition, development and maintenance including vulnerability handling and disclosure; policies to assess the effectiveness of the measures; basic cyber hygiene and cybersecurity training; cryptography and, where appropriate, encryption; human resources security, access control and asset management; and multi-factor or continuous authentication, secured voice, video and text communications and secured emergency communications where appropriate.
When: Ongoing. Where an entity finds it does not comply, it must take corrective measures without undue delay. Proportionality is judged on exposure to risk, the entity size, and the likelihood and severity of incidents.
What evidence looks like
- An approved information security policy set covering all ten measures
- An incident response plan that has been exercised, with the exercise record
- Tested backups with a documented recovery time
- A supplier register with security assessments of direct suppliers
- Evidence of multi-factor authentication coverage
In Italy
Implement the risk-management measures, to the specification ACN sets
Art. 24 requires appropriate and proportionate technical, operational and organisational measures on a multi-risk basis, at least: risk-analysis and information-system security policies; incident handling including the procedures and tools for the arts. 25 and 26 notifications; business continuity with backup management, disaster recovery where applicable and crisis management; supply chain security covering the security aspects of each entity’s relationships with its direct suppliers and service providers; and security in acquisition, development and maintenance. What art. 24 does not do is tell you the level: art. 31 empowers ACN to set proportionate obligations and graduated implementation timetables, differentiated by relevance category, by sector and entity type, and by whether you are essential or important — through determinazioni under art. 40(5) that this pack has not read.
When: Eighteen months from the ACN communication, on the same art. 42(1)(c) clock as the governance duties. ACN may also suspend that clock in cases it identifies under art. 31(3).
This attaches when
- A public administration listed in allegato III, regardless of size
- An allegato IV entity type, once identified under art. 3(13)
- Already an operator of essential services under d.lgs. 65/2018
What evidence looks like
- The risk analysis and the information-system security policies it drives
- An incident procedure that can actually produce the arts. 25 and 26 notifications
- Tested backups and a disaster-recovery plan, with the test dates
- A supplier register covering direct suppliers and service providers