Laki yhteiskunnan kriittisen infrastruktuurin suojaamisesta ja häiriönsietokyvyn parantamisesta (Suomi)

Requirement

15 §.(2).3: Poikkeamiin vastaaminen ja niiden lieventäminen

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

Kriittisen toimijan on toteutettava häiriönsietokykynsä varmistamiseksi asianmukaisia ja oikeasuhteisia teknisiä, turvallisuuteen liittyviä ja organisatorisia toimenpiteitä, jotka perustuvat 14 §:ssä tarkoitettuun riskiarviontiin ja muihin asiaan kuuluviin tietoihin. Tässä tarkoituksessa kriittisen toimijan on laadittava asianmukaisia ja oikeasuhtaisia teknisiä, turvallisuuteen liittyviä ja organisatorisia toimenpiteitä sisältävä suunnitelma häiriönsietokyvyn varmistamiseksi.

Suunnitelmassa on oltava selostus toimenpiteistä poikkeamien seurauksiin ja häiriötilanteisiin vastaamiseksi, torjumiseksi ja lieventämiseksi.

See how Cyberday guides you to fulfill this requirement:

Start free trial

This requirement is part of the framework:

Laki yhteiskunnan kriittisen infrastruktuurin suojaamisesta ja häiriönsietokyvyn parantamisesta (Suomi)

Other requirements of the framework

15 §.(2).3: Poikkeamiin vastaaminen ja niiden lieventäminen

Best practices

How to implement:

15 §.(2).3: Poikkeamiin vastaaminen ja niiden lieventäminen

This policy on

15 §.(2).3: Poikkeamiin vastaaminen ja niiden lieventäminen

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.

Kriittisen toimijan on toteutettava häiriönsietokykynsä varmistamiseksi asianmukaisia ja oikeasuhteisia teknisiä, turvallisuuteen liittyviä ja organisatorisia toimenpiteitä, jotka perustuvat 14 §:ssä tarkoitettuun riskiarviontiin ja muihin asiaan kuuluviin tietoihin. Tässä tarkoituksessa kriittisen toimijan on laadittava asianmukaisia ja oikeasuhtaisia teknisiä, turvallisuuteen liittyviä ja organisatorisia toimenpiteitä sisältävä suunnitelma häiriönsietokyvyn varmistamiseksi.

Suunnitelmassa on oltava selostus toimenpiteistä poikkeamien seurauksiin ja häiriötilanteisiin vastaamiseksi, torjumiseksi ja lieventämiseksi.

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

15 §.(2).3: Poikkeamiin vastaaminen ja niiden lieventäminen

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

15 §.(2).3: Poikkeamiin vastaaminen ja niiden lieventäminen

of the framework

Laki yhteiskunnan kriittisen infrastruktuurin suojaamisesta ja häiriönsietokyvyn parantamisesta (Suomi)

Task name

Priority

Task completes

Complete these tasks to increase your compliance in this policy.

Critical

Regular testing, evaluation, and recovery instructions for backups

Critical

High

Normal

Low

Technical cyber security

Backups

Regular testing, evaluation, and recovery instructions for backups

Članak 30.1.c: Kontinuitet poslovanja NIS2 Croatia

9.10 §: Varmuuskopiointi ja jatkuvuuden hallinta Kyberturvallisuuslaki

5.2.9: Backup and recovery management TISAX

30 § 3.3°: La continuité et la gestion des crises NIS2 Belgium

2.9.3: Test backups regularly NSM ICT-SP

Personnel guidelines for reporting security incidents

Critical

High

Normal

Low

Incident management

Incident management and response

Personnel guidelines for reporting security incidents

Članak 30.1.b: Postupanje s incidentima, uključujući njihovo praćenje, evidentiranje i prijavljivanje NIS2 Croatia

2.2(1): Ansvar for den behandlingsansvarlige Norm for informasjonssikkerhet

9.9a §: Poikkeamien havainnointi Kyberturvallisuuslaki

1.6.1: Reporting of security events TISAX

1.3.2: Classification of information assets TISAX

Treatment process and documentation of occurred security incidents

Critical

High

Normal

Low

Incident management

Incident management and response

Treatment process and documentation of occurred security incidents

Članak 30.1.b: Postupanje s incidentima, uključujući njihovo praćenje, evidentiranje i prijavljivanje NIS2 Croatia

9.9b §: Poikkeamien käsittely Kyberturvallisuuslaki

1.6.2: Management of reported events TISAX

30 § 3.2° (incidents): La gestion des incidents NIS2 Belgium

4.4.2: Review identified compromised security measures NSM ICT-SP

Including suppliers in incident management

Critical

High

Normal

Low

Incident management

Incident management and response

Including suppliers in incident management

GV.SC-08: Including relevant suppliers and third parties in incident activities NIST 2.0

ID.IM-02: Improvements from security tests and exercises NIST 2.0

13.1.c: Responding to incidents CER

§ 8: Rapporteringskrav för leverantörer MSBFS 2020:8

§ 14.3: Incidenthantering och respons NIS2 Åland

Internal communication in an incident situation

Critical

High

Normal

Low

Incident management

Incident management and response

Internal communication in an incident situation

1.6.1: Reporting of security events TISAX

DE.AE-06: Information on adverse events NIST 2.0

RS.CO-02: Notifying stakeholders of incidents NIST 2.0

RS.CO-03: Sharing Information with stakeholders NIST 2.0

17.2: Establish and Maintain Contact Information for Reporting Security Incidents CIS 18

The first level response process to security incidents

Critical

High

Normal

Low

Incident management

Incident management and response

The first level response process to security incidents

Članak 30.1.b: Postupanje s incidentima, uključujući njihovo praćenje, evidentiranje i prijavljivanje NIS2 Croatia

9.9b §: Poikkeamien käsittely Kyberturvallisuuslaki

1.6.2: Management of reported events TISAX

30 § 3.2° (incidents): La gestion des incidents NIS2 Belgium

4.2.1: Review log data and collect relevant data on the incident to create a good basis for making decisions NSM ICT-SP

Incident containing measures

Critical

High

Normal

Low

Incident management

Incident management and response

Incident containing measures

RS.MI-1: Incident containment NIST

Article 17: ICT-related incident management process DORA

RS.MI-1: Incidents are contained.CyberFundamentals

4.3.2: Determine whether the incident is under control and take the necessary reactive measures NSM ICT-SP

RS.MI-01: Incident containment NIST 2.0

Establishing a crisis management team and process

Critical

High

Normal

Low

Risk management and leadership

Continuity management

Establishing a crisis management team and process

1.6.3: Crisis preparedness TISAX

4.3.2: Determine whether the incident is under control and take the necessary reactive measures NSM ICT-SP

RC.RP-02: Recovery actions NIST 2.0

15.2.γ: Επιχειρησιακή συνέχεια και αντίγραφα ασφαλείας NIS2 Greece

§ 30.(2).3: Aufrechterhaltung des Betriebs NIS2 Germany

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