Concept skos:Concept Code ID.RA-03.1

Threats shall be identified and assessed in relation to all relevant assets, including software, network and system architectures, and facilities.

Also known as

skos:altLabel

Threat assessment for assets

Note

skos:note

The goal of this control is to ensure that threats are systematicallyidentified and assessed in relation to all relevant assets, including software, network and system architectures, and facilities. This builds on ID.RA-01.1, which establishes the foundation for identifying both threats and vulnerabilities across critical assets. To achieve this goal, the organisation should:

  • Extend Threat Identification Across All Assets Threats should be assessed in relation to all relevant assets, including IT and OT systems, applications, net- work designs, and physical facilities that support critical operations.
  • Maintain a Dedicated Threat Intelligence Process A structured process should be in place to gather, analyse, and assess threat intelligence from internal and external sources, including sector-specific advisories and OT-focused threat feeds.
  • Differentiate Threat Intelligence from Vulnerability Management Threat intelligence should be managed separately from vulnerability management, with distinct processes and evidence to ensure clarity and focus.Threats refer to potential actors or events, while vulnerabilities refer to weaknesses that could be exploited.
  • Integrate with Risk Analysis Identified threats should be linked to known vulnerabilities and recorded in a central risk register to support prioritisation and mitigation planning, as outlined in ID.RA-01.1.
  • Include OT-Specific Threats ThreatassessmentsshouldconsiderOT-specificriskssuchassupplychaincompromise,unauthorisedremote access, and exploitation of legacy systems or proprietary protocols.

Place in the list

For people working with the data

Identifier (URI) http://cyfun.data.gift/data/requirement_ID_RA_03_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-03.1: Threats shall be identified and assessed in relation to all relevant assets, including software, network and system architectures, and facilities.

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

ID.RA-03.1

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

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p68

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

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_IMPORTANT_E_p49

has broader

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

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

note

A general note, for any purpose.

<div><p>The goal of this control is to ensure that threats are systematicallyidentified and assessed in relation to all relevant assets, including software, network and system architectures, and facilities. This builds on ID.RA-01.1, which establishes the foundation for identifying both threats and vulnerabilities across critical assets. To achieve this goal, the organisation should:</p><ul><li>Extend Threat Identification Across All Assets Threats should be assessed in relation to all relevant assets, including IT and OT systems, applications, net- work designs, and physical facilities that support critical operations.</li><li>Maintain a Dedicated Threat Intelligence Process A structured process should be in place to gather, analyse, and assess threat intelligence from internal and external sources, including sector-specific advisories and OT-focused threat feeds.</li><li>Differentiate Threat Intelligence from Vulnerability Management Threat intelligence should be managed separately from vulnerability management, with distinct processes and evidence to ensure clarity and focus.Threats refer to potential actors or events, while vulnerabilities refer to weaknesses that could be exploited.</li><li>Integrate with Risk Analysis Identified threats should be linked to known vulnerabilities and recorded in a central risk register to support prioritisation and mitigation planning, as outlined in ID.RA-01.1.</li><li>Include OT-Specific Threats ThreatassessmentsshouldconsiderOT-specificriskssuchassupplychaincompromise,unauthorisedremote access, and exploitation of legacy systems or proprietary protocols.</li></ul></div>

note

A general note, for any purpose.

The goal of this control is to ensure that threats are systematicallyidentified and assessed in relation to all relevant assets, including software, network and system architectures, and facilities. This builds on ID.RA-01.1, which establishes the foundation for identifying both threats and vulnerabilities across critical assets. To achieve this goal, the organisation should: - Extend Threat Identification Across All Assets Threats should be assessed in relation to all relevant assets, including IT and OT systems, applications, net- work designs, and physical facilities that support critical operations. - Maintain a Dedicated Threat Intelligence Process A structured process should be in place to gather, analyse, and assess threat intelligence from internal and external sources, including sector-specific advisories and OT-focused threat feeds. - Differentiate Threat Intelligence from Vulnerability Management Threat intelligence should be managed separately from vulnerability management, with distinct processes and evidence to ensure clarity and focus.Threats refer to potential actors or events, while vulnerabilities refer to weaknesses that could be exploited. - Integrate with Risk Analysis Identified threats should be linked to known vulnerabilities and recorded in a central risk register to support prioritisation and mitigation planning, as outlined in ID.RA-01.1. - Include OT-Specific Threats ThreatassessmentsshouldconsiderOT-specificriskssuchassupplychaincompromise,unauthorisedremote access, and exploitation of legacy systems or proprietary protocols.

note

A general note, for any purpose.

The goal of this control is to ensure that threats are systematicallyidentified and assessed in relation to all relevant assets, including software, network and system architectures, and facilities. This builds on ID.RA-01.1, which establishes the foundation for identifying both threats and vulnerabilities across critical assets. To achieve this goal, the organisation should: - Extend Threat Identification Across All Assets Threats should be assessed in relation to all relevant assets, including IT and OT systems, applications, net- work designs, and physical facilities that support critical operations. - Maintain a Dedicated Threat Intelligence Process A structured process should be in place to gather, analyse, and assess threat intelligence from internal and external sources, including sector-specific advisories and OT-focused threat feeds. - Differentiate Threat Intelligence from Vulnerability Management Threat intelligence should be managed separately from vulnerability management, with distinct processes and evidence to ensure clarity and focus.Threats refer to potential actors or events, while vulnerabilities refer to weaknesses that could be exploited. - Integrate with Risk Analysis Identified threats should be linked to known vulnerabilities and recorded in a central risk register to support prioritisation and mitigation planning, as outlined in ID.RA-01.1. - Include OT-Specific Threats ThreatassessmentsshouldconsiderOT-specificriskssuchassupplychaincompromise,unauthorisedremote access, and exploitation of legacy systems or proprietary protocols.

note

A general note, for any purpose.

The goal of this control is to ensure that threats are systematicallyidentified and assessed in relation to all relevant assets, including software, network and system architectures, and facilities. This builds on ID.RA-01.1, which establishes the foundation for identifying both threats and vulnerabilities across critical assets. To achieve this goal, the organisation should: • Extend Threat Identification Across All Assets Threats should be assessed in relation to all relevant assets, including IT and OT systems, applications, net- work designs, and physical facilities that support critical operations. • Maintain a Dedicated Threat Intelligence Process A structured process should be in place to gather, analyse, and assess threat intelligence from internal and external sources, including sector-specific advisories and OT-focused threat feeds. • Differentiate Threat Intelligence from Vulnerability Management Threat intelligence should be managed separately from vulnerability management, with distinct processes and evidence to ensure clarity and focus.Threats refer to potential actors or events, while vulnerabilities refer to weaknesses that could be exploited. • Integrate with Risk Analysis Identified threats should be linked to known vulnerabilities and recorded in a central risk register to support prioritisation and mitigation planning, as outlined in ID.RA-01.1. • Include OT-Specific Threats ThreatassessmentsshouldconsiderOT-specificriskssuchassupplychaincompromise,unauthorisedremote access, and exploitation of legacy systems or proprietary protocols.

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

alternative label

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

Threat assessment for assets

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.

Threats shall be identified and assessed in relation to all relevant assets, including software, network and system architectures, and facilities.

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.