Concept skos:Concept Code GV.SC-07.2

A documented list of all critical suppliers, vendors and partners of the organisation that may be involved in a major incident shall be established, kept up-to-date and made available online and off-line with due regard to confidentiality and security.

Also known as

skos:altLabel

Critical supplier registry

Note

skos:note

The goal of this control is to ensure that a reliable, up-to-date list of critical suppliers, vendors, and partners is maintained and accessible, both online and offline, to support rapid response during major incidents, while safeguarding confidentiality and security. To achieve this goal:

  • Maintain a Comprehensive Record A complete list of suppliers, vendors, and partners should be maintained as a foundation for identifying those critical to operations, including OT environments.
  • Define Criticality Criteria Clear criteria should be established to classify supplier criticality based on factors such as:
    • Sensitivity of data handled
    • Access to systems or networks
    • Importance to core business or OT functions
  • Document Key Information For each critical supplier, the list should include:
    • Primary and secondary contact details
    • Description of services provided
    • Escalation paths and support availability
  • Ensure Online and Offline Availability The list should be:
    • Regularly updated and securely stored
    • Accessible both online and offline (e.g. printed copies, encrypted USBs) to ensure availability during cyber incidents or outages

Place in the list

For people working with the data

Identifier (URI) http://cyfun.data.gift/data/requirement_GV_SC_07_2
All data (19 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-07.2: A documented list of all critical suppliers, vendors and partners of the organisation that may be involved in a major incident shall be established, kept up-to-date and made available online and off-line with due regard to confidentiality and security.

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

GV.SC-07.2

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

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p38

has broader

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

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

note

A general note, for any purpose.

The goal of this control is to ensure that a reliable, up-to-date list of critical suppliers, vendors, and partners is maintained and accessible, both online and offline, to support rapid response during major incidents, while safeguarding confidentiality and security. To achieve this goal: • Maintain a Comprehensive Record A complete list of suppliers, vendors, and partners should be maintained as a foundation for identifying those critical to operations, including OT environments. • Define Criticality Criteria Clear criteria should be established to classify supplier criticality based on factors such as: o Sensitivity of data handled o Access to systems or networks o Importance to core business or OT functions • Document Key Information For each critical supplier, the list should include: o Primary and secondary contact details o Description of services provided o Escalation paths and support availability • Ensure Online and Offline Availability The list should be: o Regularly updated and securely stored o Accessible both online and offline (e.g. printed copies, encrypted USBs) to ensure availability during cyber incidents or outages

note

A general note, for any purpose.

<div><p>The goal of this control is to ensure that a reliable, up-to-date list of critical suppliers, vendors, and partners is maintained and accessible, both online and offline, to support rapid response during major incidents, while safeguarding confidentiality and security. To achieve this goal:</p><ul><li>Maintain a Comprehensive Record A complete list of suppliers, vendors, and partners should be maintained as a foundation for identifying those critical to operations, including OT environments.</li><li>Define Criticality Criteria Clear criteria should be established to classify supplier criticality based on factors such as:<ul><li>Sensitivity of data handled</li><li>Access to systems or networks</li><li>Importance to core business or OT functions</li></ul></li><li>Document Key Information For each critical supplier, the list should include:<ul><li>Primary and secondary contact details</li><li>Description of services provided</li><li>Escalation paths and support availability</li></ul></li><li>Ensure Online and Offline Availability The list should be:<ul><li>Regularly updated and securely stored</li><li>Accessible both online and offline (e.g. printed copies, encrypted USBs) to ensure availability during cyber incidents or outages</li></ul></li></ul></div>

note

A general note, for any purpose.

The goal of this control is to ensure that a reliable, up-to-date list of critical suppliers, vendors, and partners is maintained and accessible, both online and offline, to support rapid response during major incidents, while safeguarding confidentiality and security. To achieve this goal: - Maintain a Comprehensive Record A complete list of suppliers, vendors, and partners should be maintained as a foundation for identifying those critical to operations, including OT environments. - Define Criticality Criteria Clear criteria should be established to classify supplier criticality based on factors such as: - Sensitivity of data handled - Access to systems or networks - Importance to core business or OT functions - Document Key Information For each critical supplier, the list should include: - Primary and secondary contact details - Description of services provided - Escalation paths and support availability - Ensure Online and Offline Availability The list should be: - Regularly updated and securely stored - Accessible both online and offline (e.g. printed copies, encrypted USBs) to ensure availability during cyber incidents or outages

note

A general note, for any purpose.

The goal of this control is to ensure that a reliable, up-to-date list of critical suppliers, vendors, and partners is maintained and accessible, both online and offline, to support rapid response during major incidents, while safeguarding confidentiality and security. To achieve this goal: - Maintain a Comprehensive Record A complete list of suppliers, vendors, and partners should be maintained as a foundation for identifying those critical to operations, including OT environments. - Define Criticality Criteria Clear criteria should be established to classify supplier criticality based on factors such as: - Sensitivity of data handled - Access to systems or networks - Importance to core business or OT functions - Document Key Information For each critical supplier, the list should include: - Primary and secondary contact details - Description of services provided - Escalation paths and support availability - Ensure Online and Offline Availability The list should be: - Regularly updated and securely stored - Accessible both online and offline (e.g. printed copies, encrypted USBs) to ensure availability during cyber incidents or outages

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-07.2

alternative label

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

Critical supplier registry

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.

A documented list of all critical suppliers, vendors and partners of the organisation that may be involved in a major incident shall be established, kept up-to-date and made available online and off-line with due regard to confidentiality and security.

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_IMPORTANT_to_ESSENTIAL

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_ESSENTIAL

triple count

The number of triples associated with the subject.

17

in dataset

Specifies the dataset the subject is part of.

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

Resultaten 1 - 19 of 19

References

Inverse links to the subject.