Concept skos:Concept Code 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.

Also known as

skos:altLabel

Supplier incident planning contacts

Note

skos:note

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.

Place in the list

For people working with the data

Identifier (URI) http://cyfun.data.gift/data/requirement_GV_SC_08_1
All data (21 statements)

Properties and relations

Direct links from the subject.

Property Value

type

The subject is an instance of a class.

http://cyfun.data.gift/ontology#Requirement

type

The subject is an instance of a class.

Concept

An idea or notion; a unit of thought.

label

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.

http://cyfun.data.gift/ontology#requirementId

GV.SC-08.1

http://cyfun.data.gift/ontology#foundIn

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p40

http://cyfun.data.gift/ontology#foundIn

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_IMPORTANT_E_p28

has broader

Relates a concept to a concept that is more general in meaning.

http://cyfun.data.gift/data/subcategory_GV.SC-08

note

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.

note

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>

note

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.

note

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.

notation

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

alternative label

skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties.

Supplier incident planning contacts

preferred label

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.

is in scheme

Relates a resource (for example a concept) to a concept scheme in which it is included.

http://cyfun.data.gift/data/CyFun2025

is in scheme

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

is in scheme

Relates a resource (for example a concept) to a concept scheme in which it is included.

http://cyfun.data.gift/data/CyFun2025_IMPORTANT

is in scheme

Relates a resource (for example a concept) to a concept scheme in which it is included.

http://cyfun.data.gift/data/CyFun2025_ESSENTIAL

http://cyfun.data.gift/ontology#level

http://cyfun.data.gift/data/level_IMPORTANT

triple count

The number of triples associated with the subject.

19

in dataset

Specifies the dataset the subject is part of.

http://data.gift/d/datasets/69E8863AA6CE46D9ACD13109

Resultaten 1 - 21 of 21

References

Inverse links to the subject.