Direct links from the subject.
| Property | Value |
|---|---|
|
The subject is an instance of a class. |
|
|
The subject is an instance of a class. |
An idea or notion; a unit of thought. |
|
A human-readable name for the subject. |
GV.OC-01.1: The organisation's mission shall be established, communicated and shall form the basis for information and cybersecurity risk management. |
|
GV.OC-01.1 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p11 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_IMPORTANT_E_p11 |
|
|
Relates a concept to a concept that is more general in meaning. |
|
|
A general note, for any purpose. |
The goal of this control is to ensure that the organisation’s mission is clearly defined and communicated, and that it serves as the foundation for managing information and cybersecurity risks. Understanding the mission helps identify which risks could interfere with achieving strategic objectives. To achieve this goal, the following should be considered: - The organisation’s mission should be communicated through materials such asvision and mission statements, service strategies, or marketing documents. This helps guide risk identification and prioritisation. - Business processes and strategic goals should be developedwith consideration forinformation securityand cybersecurity. This includes understanding how risks may affect operations, assets, individuals, partners, or broader societal interests. - The need to protect sensitive information, including personal data, should be assessed based on the organi- sation’s mission and how its systems and services operate. - The mission and related business processes should be reviewed regularly, for example once a year, to ensure they remain relevant and continue to support effective risk management. |
|
A general note, for any purpose. |
The goal of this control is to ensure that the organisation’s mission is clearly defined and communicated, and that it serves as the foundation for managing information and cybersecurity risks. Understanding the mission helps identify which risks could interfere with achieving strategic objectives. To achieve this goal, the following should be considered: - The organisation’s mission should be communicated through materials such asvision and mission statements, service strategies, or marketing documents. This helps guide risk identification and prioritisation. - Business processes and strategic goals should be developedwith consideration forinformation securityand cybersecurity. This includes understanding how risks may affect operations, assets, individuals, partners, or broader societal interests. - The need to protect sensitive information, including personal data, should be assessed based on the organi- sation’s mission and how its systems and services operate. - The mission and related business processes should be reviewed regularly, for example once a year, to ensure they remain relevant and continue to support effective risk management. |
|
A general note, for any purpose. |
The goal of this control is to ensure that the organisation’s mission is clearly defined and communicated, and that it serves as the foundation for managing information and cybersecurity risks. Understanding the mission helps identify which risks could interfere with achieving strategic objectives. To achieve this goal, the following should be considered: • The organisation’s mission should be communicated through materials such asvision and mission statements, service strategies, or marketing documents. This helps guide risk identification and prioritisation. • Business processes and strategic goals should be developedwith consideration forinformation securityand cybersecurity. This includes understanding how risks may affect operations, assets, individuals, partners, or broader societal interests. • The need to protect sensitive information, including personal data, should be assessed based on the organi- sation’s mission and how its systems and services operate. • The mission and related business processes should be reviewed regularly, for example once a year, to ensure they remain relevant and continue to support effective risk management. |
|
A general note, for any purpose. |
<div><p>The goal of this control is to ensure that the organisation’s mission is clearly defined and communicated, and that it serves as the foundation for managing information and cybersecurity risks. Understanding the mission helps identify which risks could interfere with achieving strategic objectives. To achieve this goal, the following should be considered:</p><ul><li>The organisation’s mission should be communicated through materials such asvision and mission statements, service strategies, or marketing documents. This helps guide risk identification and prioritisation.</li><li>Business processes and strategic goals should be developedwith consideration forinformation securityand cybersecurity. This includes understanding how risks may affect operations, assets, individuals, partners, or broader societal interests.</li><li>The need to protect sensitive information, including personal data, should be assessed based on the organi- sation’s mission and how its systems and services operate.</li><li>The mission and related business processes should be reviewed regularly, for example once a year, to ensure they remain relevant and continue to support effective risk management.</li></ul></div> |
|
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-01.1 |
|
skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties. |
Organisational mission for cybersecurity |
|
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's mission shall be established, communicated and shall form the basis for information and cybersecurity risk management. |
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
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 |
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
The number of triples associated with the subject. |
19 |
|
Specifies the dataset the subject is part of. |
Resultaten 1 - 21 of 21
Inverse links to the subject.
| Property | Subject |
|---|---|
|
Relates a concept to a concept that is more specific in meaning. |
Resultaten 1 - 1 of 1