Concept skos:Concept Code GV.PO-01.2

Organisational-wide information and cybersecurity policies and procedures shall include the use of cryptography and, where appropriate, encryption, reflect changes in requirements, threats, technology and organisational roles, and be approved by senior management, who oversee its implementation. This control builds further on GV.PO-01.1 and focuses on the content and oversight of the cyberand information security policies themselves. It ensures that specific technical topics (such as cryptography and encryption) are addressed, policies are responsive to change and Senior leadership is actively involved in approval and oversight. Consider the following elements to be covered: · Define Scope & Objectives Ensure policies apply organisation-wide and align with business and risk priorities. · Include Cryptography & Encryption · Address encryption at-rest/in-transit, key management, and approved algorithms. · Define where encryption is required (e.g., personal data, remote access). · Keep Policies Current Update policies to reflect changes in: · Legal/regulatory requirements · Threat landscape · Technology · Organisational structure · Senior Management Oversight · Require formal approval by senior leadership. · Assign a policy owner (e.g., CISO) to oversee implementation and compliance. · Assign Roles & Responsibilities · Use ENISA ECSF Role Profiles https://www.enisa.europa.eu/publications/european-cybersecurity-skills-framework-role-profiles) to: · Define cybersecurity roles (e.g., Policy Officer, Risk Manager) · Align tasks, skills, and competencies · Communicate & Train Disseminate policies and provide role-specific training. · Monitor & Enforce Use technical controls and audits to ensure compliance.

Also known as

skos:altLabel

Cryptography and encryption policy

Place in the list

For people working with the data

Identifier (URI) http://cyfun.data.gift/data/requirement_GV_PO_01_2
All data (17 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.PO-01.2: Organisational-wide information and cybersecurity policies and procedures shall include the use of cryptography and, where appropriate, encryption, reflect changes in requirements, threats, technology and organisational roles, and be approved by senior management, who oversee its implementation. This control builds further on GV.PO-01.1 and focuses on the content and oversight of the cyberand information security policies themselves. It ensures that specific technical topics (such as cryptography and encryption) are addressed, policies are responsive to change and Senior leadership is actively involved in approval and oversight. Consider the following elements to be covered: · Define Scope & Objectives Ensure policies apply organisation-wide and align with business and risk priorities. · Include Cryptography & Encryption · Address encryption at-rest/in-transit, key management, and approved algorithms. · Define where encryption is required (e.g., personal data, remote access). · Keep Policies Current Update policies to reflect changes in: · Legal/regulatory requirements · Threat landscape · Technology · Organisational structure · Senior Management Oversight · Require formal approval by senior leadership. · Assign a policy owner (e.g., CISO) to oversee implementation and compliance. · Assign Roles & Responsibilities · Use ENISA ECSF Role Profiles https://www.enisa.europa.eu/publications/european-cybersecurity-skills-framework-role-profiles) to: · Define cybersecurity roles (e.g., Policy Officer, Risk Manager) · Align tasks, skills, and competencies · Communicate & Train Disseminate policies and provide role-specific training. · Monitor & Enforce Use technical controls and audits to ensure compliance.

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

GV.PO-01.2

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

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p29

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

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_IMPORTANT_E_p25

has broader

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

http://cyfun.data.gift/data/subcategory_GV.PO-01

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.PO-01.2

alternative label

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

Cryptography and encryption policy

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.

Organisational-wide information and cybersecurity policies and procedures shall include the use of cryptography and, where appropriate, encryption, reflect changes in requirements, threats, technology and organisational roles, and be approved by senior management, who oversee its implementation. This control builds further on GV.PO-01.1 and focuses on the content and oversight of the cyberand information security policies themselves. It ensures that specific technical topics (such as cryptography and encryption) are addressed, policies are responsive to change and Senior leadership is actively involved in approval and oversight. Consider the following elements to be covered: · Define Scope & Objectives Ensure policies apply organisation-wide and align with business and risk priorities. · Include Cryptography & Encryption · Address encryption at-rest/in-transit, key management, and approved algorithms. · Define where encryption is required (e.g., personal data, remote access). · Keep Policies Current Update policies to reflect changes in: · Legal/regulatory requirements · Threat landscape · Technology · Organisational structure · Senior Management Oversight · Require formal approval by senior leadership. · Assign a policy owner (e.g., CISO) to oversee implementation and compliance. · Assign Roles & Responsibilities · Use ENISA ECSF Role Profiles https://www.enisa.europa.eu/publications/european-cybersecurity-skills-framework-role-profiles) to: · Define cybersecurity roles (e.g., Policy Officer, Risk Manager) · Align tasks, skills, and competencies · Communicate & Train Disseminate policies and provide role-specific training. · Monitor & Enforce Use technical controls and audits to ensure compliance.

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.

15

in dataset

Specifies the dataset the subject is part of.

http://data.gift/d/datasets/69E8863AA6CE46D9ACD13109

Resultaten 1 - 17 of 17

References

Inverse links to the subject.