Concept skos:Concept Code GV.SC-10.1

Cybersecurity supply chain risk management plans shall include actions and respon- sibilities for managing risks that may arise after a supplier relationship or service agreement has ended.

Also known as

skos:altLabel

Post-termination supply chain risk management

Note

skos:note

The goal of this control is to ensure that residual cybersecurity and information security risks are effectively addressed after supplier relationships end, thereby preventing disruptions, data exposure, and vulnerabilities in operational and OT environments. To achieve this goal:

  • Plan for Termination of the Relationship Formal offboarding procedures should be defined for ending supplier relationships under both normal and adverse conditions, including breach, insolvency, or security incidents.
  • Ensure Secure Transition or Exit Transition plans should be developed for critical services, to maintain continuity and address supply chain resilience, including fallback suppliers or internal alternatives.
  • Revoke Access and Secure Data Supplieraccess to systems, networks, and data should be promptlyrevoked.All credentials and remote access tools should be deactivated or removed.
  • Protect Organisational Assets Devices, storage media, and documents containing organisational data should be securely returned or sani- tised. Controls should prevent unauthorised retention or leakage of sensitive information.
  • Address Component Obsolescence Plans should be in place to manage end-of-life components or services, ensuring continued support or secure replacements, especially for OT systems.
  • Monitor Residual Risks Post-termination risks should be identified, assessed, and escalated to senior management when necessary. These risks should be tracked within the enterprise risk management process.

Place in the list

For people working with the data

Identifier (URI) http://cyfun.data.gift/data/requirement_GV_SC_10_1
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-10.1: Cybersecurity supply chain risk management plans shall include actions and respon- sibilities for managing risks that may arise after a supplier relationship or service agreement has ended.

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

GV.SC-10.1

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

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p42

has broader

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

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

note

A general note, for any purpose.

<div><p>The goal of this control is to ensure that residual cybersecurity and information security risks are effectively addressed after supplier relationships end, thereby preventing disruptions, data exposure, and vulnerabilities in operational and OT environments. To achieve this goal:</p><ul><li>Plan for Termination of the Relationship Formal offboarding procedures should be defined for ending supplier relationships under both normal and adverse conditions, including breach, insolvency, or security incidents.</li><li>Ensure Secure Transition or Exit Transition plans should be developed for critical services, to maintain continuity and address supply chain resilience, including fallback suppliers or internal alternatives.</li><li>Revoke Access and Secure Data Supplieraccess to systems, networks, and data should be promptlyrevoked.All credentials and remote access tools should be deactivated or removed.</li><li>Protect Organisational Assets Devices, storage media, and documents containing organisational data should be securely returned or sani- tised. Controls should prevent unauthorised retention or leakage of sensitive information.</li><li>Address Component Obsolescence Plans should be in place to manage end-of-life components or services, ensuring continued support or secure replacements, especially for OT systems.</li><li>Monitor Residual Risks Post-termination risks should be identified, assessed, and escalated to senior management when necessary. These risks should be tracked within the enterprise risk management process.</li></ul></div>

note

A general note, for any purpose.

The goal of this control is to ensure that residual cybersecurity and information security risks are effectively addressed after supplier relationships end, thereby preventing disruptions, data exposure, and vulnerabilities in operational and OT environments. To achieve this goal: • Plan for Termination of the Relationship Formal offboarding procedures should be defined for ending supplier relationships under both normal and adverse conditions, including breach, insolvency, or security incidents. • Ensure Secure Transition or Exit Transition plans should be developed for critical services, to maintain continuity and address supply chain resilience, including fallback suppliers or internal alternatives. • Revoke Access and Secure Data Supplieraccess to systems, networks, and data should be promptlyrevoked.All credentials and remote access tools should be deactivated or removed. • Protect Organisational Assets Devices, storage media, and documents containing organisational data should be securely returned or sani- tised. Controls should prevent unauthorised retention or leakage of sensitive information. • Address Component Obsolescence Plans should be in place to manage end-of-life components or services, ensuring continued support or secure replacements, especially for OT systems. • Monitor Residual Risks Post-termination risks should be identified, assessed, and escalated to senior management when necessary. These risks should be tracked within the enterprise risk management process.

note

A general note, for any purpose.

The goal of this control is to ensure that residual cybersecurity and information security risks are effectively addressed after supplier relationships end, thereby preventing disruptions, data exposure, and vulnerabilities in operational and OT environments. To achieve this goal: - Plan for Termination of the Relationship Formal offboarding procedures should be defined for ending supplier relationships under both normal and adverse conditions, including breach, insolvency, or security incidents. - Ensure Secure Transition or Exit Transition plans should be developed for critical services, to maintain continuity and address supply chain resilience, including fallback suppliers or internal alternatives. - Revoke Access and Secure Data Supplieraccess to systems, networks, and data should be promptlyrevoked.All credentials and remote access tools should be deactivated or removed. - Protect Organisational Assets Devices, storage media, and documents containing organisational data should be securely returned or sani- tised. Controls should prevent unauthorised retention or leakage of sensitive information. - Address Component Obsolescence Plans should be in place to manage end-of-life components or services, ensuring continued support or secure replacements, especially for OT systems. - Monitor Residual Risks Post-termination risks should be identified, assessed, and escalated to senior management when necessary. These risks should be tracked within the enterprise risk management process.

note

A general note, for any purpose.

The goal of this control is to ensure that residual cybersecurity and information security risks are effectively addressed after supplier relationships end, thereby preventing disruptions, data exposure, and vulnerabilities in operational and OT environments. To achieve this goal: - Plan for Termination of the Relationship Formal offboarding procedures should be defined for ending supplier relationships under both normal and adverse conditions, including breach, insolvency, or security incidents. - Ensure Secure Transition or Exit Transition plans should be developed for critical services, to maintain continuity and address supply chain resilience, including fallback suppliers or internal alternatives. - Revoke Access and Secure Data Supplieraccess to systems, networks, and data should be promptlyrevoked.All credentials and remote access tools should be deactivated or removed. - Protect Organisational Assets Devices, storage media, and documents containing organisational data should be securely returned or sani- tised. Controls should prevent unauthorised retention or leakage of sensitive information. - Address Component Obsolescence Plans should be in place to manage end-of-life components or services, ensuring continued support or secure replacements, especially for OT systems. - Monitor Residual Risks Post-termination risks should be identified, assessed, and escalated to senior management when necessary. These risks should be tracked within the enterprise risk management process.

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

alternative label

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

Post-termination supply chain risk management

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.

Cybersecurity supply chain risk management plans shall include actions and respon- sibilities for managing risks that may arise after a supplier relationship or service agreement has ended.

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.