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.5: is an evolution — not a repetition — of PR.DS-11.3 and PR.DS-11.4. While the earlier controls focus on where and how backups are stored and verified, PR.DS-11.5 focuses on what is being backed up and how it is logically separated to optimise recovery: · PR.DS-11.3 ensures backups are secure and stored separately. · PR.DS-11.4 ensures backups are tested and integrated into recovery planning. · PR.DS-11.5 ensures functional separation between system and data backups to enable faster, more targeted recovery. |
|
PR.DS-11.5 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p119 |
|
|
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 support faster and more reliable recovery by separating backups of critical systems (e.g. operating systems, configurations, applications) from backups of critical information (e.g. business data, documents, databases). To achieve this goal, the organisation should: - Separate backup scopes - System backups should include operating systems, configurations, installed software, and system-level settings. - Information backups should include business-critical data such as databases, documents, and application data. - Use tailored backup methods - System backups should use full images or snapshots to capture the complete system state. - Information backups should use incremental or differential methods to efficiently capture data changes. - Encrypt sensitive data Both system and information backups should be encrypted during storage and transmission, especially when containing sensitive or regulated data. - Align with recovery objectives Backup separation should reflect different RecoveryTime Objectives (RTOs) and Recovery Point Objectives (RPOs). For example, system recovery may require faster restoration than business data. - Document and automate - Backup scopes and procedures should be clearly documented. - Backup processes should be automated where possible to reduce human error and ensure consistency. OT-Specific Considerations In OTenvironments, separating system and data backups helps restore control systems quicklywithout waiting for large data sets to be recovered. This supports operational continuity and reduces downtime in critical industrial processes. Relation with PR.DS-11.3 and PR.DS-11.4 |
|
A general note, for any purpose. |
The goal of this control is to support faster and more reliable recovery by separating backups of critical systems (e.g. operating systems, configurations, applications) from backups of critical information (e.g. business data, documents, databases). To achieve this goal, the organisation should: - Separate backup scopes - System backups should include operating systems, configurations, installed software, and system-level settings. - Information backups should include business-critical data such as databases, documents, and application data. - Use tailored backup methods - System backups should use full images or snapshots to capture the complete system state. - Information backups should use incremental or differential methods to efficiently capture data changes. - Encrypt sensitive data Both system and information backups should be encrypted during storage and transmission, especially when containing sensitive or regulated data. - Align with recovery objectives Backup separation should reflect different RecoveryTime Objectives (RTOs) and Recovery Point Objectives (RPOs). For example, system recovery may require faster restoration than business data. - Document and automate - Backup scopes and procedures should be clearly documented. - Backup processes should be automated where possible to reduce human error and ensure consistency. OT-Specific Considerations In OTenvironments, separating system and data backups helps restore control systems quicklywithout waiting for large data sets to be recovered. This supports operational continuity and reduces downtime in critical industrial processes. Relation with PR.DS-11.3 and PR.DS-11.4 |
|
A general note, for any purpose. |
<div><p>The goal of this control is to support faster and more reliable recovery by separating backups of critical systems (e.g. operating systems, configurations, applications) from backups of critical information (e.g. business data, documents, databases). To achieve this goal, the organisation should:</p><ul><li>Separate backup scopes<ul><li>System backups should include operating systems, configurations, installed software, and system-level settings.</li><li>Information backups should include business-critical data such as databases, documents, and application data.</li></ul></li><li>Use tailored backup methods<ul><li>System backups should use full images or snapshots to capture the complete system state.</li><li>Information backups should use incremental or differential methods to efficiently capture data changes.</li></ul></li><li>Encrypt sensitive data Both system and information backups should be encrypted during storage and transmission, especially when containing sensitive or regulated data.</li><li>Align with recovery objectives Backup separation should reflect different RecoveryTime Objectives (RTOs) and Recovery Point Objectives (RPOs). For example, system recovery may require faster restoration than business data.</li><li>Document and automate<ul><li>Backup scopes and procedures should be clearly documented.</li><li>Backup processes should be automated where possible to reduce human error and ensure consistency. OT-Specific Considerations In OTenvironments, separating system and data backups helps restore control systems quicklywithout waiting for large data sets to be recovered. This supports operational continuity and reduces downtime in critical industrial processes. Relation with PR.DS-11.3 and PR.DS-11.4</li></ul></li></ul></div> |
|
A general note, for any purpose. |
The goal of this control is to support faster and more reliable recovery by separating backups of critical systems (e.g. operating systems, configurations, applications) from backups of critical information (e.g. business data, documents, databases). To achieve this goal, the organisation should: • Separate backup scopes o System backups should include operating systems, configurations, installed software, and system-level settings. o Information backups should include business-critical data such as databases, documents, and application data. • Use tailored backup methods o System backups should use full images or snapshots to capture the complete system state. o Information backups should use incremental or differential methods to efficiently capture data changes. • Encrypt sensitive data Both system and information backups should be encrypted during storage and transmission, especially when containing sensitive or regulated data. • Align with recovery objectives Backup separation should reflect different RecoveryTime Objectives (RTOs) and Recovery Point Objectives (RPOs). For example, system recovery may require faster restoration than business data. • Document and automate o Backup scopes and procedures should be clearly documented. o Backup processes should be automated where possible to reduce human error and ensure consistency. OT-Specific Considerations In OTenvironments, separating system and data backups helps restore control systems quicklywithout waiting for large data sets to be recovered. This supports operational continuity and reduces downtime in critical industrial processes. Relation with PR.DS-11.3 and PR.DS-11.4 |
|
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.5 |
|
skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties. |
System and data backup separation |
|
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. |
is an evolution — not a repetition — of PR.DS-11.3 and PR.DS-11.4. While the earlier controls focus on where and how backups are stored and verified, PR.DS-11.5 focuses on what is being backed up and how it is logically separated to optimise recovery: · PR.DS-11.3 ensures backups are secure and stored separately. · PR.DS-11.4 ensures backups are tested and integrated into recovery planning. · PR.DS-11.5 ensures functional separation between system and data backups to enable faster, more targeted 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