Concept skos:Concept Code RC.CO-03.1

Recovery activities and progress in restoring operational capabilities shall be communicated to designated internal and external stakeholders in accordance with established communication procedures.

Also known as

skos:altLabel

Recovery progress communication

Note

skos:note

The goal of this control is to ensure that recovery efforts and the progress of restoring operational capabilities are clearly and consistently communicated to all relevant internal and external stakeholders. This supports transparency, coordination, and informed decision-making during the recovery phase of an incident. To achieve this goal the following should be considered:

  • Recovery updates, including progress on restoring systems and services, should be shared securely and consistently with internal and external stakeholders, in line with the organisation’s response plans and information-sharing agreements.
  • Senior leadership should receive regular updates on the status of recovery efforts, especially during major incidents.
  • Communication protocols defined in contracts with suppliers and partners should be followed to ensure timely and accurate information exchange.
  • Crisis communication with critical suppliers should be coordinated to support aligned recovery actions.
  • If no actual incidents have occurred, tabletop exercises should be conducted to test and validate recovery communication procedures and stakeholder coordination.

Place in the list

For people working with the data

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

RC.CO-03.1: Recovery activities and progress in restoring operational capabilities shall be communicated to designated internal and external stakeholders in accordance with established communication procedures.

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

RC.CO-03.1

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

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p180

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

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_IMPORTANT_E_p121

has broader

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

http://cyfun.data.gift/data/subcategory_RC.CO-03

note

A general note, for any purpose.

<div><p>The goal of this control is to ensure that recovery efforts and the progress of restoring operational capabilities are clearly and consistently communicated to all relevant internal and external stakeholders. This supports transparency, coordination, and informed decision-making during the recovery phase of an incident. To achieve this goal the following should be considered:</p><ul><ul><li>Recovery updates, including progress on restoring systems and services, should be shared securely and consistently with internal and external stakeholders, in line with the organisation’s response plans and information-sharing agreements.</li><li>Senior leadership should receive regular updates on the status of recovery efforts, especially during major incidents.</li><li>Communication protocols defined in contracts with suppliers and partners should be followed to ensure timely and accurate information exchange.</li><li>Crisis communication with critical suppliers should be coordinated to support aligned recovery actions.</li><li>If no actual incidents have occurred, tabletop exercises should be conducted to test and validate recovery communication procedures and stakeholder coordination.</li></ul></ul></div>

note

A general note, for any purpose.

The goal of this control is to ensure that recovery efforts and the progress of restoring operational capabilities are clearly and consistently communicated to all relevant internal and external stakeholders. This supports transparency, coordination, and informed decision-making during the recovery phase of an incident. To achieve this goal the following should be considered: - Recovery updates, including progress on restoring systems and services, should be shared securely and consistently with internal and external stakeholders, in line with the organisation’s response plans and information-sharing agreements. - Senior leadership should receive regular updates on the status of recovery efforts, especially during major incidents. - Communication protocols defined in contracts with suppliers and partners should be followed to ensure timely and accurate information exchange. - Crisis communication with critical suppliers should be coordinated to support aligned recovery actions. - If no actual incidents have occurred, tabletop exercises should be conducted to test and validate recovery communication procedures and stakeholder coordination.

note

A general note, for any purpose.

The goal of this control is to ensure that recovery efforts and the progress of restoring operational capabilities are clearly and consistently communicated to all relevant internal and external stakeholders. This supports transparency, coordination, and informed decision-making during the recovery phase of an incident. To achieve this goal the following should be considered: - Recovery updates, including progress on restoring systems and services, should be shared securely and consistently with internal and external stakeholders, in line with the organisation’s response plans and information-sharing agreements. - Senior leadership should receive regular updates on the status of recovery efforts, especially during major incidents. - Communication protocols defined in contracts with suppliers and partners should be followed to ensure timely and accurate information exchange. - Crisis communication with critical suppliers should be coordinated to support aligned recovery actions. - If no actual incidents have occurred, tabletop exercises should be conducted to test and validate recovery communication procedures and stakeholder coordination.

note

A general note, for any purpose.

The goal of this control is to ensure that recovery efforts and the progress of restoring operational capabilities are clearly and consistently communicated to all relevant internal and external stakeholders. This supports transparency, coordination, and informed decision-making during the recovery phase of an incident. To achieve this goal the following should be considered: o Recovery updates, including progress on restoring systems and services, should be shared securely and consistently with internal and external stakeholders, in line with the organisation’s response plans and information-sharing agreements. o Senior leadership should receive regular updates on the status of recovery efforts, especially during major incidents. o Communication protocols defined in contracts with suppliers and partners should be followed to ensure timely and accurate information exchange. o Crisis communication with critical suppliers should be coordinated to support aligned recovery actions. o If no actual incidents have occurred, tabletop exercises should be conducted to test and validate recovery communication procedures and stakeholder coordination.

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.

RC.CO-03.1

alternative label

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

Recovery progress communication

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.

Recovery activities and progress in restoring operational capabilities shall be communicated to designated internal and external stakeholders in accordance with established communication procedures.

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_ManagementAspects

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_KeyMeasures

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

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

1

triple count

The number of triples associated with the subject.

22

in dataset

Specifies the dataset the subject is part of.

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

Resultaten 1 - 24 of 24

References

Inverse links to the subject.