Technology · HSM

Hardware is the root of trust.

FIPS 140-2 Level 3 modules hold keys that cannot be extracted — physical tamper opens the module, zeroizes the memory, and leaves an audit trail. Validator keys, KMS root keys, and attestation keys never touch RAM outside the HSM.

What FIPS 140-2 Level 3 actually requires

The certification that regulated banks insist on, broken down.

Tamper-evident

Physical enclosure shows evidence of attempted entry; the module zeroizes all plaintext CSPs on detection.

Identity-based auth

Every operator authenticates per-session with split-knowledge quorum. No shared admin password.

Trusted path

Key material enters/exits only via cryptographically authenticated channels — never over unprotected interfaces.

EFP / EFT

Environmental failure protection and test — fault injection via voltage, temperature, or timing is defended and logged.

Certified modules we deploy

We deploy across multiple vendors for vendor-diversity; a single vendor CVE cannot compromise the validator set.

VendorCertification / deployment
AWS CloudHSM
FIPS 140-2 L3
16 AWS regions, dedicated single-tenant
Azure Dedicated HSM
FIPS 140-2 L3
Thales Luna Network HSM
GCP Cloud HSM
FIPS 140-2 L3
Marvell LiquidSec
Thales Luna Network HSM 7
FIPS 140-2 L3 + Common Criteria EAL4+
On-prem / colo
YubiHSM 2
FIPS 140-2 L3 (limited)
Edge / dev / small cohort

What lives in the HSM.

The HSM is the last line. Only keys that must never leak live there — everything else is wrapped and stored in KMS or MPC cohorts.

UseAlgorithm / policy
Validator keys (Quasar)
BLS12-381 + ML-DSA
Sign on consensus votes; rate-limited
Root CA for mTLS
P-384 ECDSA
Sign intermediate CAs yearly; never exported
KMS master KEK
AES-256
Wraps all tenant DEKs
Compliance attestation
Ed25519
Signs SOC 2 / ATS-N log roots
HSM-backed MPC share
CGGMP21 share (secp256k1)
One share of treasury cohort; quorum required

Operational controls.

Quorum login: m-of-n smart-card operators, no single admin
Geographic split: shares of master KEK held in separate data centers
Tamper-response: any chassis breach zeroizes all plaintext CSPs
Secure firmware updates: signed by vendor + our key, dual-attested
Audit export: every op signed into the KMS audit log
Disaster recovery: M-of-N key backup across jurisdictions

HSM + MPC

The HSM holds one MPC share. This is strictly better than either alone.

HSM alone

Strong per-key security; single point of trust. Vendor compromise or insider access can be catastrophic.

MPC alone

No single party holds the key; depends on operational security of every share-holder's environment.

HSM + MPC (Lux default)

One share lives inside an HSM under quorum access, others across independent regions. Attacker needs HSM bypass and enough cohort shares.

Hardware-rooted from day one.

Deploy on our HSM fleet or bring your own module (HYOK).