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. |
ID.AM-07.1: Data that the organisation stores and uses shall be identified. |
|
ID.AM-07.1 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_BASIC_E_p18 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p54 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_IMPORTANT_E_p38 |
|
|
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 all data stored and used by the organisation is clearly identified. This supports proper data management, protection, and alignment with business and regulatory requirements. To achieve this goal, the following should be considered: - Data Identification All types of data, regardless of format, location, or system, should be identified and recorded. - Data Classification Identified data should be classified using standard categories such as: - Public - Internal - Confidential - Restricted - Data-to-Asset Mapping Data should be linked to the assets that store or process it, including physical devices, systems, software, and applications listed in the inventories from ID.AM-01 and ID.AM-02. - Documentation and Maintenance Data types, classifications, and associated assets should be documented and regularly updated to reflect changes in the environment. |
|
A general note, for any purpose. |
<div><p>The goal of this control is to ensure that all data stored and used by the organisation is clearly identified. This supports proper data management, protection, and alignment with business and regulatory requirements. To achieve this goal, the following should be considered:</p><ul><li>Data Identification All types of data, regardless of format, location, or system, should be identified and recorded.</li><li>Data Classification Identified data should be classified using standard categories such as:<ul><li>Public</li><li>Internal</li><li>Confidential</li><li>Restricted</li></ul></li><li>Data-to-Asset Mapping Data should be linked to the assets that store or process it, including physical devices, systems, software, and applications listed in the inventories from ID.AM-01 and ID.AM-02.</li><li>Documentation and Maintenance Data types, classifications, and associated assets should be documented and regularly updated to reflect changes in the environment.</li></ul></div> |
|
A general note, for any purpose. |
The goal of this control is to ensure that all data stored and used by the organisation is clearly identified. This supports proper data management, protection, and alignment with business and regulatory requirements. To achieve this goal, the following should be considered: • Data Identification All types of data, regardless of format, location, or system, should be identified and recorded. • Data Classification Identified data should be classified using standard categories such as: o Public o Internal o Confidential o Restricted • Data-to-Asset Mapping Data should be linked to the assets that store or process it, including physical devices, systems, software, and applications listed in the inventories from ID.AM-01 and ID.AM-02. • Documentation and Maintenance Data types, classifications, and associated assets should be documented and regularly updated to reflect changes in the environment. |
|
A general note, for any purpose. |
The goal of this control is to ensure that all data stored and used by the organisation is clearly identified. This supports proper data management, protection, and alignment with business and regulatory requirements. To achieve this goal, the following should be considered: - Data Identification All types of data, regardless of format, location, or system, should be identified and recorded. - Data Classification Identified data should be classified using standard categories such as: - Public - Internal - Confidential - Restricted - Data-to-Asset Mapping Data should be linked to the assets that store or process it, including physical devices, systems, software, and applications listed in the inventories from ID.AM-01 and ID.AM-02. - Documentation and Maintenance Data types, classifications, and associated assets should be documented and regularly updated to reflect changes in the environment. |
|
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. |
ID.AM-07.1 |
|
skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties. |
Data 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. |
Data that the organisation stores and uses shall be identified. |
|
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