QUANTASEAL
QUANTASEAL
This document specifies the encrypted payload envelope used by QuantaSeal for all data-in-transit and at-rest operations. It is published as an open specification so security researchers can verify the design and enterprise customers can decrypt their own data without QuantaSeal software.
Security researcher audit
Independent verification that the cryptographic design is correct - not just claimed.
Key escrow / business continuity
Enterprise customers can decrypt their data with any compliant liboqs implementation if QuantaSeal ever ceases to operate.
Third-party interoperability
Any open-source project can implement a compatible encoder or decoder using this spec.
{
"encrypted": {
"ciphertext_kem": "<base64, exactly 1088 bytes - ML-KEM-768>",
"ciphertext_data": "<base64 - nonce[12] || AES-GCM-ciphertext || tag[16]>",
"tenant_id": "<uuid>",
"algorithm": "ML-KEM-768"
},
"signature": {
"pqc_signature": "<base64, ≤ 3309 bytes - ML-DSA-65>",
"hmac_signature": "<base64, 64 bytes - HMAC-SHA-512>",
"tenant_id": "<uuid>",
"algorithm": "ML-DSA-65+HMAC-SHA-512"
}
}| Algorithm | Standard | Security Level | Public Key | Secret Key | CT / Sig | Notes |
|---|---|---|---|---|---|---|
| ML-KEM-768 | NIST FIPS 203 | 3 | 1,184 | 2,400 | 1,088 | shared secret = 32 bytes |
| ML-DSA-65 | NIST FIPS 204 | 3 | 1,952 | 4,032 | ≤ 3,309 | max signature bytes |
| AES-256-GCM | NIST FIPS 197 + SP 800-38D | - | - | 32 | 16 (tag) | nonce = 12 bytes |
| HKDF-SHA-512 | RFC 5869 | - | - | - | 32 | output key length (AES key) |
All sizes in bytes. Source: NIST FIPS 203 §4 Table 2, FIPS 204 §4 Table 2, FIPS 197, RFC 5869.
Enterprise customers can decrypt all QuantaSeal-protected data independently using any conformant ML-KEM-768 + AES-256-GCM implementation (e.g. liboqs, AWS Encryption SDK with custom KDF).
Required key material (exportable on request per the QuantaSeal SLA):
Live NIST Parameter Verification
Every result on the attestation page is generated by running fresh ML-KEM-768 and ML-DSA-65 operations on our production backend - validated against this spec in real time.