Concept skos:Concept Code RS.MA-01.1

An incident response plan, including defined roles, responsibilities, and authorities, shall be executed during or after a cybersecurity event affecting the organisation's critical systems.

Also known as

skos:altLabel

Incident response plan execution

Note

skos:note

The goal of this control is to ensure that a well-defined incident response plan is executed during or after a cybersecurity event affecting the organisation’s critical systems, enabling timely detection, containment, communication, and recovery. To support this goal, the organisation should:

  • Develop a Documented Response Plan The plan should include predefined instructions and procedures to detect cybersecurity incidents, respond effectively, and support the recovery of critical systems.
  • Include Detection Capabilities Detection technologies should be in place to automatically report confirmed incidents and trigger response actions.
  • Define Roles, Responsibilities, and Authorities The plan should clearly identify:
    • Who is involved in the response
    • Contact details for key personnel
    • Who has the authority to initiate recovery
    • Who is responsible for external communication (e.g. regulators, partners, media)
  • Review and Update the Plan Regularly The plan should be reviewed and updated to reflect changes in the threat landscape, organisational structure, or lessons learned from past incidents.
  • Test the Plan Through Exercises Simulations and tabletop exercises should be conducted to validate the plan’s effectiveness and identify areas for improvement.
  • Include OT Environments The plan should address incident response in OT systems, including coordination with safety protocols, isola- tion of affected industrial assets, and restoration of operational processes.

Place in the list

For people working with the data

Identifier (URI) http://cyfun.data.gift/data/requirement_RS_MA_01_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.MA-01.1: An incident response plan, including defined roles, responsibilities, and authorities, shall be executed during or after a cybersecurity event affecting the organisation's critical systems.

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

RS.MA-01.1

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

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_BASIC_E_p47

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

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p163

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

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_IMPORTANT_E_p109

has broader

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

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

note

A general note, for any purpose.

The goal of this control is to ensure that a well-defined incident response plan is executed during or after a cybersecurity event affecting the organisation’s critical systems, enabling timely detection, containment, communication, and recovery. To support this goal, the organisation should: • Develop a Documented Response Plan The plan should include predefined instructions and procedures to detect cybersecurity incidents, respond effectively, and support the recovery of critical systems. • Include Detection Capabilities Detection technologies should be in place to automatically report confirmed incidents and trigger response actions. • Define Roles, Responsibilities, and Authorities The plan should clearly identify: o Who is involved in the response o Contact details for key personnel o Who has the authority to initiate recovery o Who is responsible for external communication (e.g. regulators, partners, media) • Review and Update the Plan Regularly The plan should be reviewed and updated to reflect changes in the threat landscape, organisational structure, or lessons learned from past incidents. • Test the Plan Through Exercises Simulations and tabletop exercises should be conducted to validate the plan’s effectiveness and identify areas for improvement. • Include OT Environments The plan should address incident response in OT systems, including coordination with safety protocols, isola- tion of affected industrial assets, and restoration of operational processes.

note

A general note, for any purpose.

<div><p>The goal of this control is to ensure that a well-defined incident response plan is executed during or after a cybersecurity event affecting the organisation’s critical systems, enabling timely detection, containment, communication, and recovery. To support this goal, the organisation should:</p><ul><li>Develop a Documented Response Plan The plan should include predefined instructions and procedures to detect cybersecurity incidents, respond effectively, and support the recovery of critical systems.</li><li>Include Detection Capabilities Detection technologies should be in place to automatically report confirmed incidents and trigger response actions.</li><li>Define Roles, Responsibilities, and Authorities The plan should clearly identify:<ul><li>Who is involved in the response</li><li>Contact details for key personnel</li><li>Who has the authority to initiate recovery</li><li>Who is responsible for external communication (e.g. regulators, partners, media)</li></ul></li><li>Review and Update the Plan Regularly The plan should be reviewed and updated to reflect changes in the threat landscape, organisational structure, or lessons learned from past incidents.</li><li>Test the Plan Through Exercises Simulations and tabletop exercises should be conducted to validate the plan’s effectiveness and identify areas for improvement.</li><li>Include OT Environments The plan should address incident response in OT systems, including coordination with safety protocols, isola- tion of affected industrial assets, and restoration of operational processes.</li></ul></div>

note

A general note, for any purpose.

The goal of this control is to ensure that a well-defined incident response plan is executed during or after a cybersecurity event affecting the organisation’s critical systems, enabling timely detection, containment, communication, and recovery. To support this goal, the organisation should: - Develop a Documented Response Plan The plan should include predefined instructions and procedures to detect cybersecurity incidents, respond effectively, and support the recovery of critical systems. - Include Detection Capabilities Detection technologies should be in place to automatically report confirmed incidents and trigger response actions. - Define Roles, Responsibilities, and Authorities The plan should clearly identify: - Who is involved in the response - Contact details for key personnel - Who has the authority to initiate recovery - Who is responsible for external communication (e.g. regulators, partners, media) - Review and Update the Plan Regularly The plan should be reviewed and updated to reflect changes in the threat landscape, organisational structure, or lessons learned from past incidents. - Test the Plan Through Exercises Simulations and tabletop exercises should be conducted to validate the plan’s effectiveness and identify areas for improvement. - Include OT Environments The plan should address incident response in OT systems, including coordination with safety protocols, isola- tion of affected industrial assets, and restoration of operational processes.

note

A general note, for any purpose.

The goal of this control is to ensure that a well-defined incident response plan is executed during or after a cybersecurity event affecting the organisation’s critical systems, enabling timely detection, containment, communication, and recovery. To support this goal, the organisation should: - Develop a Documented Response Plan The plan should include predefined instructions and procedures to detect cybersecurity incidents, respond effectively, and support the recovery of critical systems. - Include Detection Capabilities Detection technologies should be in place to automatically report confirmed incidents and trigger response actions. - Define Roles, Responsibilities, and Authorities The plan should clearly identify: - Who is involved in the response - Contact details for key personnel - Who has the authority to initiate recovery - Who is responsible for external communication (e.g. regulators, partners, media) - Review and Update the Plan Regularly The plan should be reviewed and updated to reflect changes in the threat landscape, organisational structure, or lessons learned from past incidents. - Test the Plan Through Exercises Simulations and tabletop exercises should be conducted to validate the plan’s effectiveness and identify areas for improvement. - Include OT Environments The plan should address incident response in OT systems, including coordination with safety protocols, isola- tion of affected industrial assets, and restoration of operational processes.

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

alternative label

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

Incident response plan execution

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.

An incident response plan, including defined roles, responsibilities, and authorities, shall be executed during or after a cybersecurity event affecting the organisation's critical systems.

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.