Direct links from the subject.
| Property | Value |
|---|---|
|
The subject is an instance of a class. |
|
|
The subject is an instance of a class. |
An idea or notion; a unit of thought. |
|
A human-readable name for the subject. |
RC.RP-01.1: A recovery process for disasters and information/cybersecurity incidents shall be developed and executed. |
|
RC.RP-01.1 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_BASIC_E_p51 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p177 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_IMPORTANT_E_p119 |
|
|
Relates a concept to a concept that is more general in meaning. |
|
|
A general note, for any purpose. |
<div><p>The goal of this control is to ensure the organisation can respond quickly and effectively to disasters, informa- tion security incidents, and cybersecurity events by developing and executing a structured recovery process that protects people, systems, and data. To support this goal, the organisation should:</p><ul><li>Develop a Recovery Process Adocumented process should guide immediate actions in the event of a fire, medical emergency, theft, nat- ural disaster, or information/cybersecurity incident.</li><li>Define Roles and Responsibilities The recovery process should specify who is authorised to initiate recovery procedures and who will com- municate with external stakeholders.</li><li>Protect Information and Systems The process should include steps for securing information and systems, such as shutting down or locking devices, switching to backup sites, or securing physical documents.</li><li>Establish Contact Procedures Alist ofinternal and external contacts should be maintained and included in the recoveryplan forquick access during an incident.</li><li>Ensure Awareness and Readiness Individualswith recoveryresponsibilities should be familiarwith the recoveryplan and understand the author- isations required to carry out each step.</li><li>Integrate with the Incident Response Plan The recovery process should be part of or aligned with the broader Incident Response Plan (IRP) to ensure consistency and coordination.</li><li>Include OT Environments Recovery planning should address OT systems, including procedures for restoring industrial operations, securing control systems, and coordinating with safety protocols.</li><li>Plan for Future Enhancements This control serves as a foundation for more advanced recovery planning, as further developed in control</li></ul></div> |
|
A general note, for any purpose. |
The goal of this control is to ensure the organisation can respond quickly and effectively to disasters, informa- tion security incidents, and cybersecurity events by developing and executing a structured recovery process that protects people, systems, and data. To support this goal, the organisation should: - Develop a Recovery Process Adocumented process should guide immediate actions in the event of a fire, medical emergency, theft, nat- ural disaster, or information/cybersecurity incident. - Define Roles and Responsibilities The recovery process should specify who is authorised to initiate recovery procedures and who will com- municate with external stakeholders. - Protect Information and Systems The process should include steps for securing information and systems, such as shutting down or locking devices, switching to backup sites, or securing physical documents. - Establish Contact Procedures Alist ofinternal and external contacts should be maintained and included in the recoveryplan forquick access during an incident. - Ensure Awareness and Readiness Individualswith recoveryresponsibilities should be familiarwith the recoveryplan and understand the author- isations required to carry out each step. - Integrate with the Incident Response Plan The recovery process should be part of or aligned with the broader Incident Response Plan (IRP) to ensure consistency and coordination. - Include OT Environments Recovery planning should address OT systems, including procedures for restoring industrial operations, securing control systems, and coordinating with safety protocols. - Plan for Future Enhancements This control serves as a foundation for more advanced recovery planning, as further developed in control |
|
A general note, for any purpose. |
The goal of this control is to ensure the organisation can respond quickly and effectively to disasters, informa- tion security incidents, and cybersecurity events by developing and executing a structured recovery process that protects people, systems, and data. To support this goal, the organisation should: • Develop a Recovery Process Adocumented process should guide immediate actions in the event of a fire, medical emergency, theft, nat- ural disaster, or information/cybersecurity incident. • Define Roles and Responsibilities The recovery process should specify who is authorised to initiate recovery procedures and who will com- municate with external stakeholders. • Protect Information and Systems The process should include steps for securing information and systems, such as shutting down or locking devices, switching to backup sites, or securing physical documents. • Establish Contact Procedures Alist ofinternal and external contacts should be maintained and included in the recoveryplan forquick access during an incident. • Ensure Awareness and Readiness Individualswith recoveryresponsibilities should be familiarwith the recoveryplan and understand the author- isations required to carry out each step. • Integrate with the Incident Response Plan The recovery process should be part of or aligned with the broader Incident Response Plan (IRP) to ensure consistency and coordination. • Include OT Environments Recovery planning should address OT systems, including procedures for restoring industrial operations, securing control systems, and coordinating with safety protocols. • Plan for Future Enhancements This control serves as a foundation for more advanced recovery planning, as further developed in control |
|
A general note, for any purpose. |
The goal of this control is to ensure the organisation can respond quickly and effectively to disasters, informa- tion security incidents, and cybersecurity events by developing and executing a structured recovery process that protects people, systems, and data. To support this goal, the organisation should: - Develop a Recovery Process Adocumented process should guide immediate actions in the event of a fire, medical emergency, theft, nat- ural disaster, or information/cybersecurity incident. - Define Roles and Responsibilities The recovery process should specify who is authorised to initiate recovery procedures and who will com- municate with external stakeholders. - Protect Information and Systems The process should include steps for securing information and systems, such as shutting down or locking devices, switching to backup sites, or securing physical documents. - Establish Contact Procedures Alist ofinternal and external contacts should be maintained and included in the recoveryplan forquick access during an incident. - Ensure Awareness and Readiness Individualswith recoveryresponsibilities should be familiarwith the recoveryplan and understand the author- isations required to carry out each step. - Integrate with the Incident Response Plan The recovery process should be part of or aligned with the broader Incident Response Plan (IRP) to ensure consistency and coordination. - Include OT Environments Recovery planning should address OT systems, including procedures for restoring industrial operations, securing control systems, and coordinating with safety protocols. - Plan for Future Enhancements This control serves as a foundation for more advanced recovery planning, as further developed in control |
|
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.RP-01.1 |
|
skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties. |
Recovery process execution |
|
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. |
A recovery process for disasters and information/cybersecurity incidents shall be developed and executed. |
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
The number of triples associated with the subject. |
21 |
|
Specifies the dataset the subject is part of. |
Resultaten 1 - 23 of 23
Inverse links to the subject.
| Property | Subject |
|---|---|
|
Relates a concept to a concept that is more specific in meaning. |
Resultaten 1 - 1 of 1