CIS Control 11: Data Recovery
Back up your data, keep a copy attackers can't reach, and test that you can actually restore it. When ransomware or a disaster hits, recovery decides how long you're down.
What it means
Establish and maintain data recovery practices good enough to restore your systems to a trusted, pre-incident state.
Why it matters
Nearly two-thirds of breach cost is downtime, lost business and the time it takes to find the problem (IBM Cost of a Data Breach Report 2026). Backups that work, and a copy ransomware can't reach, shorten all three.
Key safeguards
Establish and maintain a data recovery process (IG1)
Perform automated backups (IG1)
Protect recovery data, for example with encryption (IG1)
Establish and maintain an isolated instance of recovery data (IG1)
Test data recovery (IG2)
How Prominic helps
Backup and disaster recovery: offsite copies on Proxmox Backup hosts in our Illinois data centers, from simple backups up to standby systems
Air-gapped extended backups: a recovery copy ransomware can't reach
Hosted virtual desktops rebuild from one clean central image, not hundreds of individual PCs
Microsoft 365 backup and restore
Restore tests and a written recovery plan
Where it fits
Backups and an isolated copy are IG1; regular restore testing comes in IG2.
See also: Control 3: Data Protection, and Control 17: Incident Response Management.
