Essential Eight RB-ML1.2 Ensure backups are synchronised for restoration to a common point in time
What it says
Backups of data, applications and settings are synchronised to enable restoration to a common point in time.
Quoted as published. Everything else on this page is written by Control Stack.
What it means
In plain EnglishEnsure data, applications, and settings are backed up together to restore them to the same point in time.
This control is about making sure that whenever you back up your computer data, your applications, and your settings, they are all synced up. It's like having a time machine that can take your entire computer system back to a specific date. Without this, if something goes wrong, you might end up with data that doesn't match the applications or settings, which can cause more headaches during recovery.
Free. Save your status, tasks and notes.
Why it matters
Unsynchronised backups risk data mismatch, leading to extended downtime and potential data loss during recovery, harming operational continuity.
How to implement
The IT team should schedule regular backups of data, applications, and settings to occur at the same time.
Use backup software that allows all elements to be backed up simultaneously.
System administrators should verify that all critical data and applications are included in the backup process.
Use a checklist to ensure no important elements are missed.
The IT team should configure alert notifications for any failures in the backup syncing process.
Use an automated system to send alerts to IT staff immediately if backups fail to sync.
Security officers should ensure backup data is encrypted to protect it during transfer and storage.
Implement encryption protocols on backup systems.
The IT team should conduct regular tests of the entire restoration process to ensure it can effectively restore systems to the same point in time.
Schedule these tests as part of your disaster recovery exercises.
Keep it running
Regularly verify backup synchronisation so data, apps and settings can be restored to the same point in time, preventing mismatch and recovery errors.
Evidence and audit
- Check 1 of 2What an auditor asks for
Ask for
How does the organisation ensure that backups of data, applications, and settings are synchronised?
Look at
Examine the backup logs and configurations for evidence of scheduled synchronised backups.
Good evidence
The organisation has documented backup procedures showing synchronised backup schedules and logs that demonstrate successful synchronisations.
- Check 2 of 2What an auditor asks for
Ask for
How does the organisation test the restoration of backups to a common point in time?
Look at
Review the disaster recovery exercise reports that include results of restoration tests.
Good evidence
The organisation conducts regular disaster recovery exercises with documented restoration tests that verify data, applications, and settings are restored synchronously.
Mappings
Closest match in ASD Information Security Manual: ISM-1810, Ensuring data backup synchronisation, which asks for the same thing.
ISO/IEC 27001: 1 mapping
This control partially meets A.8.13.
E8-RB-ML1.2 requires backups of data, applications and settings to be synchronised so restoration can occur to a common point in time. ISO/IEC 27001:2022 Annex A 8.13 is broader because it requires maintaining backup copies of information, software and systems and regularly testing them in line with a backup policy, without mandating synchronisation specifically. E8-RB-ML1.2 can be implemented as a specific design requirement within an Annex A 8.13-compliant backup program.
ASD Information Security Manual: 7 mappings
This control is equivalent to ISM-1810.
ISM-1810 requires backups of data, applications and settings to be synchronised so restoration can occur to a common point in time. E8-RB-ML1.2 states the same requirement with the same restoration objective and scope across data, applications and settings. Implementing E8-RB-ML1.2 would largely satisfy ISM-1810 without needing additional interpretation.
This control partially meets ISM-1511.
E8-RB-ML1.2 requires synchronising backups across data, applications and settings to enable restoration to a common point in time. ISM-1511 is broader as it requires performing and retaining backups in accordance with business criticality and continuity requirements, without being limited to synchronisation. Synchronisation in E8-RB-ML1.2 is a specific quality attribute that can sit within the wider backup regime described by ISM-1511.
This control partially meets ISM-1555.
ISM-1555 requires mobile devices to be backed up prior to overseas travel alongside updating and data minimisation steps. E8-RB-ML1.2 relates by specifying a quality attribute of backups (synchronised to a common point in time) that strengthens the usefulness of the pre-travel backup required by ISM-1555. ISM-1555 does not require point-in-time synchronisation, so it is a narrower, event-based backup requirement compared with the broader backup consistency requirement in E8-RB-ML1.2.
This control partially overlaps ISM-1547.
ISM-1547 requires organisations to develop, implement, and maintain data backup processes and procedures. E8-RB-ML1.2 relates by specifying a concrete procedural/technical requirement: backups must be synchronised so restoration can occur to a common point in time. ISM-1547 is broader because it does not mandate synchronisation specifically, but it would typically include it where required by business needs.
This control partially overlaps ISM-1548.
ISM-1548 requires organisations to develop, implement and maintain data restoration processes and supporting procedures. E8-RB-ML1.2 relates by requiring backups be synchronised so restoration can occur to a common point in time, which is a specific design requirement that restoration procedures must account for.
This control partially overlaps ISM-1811.
ISM-1811 requires backups to be retained securely and resiliently so they remain usable when needed. E8-RB-ML1.2 relates by requiring synchronisation of backups to enable restoration to a common point in time, which is a key resilience characteristic for recovery. ISM-1811 is broader about secure/resilient retention, while E8-RB-ML1.2 is specifically about consistency and recoverability across systems rather than retention security controls.
This control supports ISM-1515.
ISM-1515 requires organisations to test restoring data, applications and settings from backups to a common point in time during disaster recovery exercises. E8-RB-ML1.2 requires backups to be synchronised so that such a common point-in-time restoration is possible. Without the synchronisation in E8-RB-ML1.2, the restoration test in ISM-1515 cannot be meaningfully executed to a common point in time.
ASD Essentials for enterprise IT: 1 mapping
- IT.PRO-10.1Back up data, applications and settings on schedule to encrypted, resilient storagePartially overlaps
This control partially overlaps IT.PRO-10.1.
IT.PRO-10.1 requires scheduled backups of important data, applications and settings to secure, resilient, encrypted storage that is immutable, offline, isolated or equivalently protected; E8-RB-ML1.2 requires those backups to be synchronised so they can be restored to a common point in time, adding a consistency requirement.
Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.