We review backup administration accounts, repository access and retention settings. We restore selected workloads and verify the data and that the application runs again. If the backup infrastructure needs to be set up or renewed after the review, this is done within enterprise backup and disaster recovery setup.
Immutability, an offline copy, separate privileges and restore testing are different controls; we evaluate each separately. We measure the restore time during testing.
01
Is a cloud backup enough on its own?
A cloud copy meets the off-site requirement; but if it can be deleted with the same credentials, it doesn’t protect against ransomware. Immutability and separate privileges are needed.
02
How often should restores be tested?
The frequency depends on the system’s criticality and how quickly it changes. A common starting point is a restore test every three months for critical systems and a comprehensive exercise once a year.
03
Is Microsoft 365 data in scope too?
Yes. The need for separate backup and retention periods is evaluated for Exchange Online, OneDrive, SharePoint and Teams data.
04
What should we do first in a ransomware incident?
Notify the people responsible in the incident response plan. Isolating affected systems from the network, checking the state of the backups and preserving evidence are carried out by the people defined in the plan.
Implementation approach
Controlled, documented, sustainable
01 / ANALYSIS
Current state
Backup coverage, retention periods and the architecture are reviewed.
02 / PLAN
Access path analysis
The access paths to the backups if a privileged account is compromised are mapped.
03 / EXECUTION
Hardening
Identity, network and storage separation and immutability are put in place.
04 / HANDOVER
Recovery exercise
Critical systems are restored and the times are measured.