In a Zero-Knowledge architecture, the management of encryption keys is a critical operational decision. StateWarden delegates full authority over key custody to you.
We provide two distinct encryption modes, tailored to balance the operational requirements of large-scale deployments against the strict mathematical isolation of individual endpoints: Device Key Mode and Global Key Mode.
1. Device Key Mode (Maximum Isolation)
By default, StateWarden Realms are configured in Device Key Mode.
How it Works
When a new Agent is paired with the Realm, the administrator triggers key provisioning from the Devices page (the Key Required action). A unique Master Key is generated for that device, displayed to the administrator once, and delivered to the Agent; the Control Plane never stores the key itself. The administrator must save this key in a secure location (e.g., an Enterprise Password Manager).
The Security Profile
- Cryptographic Isolation: Every single server, workstation, and database node possesses its own distinct encryption key.
- Blast Radius Containment: If the Master Key for the
web-server-01backup is somehow compromised or leaked by an employee, the attacker gains absolutely zero insight into the backups ofdatabase-node-primary. - The Trade-off: Administrative overhead. Restoring 50 different servers requires an administrator to retrieve and input 50 different Master Keys into the respective Agents or Recovery ISOs.
Device Key Mode provides the strongest compartmentalization of the two modes and is recommended for environments with strict isolation requirements, such as regulated or classified data processing.
2. Global Key Mode (Enterprise Operations)
For large-scale enterprise environments where speed of deployment and simplified disaster recovery are paramount, StateWarden offers Global Key Mode.
How it Works
Instead of each Agent generating a unique key, the Realm Administrator provisions a single, cryptographic Global Master Key.
Crucially, because StateWarden is a Zero-Knowledge system, this key is NEVER saved to the Artemis Control Plane database.
The Provisioning Process ("Late-Joiners")
When a new Agent (a "Late-Joiner") pairs with a Realm operating in Global Key Mode, it cannot perform backups until it receives the key. On the Devices page the device is flagged with a KEY REQUIRED chip, and its action button reads Sync Master Key. (If the Realm's Global Master Key has not been generated yet, the action instead shows Key Managed Globally, and the key must first be generated on the Security & Compliance page.)
- The Administrator clicks Sync Master Key on the affected device.
- The Administrator pastes the Global Master Key into the provisioning dialog and submits it.
- The Control Plane delivers the key to the Agent. For agents that support it, the key is encapsulated with the device's ML-KEM (Kyber) public key (PQ-hybrid); legacy agents receive it over the established mTLS channel.
- The Agent adopts the key and the device becomes compliant (SECURED). While a sync is in progress, the chip shows SYNCING....
- The Dashboard clears the key from the dialog after submission; the Control Plane never stores the key itself.
Per-device key rotation is not available in Global Key Mode. Key rotation is performed at the Realm level on the Security & Compliance page, and rotating the Global Master Key invalidates all existing backups in the Realm.
The Security Profile
- Operational Velocity: Restoring an entire datacenter (500 VMs) during a crisis requires only one Master Key to be managed and injected into the recovery processes.
- Deduplication Efficiency: Because all Agents use the same encryption key, the PrimeKEM engine achieves maximum cross-device deduplication on the Driad storage nodes. A Windows update installed on 500 workstations is only stored once globally.
- The Trade-off: If the Global Master Key is compromised, the entirety of the Realm's backup repository is exposed.
3. Switching Encryption Strategies
The encryption strategy is selected on the Security & Compliance page (/security) under Encryption Strategy: Per-Device Isolation or Global Master Key.
Changing the strategy is a destructive operation in either direction and is protected by step-up MFA:
- All existing backups in the Realm are invalidated (soft-deleted).
- The encryption keys of all paired devices are revoked; every device must be re-provisioned under the new strategy before backups can resume.
Treat a strategy change as a planned maintenance operation, not a toggle. Choose the strategy that aligns with your organization's threat model and disaster recovery SLAs before populating the Realm with production backups.
StateWarden: Resilience Engineered.