TiHL: Suositus tietoturvan vähimmäisvaatimuksista

Requirement

2.5: Riskienhallinta

Oh no! No description found. But not to worry. Read from Tasks below how to advance this topic.

Tiedonhallintayksiköiden on selvitettävä olennaiset tietoturvallisuuteen kohdistuvat riskit ja mitoitettava tietoturvallisuustoimenpiteet riskiarvioinnin mukaisesti. Lisäksi organisaatioita suositellaan käyttämään dokumentoitua riskienhallinnan menetelmää ja ohjeistamaan sen soveltaminen tietoturvallisuusriskien hallinnassa.

Fulfill this requirement by completing the tasks below ->

This requirement is part of the framework:

TiHL: Suositus tietoturvan vähimmäisvaatimuksista

Other requirements of the framework

2.5: Riskienhallinta

Best practices

How to implement:

2.5: Riskienhallinta

This policy on

2.5: Riskienhallinta

provides a set concrete tasks you can complete to secure this topic. Follow these best practices to ensure compliance and strengthen your overall security posture.

Read below what concrete actions you can take to improve this ->

Frameworks that include requirements for this topic:

No items found.

How to improve security around this topic

In Cyberday, requirements and controls are mapped to universal tasks. A set of tasks in the same topic create a Policy, such as this one.

Here's a list of tasks that help you improve your information and cyber security related to

2.5: Riskienhallinta

Task name

Priority

Task completes

Complete these tasks to increase your compliance in this policy.

Critical

No other tasks found.

Complete these tasks in Cyberday ISMS ->

How to comply with this requirement

In Cyberday, requirements and controls are mapped to universal tasks. Each requirement is fulfilled with one or multiple tasks.

Here's a list of tasks that help you comply with the requirement

2.5: Riskienhallinta

of the framework

TiHL: Suositus tietoturvan vähimmäisvaatimuksista

Task name

Priority

Task completes

Complete these tasks to increase your compliance in this policy.

Critical

Data system listing and owner assignment

Critical

High

Normal

Low

System management

Data system management

Data system listing and owner assignment

This task helps you comply with the following requirements

Članak 30.1.i (Imovina): Upravljanja programskom i sklopovskom imovinom NIS2 Croatia

4.1: Tietojärjestelmien tietoturvallisuus TiHL tietoturvavaatimukset

2.5: Riskienhallinta TiHL tietoturvavaatimukset

9.5 §: Suojattavan omaisuuden hallinta Kyberturvallisuuslaki

1.3.1: Identification of information assets TISAX

Identification and documentation of cyber security risks

Critical

High

Normal

Low

Risk management and leadership

Risk management

Identification and documentation of cyber security risks

This task helps you comply with the following requirements

Č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

Risk management procedure -report publishing and maintenance

Critical

High

Normal

Low

Risk management and leadership

Risk management

Risk management procedure -report publishing and maintenance

This task helps you comply with the following requirements

Č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

Documentation of data sets for data stores

Critical

High

Normal

Low

Management of data sets

Documentation of data sets for data stores

This task helps you comply with the following requirements

Članak 30.1.i (Imovina): Upravljanja programskom i sklopovskom imovinom NIS2 Croatia

2.4: Luokittelu ja turvallisuusluokittelu TiHL tietoturvavaatimukset

3.1: Tietoaineistojen tietoturvallisuus TiHL tietoturvavaatimukset

2.5: Riskienhallinta TiHL tietoturvavaatimukset

9.5 §: Suojattavan omaisuuden hallinta Kyberturvallisuuslaki

Enabling asset-based risk management in the ISMS

Critical

High

Normal

Low

Risk management and leadership

Risk management

Enabling asset-based risk management in the ISMS

This task helps you comply with the following requirements

Article 8: Identification DORA

2.5: Riskienhallinta TiHL tietoturvavaatimukset

5.2.2: Seperation of testing and development environments TISAX

1.1.3: Identify the organisation’s processes for ICT risk management NSM ICT-SP

Article 31: ICT risk management DORA simplified RMF

Assessment of the impact and likelihood of the risks and the scales used

Critical

High

Normal

Low

Risk management and leadership

Risk management

Assessment of the impact and likelihood of the risks and the scales used

This task helps you comply with the following requirements

ID.RA-4: Impacts on business NIST

Article 6: ICT risk management framework DORA

2.5: Riskienhallinta TiHL tietoturvavaatimukset

1.4.1: Management of Information Security Risks TISAX

ID.RA-04: Impacts and likelihoods of threats NIST 2.0

Monitoring the status of risk management

Critical

High

Normal

Low

Risk management and leadership

Risk management

Monitoring the status of risk management

This task helps you comply with the following requirements

14.5.2): Aukščiausiosios vadovybės atsakomybė NIS2 Lithuania

19: Riskienhallinan tilanteen seuraaminen Digiturvan kokonaiskuvapalvelu

CC5.1: Control activities for mitigation of risks SOC 2

Article 6: ICT risk management framework DORA

2.5: Riskienhallinta TiHL tietoturvavaatimukset

Assessment of residual risks

Critical

High

Normal

Low

Risk management and leadership

Risk management

Assessment of residual risks

This task helps you comply with the following requirements

Č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

Complete these tasks in Cyberday ISMS ->

The ISMS component hierachy

When building an ISMS, it's important to understand the different levels of information hierarchy. Here's how Cyberday is structured.

Framework

Sets the overall compliance standard or regulation your organization needs to follow.

Requirements

Break down the framework into specific obligations that must be met.

Tasks

Concrete actions and activities your team carries out to satisfy each requirement.

Policies

Documented rules and practices that are created and maintained as a result of completing tasks.

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.

Start free trial