Concept skos:Concept Code GV.OC-03.1

Legal and regulatory requirements regarding information and cybersecurity shall be identified and implemented.

Also known as

skos:altLabel

Legal and regulatory requirements identification

Note

skos:note

The goal of this control is to ensure that legal, regulatory, and contractual requirements related to information security and cybersecurity are identified, monitored, and implemented. To achieve this goal, the following should be considered:

  • A process should be established to track and apply relevant legal and regulatory requirements related to both information security and cybersecurity.
  • These requirements should be integrated into all relevant policies, procedures, and operational practices.
  • The areas that should be covered include, but are not limited to:
    • Risk assessments and protection of information systems
    • Incident response, business continuity, and crisis management
    • Supply chain security and secure system development
    • Vulnerability management and secure configuration
    • Security awareness and training
    • Cryptographic controls and secure communications
    • Emergency communication systems
    • Access control, asset management, and Multi-Factor Authentication (MFA)
    • Coordinated vulnerability disclosure
    • (…)

Place in the list

For people working with the data

Identifier (URI) http://cyfun.data.gift/data/requirement_GV_OC_03_1
All data (23 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-03.1: Legal and regulatory requirements regarding information and cybersecurity shall be identified and implemented.

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

GV.OC-03.1

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

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_BASIC_E_p9

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

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p13

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

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_IMPORTANT_E_p12

has broader

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

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

note

A general note, for any purpose.

<div><p>The goal of this control is to ensure that legal, regulatory, and contractual requirements related to information security and cybersecurity are identified, monitored, and implemented. To achieve this goal, the following should be considered:</p><ul><li>A process should be established to track and apply relevant legal and regulatory requirements related to both information security and cybersecurity.</li><li>These requirements should be integrated into all relevant policies, procedures, and operational practices.</li><li>The areas that should be covered include, but are not limited to:<ul><li>Risk assessments and protection of information systems</li><li>Incident response, business continuity, and crisis management</li><li>Supply chain security and secure system development</li><li>Vulnerability management and secure configuration</li><li>Security awareness and training</li><li>Cryptographic controls and secure communications</li><li>Emergency communication systems</li><li>Access control, asset management, and Multi-Factor Authentication (MFA)</li><li>Coordinated vulnerability disclosure</li><li>(…)</li></ul></li></ul></div>

note

A general note, for any purpose.

The goal of this control is to ensure that legal, regulatory, and contractual requirements related to information security and cybersecurity are identified, monitored, and implemented. To achieve this goal, the following should be considered: - A process should be established to track and apply relevant legal and regulatory requirements related to both information security and cybersecurity. - These requirements should be integrated into all relevant policies, procedures, and operational practices. - The areas that should be covered include, but are not limited to: - Risk assessments and protection of information systems - Incident response, business continuity, and crisis management - Supply chain security and secure system development - Vulnerability management and secure configuration - Security awareness and training - Cryptographic controls and secure communications - Emergency communication systems - Access control, asset management, and Multi-Factor Authentication (MFA) - Coordinated vulnerability disclosure - (…)

note

A general note, for any purpose.

The goal of this control is to ensure that legal, regulatory, and contractual requirements related to information security and cybersecurity are identified, monitored, and implemented. To achieve this goal, the following should be considered: - A process should be established to track and apply relevant legal and regulatory requirements related to both information security and cybersecurity. - These requirements should be integrated into all relevant policies, procedures, and operational practices. - The areas that should be covered include, but are not limited to: - Risk assessments and protection of information systems - Incident response, business continuity, and crisis management - Supply chain security and secure system development - Vulnerability management and secure configuration - Security awareness and training - Cryptographic controls and secure communications - Emergency communication systems - Access control, asset management, and Multi-Factor Authentication (MFA) - Coordinated vulnerability disclosure - (…)

note

A general note, for any purpose.

The goal of this control is to ensure that legal, regulatory, and contractual requirements related to information security and cybersecurity are identified, monitored, and implemented. To achieve this goal, the following should be considered: • A process should be established to track and apply relevant legal and regulatory requirements related to both information security and cybersecurity. • These requirements should be integrated into all relevant policies, procedures, and operational practices. • The areas that should be covered include, but are not limited to: o Risk assessments and protection of information systems o Incident response, business continuity, and crisis management o Supply chain security and secure system development o Vulnerability management and secure configuration o Security awareness and training o Cryptographic controls and secure communications o Emergency communication systems o Access control, asset management, and Multi-Factor Authentication (MFA) o Coordinated vulnerability disclosure o (…)

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

alternative label

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

Legal and regulatory requirements identification

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.

Legal and regulatory requirements regarding information and cybersecurity shall be identified and implemented.

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

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_BASIC

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_BASIC

triple count

The number of triples associated with the subject.

21

in dataset

Specifies the dataset the subject is part of.

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

Resultaten 1 - 23 of 23

References

Inverse links to the subject.