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. |
PR.DS-11.4: The organisation shall regularly verify the integrity and recoverability of backups through coordinated testing with all relevant continuity and incident response func- tions. Backup testing shall be integrated into broader resilience planning, including business continuity, disaster recovery, and cyber incident response. |
|
PR.DS-11.4 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p118 |
|
|
Relates a concept to a concept that is more general in meaning. |
|
|
A general note, for any purpose. |
<div><p>This control is an evolution of PR.DS-11.3 and ensures that backup systems are not only in place but are regularly tested and aligned with the organisation’s broader recovery and continuity plans. It highlights the importance of coordination across teams and proactive planning, helping the organisation stay prepared to recover quickly and effectively from serious incidents. To ensure that backup and recovery capabilities are effective and integrated into the organisation’s overall resilience strategy, the following practices should be implemented:</p><ul><li>Coordinate Backup Testing Across Plans Backup verification should be planned and executed in coordination with the teams responsible for the organisation’s key continuity and response plans. These include:<ul><li>Business Continuity Plans (BCP)</li><li>Disaster Recovery Plans (DRP)</li><li>Contingency Plans</li><li>Continuity of Operations Plans (COOP)</li><li>Crisis Communications Plans</li><li>Critical Infrastructure Protection Plans</li><li>Cyber Incident Response Plans</li></ul></li><li>Include Backup Recovery in Scenario Testing During exercises or simulations of incidents (e.g. cyberattacks, system failures, or natural disasters), the recovery of backup data should be explicitly tested. This ensures that backups are not only available but also usable and aligned with recovery time and recovery point objectives (RTO/RPO).</li><li>Document and Review Results The outcomes of backup verification and recovery tests should be documented and reviewed with relevant stakeholders to identify gaps and improve procedures.</li></ul></div> |
|
A general note, for any purpose. |
This control is an evolution of PR.DS-11.3 and ensures that backup systems are not only in place but are regularly tested and aligned with the organisation’s broader recovery and continuity plans. It highlights the importance of coordination across teams and proactive planning, helping the organisation stay prepared to recover quickly and effectively from serious incidents. To ensure that backup and recovery capabilities are effective and integrated into the organisation’s overall resilience strategy, the following practices should be implemented: - Coordinate Backup Testing Across Plans Backup verification should be planned and executed in coordination with the teams responsible for the organisation’s key continuity and response plans. These include: - Business Continuity Plans (BCP) - Disaster Recovery Plans (DRP) - Contingency Plans - Continuity of Operations Plans (COOP) - Crisis Communications Plans - Critical Infrastructure Protection Plans - Cyber Incident Response Plans - Include Backup Recovery in Scenario Testing During exercises or simulations of incidents (e.g. cyberattacks, system failures, or natural disasters), the recovery of backup data should be explicitly tested. This ensures that backups are not only available but also usable and aligned with recovery time and recovery point objectives (RTO/RPO). - Document and Review Results The outcomes of backup verification and recovery tests should be documented and reviewed with relevant stakeholders to identify gaps and improve procedures. |
|
A general note, for any purpose. |
This control is an evolution of PR.DS-11.3 and ensures that backup systems are not only in place but are regularly tested and aligned with the organisation’s broader recovery and continuity plans. It highlights the importance of coordination across teams and proactive planning, helping the organisation stay prepared to recover quickly and effectively from serious incidents. To ensure that backup and recovery capabilities are effective and integrated into the organisation’s overall resilience strategy, the following practices should be implemented: • Coordinate Backup Testing Across Plans Backup verification should be planned and executed in coordination with the teams responsible for the organisation’s key continuity and response plans. These include: o Business Continuity Plans (BCP) o Disaster Recovery Plans (DRP) o Contingency Plans o Continuity of Operations Plans (COOP) o Crisis Communications Plans o Critical Infrastructure Protection Plans o Cyber Incident Response Plans • Include Backup Recovery in Scenario Testing During exercises or simulations of incidents (e.g. cyberattacks, system failures, or natural disasters), the recovery of backup data should be explicitly tested. This ensures that backups are not only available but also usable and aligned with recovery time and recovery point objectives (RTO/RPO). • Document and Review Results The outcomes of backup verification and recovery tests should be documented and reviewed with relevant stakeholders to identify gaps and improve procedures. |
|
A general note, for any purpose. |
This control is an evolution of PR.DS-11.3 and ensures that backup systems are not only in place but are regularly tested and aligned with the organisation’s broader recovery and continuity plans. It highlights the importance of coordination across teams and proactive planning, helping the organisation stay prepared to recover quickly and effectively from serious incidents. To ensure that backup and recovery capabilities are effective and integrated into the organisation’s overall resilience strategy, the following practices should be implemented: - Coordinate Backup Testing Across Plans Backup verification should be planned and executed in coordination with the teams responsible for the organisation’s key continuity and response plans. These include: - Business Continuity Plans (BCP) - Disaster Recovery Plans (DRP) - Contingency Plans - Continuity of Operations Plans (COOP) - Crisis Communications Plans - Critical Infrastructure Protection Plans - Cyber Incident Response Plans - Include Backup Recovery in Scenario Testing During exercises or simulations of incidents (e.g. cyberattacks, system failures, or natural disasters), the recovery of backup data should be explicitly tested. This ensures that backups are not only available but also usable and aligned with recovery time and recovery point objectives (RTO/RPO). - Document and Review Results The outcomes of backup verification and recovery tests should be documented and reviewed with relevant stakeholders to identify gaps and improve procedures. |
|
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. |
PR.DS-11.4 |
|
skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties. |
Backup recoverability testing |
|
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 shall regularly verify the integrity and recoverability of backups through coordinated testing with all relevant continuity and incident response func- tions. Backup testing shall be integrated into broader resilience planning, including business continuity, disaster recovery, and cyber incident response. |
|
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