Concept
skos:Concept
Code
ID.RA-06.1
Risk responses shall be identified, prioritised, planned, tracked and communicated.
Also known as
skos:altLabel
Risk response planning and tracking
Note
skos:note
The goal of this control is to ensure that risk responses are clearly identified, prioritised, planned, tracked, and communicated to support effective risk mitigation and informed decision-making across the organisation. To achieve this goal, the organisation should:
- Apply Risk Response Criteria Decisions to accept, transfer, mitigate, oravoid risk should followthe organisation’svulnerabilitymanagement criteria, as referenced in ID.RA-08.1.
- Select Compensating Controls Thoughtfully Where direct mitigation is not feasible, compensating controls should be selected based on the same criteria to ensure consistent risk reduction.
- Base Actions on Risk Assessment Findings All risk response decisions should be grounded in the results of documented risk assessments, ensuring alignment with actual threats, vulnerabilities, and business impact.
- Track Implementation Progress Risk response actions should be tracked using structured tools such as a risk register, plan of action and milestones, or risk detail reports.
- Communicate in Priority Order Planned risk responses should be communicated to affected stakeholders in order of priority, ensuring timely awareness and coordination.
- Include OT-Specific Considerations Risk responses in OT environments should account for operational constraints, safety requirements, and system availability, especially when planning mitigation or compensating controls.
Place in the list
For people working with the data
http://cyfun.data.gift/data/requirement_ID_RA_06_1
All data (24 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-06.1: Risk responses shall be identified, prioritised, planned, tracked and communicated. |
|
ID.RA-06.1 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_IMPORTANT_E_p51 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p70 |
|
|
Relates a concept to a concept that is more general in meaning. |
|
|
A general note, for any purpose. |
The goal of this control is to ensure that risk responses are clearly identified, prioritised, planned, tracked, and communicated to support effective risk mitigation and informed decision-making across the organisation. To achieve this goal, the organisation should: - Apply Risk Response Criteria Decisions to accept, transfer, mitigate, oravoid risk should followthe organisation’svulnerabilitymanagement criteria, as referenced in ID.RA-08.1. - Select Compensating Controls Thoughtfully Where direct mitigation is not feasible, compensating controls should be selected based on the same criteria to ensure consistent risk reduction. - Base Actions on Risk Assessment Findings All risk response decisions should be grounded in the results of documented risk assessments, ensuring alignment with actual threats, vulnerabilities, and business impact. - Track Implementation Progress Risk response actions should be tracked using structured tools such as a risk register, plan of action and milestones, or risk detail reports. - Communicate in Priority Order Planned risk responses should be communicated to affected stakeholders in order of priority, ensuring timely awareness and coordination. - Include OT-Specific Considerations Risk responses in OT environments should account for operational constraints, safety requirements, and system availability, especially when planning mitigation or compensating controls. |
|
A general note, for any purpose. |
The goal of this control is to ensure that risk responses are clearly identified, prioritised, planned, tracked, and communicated to support effective risk mitigation and informed decision-making across the organisation. To achieve this goal, the organisation should: • Apply Risk Response Criteria Decisions to accept, transfer, mitigate, oravoid risk should followthe organisation’svulnerabilitymanagement criteria, as referenced in ID.RA-08.1. • Select Compensating Controls Thoughtfully Where direct mitigation is not feasible, compensating controls should be selected based on the same criteria to ensure consistent risk reduction. • Base Actions on Risk Assessment Findings All risk response decisions should be grounded in the results of documented risk assessments, ensuring alignment with actual threats, vulnerabilities, and business impact. • Track Implementation Progress Risk response actions should be tracked using structured tools such as a risk register, plan of action and milestones, or risk detail reports. • Communicate in Priority Order Planned risk responses should be communicated to affected stakeholders in order of priority, ensuring timely awareness and coordination. • Include OT-Specific Considerations Risk responses in OT environments should account for operational constraints, safety requirements, and system availability, especially when planning mitigation or compensating controls. |
|
A general note, for any purpose. |
<div><p>The goal of this control is to ensure that risk responses are clearly identified, prioritised, planned, tracked, and communicated to support effective risk mitigation and informed decision-making across the organisation. To achieve this goal, the organisation should:</p><ul><li>Apply Risk Response Criteria Decisions to accept, transfer, mitigate, oravoid risk should followthe organisation’svulnerabilitymanagement criteria, as referenced in ID.RA-08.1.</li><li>Select Compensating Controls Thoughtfully Where direct mitigation is not feasible, compensating controls should be selected based on the same criteria to ensure consistent risk reduction.</li><li>Base Actions on Risk Assessment Findings All risk response decisions should be grounded in the results of documented risk assessments, ensuring alignment with actual threats, vulnerabilities, and business impact.</li><li>Track Implementation Progress Risk response actions should be tracked using structured tools such as a risk register, plan of action and milestones, or risk detail reports.</li><li>Communicate in Priority Order Planned risk responses should be communicated to affected stakeholders in order of priority, ensuring timely awareness and coordination.</li><li>Include OT-Specific Considerations Risk responses in OT environments should account for operational constraints, safety requirements, and system availability, especially when planning mitigation or compensating controls.</li></ul></div> |
|
A general note, for any purpose. |
The goal of this control is to ensure that risk responses are clearly identified, prioritised, planned, tracked, and communicated to support effective risk mitigation and informed decision-making across the organisation. To achieve this goal, the organisation should: - Apply Risk Response Criteria Decisions to accept, transfer, mitigate, oravoid risk should followthe organisation’svulnerabilitymanagement criteria, as referenced in ID.RA-08.1. - Select Compensating Controls Thoughtfully Where direct mitigation is not feasible, compensating controls should be selected based on the same criteria to ensure consistent risk reduction. - Base Actions on Risk Assessment Findings All risk response decisions should be grounded in the results of documented risk assessments, ensuring alignment with actual threats, vulnerabilities, and business impact. - Track Implementation Progress Risk response actions should be tracked using structured tools such as a risk register, plan of action and milestones, or risk detail reports. - Communicate in Priority Order Planned risk responses should be communicated to affected stakeholders in order of priority, ensuring timely awareness and coordination. - Include OT-Specific Considerations Risk responses in OT environments should account for operational constraints, safety requirements, and system availability, especially when planning mitigation or compensating controls. |
|
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-06.1 |
|
skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties. |
Risk response planning and tracking |
|
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. |
Risk responses shall be identified, prioritised, planned, tracked and communicated. |
|
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. |
http://cyfun.data.gift/data/CyFun2025_delta_BASIC_to_IMPORTANT |
|
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. |
|
|
1 |
|
|
The number of triples associated with the subject. |
22 |
|
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. |