Concept skos:Concept Code ID.RA-08.1

The organisation shall establish and implement a vulnerability management plan to identify, analyse, assess, mitigate and communicate all types of vulnerabilities including in the form of a Coordinated Vulnerability Disclosure (CVD) according to applicable legal modalities.

Also known as

skos:altLabel

Vulnerability management plan

Note

skos:note

The goal of this control is to ensure that all types of vulnerabilities are systematically identified, analysed, assessed, mitigated, and communicated through a documented vulnerability management plan. This includes handling disclosures in line with Coordinated Vulnerability Disclosure (CVD) practices and applicable legal requirements. To achieve this goal, the organisation should:

  • Establish a Comprehensive Vulnerability Management Plan The plan should cover vulnerabilities from internal testing, external sources such as security bulletins, and disclosures from researchers, vendors, partners, or government cybersecurity bodies.
  • Assign Responsibilities and Monitor Implementation Clearroles should be defined forprocessing, analysing, and responding to disclosedvulnerabilities. Implemen- tation of procedures should be monitored to ensure timely and effective handling.
  • Support Coordinated Vulnerability Disclosure (CVD) The plan should include procedures forreceiving and responding tovulnerabilityreports from external parties. CVD practices should align with guidance provided by ENISA’s CVD framework, which outlines legal, tech- nical, and communication considerations.
  • Ensure OT-Specific Coverage The plan should address vulnerabilities in OT environments, including legacy systems, vendor-managed components, and embedded firmware, where patching or mitigation may require coordination with engi- neering teams.

Place in the list

For people working with the data

Identifier (URI) http://cyfun.data.gift/data/requirement_ID_RA_08_1
All data (23 statements)

Properties and relations

Direct links from the subject.

Property Value

type

The subject is an instance of a class.

http://cyfun.data.gift/ontology#Requirement

type

The subject is an instance of a class.

Concept

An idea or notion; a unit of thought.

label

A human-readable name for the subject.

ID.RA-08.1: The organisation shall establish and implement a vulnerability management plan to identify, analyse, assess, mitigate and communicate all types of vulnerabilities including in the form of a Coordinated Vulnerability Disclosure (CVD) according to applicable legal modalities.

http://cyfun.data.gift/ontology#requirementId

ID.RA-08.1

http://cyfun.data.gift/ontology#foundIn

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p71

http://cyfun.data.gift/ontology#foundIn

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_IMPORTANT_E_p52

has broader

Relates a concept to a concept that is more general in meaning.

http://cyfun.data.gift/data/subcategory_ID.RA-08

note

A general note, for any purpose.

The goal of this control is to ensure that all types of vulnerabilities are systematically identified, analysed, assessed, mitigated, and communicated through a documented vulnerability management plan. This includes handling disclosures in line with Coordinated Vulnerability Disclosure (CVD) practices and applicable legal requirements. To achieve this goal, the organisation should: - Establish a Comprehensive Vulnerability Management Plan The plan should cover vulnerabilities from internal testing, external sources such as security bulletins, and disclosures from researchers, vendors, partners, or government cybersecurity bodies. - Assign Responsibilities and Monitor Implementation Clearroles should be defined forprocessing, analysing, and responding to disclosedvulnerabilities. Implemen- tation of procedures should be monitored to ensure timely and effective handling. - Support Coordinated Vulnerability Disclosure (CVD) The plan should include procedures forreceiving and responding tovulnerabilityreports from external parties. CVD practices should align with guidance provided by ENISA’s CVD framework, which outlines legal, tech- nical, and communication considerations. - Ensure OT-Specific Coverage The plan should address vulnerabilities in OT environments, including legacy systems, vendor-managed components, and embedded firmware, where patching or mitigation may require coordination with engi- neering teams.

note

A general note, for any purpose.

The goal of this control is to ensure that all types of vulnerabilities are systematically identified, analysed, assessed, mitigated, and communicated through a documented vulnerability management plan. This includes handling disclosures in line with Coordinated Vulnerability Disclosure (CVD) practices and applicable legal requirements. To achieve this goal, the organisation should: - Establish a Comprehensive Vulnerability Management Plan The plan should cover vulnerabilities from internal testing, external sources such as security bulletins, and disclosures from researchers, vendors, partners, or government cybersecurity bodies. - Assign Responsibilities and Monitor Implementation Clearroles should be defined forprocessing, analysing, and responding to disclosedvulnerabilities. Implemen- tation of procedures should be monitored to ensure timely and effective handling. - Support Coordinated Vulnerability Disclosure (CVD) The plan should include procedures forreceiving and responding tovulnerabilityreports from external parties. CVD practices should align with guidance provided by ENISA’s CVD framework, which outlines legal, tech- nical, and communication considerations. - Ensure OT-Specific Coverage The plan should address vulnerabilities in OT environments, including legacy systems, vendor-managed components, and embedded firmware, where patching or mitigation may require coordination with engi- neering teams.

note

A general note, for any purpose.

The goal of this control is to ensure that all types of vulnerabilities are systematically identified, analysed, assessed, mitigated, and communicated through a documented vulnerability management plan. This includes handling disclosures in line with Coordinated Vulnerability Disclosure (CVD) practices and applicable legal requirements. To achieve this goal, the organisation should: • Establish a Comprehensive Vulnerability Management Plan The plan should cover vulnerabilities from internal testing, external sources such as security bulletins, and disclosures from researchers, vendors, partners, or government cybersecurity bodies. • Assign Responsibilities and Monitor Implementation Clearroles should be defined forprocessing, analysing, and responding to disclosedvulnerabilities. Implemen- tation of procedures should be monitored to ensure timely and effective handling. • Support Coordinated Vulnerability Disclosure (CVD) The plan should include procedures forreceiving and responding tovulnerabilityreports from external parties. CVD practices should align with guidance provided by ENISA’s CVD framework, which outlines legal, tech- nical, and communication considerations. • Ensure OT-Specific Coverage The plan should address vulnerabilities in OT environments, including legacy systems, vendor-managed components, and embedded firmware, where patching or mitigation may require coordination with engi- neering teams.

note

A general note, for any purpose.

<div><p>The goal of this control is to ensure that all types of vulnerabilities are systematically identified, analysed, assessed, mitigated, and communicated through a documented vulnerability management plan. This includes handling disclosures in line with Coordinated Vulnerability Disclosure (CVD) practices and applicable legal requirements. To achieve this goal, the organisation should:</p><ul><li>Establish a Comprehensive Vulnerability Management Plan The plan should cover vulnerabilities from internal testing, external sources such as security bulletins, and disclosures from researchers, vendors, partners, or government cybersecurity bodies.</li><li>Assign Responsibilities and Monitor Implementation Clearroles should be defined forprocessing, analysing, and responding to disclosedvulnerabilities. Implemen- tation of procedures should be monitored to ensure timely and effective handling.</li><li>Support Coordinated Vulnerability Disclosure (CVD) The plan should include procedures forreceiving and responding tovulnerabilityreports from external parties. CVD practices should align with guidance provided by ENISA’s CVD framework, which outlines legal, tech- nical, and communication considerations.</li><li>Ensure OT-Specific Coverage The plan should address vulnerabilities in OT environments, including legacy systems, vendor-managed components, and embedded firmware, where patching or mitigation may require coordination with engi- neering teams.</li></ul></div>

notation

A notation, also known as classification code, is a string of characters such as "T58.5" or "303.4833" used to uniquely identify a concept within the scope of a given concept scheme.

ID.RA-08.1

alternative label

skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties.

Vulnerability management plan

preferred label

A resource has no more than one value of skos:prefLabel per language tag, and no more than one value of skos:prefLabel without language tag.

The organisation shall establish and implement a vulnerability management plan to identify, analyse, assess, mitigate and communicate all types of vulnerabilities including in the form of a Coordinated Vulnerability Disclosure (CVD) according to applicable legal modalities.

is in scheme

Relates a resource (for example a concept) to a concept scheme in which it is included.

http://cyfun.data.gift/data/CyFun2025

is in scheme

Relates a resource (for example a concept) to a concept scheme in which it is included.

http://cyfun.data.gift/data/CyFun2025_KeyMeasures

is in scheme

Relates a resource (for example a concept) to a concept scheme in which it is included.

http://cyfun.data.gift/data/CyFun2025_delta_BASIC_to_IMPORTANT

is in scheme

Relates a resource (for example a concept) to a concept scheme in which it is included.

http://cyfun.data.gift/data/CyFun2025_IMPORTANT

is in scheme

Relates a resource (for example a concept) to a concept scheme in which it is included.

http://cyfun.data.gift/data/CyFun2025_ESSENTIAL

http://cyfun.data.gift/ontology#level

http://cyfun.data.gift/data/level_IMPORTANT

http://cyfun.data.gift/ontology#isKeyMeasure

1

triple count

The number of triples associated with the subject.

21

in dataset

Specifies the dataset the subject is part of.

http://data.gift/d/datasets/69E8863AA6CE46D9ACD13109

Resultaten 1 - 23 of 23

References

Inverse links to the subject.