Security guidelines for implementing homomorphic encryption¶
Authors: J.-P. Bossuat; R. Cammarota; I. Chillotti; B. R. Curtis; W. Dai; H. Gong; E. Hales; D. Kim; B. Kumara; C. Lee; X. Lu; C. Maple; A. Pedrouzo-Ulloa; R. Player; Y. Polyakov; L. A. R. Lopez; Y. Song; D. Yhee
Year: 2024
type: other collection: sok-references status: auto
Links: ePrint 2024/463
Summary¶
Auto-extracted summary (unreviewed)
A multi-institution guidelines document, written in the context of the ISO/IEC FHE standardization effort, that provides example LWE parameter sets targeting specific security levels and complete FHE parameter sets (covering security, correctness and performance) for BFV, BGV, CKKS and DM/CGGI. It also surveys the parameter-selection support in open-source FHE libraries (OpenFHE, SEAL, EVA, Concrete) and releases the Lattice-Estimator-based scripts used to estimate the concrete security of the proposed parameters.
Abstract¶
Fully Homomorphic Encryption (FHE) is a cryptographic primitive that allows performing arbitrary operations on encrypted data. Since the conception of the idea in [RAD78], it has been considered a holy grail of cryptography. After the first construction in 2009 [Gen09], it has evolved to become a practical primitive with strong security guarantees. Most modern constructions are based on well-known lattice problems such as Learning With Errors (LWE). Besides its academic appeal, in recent years FHE has also attracted significant attention from industry, thanks to its applicability to a considerable number of real-world use-cases. An upcoming standardization effort by ISO/IEC aims to support the wider adoption of these techniques. However, one of the main challenges that standards bodies, developers, and end users usually encounter is establishing parameters. This is particularly hard in the case of FHE because the parameters are not only related to the security level of the system, but also to the type of operations that the system is able to Corresponding authors handle. In this paper we provide examples of parameter sets for LWE targeting particular security levels, that can be used in the context of FHE constructions. We also give examples of complete FHE parameter sets, including the parameters relevant for correctness and performance, alongside those relevant for security. As an additional contribution, we survey the parameter selection support offered in open-source FHE libraries.
Source: pdf
Extracted details¶
| Field | Value | Source | Confidence |
|---|---|---|---|
| contribution | Example LWE parameter sets targeting particular security levels for FHE constructions | llm | 0.80 |
| contribution | Complete FHE parameter sets including correctness and performance parameters for BFV, BGV, CKKS, DM and CGGI | llm | 0.80 |
| contribution | Survey of parameter selection support in open-source FHE libraries | llm | 0.80 |
| contribution | Open-source scripts to estimate and re-run the concrete security of the parameter sets with the Lattice Estimator | llm | 0.80 |
| schemes | BFV | llm | 0.80 |
| schemes | BGV | llm | 0.80 |
| schemes | CKKS | llm | 0.80 |
| schemes | FHEW | llm | 0.80 |
| schemes | TFHE | llm | 0.80 |
| schemes | LWE | llm | 0.80 |
| libraries | OpenFHE | llm | 0.80 |
| libraries | SEAL | llm | 0.80 |
| libraries | EVA | llm | 0.80 |
| libraries | Concrete | llm | 0.80 |
| libraries | Lattice Estimator | llm | 0.80 |
| tasks | FHE parameter selection | llm | 0.80 |
| tasks | FHE standardization | llm | 0.80 |
| interaction | non-interactive FHE | llm | 0.80 |
| code url | https://github.com/gong-cr/FHE-Security-Guidelines/.Our (URL found in the full text) | regex | 0.50 |
| code url | https://github.com/malb/lattice-estimator.2 (URL found in the full text) | regex | 0.50 |
| code url | https://github.com/gong-cr/FHE-Security-Guidelines/ (URL found in the full text) | regex | 0.50 |
| code url | https://github.com/gong-cr/FHE-Security-Guidelines/ | llm | 0.80 |
| limitations | Parameter sets must be updated in response to advances in lattice cryptanalysis | llm | 0.80 |
| limitations | Optimal parameter choice is application- and library-dependent; correctness and efficiency must be considered alongside security | llm | 0.80 |
| limitations | Only a subset of FHE schemes, noise distributions and attack scenarios are covered | llm | 0.80 |
| llm relevance | low | llm | 0.80 |
SoK reference [56]¶
J.-P. Bossuat, R. Cammarota, I. Chillotti, B. R. Curtis, W. Dai, H. Gong, E. Hales, D. Kim, B. Kumara, C. Lee, X. Lu, C. Maple, A. Pedrouzo-Ulloa, R. Player, Y. Polyakov, L. A. R. Lopez, Y. Song, and D. Yhee, “Security guidelines for implementing homomorphic encryption,” IACR Communications in Cryptology (CiC), vol. 1, no. 4, p. 26, 2024.
Listed on the reference page of the site.
Keyword mentions¶
Counts of vocabulary terms in the full text (first page of occurrence in brackets).
- scheme: TFHE 47 [p.1], CKKS 37 [p.1], BFV 37 [p.1], BGV 35 [p.1], NTRU 20 [p.3], FHEW 4 [p.20], RSA 4 [p.27], Leveled / somewhat HE 3 [p.14], MPC 2 [p.29]
- library: OpenFHE 25 [p.14], Microsoft SEAL 15 [p.14], TFHE-rs 13 [p.15], Concrete (Zama) 12 [p.1], Lattigo 7 [p.17], Zama 6 [p.1], EVA / CHET 5 [p.20], HElib 2 [p.19], HEaaN (library) 1 [p.19], Phantom 1 [p.19], Liberate.FHE 1 [p.19]
- model: k-NN 1 [p.23]
- technique: Bootstrapping 63 [p.6], Key switching 12 [p.11], Compiler 9 [p.4], RNS 8 [p.14], Lookup table 3 [p.3], Functional bootstrapping 2 [p.28], Polynomial approximation 2 [p.32], SIMD packing 2 [p.18], Rotations 2 [p.2], Noise flooding 2 [p.8]
- assumption: LWE 106 [p.1], Lattice-based 79 [p.1], RLWE 26 [p.2], Post-quantum 2 [p.22], IND-CPA 2 [p.7], IND-CPA-D 2 [p.8]
- task: Language modeling / generation 5 [p.9]
- topic: Homomorphic encryption 131 [p.1], Open source 18 [p.2]
Files¶
| Path (under papers/) | Collection | Pages | Size | SHA-256 | Note |
|---|---|---|---|---|---|
references/sok-references/056_security-guidelines-for-implementing-homomorphic-encryption.pdf |
sok-references | 33 | 553.6 KB | 44419917b3a1 |
Database key: security-guidelines-for-implementing-homomorphic-encryption · created 2026-11-05 · updated 2026-11-05 · edit with python3 tools/paperdb.py set security-guidelines-for-implementing-homomorphic-encryption COLUMN VALUE