Concept skos:Concept Code GV.OC-02.1

The organisation shall demonstrate it understands and considers the needs and expectations of both internal and external stakeholders regarding information and cybersecurity risk management.

Also known as

skos:altLabel

Stakeholder needs and expectations

Note

skos:note

The goal of this control is to ensure that the organisation understands and takes into account the needs and expectations of both internal and external stakeholders when managing information and cybersecurity risks. This helps to align cybersecurity efforts with business priorities, legal obligations, and stakeholder trust. To achieve this goal, the following should be considered:

  • The organisation should identify key internal stakeholders such as employees, senior management, board members, and internal auditors.Theirroles, responsibilities, and expectations related to cybersecurityshould be understood and documented.
  • Key external stakeholders, including customers, suppliers, partners, regulators, shareholders, service pro- viders, and external auditors, should be identified, and their compliance, contractual, and data protection expectations should be considered.
  • Stakeholder needs and expectations should be gathered through methods such as interviews, surveys, contract reviews, or regulatory analysis.
  • These insights should be integrated into the organisation’s cybersecurityrisk management strategyto ensure alignment with business and regulatory priorities.
  • Regular communication channels should be established to keep stakeholders informed and engaged in cybersecurity matters.
  • Stakeholder expectations should be reviewed and updated periodically, especially when there are changes in business operations, legal requirements, or risk exposure.

Place in the list

For people working with the data

Identifier (URI) http://cyfun.data.gift/data/requirement_GV_OC_02_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.OC-02.1: The organisation shall demonstrate it understands and considers the needs and expectations of both internal and external stakeholders regarding information and cybersecurity risk management.

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

GV.OC-02.1

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

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p12

has broader

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

http://cyfun.data.gift/data/subcategory_GV.OC-02

note

A general note, for any purpose.

<div><p>The goal of this control is to ensure that the organisation understands and takes into account the needs and expectations of both internal and external stakeholders when managing information and cybersecurity risks. This helps to align cybersecurity efforts with business priorities, legal obligations, and stakeholder trust. To achieve this goal, the following should be considered:</p><ul><li>The organisation should identify key internal stakeholders such as employees, senior management, board members, and internal auditors.Theirroles, responsibilities, and expectations related to cybersecurityshould be understood and documented.</li><li>Key external stakeholders, including customers, suppliers, partners, regulators, shareholders, service pro- viders, and external auditors, should be identified, and their compliance, contractual, and data protection expectations should be considered.</li><li>Stakeholder needs and expectations should be gathered through methods such as interviews, surveys, contract reviews, or regulatory analysis.</li><li>These insights should be integrated into the organisation’s cybersecurityrisk management strategyto ensure alignment with business and regulatory priorities.</li><li>Regular communication channels should be established to keep stakeholders informed and engaged in cybersecurity matters.</li><li>Stakeholder expectations should be reviewed and updated periodically, especially when there are changes in business operations, legal requirements, or risk exposure.</li></ul></div>

note

A general note, for any purpose.

The goal of this control is to ensure that the organisation understands and takes into account the needs and expectations of both internal and external stakeholders when managing information and cybersecurity risks. This helps to align cybersecurity efforts with business priorities, legal obligations, and stakeholder trust. To achieve this goal, the following should be considered: • The organisation should identify key internal stakeholders such as employees, senior management, board members, and internal auditors.Theirroles, responsibilities, and expectations related to cybersecurityshould be understood and documented. • Key external stakeholders, including customers, suppliers, partners, regulators, shareholders, service pro- viders, and external auditors, should be identified, and their compliance, contractual, and data protection expectations should be considered. • Stakeholder needs and expectations should be gathered through methods such as interviews, surveys, contract reviews, or regulatory analysis. • These insights should be integrated into the organisation’s cybersecurityrisk management strategyto ensure alignment with business and regulatory priorities. • Regular communication channels should be established to keep stakeholders informed and engaged in cybersecurity matters. • Stakeholder expectations should be reviewed and updated periodically, especially when there are changes in business operations, legal requirements, or risk exposure.

note

A general note, for any purpose.

The goal of this control is to ensure that the organisation understands and takes into account the needs and expectations of both internal and external stakeholders when managing information and cybersecurity risks. This helps to align cybersecurity efforts with business priorities, legal obligations, and stakeholder trust. To achieve this goal, the following should be considered: - The organisation should identify key internal stakeholders such as employees, senior management, board members, and internal auditors.Theirroles, responsibilities, and expectations related to cybersecurityshould be understood and documented. - Key external stakeholders, including customers, suppliers, partners, regulators, shareholders, service pro- viders, and external auditors, should be identified, and their compliance, contractual, and data protection expectations should be considered. - Stakeholder needs and expectations should be gathered through methods such as interviews, surveys, contract reviews, or regulatory analysis. - These insights should be integrated into the organisation’s cybersecurityrisk management strategyto ensure alignment with business and regulatory priorities. - Regular communication channels should be established to keep stakeholders informed and engaged in cybersecurity matters. - Stakeholder expectations should be reviewed and updated periodically, especially when there are changes in business operations, legal requirements, or risk exposure.

note

A general note, for any purpose.

The goal of this control is to ensure that the organisation understands and takes into account the needs and expectations of both internal and external stakeholders when managing information and cybersecurity risks. This helps to align cybersecurity efforts with business priorities, legal obligations, and stakeholder trust. To achieve this goal, the following should be considered: - The organisation should identify key internal stakeholders such as employees, senior management, board members, and internal auditors.Theirroles, responsibilities, and expectations related to cybersecurityshould be understood and documented. - Key external stakeholders, including customers, suppliers, partners, regulators, shareholders, service pro- viders, and external auditors, should be identified, and their compliance, contractual, and data protection expectations should be considered. - Stakeholder needs and expectations should be gathered through methods such as interviews, surveys, contract reviews, or regulatory analysis. - These insights should be integrated into the organisation’s cybersecurityrisk management strategyto ensure alignment with business and regulatory priorities. - Regular communication channels should be established to keep stakeholders informed and engaged in cybersecurity matters. - Stakeholder expectations should be reviewed and updated periodically, especially when there are changes in business operations, legal requirements, or risk exposure.

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.OC-02.1

alternative label

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

Stakeholder needs and expectations

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 demonstrate it understands and considers the needs and expectations of both internal and external stakeholders regarding information and cybersecurity risk management.

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.