Customers receive quarterly notifications to check in their devices. A check in is a login, a page, and a YubiKey tap.
The tap produces a digital signature over a check in specific message, uploaded and verified against the device public keys Station70 holds.
Asynchronous processes verify every KMS key in the production environment is available for decryption.
The ciphertext scanner walks every backup component and verifies contents against the SHA 256 fingerprints stored in a separate system.
Any missing or tampered component raises an engineering alert before a recovery is ever needed, not during one.
Everything lands in a backup verification report the customer retrieves from the site and can hand to auditors, who can independently verify the device signatures.
Quarterly, low burden device attestations: insert, tap, done. Proves accounts and devices are alive.
Station70 verifies each check in against registered device public keys; auditors can re verify independently.
Asynchronous verification that every cloud key required for recovery responds.
Periodic sweep of all backup components against fingerprints held in separate storage.
The customer facing artifact: proof of backup for auditors, regulators, and insurers.
Backups fail silently: lost devices, forgotten PINs, and departed employees only surface at recovery time unless check ins force the question quarterly.
Signatures are independently verifiable, so proof of backup does not require trusting Station70’s word.
Fingerprints live in a separate storage system from ciphertexts, so tampering with one without the other is detectable.
Check ins double as personnel audits: they enumerate exactly which accounts and devices remain active on each policy.
Walk through the trust model, policy design, and rollout with our security and solutions team.