Content library
NIS2 Directive
21.2.a: Risk management and information system security

Requirement description

The measures referred to in paragraph 1 shall be based on an all-hazards approach that aims to protect network and information systems and the physical environment of those systems from incidents, and shall include measures for maintaining policies on risk analysis and information system security.

How to fill the requirement

NIS2 Directive

21.2.a: Risk management and information system security

Task name
Priority
Status
Theme
Policy
Other requirements
Identification and documentation of cyber security risks
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Risk management and leadership
Risk management
43
requirements

Examples of other requirements this task affects

Članak 30.1.a: Politike analize rizika i sigurnosti informacijskih sustava
NIS2 Croatia
2.5: Riskienhallinta
TiHL tietoturvavaatimukset
7 §: Riskienhallinta
Kyberturvallisuuslaki
1.4.1: Management of Information Security Risks
TISAX
13 §: Tietoaineistojen ja tietojärjestelmien tietoturvallisuus
TiHL
See all related requirements and other information from tasks own page.
Go to >
Identification and documentation of cyber security risks
1. Task description

The organization proactively seeks to list and assess the likelihood and severity of various cyber security risks. The documentation shall include the following:

  • Description of the risk
  • Evaluated impact and likelihood of the risk
  • Tasks for managing the risk or other treatment options
  • Acceptability of the risk
Risk management procedure -report publishing and maintenance
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Risk management and leadership
Risk management
44
requirements

Examples of other requirements this task affects

Članak 30.1.a: Politike analize rizika i sigurnosti informacijskih sustava
NIS2 Croatia
2.5: Riskienhallinta
TiHL tietoturvavaatimukset
8 §: Kyberturvallisuutta koskeva riskienhallinnan toimintamalli
Kyberturvallisuuslaki
1.4.1: Management of Information Security Risks
TISAX
30 § 1°: Gestion des risques et maîtrise des incidents
NIS2 Belgium
See all related requirements and other information from tasks own page.
Go to >
Risk management procedure -report publishing and maintenance
1. Task description

The organization has defined procedures for assessing and treating cyber security risks. The definition includes at least:

  • Risk identification methods
  • Methods for risk analysis
  • Criteria for risk evaluation (impact and likelihood)
  • Risk priorisation, treatment options and defining control tasks
  • Risk acceptance criteria
  • Process implementation cycle, resourcing and responsibilities
  • The results should be included into the organization risk management process

The task owner regularly checks that the procedure is clear and produces consistent results.

Documentation of linked risks for identified security incidents
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Risk management and leadership
Risk management
15
requirements

Examples of other requirements this task affects

Članak 30.1.a: Politike analize rizika i sigurnosti informacijskih sustava
NIS2 Croatia
7 §: Riskienhallinta
Kyberturvallisuuslaki
30 § 3.1°: L'analyse des risques et à la sécurité des systèmes d'information
NIS2 Belgium
4.4.1: Identify experiences and lessons learnt from incidents
NSM ICT-SP
4.3.1: Identify extent and impact on business processes
NSM ICT-SP
See all related requirements and other information from tasks own page.
Go to >
Documentation of linked risks for identified security incidents
1. Task description

Organization assesses cyber security risks by responding to situations where security has been mildly or severely compromised. The documentation shall include at least the following:

  • Description of the incident
  • Risks associated with the incident
  • New tasks introduced as a result of the incident
  • Other measures taken due to the incident
Evaluation process and documentation of significant security-related changes
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Risk management and leadership
Risk management
35
requirements

Examples of other requirements this task affects

Članak 30.1.a: Politike analize rizika i sigurnosti informacijskih sustava
NIS2 Croatia
7 §: Riskienhallinta
Kyberturvallisuuslaki
5.2.1: Change management
TISAX
30 § 3.1°: L'analyse des risques et à la sécurité des systèmes d'information
NIS2 Belgium
2.10.1: Include security in the organisation’s change management process
NSM ICT-SP
See all related requirements and other information from tasks own page.
Go to >
Evaluation process and documentation of significant security-related changes
1. Task description

In systematic cyber security work, the impact of significant changes must be assessed in advance and they must be executed in a controlled way. The consequences of unintentional changes must be assessed and efforts made to mitigate possible adverse effects.

Significant changes may include: changes in the organization, operating environment, business processes and data systems. Changes can be identified e.g. through management reviews and other cyber security work.

Risk level accepted by the organization
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Risk management and leadership
Risk management
20
requirements

Examples of other requirements this task affects

Članak 30.1.a: Politike analize rizika i sigurnosti informacijskih sustava
NIS2 Croatia
8 §: Kyberturvallisuutta koskeva riskienhallinnan toimintamalli
Kyberturvallisuuslaki
30 § 3.1°: L'analyse des risques et à la sécurité des systèmes d'information
NIS2 Belgium
1.1.4: Identify the organisation’s tolerances for ICT risk
NSM ICT-SP
1.1.2: Identify the organisation’s structures and processes for security management
NSM ICT-SP
See all related requirements and other information from tasks own page.
Go to >
Risk level accepted by the organization
1. Task description

The organization must determine an acceptable level for risks. The level is calculated based on the likelihood, impact and control of the risks.

Assessment of residual risks
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Risk management and leadership
Risk management
12
requirements

Examples of other requirements this task affects

Članak 30.1.a: Politike analize rizika i sigurnosti informacijskih sustava
NIS2 Croatia
2.5: Riskienhallinta
TiHL tietoturvavaatimukset
7 §: Riskienhallinta
Kyberturvallisuuslaki
30 § 3.1°: L'analyse des risques et à la sécurité des systèmes d'information
NIS2 Belgium
ID.GV-4: Governance and risk management processes address cybersecurity risks.
CyberFundamentals
See all related requirements and other information from tasks own page.
Go to >
Assessment of residual risks
1. Task description

After risk treatment, the organization assesses the remaining level of residual risk per risk.

Regarding the residual risk, clear decisions are made by the risk owner to either close the risk or return the risk to the processing queue.

Continuous improvement of the risk management process
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Risk management and leadership
Risk management
13
requirements

Examples of other requirements this task affects

Članak 30.1.a: Politike analize rizika i sigurnosti informacijskih sustava
NIS2 Croatia
8 §: Kyberturvallisuutta koskeva riskienhallinnan toimintamalli
Kyberturvallisuuslaki
1.4.1: Management of Information Security Risks
TISAX
30 § 3.1°: L'analyse des risques et à la sécurité des systèmes d'information
NIS2 Belgium
ID.GV-4: Governance and risk management processes address cybersecurity risks.
CyberFundamentals
See all related requirements and other information from tasks own page.
Go to >
Continuous improvement of the risk management process
1. Task description

The organization has an operating model for continuously improving the functionality and efficiency of the risk management process.

In the improvement, it is possible to use e.g. general standards (e.g. ISO 27005) or feedback from people involved in risk management.

Tasks included in the policy

Task name
Priority
Status
Theme
Policy
Other requirements
No items found.

Never duplicate effort. Do it once - improve compliance across frameworks.

Reach multi-framework compliance in the simplest possible way
Security frameworks tend to share the same core requirements - like risk management, backup, malware, personnel awareness or access management.
Cyberday maps all frameworks’ requirements into shared tasks - one single plan that improves all frameworks’ compliance.
Do it once - we automatically apply it to all current and future frameworks.
Get to know Cyberday
Start your free trial
Cyberday is your all-in-one solution for building a secure and compliant organization. Whether you're setting up a cyber security plan, evaluating policies, implementing tasks, or generating automated reports, Cyberday simplifies the entire process.
With AI-driven insights and a user-friendly interface, it's easier than ever to stay ahead of compliance requirements and focus on continuous improvement.
Clear framework compliance plans
Activate relevant frameworks and turn them into actionable policies tailored to your needs.
Credible reports to proof your compliance
Use guided tasks to ensure secure implementations and create professional reports with just a few clicks.
AI-powered improvement suggestions
Focus on the most impactful improvements in your compliance with help from Cyberday AI.