Content library
Nacionālās kiberdrošības likums (Latvia)
39: Koordinēta ievainojamību atklāšana

Requirement description

(1) Ja persona subjekta informācijas sistēmā vai elektronisko sakaru tīklā konstatē ievainojamību, tā nekavējoties, bet ne vēlāk kā piecu darbdienu laikā iesniedz ievainojamības atklāšanas ziņojumu kompetentajai kiberincidentu novēršanas institūcijai.
(2) Ievainojamības atklāšanas ziņojumā iekļauj šādu informāciju:
- Ievainojamības konstatēšanas datumu un laiku (ja iespējams);
- Ziņas par informācijas sistēmu vai elektronisko sakaru tīklu, kurā konstatēta ievainojamība;
- Ievainojamības aprakstu;
- Ievainojamības konstatēšanai izmantotās metodoloģijas vai veikto darbību secības aprakstu;
- Ievainojamības atklāšanas ziņojuma iesniedzēja kontaktinformāciju;
- Citas ziņas, ko ievainojamības atklāšanas ziņojuma iesniedzējs uzskata par nepieciešamām konstatētās ievainojamības identificēšanai un novēršanai.

How to fill the requirement

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

39: Koordinēta ievainojamību atklāšana

Task name
Priority
Status
Theme
Policy
Other requirements
Standards for submitting vulnerability reports
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Development and cloud
Technical vulnerability management
1
requirements

Examples of other requirements this task affects

39: Koordinēta ievainojamību atklāšana
NIS2 Latvia
See all related requirements and other information from tasks own page.
Go to >
Standards for submitting vulnerability reports
1. Task description

The organization should have documented processes and templates for reporting detected vulnerabilities.

The vulnerability detection reports should be submitted immediately to the competent cyber incident prevention institution, and no longer than five days after detecting the vulnerability.

The detection report should include the following information:

  • Date and time of detection of vulnerability (if possible);
  • Information about the information system or electronic communication network in which a vulnerability has been detected;
  • A description of the vulnerability;
  • A description of the methodology used to detect the vulnerability or the sequence of actions performed;
  • Contact information of the vulnerability disclosure report submitter;
  • Other information that the submitter of the vulnerability detection report considers necessary for the identification and prevention of the identified vulnerability.
Defining metrics related to vulnerability management
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Development and cloud
Technical vulnerability management
4
requirements

Examples of other requirements this task affects

39: Koordinēta ievainojamību atklāšana
NIS2 Latvia
16.2: Establish and Maintain a Process to Accept and Address Software Vulnerabilities
CIS 18
See all related requirements and other information from tasks own page.
Go to >
Defining metrics related to vulnerability management
1. Task description

The organization needs to define Monitored Metrics for identifying and correcting vulnerabilities. Meters must be monitored at specified intervals.

Detection process testing and compliance
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Incident management
Incident management and response
5
requirements

Examples of other requirements this task affects

DE.DP-2: Detection activities
NIST
TEK-13: Poikkeamien havainnointikyky ja toipuminen
Julkri
CC7.2: Monitoring of system components for anomalies
SOC 2
DE.DP-2: Detection activities comply with all applicable requirements.
CyberFundamentals
39: Koordinēta ievainojamību atklāšana
NIS2 Latvia
See all related requirements and other information from tasks own page.
Go to >
Detection process testing and compliance
1. Task description

Detection processes and procedures are maintained and tested to ensure awareness of anomalous events. Detection activities must comply with all relevant requirements.

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.