When a vendor claims their platform is secured by "enterprise-grade AES-256 Encryption," they are usually telling a half-truth. While AES-256 is a secure standard, the true measure of a system's security lies not in the algorithm, but in how the keys are managed and where the encryption occurs.
If the vendor's central server holds the decryption keys, their platform is compromised by design. A breach of their database exposes your entire infrastructure.
StateWarden rejects this model. Our data protection relies on Zero-Knowledge principles and a Cascade Cryptography architecture: every chunk is protected by multiple independent authenticated-encryption transformations using AES-256-GCM and ChaCha20-Poly1305.
1. The Zero-Knowledge Imperative
The foundational rule of StateWarden is Zero-Knowledge by construction: The Control Plane (Artemis) and the Data Plane (Driad) must never possess the keys required to decrypt your data.
The Master Encryption Key exists in only two places:
- Safely stored in your physical or digital vault (e.g., a password manager, an offline backup).
- In the volatile RAM of the local StateWarden Agent executing the backup or restore.
Because the StateWarden infrastructure never stores your Master Key, a breach of the data-center infrastructure does not expose readable user data. Stored objects are encrypted, deduplicated binary blobs that cannot be decrypted without the client-side key.
2. Cascade Cryptography: Defense in Depth
Relying on a single cipher is a single point of failure. The StateWarden architecture employs a cryptographic cascade-multiple, independent cryptographic transformations layered upon each other.
Furthermore, the initial provisioning of the Agent's identity and secrets bypasses legacy TLS key exchange. Initial trust is established using a Quantum-Resistant "PQ-Hybrid Payload" encapsulated by ML-KEM (Kyber). This protects the provisioning exchange against "Harvest Now, Decrypt Later" attacks, in which recorded traffic is stored today and decrypted years later if cryptographically relevant quantum computers become available.
Once the post-quantum foundation is laid, data at rest and in transit is secured by the following mechanisms:
Content-Addressed Encrypted Chunks (BLAKE3)
Before any data is encrypted, the Agent divides the volume into blocks and calculates a collision-resistant BLAKE3 hash for each chunk. This hash drives the deduplication logic: if a block is identical to one already stored in the Driad vault, it is not transmitted again. This is the foundation of our high-speed deduplication.
Even content hashes can leak metadata. If an attacker knows the hash of a specific sensitive file (e.g., a standardized financial template), they could theoretically check whether a matching chunk exists on a storage node. PrimeKEM mitigates this by storing content-addressed encrypted chunks (BLAKE3): the chunk IDs stored on the Driad servers cannot be computed from the plaintext - or from a known plaintext hash - by anyone who does not hold the Master Key.
Independent Authenticated Encryption
The chunk payloads are protected by multiple, independent authenticated-encryption (AEAD) transformations using AES-256-GCM and ChaCha20-Poly1305. Both constructions provide confidentiality and integrity, and both benefit from mature, hardware-accelerated implementations. If a vulnerability were ever discovered in one algorithm or its implementation, the other transformation would still protect the payload.
3. Integrity Verification
Data encryption is meaningless if the underlying data becomes corrupted on the disk ("bit rot"). When you initiate a bare-metal restore, you must be able to trust that the data is intact.
StateWarden enforces integrity at two points:
- Read-After-Write (RAW) Verification: When a Driad Storage Node receives an encrypted chunk from an Agent, it writes the data to its physical disks. Before acknowledging success, Driad re-reads the data from the platter and verifies the chunk's integrity against the transmitted hash.
- Pre-Decryption Hash Checks: During a restore, the Agent downloads the encrypted chunk. Before decryption begins, it hashes the encrypted payload and compares it against the manifest. If a single bit is out of place, the Agent drops the chunk and retries the download.
Corrupted chunks fail verification and are re-fetched before they ever reach the decryption pipeline.
4. The Custody of Keys
Because StateWarden utilizes Zero-Knowledge encryption, there is no "Forgot Password" link for your Master Key.
If you lose your Master Key, your backups are permanently inaccessible. StateWarden operates no key-recovery mechanism: the same design that prevents the platform operator from reading your data also prevents any form of password reset.
Manage your keys with the utmost care. They are the only bridge between a sea of randomized data and the restoration of your infrastructure.