Trusted Execution
Cryptographic keys live inside the secure-silicon TF-M Secure Processing Environment — never on the CPU bus. A dedicated hardware Key Management Unit holds session and per-contact keys. A hardware crypto accelerator runs AES-GCM and SHA in dedicated silicon. On Android, StrongBox enforcement is the default.
Secure World key custody
All cryptography executes inside a Trusted Firmware-M Secure Processing Environment — a hardware-isolated partition modeled on Arm TrustZone-M. Keypairs never cross the boundary into the application world. Even physical debug access cannot read the secure flash. The MEMS microphone path is bound at boot: descriptors become immutable, so no later-loaded software can re-route the audio.
- Keypairs stay inside the secure partition
- Boot-locked audio path — no software re-route
- Debug access cannot read secure flash
Hardware Key Management Unit
The Key Management Unit is a dedicated hardware key-store inside the secure silicon. Pre-shared keys, session keys, and per-contact keys live in protected slots. The crypto accelerator pulls them directly into its internal registers — the CPU never sees plaintext key material on the bus. Combined with two-pass volatile memory zeroization, RAM-dump attacks against an active session are ineffective.
- Plaintext keys never reach the CPU bus
- Per-contact slots auto-zeroize on revoke
- Memory holding key material wiped before release
hardware crypto accelerator: ML-KEM + AEAD in hardware
L'acceleratore hardware crypto accelerator esegue le primitive crittografiche pesanti in hardware. ML-KEM-1024 keygen <10ms, AES-256-GCM encryption >100 Mbps. Adatto a voce real-time senza compromettere latenza.
- ML-KEM-1024 keygen/encap/decap accelerati
- AES-256-GCM full speed
- Constant-time per resistenza side-channel