What is a cyber recovery vault?
A cyber recovery vault is a separate, isolated copy of critical backup data kept specifically for recovery after a cyberattack. It combines immutable storage, restricted network access and administration that is independent of production, so that an attacker who controls the main environment, including the primary backup system, cannot reach or alter it.
What makes a vault different from another backup copy?
An ordinary second copy protects against hardware failure and site loss. A vault is designed against an intelligent adversary with administrator rights. Its defining properties work together.
| Property | What it means |
|---|---|
| Isolation | No routine network path from production. Connectivity is limited to a controlled copy process |
| Immutability | Data cannot be changed or deleted before its retention ends |
| Separate administration | Own accounts and credentials, not in the production directory |
| Limited content | Holds what is needed to rebuild: critical systems, identity, configuration |
| Verification | Copies are checked for integrity and signs of compromise |
| Recovery space | Somewhere isolated to restore and inspect before returning to production |
How is the isolation achieved?
Approaches range from physical to logical. Some designs open a network connection only while data is copied in and close it afterwards. Others keep the link in place but allow only a pull initiated from inside the vault, or only writes to an object store that then locks each object. A logical air gap of this kind, built on S3 Object Lock in compliance mode with separate credentials, gives much of the protection of physical separation while keeping the copy current and immediately usable.
How does a vault differ from a disaster recovery site?
A disaster recovery site is built for availability. It is connected, kept in close step with production and administered by the same team with the same tools, so that it can take over quickly. Those same properties mean an attack on production tends to reach it as well: replication carries encryption and deletions across. A vault trades speed of takeover for independence. Many organizations keep both, for different events.
What should be considered when building one?
Scope comes first. A vault for everything is expensive, and the systems needed to restart the business are a smaller set. Retention has to reach back beyond the time an intruder may go unnoticed. The people and credentials able to administer the vault should be few and distinct from production administrators. And the vault needs exercising: restoring from it into a clean room at least once a year shows whether it holds what a real recovery requires. Safe copy isolation covers the underlying principle.
Frequently asked questions
Does a cyber recovery vault have to be physically air-gapped?
No. Physical separation is one approach. Logical isolation with immutable storage and separate credentials is widely used and keeps the copy current.
Is a vault the same as an immutable backup?
Immutability is one ingredient. A vault adds isolation, separate administration and a verified recovery process.
What goes into a vault?
The data and configuration needed to rebuild critical services, usually including identity systems, core applications and the backup catalog.