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-02.1: The organisation's essential functions and services shall be continued with little or no loss of operational continuity, and continuity shall be maintained until full system recovery. |
|
RC.RP-02.1 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p178 |
|
|
Relates a concept to a concept that is more general in meaning. |
|
|
A general note, for any purpose. |
The goal of this control is to minimise disruption to critical operations during incidents and ensure they remain functional until systems are fully restored. To achieve this goal, the organisation should: • Plan for Continuity o Abusiness continuity plan should be maintained to identify essential functions and define procedures for uninterrupted operation during incidents. o An incident response plan should be included, detailing steps for containment, damage assessment, and staged recovery. • Sustain Operations Until Recovery o Continuity measures should support essential functions until full restoration is achieved. o Temporary workarounds, redundant systems, or manual procedures should be used where necessary to maintain operations. • Prioritise Recovery o Business impact analysis and system categorisation should be used to define recovery priorities. o Systems should be categorised based on the impact of losing availability, integrity, or confidentiality, with special attention to safety-critical OT environments. • Ensure Data Resilience o Robust backup solutions should be implemented to enable fast and reliable data restoration. o Backups should be secured and tested regularly. • Monitor and Respond o Systems should be continuously monitored to detect disruptions early. o Quick response actions should be taken to minimise operational impact. • Test and Improve o Recovery procedures should be tested regularly to ensure effectiveness. o Recovery actions should be documented and reviewed to improve readiness over time. |
|
A general note, for any purpose. |
The goal of this control is to minimise disruption to critical operations during incidents and ensure they remain functional until systems are fully restored. To achieve this goal, the organisation should: - Plan for Continuity - Abusiness continuity plan should be maintained to identify essential functions and define procedures for uninterrupted operation during incidents. - An incident response plan should be included, detailing steps for containment, damage assessment, and staged recovery. - Sustain Operations Until Recovery - Continuity measures should support essential functions until full restoration is achieved. - Temporary workarounds, redundant systems, or manual procedures should be used where necessary to maintain operations. - Prioritise Recovery - Business impact analysis and system categorisation should be used to define recovery priorities. - Systems should be categorised based on the impact of losing availability, integrity, or confidentiality, with special attention to safety-critical OT environments. - Ensure Data Resilience - Robust backup solutions should be implemented to enable fast and reliable data restoration. - Backups should be secured and tested regularly. - Monitor and Respond - Systems should be continuously monitored to detect disruptions early. - Quick response actions should be taken to minimise operational impact. - Test and Improve - Recovery procedures should be tested regularly to ensure effectiveness. - Recovery actions should be documented and reviewed to improve readiness over time. |
|
A general note, for any purpose. |
The goal of this control is to minimise disruption to critical operations during incidents and ensure they remain functional until systems are fully restored. To achieve this goal, the organisation should: - Plan for Continuity - Abusiness continuity plan should be maintained to identify essential functions and define procedures for uninterrupted operation during incidents. - An incident response plan should be included, detailing steps for containment, damage assessment, and staged recovery. - Sustain Operations Until Recovery - Continuity measures should support essential functions until full restoration is achieved. - Temporary workarounds, redundant systems, or manual procedures should be used where necessary to maintain operations. - Prioritise Recovery - Business impact analysis and system categorisation should be used to define recovery priorities. - Systems should be categorised based on the impact of losing availability, integrity, or confidentiality, with special attention to safety-critical OT environments. - Ensure Data Resilience - Robust backup solutions should be implemented to enable fast and reliable data restoration. - Backups should be secured and tested regularly. - Monitor and Respond - Systems should be continuously monitored to detect disruptions early. - Quick response actions should be taken to minimise operational impact. - Test and Improve - Recovery procedures should be tested regularly to ensure effectiveness. - Recovery actions should be documented and reviewed to improve readiness over time. |
|
A general note, for any purpose. |
<div><p>The goal of this control is to minimise disruption to critical operations during incidents and ensure they remain functional until systems are fully restored. To achieve this goal, the organisation should:</p><ul><li>Plan for Continuity<ul><li>Abusiness continuity plan should be maintained to identify essential functions and define procedures for uninterrupted operation during incidents.</li><li>An incident response plan should be included, detailing steps for containment, damage assessment, and staged recovery.</li></ul></li><li>Sustain Operations Until Recovery<ul><li>Continuity measures should support essential functions until full restoration is achieved.</li><li>Temporary workarounds, redundant systems, or manual procedures should be used where necessary to maintain operations.</li></ul></li><li>Prioritise Recovery<ul><li>Business impact analysis and system categorisation should be used to define recovery priorities.</li><li>Systems should be categorised based on the impact of losing availability, integrity, or confidentiality, with special attention to safety-critical OT environments.</li></ul></li><li>Ensure Data Resilience<ul><li>Robust backup solutions should be implemented to enable fast and reliable data restoration.</li><li>Backups should be secured and tested regularly.</li></ul></li><li>Monitor and Respond<ul><li>Systems should be continuously monitored to detect disruptions early.</li><li>Quick response actions should be taken to minimise operational impact.</li></ul></li><li>Test and Improve<ul><li>Recovery procedures should be tested regularly to ensure effectiveness.</li><li>Recovery actions should be documented and reviewed to improve readiness over time.</li></ul></li></ul></div> |
|
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-02.1 |
|
skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties. |
Operational continuity maintenance |
|
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. |
The organisation's essential functions and services shall be continued with little or no loss of operational continuity, and continuity shall be maintained until full system recovery. |
|
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. |
http://cyfun.data.gift/data/CyFun2025_delta_IMPORTANT_to_ESSENTIAL |
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
The number of triples associated with the subject. |
17 |
|
Specifies the dataset the subject is part of. |
Resultaten 1 - 19 of 19
Inverse links to the subject.
| Property | Subject |
|---|---|
|
Relates a concept to a concept that is more specific in meaning. |
Resultaten 1 - 1 of 1