Concept skos:Concept Code RS.CO-02.1

Information about cybersecurity incidents shall be communicated to employees in a way that is clear and easy to understand.

Also known as

skos:altLabel

Internal incident communication

Note

skos:note

The goal of this control is to ensure that all employees are informed about cybersecurity incidents in a timely and understandable manner, so they can respond appropriately and help reduce risks. To achieve this:

  • An Incident Response Plan (IRP) should be in place. This plan outlines how the organisation will respond to cybersecurityincidents, includingwho is responsible forwhat and howto escalate different types ofthreats.
  • The IRP should include a communication protocol that explains how to share accurate and relevant informa- tion with employees quickly and efficiently during an incident.
  • The plan should define the communication channels to be used, such as email, internal messaging platforms, phone calls, or a dedicated incident portal.
  • Templates for incident messages should be prepared in advance. These templates should include key details like the type of incident, how serious it is, which systems are affected, and what actions employees should take.
  • Messages should be written in clear, simple language that avoids technical terms, so all employees can understand what is happening and what is expected of them.
  • Senior management should receive high-level summaries that explain the impact of the incident, the risks involved, and the steps being taken to resolve it.

Place in the list

For people working with the data

Identifier (URI) http://cyfun.data.gift/data/requirement_RS_CO_02_1
All data (23 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.CO-02.1: Information about cybersecurity incidents shall be communicated to employees in a way that is clear and easy to understand.

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

RS.CO-02.1

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

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_BASIC_E_p48

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

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p170

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

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_IMPORTANT_E_p113

has broader

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

http://cyfun.data.gift/data/subcategory_RS.CO-02

note

A general note, for any purpose.

The goal of this control is to ensure that all employees are informed about cybersecurity incidents in a timely and understandable manner, so they can respond appropriately and help reduce risks. To achieve this: - An Incident Response Plan (IRP) should be in place. This plan outlines how the organisation will respond to cybersecurityincidents, includingwho is responsible forwhat and howto escalate different types ofthreats. - The IRP should include a communication protocol that explains how to share accurate and relevant informa- tion with employees quickly and efficiently during an incident. - The plan should define the communication channels to be used, such as email, internal messaging platforms, phone calls, or a dedicated incident portal. - Templates for incident messages should be prepared in advance. These templates should include key details like the type of incident, how serious it is, which systems are affected, and what actions employees should take. - Messages should be written in clear, simple language that avoids technical terms, so all employees can understand what is happening and what is expected of them. - Senior management should receive high-level summaries that explain the impact of the incident, the risks involved, and the steps being taken to resolve it.

note

A general note, for any purpose.

The goal of this control is to ensure that all employees are informed about cybersecurity incidents in a timely and understandable manner, so they can respond appropriately and help reduce risks. To achieve this: • An Incident Response Plan (IRP) should be in place. This plan outlines how the organisation will respond to cybersecurityincidents, includingwho is responsible forwhat and howto escalate different types ofthreats. • The IRP should include a communication protocol that explains how to share accurate and relevant informa- tion with employees quickly and efficiently during an incident. • The plan should define the communication channels to be used, such as email, internal messaging platforms, phone calls, or a dedicated incident portal. • Templates for incident messages should be prepared in advance. These templates should include key details like the type of incident, how serious it is, which systems are affected, and what actions employees should take. • Messages should be written in clear, simple language that avoids technical terms, so all employees can understand what is happening and what is expected of them. • Senior management should receive high-level summaries that explain the impact of the incident, the risks involved, and the steps being taken to resolve it.

note

A general note, for any purpose.

The goal of this control is to ensure that all employees are informed about cybersecurity incidents in a timely and understandable manner, so they can respond appropriately and help reduce risks. To achieve this: - An Incident Response Plan (IRP) should be in place. This plan outlines how the organisation will respond to cybersecurityincidents, includingwho is responsible forwhat and howto escalate different types ofthreats. - The IRP should include a communication protocol that explains how to share accurate and relevant informa- tion with employees quickly and efficiently during an incident. - The plan should define the communication channels to be used, such as email, internal messaging platforms, phone calls, or a dedicated incident portal. - Templates for incident messages should be prepared in advance. These templates should include key details like the type of incident, how serious it is, which systems are affected, and what actions employees should take. - Messages should be written in clear, simple language that avoids technical terms, so all employees can understand what is happening and what is expected of them. - Senior management should receive high-level summaries that explain the impact of the incident, the risks involved, and the steps being taken to resolve it.

note

A general note, for any purpose.

<div><p>The goal of this control is to ensure that all employees are informed about cybersecurity incidents in a timely and understandable manner, so they can respond appropriately and help reduce risks. To achieve this:</p><ul><li>An Incident Response Plan (IRP) should be in place. This plan outlines how the organisation will respond to cybersecurityincidents, includingwho is responsible forwhat and howto escalate different types ofthreats.</li><li>The IRP should include a communication protocol that explains how to share accurate and relevant informa- tion with employees quickly and efficiently during an incident.</li><li>The plan should define the communication channels to be used, such as email, internal messaging platforms, phone calls, or a dedicated incident portal.</li><li>Templates for incident messages should be prepared in advance. These templates should include key details like the type of incident, how serious it is, which systems are affected, and what actions employees should take.</li><li>Messages should be written in clear, simple language that avoids technical terms, so all employees can understand what is happening and what is expected of them.</li><li>Senior management should receive high-level summaries that explain the impact of the incident, the risks involved, and the steps being taken to resolve it.</li></ul></div>

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.CO-02.1

alternative label

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

Internal incident 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.

Information about cybersecurity incidents shall be communicated to employees in a way that is clear and easy to understand.

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

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_BASIC

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_BASIC

triple count

The number of triples associated with the subject.

21

in dataset

Specifies the dataset the subject is part of.

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

Resultaten 1 - 23 of 23

References

Inverse links to the subject.