Concept skos:Concept Code ID.AM-07.2

Inventories of data and associated metadata shall be maintained for designated data types.

Also known as

skos:altLabel

Data inventory and metadata management

Note

skos:note

The goal of this control is to ensure that inventories of data and their associated metadata are maintained for all data types explicitly selected or designated by policy or guidelines (for example, customer data, financial infor- mation, or production data). This supports secure data management, regulatory compliance, and operational integrity across ICT and OT environments. To achieve this goal:

  • Define a Data Classification Scheme A classification scheme should be established to categorise data types based on sensitivity and usage. This scheme should guide how data is handled, protected, and retained.
  • Apply Security Measures by Classification Level Appropriate securitycontrols should be implemented foreach classification level.These mayinclude encryp- tion, role-based access controls, and tailored data retention policies.
  • Identify and Protect Sensitive Data Types Inventories should include sensitive data such as:
    • Personally identifiable information (PII)
    • Financial and health information
    • Confidential business data
    • Intellectual property
    • Government and personnel records OT environments should also include operational data critical to safety and reliability.
  • Track Metadata for Each Data Instance Metadata should be maintained to support data governance. This includes:
    • Descriptive metadata (e.g. title, author, keywords)
    • Structural metadata (e.g. format, schema)
    • Administrative metadata (e.g. access rights, retention policy)
    • Technical metadata (e.g. encoding, checksum)
  • Monitor Data Provenance and Location The origin, ownership, and geolocation of each data instance should be documented. This helps to under- stand where and how data is stored and processed, especially in distributed or OT systems.
  • Continuously Discover and Analyse Ad Hoc Data Processes should be in place to identify new instances of sensitive data not captured by initial inventories. This helps address gaps in data flow mapping and supports ongoing data protection.
  • Consider Using the Traffic Light Protocol (TLP) TLP should be considered as a method to classify and share cybersecurity-related data, especially in incident response and threat intelligence contexts.

Place in the list

For people working with the data

Identifier (URI) http://cyfun.data.gift/data/requirement_ID_AM_07_2
All data (21 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.

ID.AM-07.2: Inventories of data and associated metadata shall be maintained for designated data types.

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

ID.AM-07.2

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

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p55

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

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_IMPORTANT_E_p39

has broader

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

http://cyfun.data.gift/data/subcategory_ID.AM-07

note

A general note, for any purpose.

The goal of this control is to ensure that inventories of data and their associated metadata are maintained for all data types explicitly selected or designated by policy or guidelines (for example, customer data, financial infor- mation, or production data). This supports secure data management, regulatory compliance, and operational integrity across ICT and OT environments. To achieve this goal: • Define a Data Classification Scheme A classification scheme should be established to categorise data types based on sensitivity and usage. This scheme should guide how data is handled, protected, and retained. • Apply Security Measures by Classification Level Appropriate securitycontrols should be implemented foreach classification level.These mayinclude encryp- tion, role-based access controls, and tailored data retention policies. • Identify and Protect Sensitive Data Types Inventories should include sensitive data such as: o Personally identifiable information (PII) o Financial and health information o Confidential business data o Intellectual property o Government and personnel records OT environments should also include operational data critical to safety and reliability. • Track Metadata for Each Data Instance Metadata should be maintained to support data governance. This includes: o Descriptive metadata (e.g. title, author, keywords) o Structural metadata (e.g. format, schema) o Administrative metadata (e.g. access rights, retention policy) o Technical metadata (e.g. encoding, checksum) • Monitor Data Provenance and Location The origin, ownership, and geolocation of each data instance should be documented. This helps to under- stand where and how data is stored and processed, especially in distributed or OT systems. • Continuously Discover and Analyse Ad Hoc Data Processes should be in place to identify new instances of sensitive data not captured by initial inventories. This helps address gaps in data flow mapping and supports ongoing data protection. • Consider Using the Traffic Light Protocol (TLP) TLP should be considered as a method to classify and share cybersecurity-related data, especially in incident response and threat intelligence contexts.

note

A general note, for any purpose.

The goal of this control is to ensure that inventories of data and their associated metadata are maintained for all data types explicitly selected or designated by policy or guidelines (for example, customer data, financial infor- mation, or production data). This supports secure data management, regulatory compliance, and operational integrity across ICT and OT environments. To achieve this goal: - Define a Data Classification Scheme A classification scheme should be established to categorise data types based on sensitivity and usage. This scheme should guide how data is handled, protected, and retained. - Apply Security Measures by Classification Level Appropriate securitycontrols should be implemented foreach classification level.These mayinclude encryp- tion, role-based access controls, and tailored data retention policies. - Identify and Protect Sensitive Data Types Inventories should include sensitive data such as: - Personally identifiable information (PII) - Financial and health information - Confidential business data - Intellectual property - Government and personnel records OT environments should also include operational data critical to safety and reliability. - Track Metadata for Each Data Instance Metadata should be maintained to support data governance. This includes: - Descriptive metadata (e.g. title, author, keywords) - Structural metadata (e.g. format, schema) - Administrative metadata (e.g. access rights, retention policy) - Technical metadata (e.g. encoding, checksum) - Monitor Data Provenance and Location The origin, ownership, and geolocation of each data instance should be documented. This helps to under- stand where and how data is stored and processed, especially in distributed or OT systems. - Continuously Discover and Analyse Ad Hoc Data Processes should be in place to identify new instances of sensitive data not captured by initial inventories. This helps address gaps in data flow mapping and supports ongoing data protection. - Consider Using the Traffic Light Protocol (TLP) TLP should be considered as a method to classify and share cybersecurity-related data, especially in incident response and threat intelligence contexts.

note

A general note, for any purpose.

<div><p>The goal of this control is to ensure that inventories of data and their associated metadata are maintained for all data types explicitly selected or designated by policy or guidelines (for example, customer data, financial infor- mation, or production data). This supports secure data management, regulatory compliance, and operational integrity across ICT and OT environments. To achieve this goal:</p><ul><li>Define a Data Classification Scheme A classification scheme should be established to categorise data types based on sensitivity and usage. This scheme should guide how data is handled, protected, and retained.</li><li>Apply Security Measures by Classification Level Appropriate securitycontrols should be implemented foreach classification level.These mayinclude encryp- tion, role-based access controls, and tailored data retention policies.</li><li>Identify and Protect Sensitive Data Types Inventories should include sensitive data such as:<ul><li>Personally identifiable information (PII)</li><li>Financial and health information</li><li>Confidential business data</li><li>Intellectual property</li><li>Government and personnel records OT environments should also include operational data critical to safety and reliability.</li></ul></li><li>Track Metadata for Each Data Instance Metadata should be maintained to support data governance. This includes:<ul><li>Descriptive metadata (e.g. title, author, keywords)</li><li>Structural metadata (e.g. format, schema)</li><li>Administrative metadata (e.g. access rights, retention policy)</li><li>Technical metadata (e.g. encoding, checksum)</li></ul></li><li>Monitor Data Provenance and Location The origin, ownership, and geolocation of each data instance should be documented. This helps to under- stand where and how data is stored and processed, especially in distributed or OT systems.</li><li>Continuously Discover and Analyse Ad Hoc Data Processes should be in place to identify new instances of sensitive data not captured by initial inventories. This helps address gaps in data flow mapping and supports ongoing data protection.</li><li>Consider Using the Traffic Light Protocol (TLP) TLP should be considered as a method to classify and share cybersecurity-related data, especially in incident response and threat intelligence contexts.</li></ul></div>

note

A general note, for any purpose.

The goal of this control is to ensure that inventories of data and their associated metadata are maintained for all data types explicitly selected or designated by policy or guidelines (for example, customer data, financial infor- mation, or production data). This supports secure data management, regulatory compliance, and operational integrity across ICT and OT environments. To achieve this goal: - Define a Data Classification Scheme A classification scheme should be established to categorise data types based on sensitivity and usage. This scheme should guide how data is handled, protected, and retained. - Apply Security Measures by Classification Level Appropriate securitycontrols should be implemented foreach classification level.These mayinclude encryp- tion, role-based access controls, and tailored data retention policies. - Identify and Protect Sensitive Data Types Inventories should include sensitive data such as: - Personally identifiable information (PII) - Financial and health information - Confidential business data - Intellectual property - Government and personnel records OT environments should also include operational data critical to safety and reliability. - Track Metadata for Each Data Instance Metadata should be maintained to support data governance. This includes: - Descriptive metadata (e.g. title, author, keywords) - Structural metadata (e.g. format, schema) - Administrative metadata (e.g. access rights, retention policy) - Technical metadata (e.g. encoding, checksum) - Monitor Data Provenance and Location The origin, ownership, and geolocation of each data instance should be documented. This helps to under- stand where and how data is stored and processed, especially in distributed or OT systems. - Continuously Discover and Analyse Ad Hoc Data Processes should be in place to identify new instances of sensitive data not captured by initial inventories. This helps address gaps in data flow mapping and supports ongoing data protection. - Consider Using the Traffic Light Protocol (TLP) TLP should be considered as a method to classify and share cybersecurity-related data, especially in incident response and threat intelligence contexts.

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.

ID.AM-07.2

alternative label

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

Data inventory and metadata management

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.

Inventories of data and associated metadata shall be maintained for designated data types.

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.

19

in dataset

Specifies the dataset the subject is part of.

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

Resultaten 1 - 21 of 21

References

Inverse links to the subject.