
Sustain
OT Data Backup
We define what must be recoverable and how often it is backed up, then carry out a test restore to confirm that recovery works.
Our approach
- Stage 01AssessMeasure your exposure
- Stage 02DesignPlan the architecture
- Stage 03DeployInstall the technology
- Stage 04SustainMaintain security
Overview
What the service covers and why it matters
We define what must be recoverable and how often each item is backed up, then prove that recovery works by carrying out a test restore.
Many plants only find out whether their backups work during an incident. Testing in advance costs far less.
- Stage
- Sustain, stage 4 of 4
- Usually follows
- Health check
- Sectors
- All
At a glance
What the work covers
- Which controllers, configurations and programs must be recoverable
- Where current backups are kept, and whether they can still be read
- How often each item is backed up, and who is responsible
- How long a rebuild takes, measured in a test
- Who is authorized to restore, and what they need to do it
- What has been proven by testing, and what has not
Why it matters
Ransomware is the best-known risk, but most recoveries follow everyday failures: a controller fails, an engineer overwrites a program, or a change goes wrong.
In each case the plant needs to restore the system quickly and correctly.
The plants that recover quickly are the ones that have already tested their recovery.
Scope
What this service does not include
- Not an IT backup project.Controller configurations, PLC logic and historian data need different handling from office file servers, and IT backup tools do not cover them.
- Not a product sale.The scope and the policy come first. The choice of backup tools and storage location comes later.
- Not an untested plan.A recovery plan that has never been tested cannot be relied on. Every plan we deliver is tested before handover.
- No shutdown.We do not change or interrupt any running system during this work.
How it works
The steps and what you receive
- Scope agreed: what must be restored, and in what order
- Existing backups located and checked
- Backup frequency set according to the cost of lost data
- Recovery targets documented and agreed with operations
- A test restore carried out on suitable hardware, planned around plant operations
- The recovery plan handed over with the test results
What you receive
- Backup scopeEvery controller, configuration and program that must be recoverable, listed with an owner.
- Retention and recovery policyHow often each item is backed up, how long it is kept and how quickly it must be restored.
- Tested recovery planA plan that has been tested, with the results recorded.
Who it is for
When this service is the right choice
- You cannot say for certain what would be lost if a controller failed today
- Backups exist but no one has tested a restore
- An insurer or regulator has asked about your recovery capability
- You rely on older hardware that will eventually fail

