Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is OT Backup and Restore?

OT backup and restore is the discipline of capturing controller logic, HMI projects, and system configurations so an industrial plant can be rebuilt and returned to production after an incident.

Illustration for the cybersecurity term OT Backup and Restore
Home / Blog / Cybersecurity Terms / What Is OT Backup and Restore?
17 November 2026

What Is OT Backup and Restore?

What Is OT Backup and Restore?

Ask an industrial site how quickly it could rebuild a control system destroyed by ransomware and the honest answer is often a shrug. The Windows servers are backed up by the corporate team. The controller logic lives on an engineer’s laptop. The HMI project exists in three versions and nobody is certain which one matches the plant. OT backup and restore is the discipline that closes that gap: capturing everything needed to reconstruct a control system, and proving the reconstruction works.

Norsk Hydro’s experience in March 2019 is the reference point. LockerGoga encrypted systems across the aluminium producer’s global operations, several plants reverted to manual control, and recovery ran into months at a reported cost of well over £45 million. What saved the company was the existence of restorable data, not the absence of an attacker.

What Actually Needs Backing Up

Why OT Restores Fail

Most failed recoveries are not failures of backup media. They are failures of assumption.

  1. Version drift. The stored project does not match what is running, because a vendor made a change on site and nobody re-exported it.
  2. Missing licences. The programming software refuses to open the project on a freshly imaged machine.
  3. Firmware mismatch. A controller replaced under warranty ships with newer firmware that will not accept the archived application without conversion.
  4. Backups on the same network. Ransomware reaches the backup share because it sits in the same broadcast domain as the engineering workstations.
  5. No one has ever tried. The procedure is written, has never been exercised, and omits three manual steps the original integrator performed from memory.

Designing the Regime

Apply the familiar 3-2-1 rule — three copies, two media types, one off-site — and add an OT-specific condition: at least one copy must be offline and immutable, held somewhere ransomware with domain credentials cannot reach. Many operators keep write-once media or a physically disconnected drive in the control room safe alongside the licence dongles.

Set frequency by rate of change rather than by calendar habit. Controller logic may be stable for a year and then change ten times during a commissioning campaign, so trigger a backup from the change management process and not only from a schedule. Historian data usually follows a nightly cycle. Agree recovery time and recovery point objectives per system with the production manager, because a two-hour objective for a packaging line and a two-hour objective for a safety-instrumented function cost very different amounts.

Proving It Works

A backup is a hypothesis until a restore tests it. Run a bare-metal recovery of one engineering workstation and one controller each year, ideally during a planned outage or against spare hardware on the bench. Record how long it took, what was missing, and who had to be telephoned. Fold the result into the disaster recovery plan and into OT incident response playbooks, where the realistic restore time usually turns out to be the deciding factor in whether to run the plant manually.

The UK Angle

Under the NIS Regulations 2018, operators of essential services are assessed against the NCSC’s Cyber Assessment Framework, where Principle D1 expects tested recovery capability rather than documented intent. The NCSC’s own offline backup guidance is the clearest short statement of what good looks like.

At Privia Security, our Emergency Action Plan Services help industrial operators write and rehearse recovery procedures that match the plant as it actually is.

FAQ – Frequently Asked Questions

How Often Should PLC Logic Be Backed Up?

Tie it to change rather than to a timetable. Export and archive the project after every download to a live controller, and additionally on a quarterly schedule to catch undocumented changes. Many sites also run an automated tool that reads the running application weekly and raises an alert when it differs from the approved archived version.

Can We Use the Corporate Backup Platform for OT?

Often yes for the Windows layer, provided the agent is supported by the control system vendor and the backup traffic does not cross the IT and OT boundary uncontrolled. Controller logic, firmware, and licence files usually need separate handling, because they come out of engineering tools as files that no agent knows to collect.

Should Safety System Backups Be Treated Differently?

Yes. Safety-instrumented system applications are change-controlled under IEC 61511 and restoring one is a safety-relevant activity, not an IT task. Keep those backups in a separate, access-restricted store, record the approval chain alongside each version, and make sure the restore procedure names who must verify the function before it is returned to service.

What Is the Single Most Common Gap You Find?

Licences and dongles. Teams back up project files diligently and then discover during a restore that the programming environment will not start, the vendor licence server is unreachable, or the hardware key is in a drawer nobody can open. Record every licence, its location, and its reissue contact in the recovery documentation.

Related Terms

You May Be Interested In These

What Is Rubeus?

Cybersecurity Terms

17 November 2026

What Is Rubeus?

Read More
What Is LoRaWAN Security?

Cybersecurity Terms

17 November 2026

What Is LoRaWAN Security?

Read More
What Is iOS Forensic Analysis?

Cybersecurity Terms

17 November 2026

What Is iOS Forensic Analysis?

Read More