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.1: Backups for the organisation's business-critical data shall be performed and stored on a different system from the device on which the original data resides. |
|
PR.DS-11.1 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_BASIC_E_p34 |
|
|
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 business-critical data is regularly backed up and securely stored on a separate system to protect against data loss, system failure, or cyberattacks such as ransomware. To support this goal, the organisation should: - Back Up Critical Data and Systems Backups should include: - Business-critical data (e.g. customer records, financial and operational data). - System data such as software configurations, device settings, documentation, and application backups. - Define a Backup Strategy - Critical data should be backed up continuously or in near-real time. - Other important data should be backed up at regular, agreed intervals. - Backups should be stored on a system that is physically or logically separate from the original data source. This means they must not reside on the same device, server, or storage array as the original data. Ideally, backups should be stored in a different security zone, network segment, or even offsite location to ensure they remain accessible and uncompromised in the event of system failure, ransomware, or other incidents affecting the primary environment. - Ensure Network Separation - Backups should not be stored on the same network as the original systems. - At least one backup copy should be kept completely offline or air-gapped to ensure recovery in the event of a network breach or ransomware attack. - Plan for Recovery RecoveryTime Objective (RTO – howquicklysystems must be restored) and RecoveryPoint Objective (RPO – how much data loss is acceptable) should be defined and reviewed regularly to ensure timely and effective restoration. - Include OT Environments Backup strategies should cover OT systems, including control system configurations, operational data, and device settings critical to industrial operations. |
|
A general note, for any purpose. |
The goal of this control is to ensure that business-critical data is regularly backed up and securely stored on a separate system to protect against data loss, system failure, or cyberattacks such as ransomware. To support this goal, the organisation should: • Back Up Critical Data and Systems Backups should include: o Business-critical data (e.g. customer records, financial and operational data). o System data such as software configurations, device settings, documentation, and application backups. • Define a Backup Strategy o Critical data should be backed up continuously or in near-real time. o Other important data should be backed up at regular, agreed intervals. o Backups should be stored on a system that is physically or logically separate from the original data source. This means they must not reside on the same device, server, or storage array as the original data. Ideally, backups should be stored in a different security zone, network segment, or even offsite location to ensure they remain accessible and uncompromised in the event of system failure, ransomware, or other incidents affecting the primary environment. • Ensure Network Separation o Backups should not be stored on the same network as the original systems. o At least one backup copy should be kept completely offline or air-gapped to ensure recovery in the event of a network breach or ransomware attack. • Plan for Recovery RecoveryTime Objective (RTO – howquicklysystems must be restored) and RecoveryPoint Objective (RPO – how much data loss is acceptable) should be defined and reviewed regularly to ensure timely and effective restoration. • Include OT Environments Backup strategies should cover OT systems, including control system configurations, operational data, and device settings critical to industrial operations. |
|
A general note, for any purpose. |
<div><p>The goal of this control is to ensure that business-critical data is regularly backed up and securely stored on a separate system to protect against data loss, system failure, or cyberattacks such as ransomware. To support this goal, the organisation should:</p><ul><li>Back Up Critical Data and Systems Backups should include:<ul><li>Business-critical data (e.g. customer records, financial and operational data).</li><li>System data such as software configurations, device settings, documentation, and application backups.</li></ul></li><li>Define a Backup Strategy<ul><li>Critical data should be backed up continuously or in near-real time.</li><li>Other important data should be backed up at regular, agreed intervals.</li><li>Backups should be stored on a system that is physically or logically separate from the original data source. This means they must not reside on the same device, server, or storage array as the original data. Ideally, backups should be stored in a different security zone, network segment, or even offsite location to ensure they remain accessible and uncompromised in the event of system failure, ransomware, or other incidents affecting the primary environment.</li></ul></li><li>Ensure Network Separation<ul><li>Backups should not be stored on the same network as the original systems.</li><li>At least one backup copy should be kept completely offline or air-gapped to ensure recovery in the event of a network breach or ransomware attack.</li></ul></li><li>Plan for Recovery RecoveryTime Objective (RTO – howquicklysystems must be restored) and RecoveryPoint Objective (RPO – how much data loss is acceptable) should be defined and reviewed regularly to ensure timely and effective restoration.</li><li>Include OT Environments Backup strategies should cover OT systems, including control system configurations, operational data, and device settings critical to industrial operations.</li></ul></div> |
|
A general note, for any purpose. |
The goal of this control is to ensure that business-critical data is regularly backed up and securely stored on a separate system to protect against data loss, system failure, or cyberattacks such as ransomware. To support this goal, the organisation should: - Back Up Critical Data and Systems Backups should include: - Business-critical data (e.g. customer records, financial and operational data). - System data such as software configurations, device settings, documentation, and application backups. - Define a Backup Strategy - Critical data should be backed up continuously or in near-real time. - Other important data should be backed up at regular, agreed intervals. - Backups should be stored on a system that is physically or logically separate from the original data source. This means they must not reside on the same device, server, or storage array as the original data. Ideally, backups should be stored in a different security zone, network segment, or even offsite location to ensure they remain accessible and uncompromised in the event of system failure, ransomware, or other incidents affecting the primary environment. - Ensure Network Separation - Backups should not be stored on the same network as the original systems. - At least one backup copy should be kept completely offline or air-gapped to ensure recovery in the event of a network breach or ransomware attack. - Plan for Recovery RecoveryTime Objective (RTO – howquicklysystems must be restored) and RecoveryPoint Objective (RPO – how much data loss is acceptable) should be defined and reviewed regularly to ensure timely and effective restoration. - Include OT Environments Backup strategies should cover OT systems, including control system configurations, operational data, and device settings critical to industrial operations. |
|
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.1 |
|
skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties. |
Critical data backup |
|
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. |
Backups for the organisation's business-critical data shall be performed and stored on a different system from the device on which the original data resides. |
|
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. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
1 |
|
|
The number of triples associated with the subject. |
23 |
|
Specifies the dataset the subject is part of. |
Resultaten 1 - 25 of 25
Inverse links to the subject.
| Property | Subject |
|---|---|
|
Relates a concept to a concept that is more specific in meaning. |
Resultaten 1 - 1 of 1