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-03.1: Legal and regulatory requirements regarding information and cybersecurity shall be identified and implemented. |
|
GV.OC-03.1 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_BASIC_E_p9 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p13 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_IMPORTANT_E_p12 |
|
|
Relates a concept to a concept that is more general in meaning. |
|
|
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> |
|
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 - (…) |
|
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 - (…) |
|
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 (…) |
|
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 |
|
skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties. |
Legal and regulatory requirements identification |
|
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. |
|
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. |
|
|
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. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
The number of triples associated with the subject. |
21 |
|
Specifies the dataset the subject is part of. |
Resultaten 1 - 23 of 23
Inverse links to the subject.
| Property | Subject |
|---|---|
|
Relates a concept to a concept that is more specific in meaning. |
Resultaten 1 - 1 of 1