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.2: The reliability and integrity of backups shall be verified and tested regularly. |
|
PR.DS-11.2 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_IMPORTANT_E_p82 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p116 |
|
|
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 ensure that backup data can be trusted and successfully restored when needed, supporting operational continuity and resilience. To achieve this goal, the organisation should: - Test Recovery Procedures Backup recovery procedures should be tested regularly to confirm that data can be restored accurately and completely. - Verify Backup Integrity - Backups should be checked for signs of compromise, corruption, or tampering before use. - Integrity checks should focus on indicators of security breaches or data loss. - Schedule Testing - All types of data sources should be included in backup and restore tests. - Testing should occur at least annually, or more frequently on a sample basis. - Align with Related Controls This control should be implemented in coordination with RC.RP-05.1 (Recovery Planning), ensuring consistency in recovery strategies. |
|
A general note, for any purpose. |
The goal of this control is to ensure that backup data can be trusted and successfully restored when needed, supporting operational continuity and resilience. To achieve this goal, the organisation should: - Test Recovery Procedures Backup recovery procedures should be tested regularly to confirm that data can be restored accurately and completely. - Verify Backup Integrity - Backups should be checked for signs of compromise, corruption, or tampering before use. - Integrity checks should focus on indicators of security breaches or data loss. - Schedule Testing - All types of data sources should be included in backup and restore tests. - Testing should occur at least annually, or more frequently on a sample basis. - Align with Related Controls This control should be implemented in coordination with RC.RP-05.1 (Recovery Planning), ensuring consistency in recovery strategies. |
|
A general note, for any purpose. |
<div><p>The goal of this control is to ensure that backup data can be trusted and successfully restored when needed, supporting operational continuity and resilience. To achieve this goal, the organisation should:</p><ul><li>Test Recovery Procedures Backup recovery procedures should be tested regularly to confirm that data can be restored accurately and completely.</li><li>Verify Backup Integrity<ul><li>Backups should be checked for signs of compromise, corruption, or tampering before use.</li><li>Integrity checks should focus on indicators of security breaches or data loss.</li></ul></li><li>Schedule Testing<ul><li>All types of data sources should be included in backup and restore tests.</li><li>Testing should occur at least annually, or more frequently on a sample basis.</li></ul></li><li>Align with Related Controls This control should be implemented in coordination with RC.RP-05.1 (Recovery Planning), ensuring consistency in recovery strategies.</li></ul></div> |
|
A general note, for any purpose. |
The goal of this control is to ensure that backup data can be trusted and successfully restored when needed, supporting operational continuity and resilience. To achieve this goal, the organisation should: • Test Recovery Procedures Backup recovery procedures should be tested regularly to confirm that data can be restored accurately and completely. • Verify Backup Integrity o Backups should be checked for signs of compromise, corruption, or tampering before use. o Integrity checks should focus on indicators of security breaches or data loss. • Schedule Testing o All types of data sources should be included in backup and restore tests. o Testing should occur at least annually, or more frequently on a sample basis. • Align with Related Controls This control should be implemented in coordination with RC.RP-05.1 (Recovery Planning), ensuring consistency in recovery strategies. |
|
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.2 |
|
skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties. |
Backup reliability and integrity verification |
|
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 reliability and integrity of backups shall be verified and tested regularly. |
|
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_BASIC_to_IMPORTANT |
|
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. |
19 |
|
Specifies the dataset the subject is part of. |
Resultaten 1 - 21 of 21
Inverse links to the subject.
| Property | Subject |
|---|---|
|
Relates a concept to a concept that is more specific in meaning. |
Resultaten 1 - 1 of 1