An Efficient Fault-Tolerance Scheme for CKKS Computation on CPUs
This paper presents an efficient fault-tolerance scheme for CPU-based fully homomorphic encryption (FHE) that reduces protection overhead and achieves 100 percent detection rate under random single-bit transient faults.
The paper proposes an efficient fault-tolerance scheme for CPU-based FHE that reduces protection overhead while maintaining a high detection rate.
Before reading this…
Applications
- →Encrypted data processing, Secure computation
To understand this paper, make sure you know these concepts first:
- Understanding of encryption, Fully homomorphic encryption, Transient faultsfind papers →
Abstract
More Like ThisFully homomorphic encryption (FHE) enables computation on encrypted data, but its long ciphertext dataflow and high-dimensional modular arithmetic make it vulnerable to silent data corruption caused by transient hardware faults. Existing protection methods either target dedicated accelerators or impose substantial execution, modular-arithmetic, and memory-access overheads on CPUs. This work presents an efficient fault-tolerance scheme for CPU-based CKKS computation. It checks the input-output consistency of polynomial operators while reducing protection overhead at three levels. First, modulus-aware bucket checksum exploits wide CPU accumulators to reduce expensive modular reductions. Second, dataflow-fused in-operator checking embeds checksum accumulation into operator dataflows, avoiding separate scans of long ciphertext polynomials. Third, cross-operator check fusion eliminates redundant checksum computations between adjacent operators while preserving end-to-end checking invariants. We implement the scheme in OpenFHE and evaluate it on representative encrypted applications and ciphertext primitives under random single-bit transient faults. It achieves a 100 percent empirical detection rate across 150,000 non-crashing corrupted-result cases and maintains application accuracy close to the fault-free baseline over a wide range of fault rates. The scheme incurs only 6.0 percent to 8.4 percent runtime overhead, averaging 6.8 percent, and reduces average protection overhead by 4.9 times compared with direct checksum-based protection.