Concept skos:Concept Code RS.AN-07.1

Incident data and metadata shall be collected and protected to ensure their accuracy, authenticity, and traceability.

Also known as

skos:altLabel

Incident data collection and protection

Note

skos:note

The goal of this control is to ensure that all relevant information about a cybersecurity incident is accurately captured, securely stored, and reliably traceable, so it can be used effectively for response, investigation, and legal or compliance purposes. Therefore the following should be considered:

  • Incident data and metadata (such as the source of the data and the time it was collected) should be gathered and stored in a way that protects them from tampering or loss.
  • The integrity and origin of this information should be preserved using methods such as:
    • Chain of custody documentation to track how the data is handled from collection to analysis.
    • Digital signatures and encryption to prevent unauthorised access and confirm authenticity.
    • Audit logs to record who accessed or changed the data and when.
  • Collecting and protecting this information should support:
    • Timely response by helping to understand when and how the incident occurred.
    • Investigation and analysis by providing reliable details about the incident’s cause, scope, and impact.
    • Legal and compliance needs by ensuring the data can be used as evidence if required.

Place in the list

For people working with the data

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

RS.AN-07.1: Incident data and metadata shall be collected and protected to ensure their accuracy, authenticity, and traceability.

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

RS.AN-07.1

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

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p168

has broader

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

http://cyfun.data.gift/data/subcategory_RS.AN-07

note

A general note, for any purpose.

The goal of this control is to ensure that all relevant information about a cybersecurity incident is accurately captured, securely stored, and reliably traceable, so it can be used effectively for response, investigation, and legal or compliance purposes. Therefore the following should be considered: • Incident data and metadata (such as the source of the data and the time it was collected) should be gathered and stored in a way that protects them from tampering or loss. • The integrity and origin of this information should be preserved using methods such as: o Chain of custody documentation to track how the data is handled from collection to analysis. o Digital signatures and encryption to prevent unauthorised access and confirm authenticity. o Audit logs to record who accessed or changed the data and when. • Collecting and protecting this information should support: o Timely response by helping to understand when and how the incident occurred. o Investigation and analysis by providing reliable details about the incident’s cause, scope, and impact. o Legal and compliance needs by ensuring the data can be used as evidence if required.

note

A general note, for any purpose.

The goal of this control is to ensure that all relevant information about a cybersecurity incident is accurately captured, securely stored, and reliably traceable, so it can be used effectively for response, investigation, and legal or compliance purposes. Therefore the following should be considered: - Incident data and metadata (such as the source of the data and the time it was collected) should be gathered and stored in a way that protects them from tampering or loss. - The integrity and origin of this information should be preserved using methods such as: - Chain of custody documentation to track how the data is handled from collection to analysis. - Digital signatures and encryption to prevent unauthorised access and confirm authenticity. - Audit logs to record who accessed or changed the data and when. - Collecting and protecting this information should support: - Timely response by helping to understand when and how the incident occurred. - Investigation and analysis by providing reliable details about the incident’s cause, scope, and impact. - Legal and compliance needs by ensuring the data can be used as evidence if required.

note

A general note, for any purpose.

<div><p>The goal of this control is to ensure that all relevant information about a cybersecurity incident is accurately captured, securely stored, and reliably traceable, so it can be used effectively for response, investigation, and legal or compliance purposes. Therefore the following should be considered:</p><ul><li>Incident data and metadata (such as the source of the data and the time it was collected) should be gathered and stored in a way that protects them from tampering or loss.</li><li>The integrity and origin of this information should be preserved using methods such as:<ul><li>Chain of custody documentation to track how the data is handled from collection to analysis.</li><li>Digital signatures and encryption to prevent unauthorised access and confirm authenticity.</li><li>Audit logs to record who accessed or changed the data and when.</li></ul></li><li>Collecting and protecting this information should support:<ul><li>Timely response by helping to understand when and how the incident occurred.</li><li>Investigation and analysis by providing reliable details about the incident’s cause, scope, and impact.</li><li>Legal and compliance needs by ensuring the data can be used as evidence if required.</li></ul></li></ul></div>

note

A general note, for any purpose.

The goal of this control is to ensure that all relevant information about a cybersecurity incident is accurately captured, securely stored, and reliably traceable, so it can be used effectively for response, investigation, and legal or compliance purposes. Therefore the following should be considered: - Incident data and metadata (such as the source of the data and the time it was collected) should be gathered and stored in a way that protects them from tampering or loss. - The integrity and origin of this information should be preserved using methods such as: - Chain of custody documentation to track how the data is handled from collection to analysis. - Digital signatures and encryption to prevent unauthorised access and confirm authenticity. - Audit logs to record who accessed or changed the data and when. - Collecting and protecting this information should support: - Timely response by helping to understand when and how the incident occurred. - Investigation and analysis by providing reliable details about the incident’s cause, scope, and impact. - Legal and compliance needs by ensuring the data can be used as evidence if required.

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.

RS.AN-07.1

alternative label

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

Incident data collection and protection

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.

Incident data and metadata shall be collected and protected to ensure their accuracy, authenticity, and traceability.

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.