Concept skos:Concept Code GV.SC-05.1

Requirements for addressing cybersecurity risks and the sharing of sensitive infor- mation in supply chains shall be established, prioritised, integrated into contracts and other types of formal agreements, and enforced.

Also known as

skos:altLabel

Supply chain cybersecurity contractual requirements

Note

skos:note

The goal of this control is to establish and enforce cybersecurity and sensitive data handling requirements in supply chain agreements, by integrating them into contracts and prioritising them based on risk. To make this happen, the following should be considered:

  • Contractual agreements and othertypes of formal agreementswith suppliers and otherrelevant third parties should define expectations, responsibilities, and security requirements.
  • Key elements of these agreements include information sharing between the organisation and its suppliers and sub-tier suppliers, security controls, incident response, and required compliance with standards and regulations.
  • Security requirements should be set for suppliers, products and services that are proportionate to the criticality and potential consequences if compromised.
  • All cybersecurity and supply chain requirements that third parties must comply with, should be included in standard contractual language (i.e., pre-drafted, commonly used terms and clauses that ensure consistency, compliance, and clarity). The contract should also specify how compliance with these requirements will be verified.
  • Considerto include in the enforcement that third-partyproviders and users (e.g. suppliers, customers, partners) should be able to demonstrate the understanding of their roles and responsibilities.
  • Consider defining security requirements in service-level agreements (SLAs) for monitoring suppliers for acceptable security performance throughout the supplier relationship lifecycle.
  • Consider to contractually require suppliers to vet their employees and guard against insider threats.
  • Consider to contractually require suppliers to provide evidence of performing acceptable security prac- tices through, for example, self-assessment (e.g. CyFun®), conformance to known standards, verifications (e.g. CyFun®), certifications (e.g. CyFun®), or inspections.
  • Keep in mind that GDPR requirements must be met if business information contains personal data (appli- cable at all levels), i.e. safeguards should be included in the contractual framework.

Place in the list

For people working with the data

Identifier (URI) http://cyfun.data.gift/data/requirement_GV_SC_05_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-05.1: Requirements for addressing cybersecurity risks and the sharing of sensitive infor- mation in supply chains shall be established, prioritised, integrated into contracts and other types of formal agreements, and enforced.

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

GV.SC-05.1

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

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p35

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

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_IMPORTANT_E_p27

has broader

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

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

note

A general note, for any purpose.

The goal of this control is to establish and enforce cybersecurity and sensitive data handling requirements in supply chain agreements, by integrating them into contracts and prioritising them based on risk. To make this happen, the following should be considered: • Contractual agreements and othertypes of formal agreementswith suppliers and otherrelevant third parties should define expectations, responsibilities, and security requirements. • Key elements of these agreements include information sharing between the organisation and its suppliers and sub-tier suppliers, security controls, incident response, and required compliance with standards and regulations. • Security requirements should be set for suppliers, products and services that are proportionate to the criticality and potential consequences if compromised. • All cybersecurity and supply chain requirements that third parties must comply with, should be included in standard contractual language (i.e., pre-drafted, commonly used terms and clauses that ensure consistency, compliance, and clarity). The contract should also specify how compliance with these requirements will be verified. • Considerto include in the enforcement that third-partyproviders and users (e.g. suppliers, customers, partners) should be able to demonstrate the understanding of their roles and responsibilities. • Consider defining security requirements in service-level agreements (SLAs) for monitoring suppliers for acceptable security performance throughout the supplier relationship lifecycle. • Consider to contractually require suppliers to vet their employees and guard against insider threats. • Consider to contractually require suppliers to provide evidence of performing acceptable security prac- tices through, for example, self-assessment (e.g. CyFun®), conformance to known standards, verifications (e.g. CyFun®), certifications (e.g. CyFun®), or inspections. • Keep in mind that GDPR requirements must be met if business information contains personal data (appli- cable at all levels), i.e. safeguards should be included in the contractual framework.

note

A general note, for any purpose.

The goal of this control is to establish and enforce cybersecurity and sensitive data handling requirements in supply chain agreements, by integrating them into contracts and prioritising them based on risk. To make this happen, the following should be considered: - Contractual agreements and othertypes of formal agreementswith suppliers and otherrelevant third parties should define expectations, responsibilities, and security requirements. - Key elements of these agreements include information sharing between the organisation and its suppliers and sub-tier suppliers, security controls, incident response, and required compliance with standards and regulations. - Security requirements should be set for suppliers, products and services that are proportionate to the criticality and potential consequences if compromised. - All cybersecurity and supply chain requirements that third parties must comply with, should be included in standard contractual language (i.e., pre-drafted, commonly used terms and clauses that ensure consistency, compliance, and clarity). The contract should also specify how compliance with these requirements will be verified. - Considerto include in the enforcement that third-partyproviders and users (e.g. suppliers, customers, partners) should be able to demonstrate the understanding of their roles and responsibilities. - Consider defining security requirements in service-level agreements (SLAs) for monitoring suppliers for acceptable security performance throughout the supplier relationship lifecycle. - Consider to contractually require suppliers to vet their employees and guard against insider threats. - Consider to contractually require suppliers to provide evidence of performing acceptable security prac- tices through, for example, self-assessment (e.g. CyFun®), conformance to known standards, verifications (e.g. CyFun®), certifications (e.g. CyFun®), or inspections. - Keep in mind that GDPR requirements must be met if business information contains personal data (appli- cable at all levels), i.e. safeguards should be included in the contractual framework.

note

A general note, for any purpose.

<div><p>The goal of this control is to establish and enforce cybersecurity and sensitive data handling requirements in supply chain agreements, by integrating them into contracts and prioritising them based on risk. To make this happen, the following should be considered:</p><ul><li>Contractual agreements and othertypes of formal agreementswith suppliers and otherrelevant third parties should define expectations, responsibilities, and security requirements.</li><li>Key elements of these agreements include information sharing between the organisation and its suppliers and sub-tier suppliers, security controls, incident response, and required compliance with standards and regulations.</li><li>Security requirements should be set for suppliers, products and services that are proportionate to the criticality and potential consequences if compromised.</li><li>All cybersecurity and supply chain requirements that third parties must comply with, should be included in standard contractual language (i.e., pre-drafted, commonly used terms and clauses that ensure consistency, compliance, and clarity). The contract should also specify how compliance with these requirements will be verified.</li><li>Considerto include in the enforcement that third-partyproviders and users (e.g. suppliers, customers, partners) should be able to demonstrate the understanding of their roles and responsibilities.</li><li>Consider defining security requirements in service-level agreements (SLAs) for monitoring suppliers for acceptable security performance throughout the supplier relationship lifecycle.</li><li>Consider to contractually require suppliers to vet their employees and guard against insider threats.</li><li>Consider to contractually require suppliers to provide evidence of performing acceptable security prac- tices through, for example, self-assessment (e.g. CyFun®), conformance to known standards, verifications (e.g. CyFun®), certifications (e.g. CyFun®), or inspections.</li><li>Keep in mind that GDPR requirements must be met if business information contains personal data (appli- cable at all levels), i.e. safeguards should be included in the contractual framework.</li></ul></div>

note

A general note, for any purpose.

The goal of this control is to establish and enforce cybersecurity and sensitive data handling requirements in supply chain agreements, by integrating them into contracts and prioritising them based on risk. To make this happen, the following should be considered: - Contractual agreements and othertypes of formal agreementswith suppliers and otherrelevant third parties should define expectations, responsibilities, and security requirements. - Key elements of these agreements include information sharing between the organisation and its suppliers and sub-tier suppliers, security controls, incident response, and required compliance with standards and regulations. - Security requirements should be set for suppliers, products and services that are proportionate to the criticality and potential consequences if compromised. - All cybersecurity and supply chain requirements that third parties must comply with, should be included in standard contractual language (i.e., pre-drafted, commonly used terms and clauses that ensure consistency, compliance, and clarity). The contract should also specify how compliance with these requirements will be verified. - Considerto include in the enforcement that third-partyproviders and users (e.g. suppliers, customers, partners) should be able to demonstrate the understanding of their roles and responsibilities. - Consider defining security requirements in service-level agreements (SLAs) for monitoring suppliers for acceptable security performance throughout the supplier relationship lifecycle. - Consider to contractually require suppliers to vet their employees and guard against insider threats. - Consider to contractually require suppliers to provide evidence of performing acceptable security prac- tices through, for example, self-assessment (e.g. CyFun®), conformance to known standards, verifications (e.g. CyFun®), certifications (e.g. CyFun®), or inspections. - Keep in mind that GDPR requirements must be met if business information contains personal data (appli- cable at all levels), i.e. safeguards should be included in the contractual framework.

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

alternative label

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

Supply chain cybersecurity contractual requirements

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.

Requirements for addressing cybersecurity risks and the sharing of sensitive infor- mation in supply chains shall be established, prioritised, integrated into contracts and other types of formal agreements, and enforced.

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.