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. |
GV.SC-08.1: The organisation shall identify and document key personnel from relevant suppliers and other third parties to include them in incident planning, response, and recovery activities. |
|
GV.SC-08.1 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p40 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_IMPORTANT_E_p28 |
|
|
Relates a concept to a concept that is more general in meaning. |
|
|
A general note, for any purpose. |
The goal ofthis control is to strengthen incident preparedness and recoverybyensuring that keypersonnel from critical suppliers and third parties are identified and actively integrated into response planning and execution. To achieve this goal: - Establish Communication Protocols Clear rules and procedures should be defined for reporting incident status and coordinating response and recovery activities between the organisation and its business-critical suppliers. - Define Roles and Responsibilities Roles, responsibilities, and authority for incident response should be documented for both internal teams and third-party participants, including those supporting OT systems and infrastructure. - Promote Joint Learning Collaborative lessons-learned sessions should be conductedwith critical suppliers and third parties following major incidents to improve future coordination and resilience. |
|
A general note, for any purpose. |
<div><p>The goal ofthis control is to strengthen incident preparedness and recoverybyensuring that keypersonnel from critical suppliers and third parties are identified and actively integrated into response planning and execution. To achieve this goal:</p><ul><li>Establish Communication Protocols Clear rules and procedures should be defined for reporting incident status and coordinating response and recovery activities between the organisation and its business-critical suppliers.</li><li>Define Roles and Responsibilities Roles, responsibilities, and authority for incident response should be documented for both internal teams and third-party participants, including those supporting OT systems and infrastructure.</li><li>Promote Joint Learning Collaborative lessons-learned sessions should be conductedwith critical suppliers and third parties following major incidents to improve future coordination and resilience.</li></ul></div> |
|
A general note, for any purpose. |
The goal ofthis control is to strengthen incident preparedness and recoverybyensuring that keypersonnel from critical suppliers and third parties are identified and actively integrated into response planning and execution. To achieve this goal: • Establish Communication Protocols Clear rules and procedures should be defined for reporting incident status and coordinating response and recovery activities between the organisation and its business-critical suppliers. • Define Roles and Responsibilities Roles, responsibilities, and authority for incident response should be documented for both internal teams and third-party participants, including those supporting OT systems and infrastructure. • Promote Joint Learning Collaborative lessons-learned sessions should be conductedwith critical suppliers and third parties following major incidents to improve future coordination and resilience. |
|
A general note, for any purpose. |
The goal ofthis control is to strengthen incident preparedness and recoverybyensuring that keypersonnel from critical suppliers and third parties are identified and actively integrated into response planning and execution. To achieve this goal: - Establish Communication Protocols Clear rules and procedures should be defined for reporting incident status and coordinating response and recovery activities between the organisation and its business-critical suppliers. - Define Roles and Responsibilities Roles, responsibilities, and authority for incident response should be documented for both internal teams and third-party participants, including those supporting OT systems and infrastructure. - Promote Joint Learning Collaborative lessons-learned sessions should be conductedwith critical suppliers and third parties following major incidents to improve future coordination and resilience. |
|
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. |
GV.SC-08.1 |
|
skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties. |
Supplier incident planning contacts |
|
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 identify and document key personnel from relevant suppliers and other third parties to include them in incident planning, response, and recovery activities. |
|
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