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. |
RS.AN-07.1: Incident data and metadata shall be collected and protected to ensure their accuracy, authenticity, and traceability. |
|
RS.AN-07.1 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p168 |
|
|
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 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. |
|
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. |
|
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> |
|
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. |
|
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 |
|
skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties. |
Incident data collection and protection |
|
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. |
|
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. |
http://cyfun.data.gift/data/CyFun2025_delta_IMPORTANT_to_ESSENTIAL |
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
The number of triples associated with the subject. |
17 |
|
Specifies the dataset the subject is part of. |
Resultaten 1 - 19 of 19
Inverse links to the subject.
| Property | Subject |
|---|---|
|
Relates a concept to a concept that is more specific in meaning. |
Resultaten 1 - 1 of 1