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.MA-05.1: Clear criteria shall be defined and applied to determine when incident recovery processes need to be initiated. |
|
RS.MA-05.1 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_IMPORTANT_E_p112 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p166 |
|
|
Relates a concept to a concept that is more general in meaning. |
|
|
A general note, for any purpose. |
<div><p>The goal of this control is to ensure that organisations have a clear, consistent, and risk-informed decision-making process for determining when to begin recovery actions following a cybersecurity incident. Therefore the following should be considered:</p><ul><li>Criteria for initiating incident recovery should be based on the known or assumed characteristics of the incident, such as its severity, scope, and potential impact on operations, data, or systems.</li><li>The decision to begin recovery should also consider the potential disruption that recovery activities may cause to ongoing operations.</li><li>Recovery Point Objectives (RPO) and RecoveryTime Objectives (RTO) should be included in the criteria to ensure that recovery actions align with business continuity requirements and acceptable downtime or data loss thresholds.</li></ul></div> |
|
A general note, for any purpose. |
The goal of this control is to ensure that organisations have a clear, consistent, and risk-informed decision-making process for determining when to begin recovery actions following a cybersecurity incident. Therefore the following should be considered: - Criteria for initiating incident recovery should be based on the known or assumed characteristics of the incident, such as its severity, scope, and potential impact on operations, data, or systems. - The decision to begin recovery should also consider the potential disruption that recovery activities may cause to ongoing operations. - Recovery Point Objectives (RPO) and RecoveryTime Objectives (RTO) should be included in the criteria to ensure that recovery actions align with business continuity requirements and acceptable downtime or data loss thresholds. |
|
A general note, for any purpose. |
The goal of this control is to ensure that organisations have a clear, consistent, and risk-informed decision-making process for determining when to begin recovery actions following a cybersecurity incident. Therefore the following should be considered: - Criteria for initiating incident recovery should be based on the known or assumed characteristics of the incident, such as its severity, scope, and potential impact on operations, data, or systems. - The decision to begin recovery should also consider the potential disruption that recovery activities may cause to ongoing operations. - Recovery Point Objectives (RPO) and RecoveryTime Objectives (RTO) should be included in the criteria to ensure that recovery actions align with business continuity requirements and acceptable downtime or data loss thresholds. |
|
A general note, for any purpose. |
The goal of this control is to ensure that organisations have a clear, consistent, and risk-informed decision-making process for determining when to begin recovery actions following a cybersecurity incident. Therefore the following should be considered: • Criteria for initiating incident recovery should be based on the known or assumed characteristics of the incident, such as its severity, scope, and potential impact on operations, data, or systems. • The decision to begin recovery should also consider the potential disruption that recovery activities may cause to ongoing operations. • Recovery Point Objectives (RPO) and RecoveryTime Objectives (RTO) should be included in the criteria to ensure that recovery actions align with business continuity requirements and acceptable downtime or data loss thresholds. |
|
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.MA-05.1 |
|
skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties. |
Recovery initiation criteria |
|
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. |
Clear criteria shall be defined and applied to determine when incident recovery processes need to be initiated. |
|
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_BASIC_to_IMPORTANT |
|
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. |
|
|
The number of triples associated with the subject. |
19 |
|
Specifies the dataset the subject is part of. |
Resultaten 1 - 21 of 21
Inverse links to the subject.
| Property | Subject |
|---|---|
|
Relates a concept to a concept that is more specific in meaning. |
Resultaten 1 - 1 of 1