Current encryption (RSA, ECC) will be broken by quantum computers. UAML uses ML-KEM-768 — the post-quantum standard certified by NIST (FIPS 203) — to protect your data today and tomorrow.
What We Use
| Standard | Purpose | NIST Reference |
|---|---|---|
| ML-KEM-768 | Key encapsulation (encryption) | FIPS 203 |
| ML-DSA | Digital signatures | FIPS 204 |
| SLH-DSA | Stateless hash signatures | FIPS 205 |
Key Features
🔑 Key Escrow with Secret Sharing
Shamir's Secret Sharing splits your master key into N parts. Any K parts can reconstruct it. Lose one backup? No problem. No single point of failure.
✍️ Signed Exports
Every data export is digitally signed. Recipients can verify the data hasn't been tampered with. Chain of custody you can prove.
🏠 Local Key Management
Keys never leave your hardware. No cloud KMS, no third-party trust. Your keys, your control.
Why Post-Quantum Matters Now
- "Harvest now, decrypt later" — adversaries collect encrypted data today to break it with quantum computers tomorrow
- Compliance — NIST recommends migrating to PQC by 2030. UAML is already there
- Long-lived data — AI agent memories may be relevant for years or decades
- Regulated industries — legal, medical, financial data needs the strongest protection available
Usage
from uaml.crypto.pqc import PQCEngine
# Generate a post-quantum keypair
engine = PQCEngine()
keypair = engine.generate_keypair()
# Encrypt data
ciphertext = engine.encrypt(b"sensitive memory data", keypair.public)
# Decrypt
plaintext = engine.decrypt(ciphertext, keypair.private)
← Back to UAML