Requirement

6.10.2: Vulnerability monitoring and handling

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

For the purpose of point 6.10.1, the relevant entities shall:

monitor information about vulnerabilities through appropriate channels, such as announcements of CSIRTs, competent authorities or information provided by suppliers or service providers;
perform, where appropriate, vulnerability scans, and record evidence of the results of the scans, at planned intervals;
address, without undue delay, vulnerabilities identified by the relevant entities as critical to their operations;
ensure that their vulnerability handling is compatible with their change management, security patch management, risk management and incident management procedures;
lay down a procedure for disclosing vulnerabilities in accordance with the applicable national coordinated vulnerability disclosure policy.

Fulfill this requirement by completing the tasks below ->

This requirement is part of the framework:

NIS2 Implementing Regulation

Other requirements of the framework

6.10.2: Vulnerability monitoring and handling

Best practices

How to implement:

6.10.2: Vulnerability monitoring and handling

This policy on

6.10.2: Vulnerability monitoring and handling

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.

For the purpose of point 6.10.1, the relevant entities shall:

monitor information about vulnerabilities through appropriate channels, such as announcements of CSIRTs, competent authorities or information provided by suppliers or service providers;
perform, where appropriate, vulnerability scans, and record evidence of the results of the scans, at planned intervals;
address, without undue delay, vulnerabilities identified by the relevant entities as critical to their operations;
ensure that their vulnerability handling is compatible with their change management, security patch management, risk management and incident management procedures;
lay down a procedure for disclosing vulnerabilities in accordance with the applicable national coordinated vulnerability disclosure policy.

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

6.10.2: Vulnerability monitoring and handling

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

6.10.2: Vulnerability monitoring and handling

of the framework

NIS2 Implementing Regulation

Task name

Priority

Task completes

Complete these tasks to increase your compliance in this policy.

Critical

Process for managing technical vulnerabilities

Critical

High

Normal

Low

Development and cloud

Technical vulnerability management

Process for managing technical vulnerabilities

This task helps you comply with the following requirements

12.6.1: Management of technical vulnerabilities ISO 27001

14.2.1: Secure development policy ISO 27001

ID.RA-1: Asset vulnerabilities NIST

PR.IP-12: Vulnerability management plan NIST

RS.AN-5: Vulnerability management process NIST

Process for vulnerability disclosure

Critical

High

Normal

Low

Development and cloud

Technical vulnerability management

Process for vulnerability disclosure

This task helps you comply with the following requirements

Art. 24.2.e.2: Sicurezza dell'acquisizione NIS2 Italy

Article 13.17: Single point of contact CRA

6.10.2: Vulnerability monitoring and handling NIS2 Guide

Process for handling and sharing vulnerability disclosures

Critical

High

Normal

Low

Partner management

Agreements and monitoring

Process for handling and sharing vulnerability disclosures

This task helps you comply with the following requirements

RS.AN-5: Processes are established to receive, analyse, and respond to vulnerabilities disclosed to the organization from internal and external sources.CyberFundamentals

ID.RA-08: Processes for handling vulnerability disclosures NIST 2.0

30 § 3.11°: Divulgation des vulnérabilités NIS2 Belgium

14.5.6): Tinklų ir informacinių sistemų saugumą NIS2 Lithuania

Vuln.6: Sharing information about potential vulnerabilities CRA

Regular vulnerability scanning

Critical

High

Normal

Low

Development and cloud

Technical vulnerability management

Regular vulnerability scanning

This task helps you comply with the following requirements

12.6.1: Management of technical vulnerabilities ISO 27001

18.2.3: Technical compliance review ISO 27001

14.2.8: System security testing ISO 27001

6.5: Tietojärjestelmien asennus, ylläpito ja päivitys Omavalvontasuunnitelma

MWP-02: Automatic file scan by anti-malware software Cyber Essentials

Evaluation process and documentation of significant security-related changes

Critical

High

Normal

Low

Risk management and leadership

Risk management

Evaluation process and documentation of significant security-related changes

This task helps you comply with the following requirements

Č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

Defining metrics related to vulnerability management

Critical

High

Normal

Low

Development and cloud

Technical vulnerability management

Defining metrics related to vulnerability management

This task helps you comply with the following requirements

16.2: Establish and Maintain a Process to Accept and Address Software Vulnerabilities CIS 18

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

Art. 24.2.e.2: Sicurezza dell'acquisizione NIS2 Italy

6.10.1: Vulnerability management process NIS2 Guide

6.10.2: Vulnerability monitoring and handling NIS2 Guide

Monitoring of technical vulnerability communications

Critical

High

Normal

Low

Development and cloud

Technical vulnerability management

Monitoring of technical vulnerability communications

This task helps you comply with the following requirements

50: Teknisten haavoittuvuuksien seuranta Digiturvan kokonaiskuvapalvelu

THREAT-1: Reduce Cybersecurity Vulnerabilities C2M2

9.3 §: Tietojärjestelmien hankinta ja kehittäminen Kyberturvallisuuslaki

Article 34: ICT operations security DORA simplified RMF

§ 47: Identifikation, reaktion og afbødning af sårbarheder Energisektor beredskabsbekendtgørelse

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