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. |
RS.MA-01.2: The organisation shall coordinate information/cybersecurity incident response actions with all predefined stakeholders. |
|
RS.MA-01.2 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p164 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_IMPORTANT_E_p110 |
|
|
Relates a concept to a concept that is more general in meaning. |
|
|
A general note, for any purpose. |
The goal ofthis control is to ensure that all relevant internal and external stakeholderswork togethereffectively during a cybersecurity or information incident. To achieve this goal: - Incident response actions should be coordinated with predefined stakeholders, including business leaders, IT and OT system owners, cybersecurity teams, vendors, HR, legal, physical security, operations, and pro- curement. - Coordination should follow the organisation’s documented incident response plans. - A lead person should be assigned to each incident to manage the response and ensure clear communication. - If needed, additional plans, such as business continuity or disaster recovery, should be activated to support the response. - Information should be shared with the right people at the right time, following established communication procedures. - Different types of incidents should be recognised and handled accordingly: - Information incidents (e.g. accidental data exposure) - Cybersecurity incidents (e.g. malware, hacking) - OT incidents (e.g. disruptions to industrial control systems) - OT incidents should involve specialised OT personnel and may require different response procedures to protect safety and operations. |
|
A general note, for any purpose. |
The goal ofthis control is to ensure that all relevant internal and external stakeholderswork togethereffectively during a cybersecurity or information incident. To achieve this goal: - Incident response actions should be coordinated with predefined stakeholders, including business leaders, IT and OT system owners, cybersecurity teams, vendors, HR, legal, physical security, operations, and pro- curement. - Coordination should follow the organisation’s documented incident response plans. - A lead person should be assigned to each incident to manage the response and ensure clear communication. - If needed, additional plans, such as business continuity or disaster recovery, should be activated to support the response. - Information should be shared with the right people at the right time, following established communication procedures. - Different types of incidents should be recognised and handled accordingly: - Information incidents (e.g. accidental data exposure) - Cybersecurity incidents (e.g. malware, hacking) - OT incidents (e.g. disruptions to industrial control systems) - OT incidents should involve specialised OT personnel and may require different response procedures to protect safety and operations. |
|
A general note, for any purpose. |
<div><p>The goal ofthis control is to ensure that all relevant internal and external stakeholderswork togethereffectively during a cybersecurity or information incident. To achieve this goal:</p><ul><li>Incident response actions should be coordinated with predefined stakeholders, including business leaders, IT and OT system owners, cybersecurity teams, vendors, HR, legal, physical security, operations, and pro- curement.</li><li>Coordination should follow the organisation’s documented incident response plans.</li><li>A lead person should be assigned to each incident to manage the response and ensure clear communication.</li><li>If needed, additional plans, such as business continuity or disaster recovery, should be activated to support the response.</li><li>Information should be shared with the right people at the right time, following established communication procedures.</li><li>Different types of incidents should be recognised and handled accordingly:<ul><li>Information incidents (e.g. accidental data exposure)</li><li>Cybersecurity incidents (e.g. malware, hacking)</li><li>OT incidents (e.g. disruptions to industrial control systems)</li></ul></li><li>OT incidents should involve specialised OT personnel and may require different response procedures to protect safety and operations.</li></ul></div> |
|
A general note, for any purpose. |
The goal ofthis control is to ensure that all relevant internal and external stakeholderswork togethereffectively during a cybersecurity or information incident. To achieve this goal: • Incident response actions should be coordinated with predefined stakeholders, including business leaders, IT and OT system owners, cybersecurity teams, vendors, HR, legal, physical security, operations, and pro- curement. • Coordination should follow the organisation’s documented incident response plans. • A lead person should be assigned to each incident to manage the response and ensure clear communication. • If needed, additional plans, such as business continuity or disaster recovery, should be activated to support the response. • Information should be shared with the right people at the right time, following established communication procedures. • Different types of incidents should be recognised and handled accordingly: o Information incidents (e.g. accidental data exposure) o Cybersecurity incidents (e.g. malware, hacking) o OT incidents (e.g. disruptions to industrial control systems) • OT incidents should involve specialised OT personnel and may require different response procedures to protect safety and operations. |
|
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. |
RS.MA-01.2 |
|
skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties. |
Incident response stakeholder 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 information/cybersecurity incident response actions with all predefined stakeholders. |
|
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. |
|
|
The number of triples associated with the subject. |
19 |
|
Specifies the dataset the subject is part of. |
Resultaten 1 - 21 of 21
Inverse links to the subject.
| Property | Subject |
|---|---|
|
Relates a concept to a concept that is more specific in meaning. |
Resultaten 1 - 1 of 1