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-08.1: A n incident’s magnitude shall be estimated and validated. |
|
RS.AN-08.1 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p169 |
|
|
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 organisations have a clear understanding of the full scope and impact of a cybersecurity incident, so that response actions can be appropriately scaled, prioritised, and coordinated. Therefore the following should be considered: • The scope and impact of an incident should be assessed by examining not only the initially affected system but also other systems or devices that may be compromised. • Indicators of Compromise (IoCs), such as unusual network activity, unauthorised access attempts, or unex- pected software changes, should be identified to understand how far the incident has spread. • Signs of persistence, including backdoors or malware that allow continued access, should be investigated to determine whether the attacker remains active in the environment. • Automated tools should be used to scan for IoCs and persistence mechanisms across potentially affected assets to support timely and thorough analysis. • The validated magnitude of the incident should inform how the incident is categorised, prioritised, and escalated, as described in RS.MA-03.1 (Important), ensuring that response actions are aligned with the actual risk and business impact. |
|
A general note, for any purpose. |
The goal of this control is to ensure that organisations have a clear understanding of the full scope and impact of a cybersecurity incident, so that response actions can be appropriately scaled, prioritised, and coordinated. Therefore the following should be considered: - The scope and impact of an incident should be assessed by examining not only the initially affected system but also other systems or devices that may be compromised. - Indicators of Compromise (IoCs), such as unusual network activity, unauthorised access attempts, or unex- pected software changes, should be identified to understand how far the incident has spread. - Signs of persistence, including backdoors or malware that allow continued access, should be investigated to determine whether the attacker remains active in the environment. - Automated tools should be used to scan for IoCs and persistence mechanisms across potentially affected assets to support timely and thorough analysis. - The validated magnitude of the incident should inform how the incident is categorised, prioritised, and escalated, as described in RS.MA-03.1 (Important), ensuring that response actions are aligned with the actual risk and business impact. |
|
A general note, for any purpose. |
The goal of this control is to ensure that organisations have a clear understanding of the full scope and impact of a cybersecurity incident, so that response actions can be appropriately scaled, prioritised, and coordinated. Therefore the following should be considered: - The scope and impact of an incident should be assessed by examining not only the initially affected system but also other systems or devices that may be compromised. - Indicators of Compromise (IoCs), such as unusual network activity, unauthorised access attempts, or unex- pected software changes, should be identified to understand how far the incident has spread. - Signs of persistence, including backdoors or malware that allow continued access, should be investigated to determine whether the attacker remains active in the environment. - Automated tools should be used to scan for IoCs and persistence mechanisms across potentially affected assets to support timely and thorough analysis. - The validated magnitude of the incident should inform how the incident is categorised, prioritised, and escalated, as described in RS.MA-03.1 (Important), ensuring that response actions are aligned with the actual risk and business impact. |
|
A general note, for any purpose. |
<div><p>The goal of this control is to ensure that organisations have a clear understanding of the full scope and impact of a cybersecurity incident, so that response actions can be appropriately scaled, prioritised, and coordinated. Therefore the following should be considered:</p><ul><li>The scope and impact of an incident should be assessed by examining not only the initially affected system but also other systems or devices that may be compromised.</li><li>Indicators of Compromise (IoCs), such as unusual network activity, unauthorised access attempts, or unex- pected software changes, should be identified to understand how far the incident has spread.</li><li>Signs of persistence, including backdoors or malware that allow continued access, should be investigated to determine whether the attacker remains active in the environment.</li><li>Automated tools should be used to scan for IoCs and persistence mechanisms across potentially affected assets to support timely and thorough analysis.</li><li>The validated magnitude of the incident should inform how the incident is categorised, prioritised, and escalated, as described in RS.MA-03.1 (Important), ensuring that response actions are aligned with the actual risk and business impact.</li></ul></div> |
|
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-08.1 |
|
skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties. |
Incident magnitude estimation |
|
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. |
A n incident’s magnitude shall be estimated and validated. |
|
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