Concept
skos:Concept
Code
ID.IM-04.2
The organisation shall coordinate the development and the testing of Incident Response Plans and other cybersecurity plans that affect operations with stake- holders to ensure that these plans align with overall organisational goals and enhance resilience.
Also known as
skos:altLabel
Incident response plan coordination
Note
skos:note
The goal of this control is to ensure that Incident Response Plans and other cybersecurityplans affecting oper- ations are aligned with organisational goals and enhance resilience through coordinated development and testing with relevant stakeholders. To achieve this goal, the organisation should:
- Review and Update Plans Regularly Plans should be reviewed and updated to reflect evolving threats, organisational changes, and operational needs.
- Engage Stakeholders Early Stakeholders, including internal teams, suppliers, and relevant third parties, should be involved early in the planning process to ensure alignment and relevance.
- Maintain Ongoing Communication Stakeholders should be kept informed of plan progress, updates, and changes to maintain shared under- standing and readiness.
- Coordinate Testing Activities Testing of plans should be coordinated with stakeholders to validate effectiveness, clarify roles, and strengthen collaborative response capabilities.
Place in the list
For people working with the data
http://cyfun.data.gift/data/requirement_ID_IM_04_2
All data (20 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.IM-04.2: The organisation shall coordinate the development and the testing of Incident Response Plans and other cybersecurity plans that affect operations with stake- holders to ensure that these plans align with overall organisational goals and enhance resilience. |
|
ID.IM-04.2 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p80 |
|
|
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 Incident Response Plans and other cybersecurityplans affecting oper- ations are aligned with organisational goals and enhance resilience through coordinated development and testing with relevant stakeholders. To achieve this goal, the organisation should: • Review and Update Plans Regularly Plans should be reviewed and updated to reflect evolving threats, organisational changes, and operational needs. • Engage Stakeholders Early Stakeholders, including internal teams, suppliers, and relevant third parties, should be involved early in the planning process to ensure alignment and relevance. • Maintain Ongoing Communication Stakeholders should be kept informed of plan progress, updates, and changes to maintain shared under- standing and readiness. • Coordinate Testing Activities Testing of plans should be coordinated with stakeholders to validate effectiveness, clarify roles, and strengthen collaborative response capabilities. |
|
A general note, for any purpose. |
The goal of this control is to ensure that Incident Response Plans and other cybersecurityplans affecting oper- ations are aligned with organisational goals and enhance resilience through coordinated development and testing with relevant stakeholders. To achieve this goal, the organisation should: - Review and Update Plans Regularly Plans should be reviewed and updated to reflect evolving threats, organisational changes, and operational needs. - Engage Stakeholders Early Stakeholders, including internal teams, suppliers, and relevant third parties, should be involved early in the planning process to ensure alignment and relevance. - Maintain Ongoing Communication Stakeholders should be kept informed of plan progress, updates, and changes to maintain shared under- standing and readiness. - Coordinate Testing Activities Testing of plans should be coordinated with stakeholders to validate effectiveness, clarify roles, and strengthen collaborative response capabilities. |
|
A general note, for any purpose. |
The goal of this control is to ensure that Incident Response Plans and other cybersecurityplans affecting oper- ations are aligned with organisational goals and enhance resilience through coordinated development and testing with relevant stakeholders. To achieve this goal, the organisation should: - Review and Update Plans Regularly Plans should be reviewed and updated to reflect evolving threats, organisational changes, and operational needs. - Engage Stakeholders Early Stakeholders, including internal teams, suppliers, and relevant third parties, should be involved early in the planning process to ensure alignment and relevance. - Maintain Ongoing Communication Stakeholders should be kept informed of plan progress, updates, and changes to maintain shared under- standing and readiness. - Coordinate Testing Activities Testing of plans should be coordinated with stakeholders to validate effectiveness, clarify roles, and strengthen collaborative response capabilities. |
|
A general note, for any purpose. |
<div><p>The goal of this control is to ensure that Incident Response Plans and other cybersecurityplans affecting oper- ations are aligned with organisational goals and enhance resilience through coordinated development and testing with relevant stakeholders. To achieve this goal, the organisation should:</p><ul><li>Review and Update Plans Regularly Plans should be reviewed and updated to reflect evolving threats, organisational changes, and operational needs.</li><li>Engage Stakeholders Early Stakeholders, including internal teams, suppliers, and relevant third parties, should be involved early in the planning process to ensure alignment and relevance.</li><li>Maintain Ongoing Communication Stakeholders should be kept informed of plan progress, updates, and changes to maintain shared under- standing and readiness.</li><li>Coordinate Testing Activities Testing of plans should be coordinated with stakeholders to validate effectiveness, clarify roles, and strengthen collaborative response capabilities.</li></ul></div> |
|
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.IM-04.2 |
|
skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties. |
Incident response plan coordination |
|
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 coordinate the development and the testing of Incident Response Plans and other cybersecurity plans that affect operations with stake- holders to ensure that these plans align with overall organisational goals and enhance resilience. |
|
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_IMPORTANT_to_ESSENTIAL |
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
The number of triples associated with the subject. |
18 |
|
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. |