Concept skos:Concept Code RS.MA-05.1

Clear criteria shall be defined and applied to determine when incident recovery processes need to be initiated.

Also known as

skos:altLabel

Recovery initiation criteria

Note

skos:note

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.

Place in the list

For people working with the data

Identifier (URI) http://cyfun.data.gift/data/requirement_RS_MA_05_1
All data (21 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.MA-05.1: Clear criteria shall be defined and applied to determine when incident recovery processes need to be initiated.

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

RS.MA-05.1

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

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_IMPORTANT_E_p112

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

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p166

has broader

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

http://cyfun.data.gift/data/subcategory_RS.MA-05

note

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>

note

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.

note

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.

note

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.

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.MA-05.1

alternative label

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

Recovery initiation criteria

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.

Clear criteria shall be defined and applied to determine when incident recovery processes need to be initiated.

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_BASIC_to_IMPORTANT

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_IMPORTANT

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_IMPORTANT

triple count

The number of triples associated with the subject.

19

in dataset

Specifies the dataset the subject is part of.

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

Resultaten 1 - 21 of 21

References

Inverse links to the subject.