Skip to content

Back up and verify a configuration

Store a device's configuration, PLC or HMI project, firmware image or supporting document, check later that the stored backup has not changed, compare it with the file on the device today, and hand over a receipt.

Roles: owners and admins set up the vault, change the policy and the vault passphrase, and delete backups. Owners, admins and editors create and download backups. Viewers can open backups and their passports and verify them. Uploads and downloads need a sign-in within the last 30 minutes: if it has been longer, sign in again.

What happens to your file

  1. The file is encrypted in your browser before it is uploaded. The vault passphrase never leaves your browser, so BreachSpider cannot read your files.
  2. The BreachSpider signing service measures the stored encrypted file and signs a list of it with two keys: a conventional key and a post-quantum key.
  3. Verifying checks that the stored file still matches that list and that both signatures check out.

Verification shows a backup has not changed since it was signed. It does not show the device runs correctly, or that the content was free of unwanted changes when it was signed.

1. Set up the vault (once, owner or admin)

  1. Open Backups & integrity (under Operations). While the vault is not set up, the page says so and shows the Set up the vault form to owners and admins.
  2. Type a Vault passphrase of at least 12 characters and the same again in Repeat passphrase. It never leaves this browser.
  3. The form shows your recovery key, once. Print it or write it down and store it apart from the passphrase.
  4. Tick I have stored the recovery key and press Set up the vault.

If the passphrase and the recovery key are both lost, no one can open the files, including BreachSpider.

2. Unlock the vault

Each time you work with backups, type the Vault passphrase and press Unlock (or Use the recovery key). Until you do, the page says "Unlock the vault to create or open backups."

3. Create a backup

  1. On Backups & integrity, press Create backup. It has four steps: What, Files, Review and Result.
  2. What: keep Device backup, type in "Find a device by tag, name or model" and pick the device. Choose the Backup type: Device configuration, PLC project, HMI project or export, Firmware image, Supporting document or Other. Storing a firmware image never changes the firmware installed on a device. Press Next.
  3. Files: choose the File. Optionally add a Name and Notes. The name, notes and file name are encrypted in your browser; BreachSpider stores only sizes, times and the device link. Press Next.
  4. Review: check the device, type and file, then press Create backup. The file is encrypted, uploaded, signed with both keys, and the stored copy is verified.
  5. Result: BreachSpider confirms, for example "Revision 1 stored, signed and verified." Press Backup passport to open it.

The backup is listed under Device backups with its site, type, date, size and Verification state, and on the device itself under Documents and configuration vault.

4. Read the backup passport

Open any backup with Open in the list. The passport shows:

  • The headline, for example Backup unchanged with "Both signatures verified".
  • Each check: Conventional signature, Post-quantum signature, File hashes, Signing keys and Restore test.
  • The statement "Integrity verified. Device operation not assessed."
  • The asset, product, site, backup type and file name, revision, who created it and when, the number and size of files, and the last verification. Technical details lists algorithms, digests and key fingerprints.

Its buttons: Verify again, Preview restore, View backup history, Download backup, Download backup package, Download verification receipt and Record a recovery test.

5. Verify again and share a receipt

  1. In the passport, press Verify again. The checks run again and the result is added to Verification history (a tab on Backups & integrity), with each check and who ran it.
  2. Press Download verification receipt. The receipt records one verification: the backup, the result, each check, and both signing keys by fingerprint. It contains no secrets.
  3. Choose Copy text, Download PDF or Download JSON, and hand it to the auditor or the customer.

6. Is the device still running this configuration?

Compare the file on the device today with a stored version, without uploading it:

  1. Open the device (Assets, a QR scan or a search) and unlock the vault in its Documents and configuration vault section.
  2. Next to the version, press Check current file and choose the file as exported from the device now.
  3. The file is hashed in your browser and compared with the sealed digest:
  4. "Unchanged: the current file is byte-for-byte identical to version 1."
  5. "Changed: the current file differs from version 1 (its digest does not match the sealed digest)." Review the change, then store the current file as a new version if it is intended.

"Unchanged" shows identical bytes only. It does not show the configuration is correct or free of malware.

7. Check a downloaded backup package

Use this when someone holds a backup outside BreachSpider and wants to know it has not changed.

  1. In the passport, press Download backup package. You get a .bspkg file (for example ETP-0001-r1.bspkg) with the encrypted files, the signed list and both signatures.
  2. On Backups & integrity, press Check a file.
  3. Tick Also check the post-quantum signature with BreachSpider. Your browser checks the conventional signature itself; for the post-quantum one BreachSpider receives only the signed list and the two signatures, never the files. Without this box the result is Verification incomplete.
  4. Press Choose a file, pick the package and press Check. The result, for example Matches signed backup, lists each check. Checking never restores, imports or changes anything.

For checks without BreachSpider, Download public keys and use the offline checker described there.

8. Record a recovery test

When your team proves a backup can be used, for example by loading it into a spare controller or opening the project in the vendor tool:

  1. In the passport, press Record a recovery test.
  2. Choose the Outcome (Passed, Partly passed or Failed), the Date performed, Performed by and an Evidence note, then press Record test.

The passport's Restore test then reads, for example, "Passed on 2026-11-09". BreachSpider records the test; it does not perform or judge it.

9. Set the policy (owner or admin)

Under Policy on Backups & integrity, set Restore test every (days) and Verify again every (days), then press Save policy. Without these intervals nothing is shown as due. With them, the figure Restore tests due and the Need attention list show what is due.

Restoring

Preview restore in the passport shows what a restore would involve. Nothing is restored and nothing is written to any device: a device backup is restored with the vendor's own tool after Download backup. BreachSpider never writes to equipment.

Next

Turn a finding into a change ticket