Concept skos:Concept Code RC.CO-04.1

Public updates on incident recovery shall be shared using approved communication methods and messaging, in accordance with established procedures.

Also known as

skos:altLabel

Public incident recovery updates

Note

skos:note

The goal of this control is to ensure that public communication during the recovery phase of an incident is accu- rate, timely, and delivered through approved channels, in order to maintain trust, manage reputational risk, and meet legal or regulatory obligations. To achieve this goal the following should be considered:

  • Approved methods forpublic communication, such as press releases, officialwebsites, ordesignated spokes- persons, should be defined in advance and used consistently.
  • Contact information for relevant parties (e.g. internal staff, third-party vendors, law enforcement, cyber insurance providers, government agencies) should be established and maintained.
  • Contact lists should be reviewed and verified regularly (e.g. annually) to ensure accuracy.
  • Primary and secondary communication mechanisms (e.g. phone calls, emails, letters) should be identified, considering that some methods may be unavailable during an incident.
  • Communication protocols and mechanisms should be reviewed periodicallyorwhen significant organisational changes occur.
  • If no actual incidents have occurred, tabletop exercises or simulations should be conducted to test public communication procedures and ensure readiness.

Place in the list

For people working with the data

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

RC.CO-04.1: Public updates on incident recovery shall be shared using approved communication methods and messaging, in accordance with established procedures.

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

RC.CO-04.1

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

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_IMPORTANT_E_p122

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

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p181

has broader

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

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

note

A general note, for any purpose.

The goal of this control is to ensure that public communication during the recovery phase of an incident is accu- rate, timely, and delivered through approved channels, in order to maintain trust, manage reputational risk, and meet legal or regulatory obligations. To achieve this goal the following should be considered: - Approved methods forpublic communication, such as press releases, officialwebsites, ordesignated spokes- persons, should be defined in advance and used consistently. - Contact information for relevant parties (e.g. internal staff, third-party vendors, law enforcement, cyber insurance providers, government agencies) should be established and maintained. - Contact lists should be reviewed and verified regularly (e.g. annually) to ensure accuracy. - Primary and secondary communication mechanisms (e.g. phone calls, emails, letters) should be identified, considering that some methods may be unavailable during an incident. - Communication protocols and mechanisms should be reviewed periodicallyorwhen significant organisational changes occur. - If no actual incidents have occurred, tabletop exercises or simulations should be conducted to test public communication procedures and ensure readiness.

note

A general note, for any purpose.

The goal of this control is to ensure that public communication during the recovery phase of an incident is accu- rate, timely, and delivered through approved channels, in order to maintain trust, manage reputational risk, and meet legal or regulatory obligations. To achieve this goal the following should be considered: - Approved methods forpublic communication, such as press releases, officialwebsites, ordesignated spokes- persons, should be defined in advance and used consistently. - Contact information for relevant parties (e.g. internal staff, third-party vendors, law enforcement, cyber insurance providers, government agencies) should be established and maintained. - Contact lists should be reviewed and verified regularly (e.g. annually) to ensure accuracy. - Primary and secondary communication mechanisms (e.g. phone calls, emails, letters) should be identified, considering that some methods may be unavailable during an incident. - Communication protocols and mechanisms should be reviewed periodicallyorwhen significant organisational changes occur. - If no actual incidents have occurred, tabletop exercises or simulations should be conducted to test public communication procedures and ensure readiness.

note

A general note, for any purpose.

<div><p>The goal of this control is to ensure that public communication during the recovery phase of an incident is accu- rate, timely, and delivered through approved channels, in order to maintain trust, manage reputational risk, and meet legal or regulatory obligations. To achieve this goal the following should be considered:</p><ul><li>Approved methods forpublic communication, such as press releases, officialwebsites, ordesignated spokes- persons, should be defined in advance and used consistently.</li><li>Contact information for relevant parties (e.g. internal staff, third-party vendors, law enforcement, cyber insurance providers, government agencies) should be established and maintained.</li><li>Contact lists should be reviewed and verified regularly (e.g. annually) to ensure accuracy.</li><li>Primary and secondary communication mechanisms (e.g. phone calls, emails, letters) should be identified, considering that some methods may be unavailable during an incident.</li><li>Communication protocols and mechanisms should be reviewed periodicallyorwhen significant organisational changes occur.</li><li>If no actual incidents have occurred, tabletop exercises or simulations should be conducted to test public communication procedures and ensure readiness.</li></ul></div>

note

A general note, for any purpose.

The goal of this control is to ensure that public communication during the recovery phase of an incident is accu- rate, timely, and delivered through approved channels, in order to maintain trust, manage reputational risk, and meet legal or regulatory obligations. To achieve this goal the following should be considered: • Approved methods forpublic communication, such as press releases, officialwebsites, ordesignated spokes- persons, should be defined in advance and used consistently. • Contact information for relevant parties (e.g. internal staff, third-party vendors, law enforcement, cyber insurance providers, government agencies) should be established and maintained. • Contact lists should be reviewed and verified regularly (e.g. annually) to ensure accuracy. • Primary and secondary communication mechanisms (e.g. phone calls, emails, letters) should be identified, considering that some methods may be unavailable during an incident. • Communication protocols and mechanisms should be reviewed periodicallyorwhen significant organisational changes occur. • If no actual incidents have occurred, tabletop exercises or simulations should be conducted to test public communication procedures and ensure readiness.

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-04.1

alternative label

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

Public incident recovery updates

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.

Public updates on incident recovery shall be shared using approved communication methods and messaging, in accordance with established 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_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.