Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is Homomorphic Encryption?

Homomorphic encryption allows computation on ciphertext. The result, once decrypted, matches what the same computation would have produced on the plaintext, which never has to be exposed.

Illustration for the cybersecurity term Homomorphic Encryption
Home / Blog / Cybersecurity Terms / What Is Homomorphic Encryption?
17 November 2026

What Is Homomorphic Encryption?

What Is Homomorphic Encryption?

Conventional encryption forces a choice: either data stays protected, or it gets used. Anything that needs to search, total, compare, or model must first decrypt, which is why database servers, analytics platforms, and machine learning pipelines all end up holding plaintext. Homomorphic encryption breaks the trade-off. Operations performed on ciphertext produce a ciphertext that decrypts to the correct answer, and the party doing the computing never sees the inputs or the output.

Craig Gentry showed in 2009 that a fully homomorphic scheme was possible at all, using lattice-based constructions and a technique called bootstrapping to control the noise that accumulates with every operation. His first implementation took around thirty minutes per elementary operation. The field has improved by many orders of magnitude since, which is why it has started appearing in production.

Three Degrees of Homomorphism

The schemes you will meet in libraries are BFV and BGV for exact integer arithmetic, CKKS for approximate arithmetic on real numbers — the usual choice for machine learning, because it tolerates small errors — and TFHE for fast bootstrapping over boolean circuits. Microsoft SEAL, OpenFHE, HElib, and Zama’s Concrete are the practical implementations.

What It Is Actually Used For

The technology is past the proof-of-concept stage in narrow, high-value cases:

The Costs You Must Plan For

DimensionTypical impact
ComputationHundreds to many thousands of times slower than plaintext
Ciphertext sizeExpansion of one to three orders of magnitude
ExpressivenessBranching on secret data is not possible; algorithms must be rewritten as circuits
Parameter choiceSecurity depends on noise budget and lattice parameters chosen per workload
Specialist skillScarce; parameter errors silently weaken security or corrupt results

Comparisons, sorting, and conditional logic are the awkward cases, because the computing party cannot branch on a value it cannot read. Many designs that look natural on paper become impractical once written as a fixed-depth circuit.

How It Compares with the Alternatives

Homomorphic encryption is one of several privacy-enhancing technologies, and rarely the cheapest. Secure multi-party computation splits a computation between parties so that none sees the whole input, and is often faster where the parties can interact. Trusted execution environments such as Intel SGX or AWS Nitro Enclaves keep data encrypted in memory and decrypt only inside the enclave, which is far faster but relies on hardware and has a history of side-channel research against it. Differential privacy addresses a different problem entirely: what the published results reveal, rather than who can read the inputs.

Importantly, homomorphic encryption does not solve access control. It protects data from the party performing the computation; whoever holds the decryption key still sees the result, and a flawed query can reveal more than intended. Under UK GDPR, encrypted personal data processed this way remains personal data to the controller, although the arrangement can materially reduce what a processor is exposed to — a point worth stating explicitly in a data protection impact assessment rather than assuming.

For most organisations the realistic posture today is to watch the field, identify the one or two use cases where sharing plaintext is genuinely blocking something valuable, and pilot there. Where privacy-preserving architecture is on your roadmap, our infrastructure and architecture review services can assess whether it earns its complexity.

FAQ – Frequently Asked Questions

Is Homomorphic Encryption Ready for Production?

For narrow, well-defined operations such as private lookups and aggregation, yes, and Apple and Microsoft have shipped features that rely on it. For general-purpose database or application workloads it remains too slow and too restrictive. Treat it as a specialist tool for specific problems rather than a replacement for conventional encryption.

How Is It Different from Confidential Computing?

Confidential computing decrypts data inside a hardware enclave, so performance is close to normal but you must trust the chip vendor and the enclave’s isolation. Homomorphic encryption never decrypts at all, so the trust assumption is purely mathematical, at a very large performance cost. The two are often combined rather than treated as rivals.

Is It Quantum Resistant?

The main schemes are built on lattice problems, the same family underlying ML-KEM, and are currently believed to resist quantum attack. That is a useful property, but it is incidental: you would not choose homomorphic encryption for post-quantum protection when ML-KEM does that job at a tiny fraction of the cost.

Does It Let a Cloud Provider Process Data Without Seeing It?

That is precisely the promise, and it works for computations expressible as fixed-depth arithmetic circuits. The constraints are practical: the workload must be rewritten, the performance penalty must be acceptable, and your organisation still holds the keys and the resulting plaintext. It is an excellent fit for a narrow query, and a poor fit for a general application.

Related Terms

You May Be Interested In These

What Is Terrascan?

Cybersecurity Terms

17 November 2026

What Is Terrascan?

Read More
What Is Cosign?

Cybersecurity Terms

17 November 2026

What Is Cosign?

Read More
What Are GPS Spoofing and Jamming?

Cybersecurity Terms

17 November 2026

What Are GPS Spoofing and Jamming?

Read More