Concept skos:Concept Code PR.DS-01.2

The organisation shall implement automated tools where feasible to provide notifi- cation upon discovering discrepancies during integrity verification.

Also known as

skos:altLabel

Automated integrity violation notification

Note

skos:note

The goal of this control is to ensure that discrepancies in system or data integrity are detected and reported automatically, enabling timely response and reducing the risk of undetected tampering, especially in environ- ments where operational continuity and safety are critical. To achieve this goal, the organisation should:

  • Implement automated tools where feasible to continuously verify the integrity of critical data and systems.
  • Ensure these tools promptly report integrity violations when discrepancies are detected.
  • Configure alerts to notify relevant personnel, such as system administrators, business owners, and infor- mation security officers, to enable swift investigation and response.
  • Use centrally managed integrityverification solutions to streamline monitoring and reporting across both IT (Information Technology) and OT (Operational Technology) environments.
  • Follow guidance from ENISA, such as the NIS2 Technical Implementation Guidance (ENISA, 2025), which outlines best practices for automated integrity monitoring and incident response.

Place in the list

For people working with the data

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

PR.DS-01.2: The organisation shall implement automated tools where feasible to provide notifi- cation upon discovering discrepancies during integrity verification.

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

PR.DS-01.2

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

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p110

has broader

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

http://cyfun.data.gift/data/subcategory_PR.DS-01

note

A general note, for any purpose.

The goal of this control is to ensure that discrepancies in system or data integrity are detected and reported automatically, enabling timely response and reducing the risk of undetected tampering, especially in environ- ments where operational continuity and safety are critical. To achieve this goal, the organisation should: • Implement automated tools where feasible to continuously verify the integrity of critical data and systems. • Ensure these tools promptly report integrity violations when discrepancies are detected. • Configure alerts to notify relevant personnel, such as system administrators, business owners, and infor- mation security officers, to enable swift investigation and response. • Use centrally managed integrityverification solutions to streamline monitoring and reporting across both IT (Information Technology) and OT (Operational Technology) environments. • Follow guidance from ENISA, such as the NIS2 Technical Implementation Guidance (ENISA, 2025), which outlines best practices for automated integrity monitoring and incident response.

note

A general note, for any purpose.

The goal of this control is to ensure that discrepancies in system or data integrity are detected and reported automatically, enabling timely response and reducing the risk of undetected tampering, especially in environ- ments where operational continuity and safety are critical. To achieve this goal, the organisation should: - Implement automated tools where feasible to continuously verify the integrity of critical data and systems. - Ensure these tools promptly report integrity violations when discrepancies are detected. - Configure alerts to notify relevant personnel, such as system administrators, business owners, and infor- mation security officers, to enable swift investigation and response. - Use centrally managed integrityverification solutions to streamline monitoring and reporting across both IT (Information Technology) and OT (Operational Technology) environments. - Follow guidance from ENISA, such as the NIS2 Technical Implementation Guidance (ENISA, 2025), which outlines best practices for automated integrity monitoring and incident response.

note

A general note, for any purpose.

<div><p>The goal of this control is to ensure that discrepancies in system or data integrity are detected and reported automatically, enabling timely response and reducing the risk of undetected tampering, especially in environ- ments where operational continuity and safety are critical. To achieve this goal, the organisation should:</p><ul><li>Implement automated tools where feasible to continuously verify the integrity of critical data and systems.</li><li>Ensure these tools promptly report integrity violations when discrepancies are detected.</li><li>Configure alerts to notify relevant personnel, such as system administrators, business owners, and infor- mation security officers, to enable swift investigation and response.</li><li>Use centrally managed integrityverification solutions to streamline monitoring and reporting across both IT (Information Technology) and OT (Operational Technology) environments.</li><li>Follow guidance from ENISA, such as the NIS2 Technical Implementation Guidance (ENISA, 2025), which outlines best practices for automated integrity monitoring and incident response.</li></ul></div>

note

A general note, for any purpose.

The goal of this control is to ensure that discrepancies in system or data integrity are detected and reported automatically, enabling timely response and reducing the risk of undetected tampering, especially in environ- ments where operational continuity and safety are critical. To achieve this goal, the organisation should: - Implement automated tools where feasible to continuously verify the integrity of critical data and systems. - Ensure these tools promptly report integrity violations when discrepancies are detected. - Configure alerts to notify relevant personnel, such as system administrators, business owners, and infor- mation security officers, to enable swift investigation and response. - Use centrally managed integrityverification solutions to streamline monitoring and reporting across both IT (Information Technology) and OT (Operational Technology) environments. - Follow guidance from ENISA, such as the NIS2 Technical Implementation Guidance (ENISA, 2025), which outlines best practices for automated integrity monitoring and incident response.

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.

PR.DS-01.2

alternative label

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

Automated integrity violation notification

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.

The organisation shall implement automated tools where feasible to provide notifi- cation upon discovering discrepancies during integrity verification.

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_IMPORTANT_to_ESSENTIAL

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_ESSENTIAL

triple count

The number of triples associated with the subject.

17

in dataset

Specifies the dataset the subject is part of.

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

Resultaten 1 - 19 of 19

References

Inverse links to the subject.