Nacionālās kiberdrošības likums (Latvia)

Requirement

34.(1): Incidentu novēršana un informēšana

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

Konstatējot kiberincidentu, subjekts nekavējoties veic visas kiberincidenta novēršanai nepieciešamās darbības, kā arī nekavējoties par kiberincidentu informē kompetento kiberincidentu novēršanas institūciju un izpilda tās sniegtos norādījumus par rīcību kiberincidenta gadījumā. Informācijas un komunikācijas tehnoloģiju kritiskās infrastruktūras īpašnieks vai tiesiskais valdītājs kiberincidenta gadījumā nekavējoties par to informē arī kompetento valsts drošības iestādi. Ministru kabinets nosaka kārtību informēšanai par kiberincidentu un to kiberincidentu kritērijus, informācija par kuriem ir sniedzama kompetentajai kiberincidentu novēršanas institūcijai.

Fulfill this requirement by completing the tasks below ->

This requirement is part of the framework:

Nacionālās kiberdrošības likums (Latvia)

Other requirements of the framework

34.(1): Incidentu novēršana un informēšana

Best practices

How to implement:

34.(1): Incidentu novēršana un informēšana

This policy on

34.(1): Incidentu novēršana un informēšana

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.

Konstatējot kiberincidentu, subjekts nekavējoties veic visas kiberincidenta novēršanai nepieciešamās darbības, kā arī nekavējoties par kiberincidentu informē kompetento kiberincidentu novēršanas institūciju un izpilda tās sniegtos norādījumus par rīcību kiberincidenta gadījumā. Informācijas un komunikācijas tehnoloģiju kritiskās infrastruktūras īpašnieks vai tiesiskais valdītājs kiberincidenta gadījumā nekavējoties par to informē arī kompetento valsts drošības iestādi. Ministru kabinets nosaka kārtību informēšanai par kiberincidentu un to kiberincidentu kritērijus, informācija par kuriem ir sniedzama kompetentajai kiberincidentu novēršanas institūcijai.

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

34.(1): Incidentu novēršana un informēšana

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

34.(1): Incidentu novēršana un informēšana

of the framework

Nacionālās kiberdrošības likums (Latvia)

Task name

Priority

Task completes

Complete these tasks to increase your compliance in this policy.

Critical

The step-by-step process of notification of incidents to the authorities

Critical

High

Normal

Low

Incident management

Incident management and response

The step-by-step process of notification of incidents to the authorities

This task helps you comply with the following requirements

Članak 37: Obavještavanje o značajnim incidentima NIS2 Croatia

12 §: Poikkeamaa koskeva väliraportti Kyberturvallisuuslaki

13 §: Poikkeamaa koskeva loppuraportti Kyberturvallisuuslaki

11 §: Poikkeamailmoitukset viranomaiselle Kyberturvallisuuslaki

35 § 1°: Processus de notification des incidents au CSIRT NIS2 Belgium

Initial treatment of identified technical vulnerabilities

Critical

High

Normal

Low

Development and cloud

Technical vulnerability management

Initial treatment of identified technical vulnerabilities

This task helps you comply with the following requirements

12.6.1: Management of technical vulnerabilities ISO 27001

ID.RA-1: Asset vulnerabilities NIST

PR.IP-12: Vulnerability management plan NIST

RS.AN-5: Vulnerability management process NIST

RS.MI-3: New vulnerability mitigation NIST

Keeping contact with relevant authorities

Critical

High

Normal

Low

Partner management

Agreements and monitoring

Keeping contact with relevant authorities

This task helps you comply with the following requirements

Članak 37: Obavještavanje o značajnim incidentima NIS2 Croatia

11 §: Poikkeamailmoitukset viranomaiselle Kyberturvallisuuslaki

1.2.2: Information Security Responsibilities TISAX

34 § 1°: Notifications d'incidents au CSIRT et aux bénéficiaires des services NIS2 Belgium

RC.CO-1: Public relations are managed.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