Concept skos:Concept Code ID.RA-02.1

A threat and vulnerability awareness program that includes a cross-organisation information-sharing capability shall be implemented.

Also known as

skos:altLabel

Threat and vulnerability awareness programme

Note

skos:note

The goal of this control is to strengthen the organisation’s ability to anticipate and respond to cyber threats by implementing a threat and vulnerability awareness program that includes cross-organisational information sharing. To achieve this goal, the organisation should:

  • Monitor Threat Actor Tactics and Emerging Vulnerabilities Cyberthreat intelligence should include up-to-date information on threat actors, theirtactics, techniques, and procedures (TTPs), as well as vulnerabilities in emerging technologies (e.g.AI-enabled attacks, data poisoning in machine learning).
  • Establish Ongoing External Engagement The organisation should maintain active participation in securitygroups, forums, and professional associations to receive alerts, advisories, and peer insights relevant to both IT and OT environments.
  • Enable Information Sharing The program should support the sharing of unclassified and, where appropriate, classified information about vulnerabilities and incidents across departments and with trusted external partners.
  • Support OT-Specific Awareness Threat intelligence should include OT-specific sources (e.g. ICS-CERT, vendor advisories) to address vulner- abilities in industrial control systems, legacy devices, and sector-specific technologies.
  • Differentiate Threat Intelligence from Vulnerability Management The awareness program should complement, but remain distinct from, vulnerability management processes by focusing on external threat developments and strategic insights.

Place in the list

For people working with the data

Identifier (URI) http://cyfun.data.gift/data/requirement_ID_RA_02_1
All data (21 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-02.1: A threat and vulnerability awareness program that includes a cross-organisation information-sharing capability shall be implemented.

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

ID.RA-02.1

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

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_IMPORTANT_E_p48

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

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p67

has broader

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

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

note

A general note, for any purpose.

The goal of this control is to strengthen the organisation’s ability to anticipate and respond to cyber threats by implementing a threat and vulnerability awareness program that includes cross-organisational information sharing. To achieve this goal, the organisation should: • Monitor Threat Actor Tactics and Emerging Vulnerabilities Cyberthreat intelligence should include up-to-date information on threat actors, theirtactics, techniques, and procedures (TTPs), as well as vulnerabilities in emerging technologies (e.g.AI-enabled attacks, data poisoning in machine learning). • Establish Ongoing External Engagement The organisation should maintain active participation in securitygroups, forums, and professional associations to receive alerts, advisories, and peer insights relevant to both IT and OT environments. • Enable Information Sharing The program should support the sharing of unclassified and, where appropriate, classified information about vulnerabilities and incidents across departments and with trusted external partners. • Support OT-Specific Awareness Threat intelligence should include OT-specific sources (e.g. ICS-CERT, vendor advisories) to address vulner- abilities in industrial control systems, legacy devices, and sector-specific technologies. • Differentiate Threat Intelligence from Vulnerability Management The awareness program should complement, but remain distinct from, vulnerability management processes by focusing on external threat developments and strategic insights.

note

A general note, for any purpose.

The goal of this control is to strengthen the organisation’s ability to anticipate and respond to cyber threats by implementing a threat and vulnerability awareness program that includes cross-organisational information sharing. To achieve this goal, the organisation should: - Monitor Threat Actor Tactics and Emerging Vulnerabilities Cyberthreat intelligence should include up-to-date information on threat actors, theirtactics, techniques, and procedures (TTPs), as well as vulnerabilities in emerging technologies (e.g.AI-enabled attacks, data poisoning in machine learning). - Establish Ongoing External Engagement The organisation should maintain active participation in securitygroups, forums, and professional associations to receive alerts, advisories, and peer insights relevant to both IT and OT environments. - Enable Information Sharing The program should support the sharing of unclassified and, where appropriate, classified information about vulnerabilities and incidents across departments and with trusted external partners. - Support OT-Specific Awareness Threat intelligence should include OT-specific sources (e.g. ICS-CERT, vendor advisories) to address vulner- abilities in industrial control systems, legacy devices, and sector-specific technologies. - Differentiate Threat Intelligence from Vulnerability Management The awareness program should complement, but remain distinct from, vulnerability management processes by focusing on external threat developments and strategic insights.

note

A general note, for any purpose.

The goal of this control is to strengthen the organisation’s ability to anticipate and respond to cyber threats by implementing a threat and vulnerability awareness program that includes cross-organisational information sharing. To achieve this goal, the organisation should: - Monitor Threat Actor Tactics and Emerging Vulnerabilities Cyberthreat intelligence should include up-to-date information on threat actors, theirtactics, techniques, and procedures (TTPs), as well as vulnerabilities in emerging technologies (e.g.AI-enabled attacks, data poisoning in machine learning). - Establish Ongoing External Engagement The organisation should maintain active participation in securitygroups, forums, and professional associations to receive alerts, advisories, and peer insights relevant to both IT and OT environments. - Enable Information Sharing The program should support the sharing of unclassified and, where appropriate, classified information about vulnerabilities and incidents across departments and with trusted external partners. - Support OT-Specific Awareness Threat intelligence should include OT-specific sources (e.g. ICS-CERT, vendor advisories) to address vulner- abilities in industrial control systems, legacy devices, and sector-specific technologies. - Differentiate Threat Intelligence from Vulnerability Management The awareness program should complement, but remain distinct from, vulnerability management processes by focusing on external threat developments and strategic insights.

note

A general note, for any purpose.

<div><p>The goal of this control is to strengthen the organisation’s ability to anticipate and respond to cyber threats by implementing a threat and vulnerability awareness program that includes cross-organisational information sharing. To achieve this goal, the organisation should:</p><ul><li>Monitor Threat Actor Tactics and Emerging Vulnerabilities Cyberthreat intelligence should include up-to-date information on threat actors, theirtactics, techniques, and procedures (TTPs), as well as vulnerabilities in emerging technologies (e.g.AI-enabled attacks, data poisoning in machine learning).</li><li>Establish Ongoing External Engagement The organisation should maintain active participation in securitygroups, forums, and professional associations to receive alerts, advisories, and peer insights relevant to both IT and OT environments.</li><li>Enable Information Sharing The program should support the sharing of unclassified and, where appropriate, classified information about vulnerabilities and incidents across departments and with trusted external partners.</li><li>Support OT-Specific Awareness Threat intelligence should include OT-specific sources (e.g. ICS-CERT, vendor advisories) to address vulner- abilities in industrial control systems, legacy devices, and sector-specific technologies.</li><li>Differentiate Threat Intelligence from Vulnerability Management The awareness program should complement, but remain distinct from, vulnerability management processes by focusing on external threat developments and strategic insights.</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-02.1

alternative label

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

Threat and vulnerability awareness programme

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.

A threat and vulnerability awareness program that includes a cross-organisation information-sharing capability shall be implemented.

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_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

triple count

The number of triples associated with the subject.

19

in dataset

Specifies the dataset the subject is part of.

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

Resultaten 1 - 21 of 21

References

Inverse links to the subject.