Skip to content

Backups & integrity

Where: Backups & integrity in the Operations group, /app/records: Preserve equipment records. Verify every restore point. It is shown when asset operations are turned on for your organization; the vault behind it is turned on separately.

What it answers: what has a backup, what needs attention, has a backup changed since it was signed, did both signatures verify, are the signing keys trusted, when was it last checked, and has recovery actually been tested.

Each of those is a separate result. There is no single "everything is fine" badge, and a verified backup only means the stored files have not changed since they were signed: Integrity verified. Device operation not assessed. How the protection works, in depth, is in Integrity and backups.

The page at a glance

Summary cards (each opens the matching list):

Card Meaning
Assets with backups Active assets with at least one completed backup in the selected scope
Need attention Assets whose latest backup failed or could not be fully verified, whose backup creation did not finish, or that are due for a recheck under your policy
Restore tests due Completed backups with no recovery test recorded within your restore test interval. Without an interval it shows No policy set; no due date is ever invented

Tabs: Device backups, Workspace backups, Verification history (every check, with its outcome) and Operational history (identity, tag, label, maintenance and edit events).

Device backups lists each backup as asset and backup (for example PLC-03 · Siemens S7-1500, Device configuration · Revision 12), with site, type, created, size, verification and last checked. Filter by site, area, vendor, backup type, verification state and date; search by asset tag, device, product or model.

Backup types: Device configuration, PLC project, HMI project or export, Firmware image, Supporting document, Workspace export, Other. The type only describes the file: storing a firmware image never changes the firmware recorded for a device.

Revisions are permanent. A new upload creates a new revision; an earlier revision is never overwritten.

The backup passport

Open a row to see its passport: the device, site, type, revision, who created it and when, file count and size, and one line per check:

Check Results it can show
Conventional signature (Ed25519) Verified, Failed, Missing, Unsupported algorithm, Untrusted key, Trust status unavailable, Not checked
Post-quantum signature (ML-DSA-65) the same, checked on its own: a valid conventional signature never hides a missing or failed post-quantum one
File hashes Match, Do not match, Missing, Storage unavailable, Not checked
Signing keys Trusted, Not trusted, Trust status unavailable, with the time the key list was read
Restore test Not performed, Overdue, or the date of the last recorded test

The overall outcome:

Outcome Meaning
Backup unchanged, both signatures verified Every check passed, with keys from the BreachSpider key list
Verification failed A check failed. Do not rely on this backup until it is investigated
Verification incomplete A check could not be completed (for example storage or the key list could not be reached). It confirms neither a change nor no change
Legacy protection Stored in an earlier format with one signature. It is never shown as dual signed
Needs recheck Last checked before the current policy, or due under your interval. Verify again

Actions: Verify again, Preview restore (what a restore would bring back; nothing is restored), Compare versions, backup history, download, Download verification receipt, and Record a recovery test. Technical details shows the algorithms, manifest format, file digests, key ids and fingerprints and every check.

Verification receipts

A receipt records one verification: the backup and revision, what was checked, each result, when, and the ids of both signing keys. Copy it as text, or download it as PDF or JSON, to keep with your maintenance or audit records. A receipt states its limits in plain words; it is a record of a check, not a certificate.

Check a file

Check a file checks a backup package you downloaded, without restoring it or importing anything. The page says before you choose a file what runs in your browser and what asks BreachSpider: the file is read in your browser; the signed list and its signatures (never the file contents) are checked against the BreachSpider key list. A locked package is checked as stored; only after you unlock it with the passphrase are its contents checked too, and the result says which was done.

Create backup

Create backup has four steps: What (the device and the backup type), Files, Review, and Result (encrypt, upload, sign and verify, then the actual results). A backup is only Completed once its files and both signatures are stored and the first verification passed; an interrupted upload, a signing or storage failure can be retried or cancelled, and retrying never creates a duplicate revision.

The vault underneath

Per device, files are kept as numbered revisions, encrypted in your browser before upload. BreachSpider never holds your key and cannot read your files, their names, types or notes. Every revision is signed when stored: a separate signing service measures the stored encrypted bytes itself and signs a record of them with two keys, Ed25519 and the post-quantum ML-DSA-65. See Post-quantum signatures.

Setting up the vault (owners and admins)

  1. Choose a vault passphrase of at least 12 characters. It never leaves your browser.
  2. BreachSpider shows a recovery key once (six groups of five characters). Print it or write it down and store it apart from the passphrase, then confirm you stored it.

Lost passphrase and lost recovery key means lost files

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

Changing the passphrase later re-wraps the vault key only; files do not need to be encrypted again.

Storing a version

On the device panel, choose the kind (configuration or document), the file (up to 100 MB) and optional notes (also encrypted), then Encrypt and upload. The screen shows Encrypting in this browser, Uploading the encrypted file, Sealing and verifying, then "Version N stored, sealed and verified". If the upload does not complete, nothing is sealed. Uploads and downloads need a sign-in within the last 30 minutes.

Downloading

Download verifies the version first. If it does not verify, routine download is blocked; a vault admin can hand over the encrypted file for investigation with a written reason, which is logged. After download your browser decrypts the file and checks it against the digest sealed at upload: "Recovered-file integrity: Verified" means you have exactly the bytes that were stored.

Check current file: has the device's configuration changed?

Check current file answers "is the file on the device now the same as this backup?":

  1. Export the current configuration from the device and choose that file.
  2. Your browser computes its digest and compares it with this version's sealed digest. The file never leaves your browser.
  3. The result is Unchanged (byte-for-byte identical to version N) or Changed (its digest does not match).
  4. BreachSpider records only the outcome: who, when, which version, the result and the backup's own integrity state at that moment. Never the file, its name or a digest.

If the stored backup itself did not verify at that moment, the comparison is recorded as such and the screen says it cannot be relied on.

What Unchanged and Changed mean

Unchanged shows identical bytes only. It does not show the configuration is correct or free of malware. Changed means the bytes differ. Some devices write a timestamp or other session data into every export, so two exports of the same configuration can differ; review the change, and store the current file as a new version if it is intended.

Deleting a version

A vault admin can delete a version: the stored file is removed; its seal and digests are kept as a record (Deleted (seal kept)).

Workspace backups

Download encrypted backup saves your devices, sites, tags, identifiers and maintenance records as one file, encrypted in your browser with a passphrase you choose (at least 12 characters). BreachSpider never sees the passphrase or the contents of the file, and does not keep a copy: the file goes to your computer. Store it somewhere other than that computer, and keep the passphrase apart from it. An older workspace file can be opened and stored again as a signed workspace backup.

Restore from a backup opens the file in your browser and previews what restoring would bring back: removed devices (checked again after the restore), identifiers and maintenance records. Restore brings back only what is missing now, never overwrites anything that exists, restores only into the organization it came from, and one Undo reverses it. A wrong passphrase, a damaged or altered file, or a file that is not a BreachSpider backup is reported as such.

API

Backups & integrity is part of the web app and needs a signed-in session; API keys cannot use it.