Concept skos:Concept Code GV.SC-05.3

The organisation shall establish contractual requirements permitting the organisation to review the information/cybersecurity programs implemented by suppliers and third-party partners.

Also known as

skos:altLabel

Supplier security programme review rights

Note

skos:note

The goal of this control is to ensure that the organisation can assess and verify the information/cybersecurity practices of suppliers and third-party partners through contractual agreements. To achieve this goal:

  • Information/Cybersecurity Requirements Contracts should define clear information/cybersecurity expectations, including OT-specific controls where relevant.
  • Audit and Review Rights Agreements should grant the organisation the right to audit, assess, or review the information/cybersecurity programs of suppliers and partners.
  • Verification Methods Conformance should be verified through self-assessments, third-party certifications, or scheduled security evaluations.
  • Information Sharing Protocols Contracts should specify what information/cybersecurity-related information must be shared, how often, and through which channels.
  • Continuous Monitoring Suppliers should regularly report on their information/cybersecurity posture and disclose incidents that could impact operations, especially in OT environments.
  • Non-Compliance Consequences Contracts should outline consequences for failing to meet information/cybersecurity requirements, such as penalties or contract termination.

Place in the list

For people working with the data

Identifier (URI) http://cyfun.data.gift/data/requirement_GV_SC_05_3
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.3: The organisation shall establish contractual requirements permitting the organisation to review the information/cybersecurity programs implemented by suppliers and third-party partners.

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

GV.SC-05.3

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

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p36

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 ensure that the organisation can assess and verify the information/cybersecurity practices of suppliers and third-party partners through contractual agreements. To achieve this goal: • Information/Cybersecurity Requirements Contracts should define clear information/cybersecurity expectations, including OT-specific controls where relevant. • Audit and Review Rights Agreements should grant the organisation the right to audit, assess, or review the information/cybersecurity programs of suppliers and partners. • Verification Methods Conformance should be verified through self-assessments, third-party certifications, or scheduled security evaluations. • Information Sharing Protocols Contracts should specify what information/cybersecurity-related information must be shared, how often, and through which channels. • Continuous Monitoring Suppliers should regularly report on their information/cybersecurity posture and disclose incidents that could impact operations, especially in OT environments. • Non-Compliance Consequences Contracts should outline consequences for failing to meet information/cybersecurity requirements, such as penalties or contract termination.

note

A general note, for any purpose.

<div><p>The goal of this control is to ensure that the organisation can assess and verify the information/cybersecurity practices of suppliers and third-party partners through contractual agreements. To achieve this goal:</p><ul><li>Information/Cybersecurity Requirements Contracts should define clear information/cybersecurity expectations, including OT-specific controls where relevant.</li><li>Audit and Review Rights Agreements should grant the organisation the right to audit, assess, or review the information/cybersecurity programs of suppliers and partners.</li><li>Verification Methods Conformance should be verified through self-assessments, third-party certifications, or scheduled security evaluations.</li><li>Information Sharing Protocols Contracts should specify what information/cybersecurity-related information must be shared, how often, and through which channels.</li><li>Continuous Monitoring Suppliers should regularly report on their information/cybersecurity posture and disclose incidents that could impact operations, especially in OT environments.</li><li>Non-Compliance Consequences Contracts should outline consequences for failing to meet information/cybersecurity requirements, such as penalties or contract termination.</li></ul></div>

note

A general note, for any purpose.

The goal of this control is to ensure that the organisation can assess and verify the information/cybersecurity practices of suppliers and third-party partners through contractual agreements. To achieve this goal: - Information/Cybersecurity Requirements Contracts should define clear information/cybersecurity expectations, including OT-specific controls where relevant. - Audit and Review Rights Agreements should grant the organisation the right to audit, assess, or review the information/cybersecurity programs of suppliers and partners. - Verification Methods Conformance should be verified through self-assessments, third-party certifications, or scheduled security evaluations. - Information Sharing Protocols Contracts should specify what information/cybersecurity-related information must be shared, how often, and through which channels. - Continuous Monitoring Suppliers should regularly report on their information/cybersecurity posture and disclose incidents that could impact operations, especially in OT environments. - Non-Compliance Consequences Contracts should outline consequences for failing to meet information/cybersecurity requirements, such as penalties or contract termination.

note

A general note, for any purpose.

The goal of this control is to ensure that the organisation can assess and verify the information/cybersecurity practices of suppliers and third-party partners through contractual agreements. To achieve this goal: - Information/Cybersecurity Requirements Contracts should define clear information/cybersecurity expectations, including OT-specific controls where relevant. - Audit and Review Rights Agreements should grant the organisation the right to audit, assess, or review the information/cybersecurity programs of suppliers and partners. - Verification Methods Conformance should be verified through self-assessments, third-party certifications, or scheduled security evaluations. - Information Sharing Protocols Contracts should specify what information/cybersecurity-related information must be shared, how often, and through which channels. - Continuous Monitoring Suppliers should regularly report on their information/cybersecurity posture and disclose incidents that could impact operations, especially in OT environments. - Non-Compliance Consequences Contracts should outline consequences for failing to meet information/cybersecurity requirements, such as penalties or contract termination.

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.3

alternative label

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

Supplier security programme review rights

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 establish contractual requirements permitting the organisation to review the information/cybersecurity programs implemented by suppliers and third-party partners.

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_KeyMeasures

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

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

1

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.