Sealing yes, opening no
The platform only holds the public part of the key. The private part is created once and immediately overwritten server-side. Taking over the platform gains an attacker no emergency package at all.
ISMS & Risk
Emergency Kit
The plan you reach without a network, without servers and without us
Emergency plans have an awkward property: they usually sit in exactly the system that is unreachable when it matters. The emergency kit is built for the case where platform and data centre are encrypted. The crisis team then reaches emergency and recovery plans without a network and without servers, along with the BIA including RTO and RPO, backup plans with storage location and restore procedure, asset, rack and network inventory, the firewall rule set, contact details and the released documents in the original. The threat model behind it is unusual but consistent: in an emergency the platform itself counts as compromised. It can therefore seal packages and open none of them.
BSI 200-4ISO 22301ISO 27001
Features
Your benefits
No credentials, only where to find them
The package holds no password but the place of custody: which envelope, which safe, which person. The organizational question stays organizationally solved.
Cold start with a sequence
From BIA timings, dependencies and the power chains and rack positions in DCIM, a cold-start plan for the data centre is derived, with critical path and cumulative recovery time.
Prove it, do not claim it
Three test types with clear meaning: verify the signature, open the package for a test, run a timed exercise. Only the opening test finds the case where the file is flawless and the device key is gone.
Capabilities
All capabilities at a glance
- Encrypted, signed emergency package from your ISMS data
- Standalone offline viewer, usable without installation
- Printed recovery key for the safe
- Check value detects a mistyped key card
- Two scopes: portable core and full instance image
- Emergency and recovery plans, BIA with RTO and RPO
- Backup plans with storage location and restore procedure
- Asset, rack and network inventory plus firewall rule set
- Contacts for crisis team, service providers and suppliers
- Released documents in the original
- Cold-start plan with start sequence and critical path
- Emergency laptops fetch their package themselves and report back
- Status by age of the data, not by agent contact
- Full system in a container on designated nodes
- Readiness evidence for container runtime and air-gap images
- Opening tests and exercises with measured time to open
Result
Emergency readiness you can evidence: not the assurance that a package exists, but the measured time until someone has opened it.
Experience Emergency Kit live
Schedule a no-obligation demo – we will show you the module with your own use cases.