Confidential databases encrypt data to protect it in untrusted cloud environments. Every query decrypts, computes, re-encrypts. The cryptographic operations sit on the critical path — every database operation passes through them. Performance overhead is severe.
Huang, Wang, and Li remove the encryption from the critical path. Not from the system — from the path. They introduce crypto-free mappings: data-independent identifiers that the database manipulates without ever touching the plaintext. The identifiers have no cryptographic relationship to the data they represent. The actual secrets live in a trusted domain, linked to identifiers through a secure mapping that is consulted only when data enters or leaves the system.
The result: up to 78x performance improvement over traditional confidential database approaches on industry-standard benchmarks.
The structural insight is that encryption was solving two problems simultaneously — confidentiality (protecting data from the cloud) and identification (knowing which data to access) — when only the first required cryptography. The identifiers that the database uses to index, sort, and join data do not need to be encrypted as long as they reveal nothing about the data they reference. Separating the identification function from the confidentiality function and applying cryptography only where it is needed removes encryption from the operations that dominate runtime.
The design principle: apply security mechanisms at the boundary where trust changes, not throughout the computation. The interior of the database never needs to see plaintext or ciphertext — it operates on identifiers that are neither. Security lives at the edges; performance lives in the middle.