Last reviewed 10 November 2026
What a KEM is
What does a key-encapsulation mechanism produce, and why is that not bulk encryption?
You have read Algorithms. The further distinction is that a KEM produces a shared secret and does not carry the page, the file, or the health record.
One party encapsulates with the other's public key and produces a ciphertext and a shared secret. The other decapsulates with the private key and recovers the same secret. A protocol such as TLS then derives symmetric keys from that secret, and those keys protect the bulk of the traffic.
The figure shows encapsulation and decapsulation between two parties.
The KEM does not carry the page, the file, or the health record.
Encapsulation produces a ciphertext and a shared secret, and decapsulation recovers that secret. The KEM does not carry the page, the file, or the health record.
This distinction continues from Algorithms.
Continue with What changes in a TLS connection.
Sources
- NIST, FIPS 203, Module-Lattice-Based Key-Encapsulation Mechanism, for ML-KEM. FIPS 203
- NIST IR 8547, Transition to Post-Quantum Cryptography Standards, October 2026, for that pattern of use. NIST IR 8547