The problem
Why it matters.
Encrypting large data inside an HSM is slow; leaving keys on application servers is unsafe. Envelope encryption solves both, if the key-encryption key is well guarded.
With Roost
How Roost handles it.
01
EncryptYour application encrypts data with a data key.
02
WrapRoost wraps the data key with a key-encryption key that never leaves it.
03
UnwrapEach unwrap passes policy, limits and the quorum.
SIGNED
RecordWho opened which data, and when, is on record.
What you get
In the console.
- Only authenticated encryption modes; nonces are generated by the appliance
- AES-256-GCM and ARIA-256-GCM
- One key per organization: delete it and that data is unreadable, backups included
- Key versions rotate without re-encrypting data
AxowlacmeRoostM
Keys
27keys
3rotating
0exportable
| Name | Purpose | Version | Quorum | Last used |
|---|---|---|---|---|
| release-signing | code-signing | v3 active | 2 of 3 | 2 min ago |
StatusArmed PolicyApproval required Born inROOST-26-0001 ExportNever | ||||
| data-key-eu | data-key | v2 active · v1 decrypt-only | 2 of 3 | 10 s ago |
| tls-www | tls | v1 active | 2 of 3 | 1 s ago |
| ca-intermediate | ca | v1 active | 2 of 3 | 3 days ago |
See Roost refuse an unapproved signature.
A 30-minute live demo with our engineers.