A list of all company backups — what is backed up, how often, where to, and when a restore was last rehearsed.
Register of backup plans (scope, asset mapping, frequency, retention, storage location, tool, offline/immutable copy, encryption, monitoring, RPO, owner, test interval) and logged restore tests; ten templates each with a guide (provider coverage, tools, cost range, steps); key figures for overdue tests, plans without a protected copy and critical assets without an active plan. Supports controls PR.IP-4, PR.DS-4 and PR.PT-5 of the ICT minimum standard.
Almost every company backs up its data somehow. The real question is whether the backup can actually be restored when it matters and how long that takes. This module records both: what is backed up and when restoring it was last rehearsed. It backs nothing up itself — it is the register for it.
The register separates target state and evidence. The plan is the target state: scope, assigned assets, frequency, retention, storage location, tool, the four protection markers (offline copy, immutability, encryption, monitoring), RPO, owner and test interval. The restore test is the evidence: date, scope, result, measured duration and findings. The due date derives from the last successful test — a failed test does not reset the clock. The module supports PR.IP-4, PR.DS-4 and PR.PT-5 of the ICT minimum standard; it documents, it does not back up.
Features
One entry per backup: what, how often, where to, how long retained, with which program.
Link to the devices and systems from the asset register.
Ticks for offline copy, immutable storage, encryption and monitoring.
One owner per backup and an interval at which it is tested.
Log of rehearsed restores with result, duration and findings.
Key figures: overdue tests, backups without a protected copy, important devices with no backup at all.
Templates for typical backups and a suggestion for every important device without a backup.
Practical tips derived from your own entries, for example on the 3-2-1 rule or overdue tests.
Backup plans with scope, frequency, retention, storage location and tool.
Mapping to the assets of the asset register instead of re-recording the systems.
Ransomware resilience as a pair of markers: offline copy or immutable storage.
RPO per plan with a note if the chosen frequency does not meet it.
Restore tests with scope file, system or full restart, result, duration and findings.
Key figures: active plans, overdue tests, plans without a protected copy, critical assets without an active plan.
Template catalogue and suggestions per asset without a plan, matched to type and criticality; adopted as a planned plan.
Rule-based practical tips per plan (3-2-1, protected copy, encryption, RPO, test scope), condensed on the overview.
Backup status on the asset in the asset register and comparison of RPO and restore duration with the targets of dependent business processes.
How it works
You create a backup entry and describe what it covers.
You pick the devices and systems that belong to it.
You enter frequency, retention, location and program.
You name an owner and how often it should be tested.
After every test you record whether it worked, how long it took and what stood out.
Create the plan and assign the assets it covers.
Set the protection markers and the RPO and check the frequency against the RPO.
Define owner and test interval; the default is six months.
Rehearse a restore and log result, duration and findings.
Use the gap figures as a work list: overdue tests, unprotected copies, critical assets without a plan.
Use it forShow that the backups exist and can actually be restored.
Use it forDocument the backup concept and track the testing duty.
In the ICT minimum standard
PR · Protect
PR.IP-4Ensure that backups of your information are conducted, maintained and tested on a regular basis (check that you are able to revert to your backups).
PR.PT-5Ensure that mechanisms (e.g. failsafe, load balancing, hot swap) are implemented to achieve resilience requirements in normal and adverse situations.
RC · Recover
RC.RP-1Ensure that recovery plans can be executed properly after any cybersecurity incident.
Known limitationsThe module only documents — it backs nothing up, checks no backup software and cannot tell whether a backup run actually happened. Due dates are calculated from the recorded test interval.