Concept skos:Concept Code ID.RA-05.2

The organisation shall conduct and document risk assessments in which risk is determined by threats, vulnerabilities, impact on business processes and assets, and likelihood of their occurrence.

Also known as

skos:altLabel

Documented risk assessment with likelihood

Note

skos:note

The goal of this control is to ensure that risk assessments are conducted and documented using a structured approachthatconsidersthreats,vulnerabilities,businessimpact,andlikelihood.Thissupportsinformeddecision- making and prioritisation of cybersecurity efforts across both IT and OT environments. To achieve this goal, the organisation should:

  • Include Internal and External Threats Risk assessments should consider threats originating from within the organisation as well as from external actors.
  • Apply Recognised Risk Analysis Methods Qualitative and/or quantitative methods — such as the MAPGOOD model, ISO/IEC 27005, or the CIS Risk Assessment Method — should be used.These methods maybe supported byrisk management software tools.
  • Prioritise Based on Likelihood and Impact Cybersecurity resources and investments should be allocated based on the estimated likelihood of threats and the potential impact on business processes and critical assets.
  • Ensure OT-Specific Risk Considerations Risk assessments should account for OT-specific factors such as safety implications, system availability, legacy technologies, and operational constraints.

Place in the list

For people working with the data

Identifier (URI) http://cyfun.data.gift/data/requirement_ID_RA_05_2
All data (24 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-05.2: The organisation shall conduct and document risk assessments in which risk is determined by threats, vulnerabilities, impact on business processes and assets, and likelihood of their occurrence.

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

ID.RA-05.2

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

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_IMPORTANT_E_p50

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

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p69

has broader

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

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

note

A general note, for any purpose.

The goal of this control is to ensure that risk assessments are conducted and documented using a structured approachthatconsidersthreats,vulnerabilities,businessimpact,andlikelihood.Thissupportsinformeddecision- making and prioritisation of cybersecurity efforts across both IT and OT environments. To achieve this goal, the organisation should: - Include Internal and External Threats Risk assessments should consider threats originating from within the organisation as well as from external actors. - Apply Recognised Risk Analysis Methods Qualitative and/or quantitative methods — such as the MAPGOOD model, ISO/IEC 27005, or the CIS Risk Assessment Method — should be used.These methods maybe supported byrisk management software tools. - Prioritise Based on Likelihood and Impact Cybersecurity resources and investments should be allocated based on the estimated likelihood of threats and the potential impact on business processes and critical assets. - Ensure OT-Specific Risk Considerations Risk assessments should account for OT-specific factors such as safety implications, system availability, legacy technologies, and operational constraints.

note

A general note, for any purpose.

The goal of this control is to ensure that risk assessments are conducted and documented using a structured approachthatconsidersthreats,vulnerabilities,businessimpact,andlikelihood.Thissupportsinformeddecision- making and prioritisation of cybersecurity efforts across both IT and OT environments. To achieve this goal, the organisation should: • Include Internal and External Threats Risk assessments should consider threats originating from within the organisation as well as from external actors. • Apply Recognised Risk Analysis Methods Qualitative and/or quantitative methods — such as the MAPGOOD model, ISO/IEC 27005, or the CIS Risk Assessment Method — should be used.These methods maybe supported byrisk management software tools. • Prioritise Based on Likelihood and Impact Cybersecurity resources and investments should be allocated based on the estimated likelihood of threats and the potential impact on business processes and critical assets. • Ensure OT-Specific Risk Considerations Risk assessments should account for OT-specific factors such as safety implications, system availability, legacy technologies, and operational constraints.

note

A general note, for any purpose.

<div><p>The goal of this control is to ensure that risk assessments are conducted and documented using a structured approachthatconsidersthreats,vulnerabilities,businessimpact,andlikelihood.Thissupportsinformeddecision- making and prioritisation of cybersecurity efforts across both IT and OT environments. To achieve this goal, the organisation should:</p><ul><li>Include Internal and External Threats Risk assessments should consider threats originating from within the organisation as well as from external actors.</li><li>Apply Recognised Risk Analysis Methods Qualitative and/or quantitative methods — such as the MAPGOOD model, ISO/IEC 27005, or the CIS Risk Assessment Method — should be used.These methods maybe supported byrisk management software tools.</li><li>Prioritise Based on Likelihood and Impact Cybersecurity resources and investments should be allocated based on the estimated likelihood of threats and the potential impact on business processes and critical assets.</li><li>Ensure OT-Specific Risk Considerations Risk assessments should account for OT-specific factors such as safety implications, system availability, legacy technologies, and operational constraints.</li></ul></div>

note

A general note, for any purpose.

The goal of this control is to ensure that risk assessments are conducted and documented using a structured approachthatconsidersthreats,vulnerabilities,businessimpact,andlikelihood.Thissupportsinformeddecision- making and prioritisation of cybersecurity efforts across both IT and OT environments. To achieve this goal, the organisation should: - Include Internal and External Threats Risk assessments should consider threats originating from within the organisation as well as from external actors. - Apply Recognised Risk Analysis Methods Qualitative and/or quantitative methods — such as the MAPGOOD model, ISO/IEC 27005, or the CIS Risk Assessment Method — should be used.These methods maybe supported byrisk management software tools. - Prioritise Based on Likelihood and Impact Cybersecurity resources and investments should be allocated based on the estimated likelihood of threats and the potential impact on business processes and critical assets. - Ensure OT-Specific Risk Considerations Risk assessments should account for OT-specific factors such as safety implications, system availability, legacy technologies, and operational constraints.

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

alternative label

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

Documented risk assessment with likelihood

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 conduct and document risk assessments in which risk is determined by threats, vulnerabilities, impact on business processes and assets, and likelihood of their occurrence.

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_ManagementAspects

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.

22

in dataset

Specifies the dataset the subject is part of.

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

Resultaten 1 - 24 of 24

References

Inverse links to the subject.