Concept
skos:Concept
Code
ID.RA-05.1
The organisation shall conduct risk assessments in which risk is determined by threats, vulnerabilities and the impact on business processes and assets.
Also known as
skos:altLabel
Risk assessment execution
Note
skos:note
The goal of this control is to ensure that risk assessments are conducted by evaluating threats, vulnerabilities, and their potential impact on business processes and assets. This supports informed decision-making and effective risk mitigation. To achieve this goal, the following should be considered:
- IdentifyThreats and Vulnerabilities Assessments should include threats and vulnerabilities across software, network and system architectures, and facilities housing critical computing assets.
- Evaluate Business Impact The potential impact on business operations, services, and assets should be analysed to determine the severity of each risk.
- Include Human Factors Human behaviour should be considered when designing and applying security policies, especially in opera- tional technology (OT) environments.
- Document and Review Risk assessments should be documented, regularly reviewed, and updated to reflect changes in systems, operations, or the threat landscape.
Place in the list
For people working with the data
http://cyfun.data.gift/data/requirement_ID_RA_05_1
All data (23 statements)
Properties and relations
Direct links from the subject.
| Property | Value |
|---|---|
|
The subject is an instance of a class. |
|
|
The subject is an instance of a class. |
An idea or notion; a unit of thought. |
|
A human-readable name for the subject. |
ID.RA-05.1: The organisation shall conduct risk assessments in which risk is determined by threats, vulnerabilities and the impact on business processes and assets. |
|
ID.RA-05.1 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_BASIC_E_p21 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_IMPORTANT_E_p50 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p69 |
|
|
Relates a concept to a concept that is more general in meaning. |
|
|
A general note, for any purpose. |
<div><p>The goal of this control is to ensure that risk assessments are conducted by evaluating threats, vulnerabilities, and their potential impact on business processes and assets. This supports informed decision-making and effective risk mitigation. To achieve this goal, the following should be considered:</p><ul><li>IdentifyThreats and Vulnerabilities Assessments should include threats and vulnerabilities across software, network and system architectures, and facilities housing critical computing assets.</li><li>Evaluate Business Impact The potential impact on business operations, services, and assets should be analysed to determine the severity of each risk.</li><li>Include Human Factors Human behaviour should be considered when designing and applying security policies, especially in opera- tional technology (OT) environments.</li><li>Document and Review Risk assessments should be documented, regularly reviewed, and updated to reflect changes in systems, operations, or the threat landscape.</li></ul></div> |
|
A general note, for any purpose. |
The goal of this control is to ensure that risk assessments are conducted by evaluating threats, vulnerabilities, and their potential impact on business processes and assets. This supports informed decision-making and effective risk mitigation. To achieve this goal, the following should be considered: - IdentifyThreats and Vulnerabilities Assessments should include threats and vulnerabilities across software, network and system architectures, and facilities housing critical computing assets. - Evaluate Business Impact The potential impact on business operations, services, and assets should be analysed to determine the severity of each risk. - Include Human Factors Human behaviour should be considered when designing and applying security policies, especially in opera- tional technology (OT) environments. - Document and Review Risk assessments should be documented, regularly reviewed, and updated to reflect changes in systems, operations, or the threat landscape. |
|
A general note, for any purpose. |
The goal of this control is to ensure that risk assessments are conducted by evaluating threats, vulnerabilities, and their potential impact on business processes and assets. This supports informed decision-making and effective risk mitigation. To achieve this goal, the following should be considered: - IdentifyThreats and Vulnerabilities Assessments should include threats and vulnerabilities across software, network and system architectures, and facilities housing critical computing assets. - Evaluate Business Impact The potential impact on business operations, services, and assets should be analysed to determine the severity of each risk. - Include Human Factors Human behaviour should be considered when designing and applying security policies, especially in opera- tional technology (OT) environments. - Document and Review Risk assessments should be documented, regularly reviewed, and updated to reflect changes in systems, operations, or the threat landscape. |
|
A general note, for any purpose. |
The goal of this control is to ensure that risk assessments are conducted by evaluating threats, vulnerabilities, and their potential impact on business processes and assets. This supports informed decision-making and effective risk mitigation. To achieve this goal, the following should be considered: • IdentifyThreats and Vulnerabilities Assessments should include threats and vulnerabilities across software, network and system architectures, and facilities housing critical computing assets. • Evaluate Business Impact The potential impact on business operations, services, and assets should be analysed to determine the severity of each risk. • Include Human Factors Human behaviour should be considered when designing and applying security policies, especially in opera- tional technology (OT) environments. • Document and Review Risk assessments should be documented, regularly reviewed, and updated to reflect changes in systems, operations, or the threat landscape. |
|
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.1 |
|
skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties. |
Risk assessment execution |
|
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 risk assessments in which risk is determined by threats, vulnerabilities and the impact on business processes and assets. |
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
The number of triples associated with the subject. |
21 |
|
Specifies the dataset the subject is part of. |
References
Inverse links to the subject.
| Property | Subject |
|---|---|
|
Relates a concept to a concept that is more specific in meaning. |