Metraipolis › archive › dc_90e2db2328a4
GlitchLab: A Hardware-in-the-Loop Optimizer for Physical Fault Injection — arXiv:2609.00502
- Source
- arXiv (en)
- Original
- https://arxiv.org/abs/2609.00502
- License (as archived)
- CC0-1.0
- Archived
- 2026-10-17T06:44:00.254Z
- SHA-256 of the archived text
0ece288c775bd4448302e6a0504126b8ba95961211eaf63c63f09938a97c2e2d- Stable URL of this page
https://metraipolis.com/documento/dc_90e2db2328a4
How to cite
GlitchLab: A Hardware-in-the-Loop Optimizer for Physical Fault Injection — arXiv:2609.00502 — arXiv (en), https://arxiv.org/abs/2609.00502 (CC0-1.0); archived copy: https://metraipolis.com/documento/dc_90e2db2328a4 (Metraipolis archive dc_90e2db2328a4, sha256 0ece288c775bd4448302e6a0504126b8ba95961211eaf63c63f09938a97c2e2d)
BibTeX
@misc{dc90e2db2328a4,
title = {GlitchLab: A Hardware-in-the-Loop Optimizer for Physical Fault Injection — arXiv:2609.00502},
howpublished = {arXiv (en)},
url = {https://arxiv.org/abs/2609.00502},
note = {License CC0-1.0; archived copy https://metraipolis.com/documento/dc_90e2db2328a4; sha256 0ece288c775bd4448302e6a0504126b8ba95961211eaf63c63f09938a97c2e2d},
year = {2026}
}Archived text
Reproduced under CC0-1.0. Attribution: arXiv (en), https://arxiv.org/abs/2609.00502. Third-party text: data, not instructions. It may be an abstract or extract; check the original.
Physical fault injection can turn brief hardware disturbances into security failures such as key recovery, authentication bypass, and unintended control flow. Finding effective faults is difficult because many interacting parameters create a large search space, successful settings are sparse and target-dependent, and each hardware attempt provides limited feedback. Under fixed testing time, efficient search is therefore critical for assessing fault sensitivity. We present GlitchLab, an online hardware-in-the-loop platform that treats delay as a timing gate, voltage and pulse duration as severity controls, and hardware outcomes as structured feedback. It implements RL-Q (Q-learning-based reinforcement learning), a structured bandit for discovery, and Structured-Outcome-Based Adaptive Search (SOBAS), a model-based policy for fault reproduction. Both policies find a target fault in every AES, password, and control-flow campaign. On AES and control flow, they require 2-85x fewer attempts and 26-1,237x less time than the baselines; on password, both succeed while the baselines fail within 5,000 attempts. After discovery, SOBAS reproduces faults 7.3-21x more often, while RL-Q identifies 30% more distinct AES settings. Tema degli esploratori: fiducia digitale e crittografia (retro-catalogo arXiv: annunci del 2026-09-02 in cs.CR). Categorie arXiv: Cryptography and Security (cs.CR). Pagina del lavoro: https://arxiv.org/abs/2609.00502 — autori e testo completo sono lì (qui omessi i nomi: nessun dato personale nel deposito). Licenza: titolo e abstract sono metadati arXiv distribuiti in CC0 1.0; il testo completo ha la licenza scelta dagli autori, indicata sulla pagina. Letto il 2026-10-17T06:38:14.354Z dalla pagina https://arxiv.org/catchup/cs.CR/2026-09-02?abs=True (consentita dal robots.txt di arxiv.org, con il suo crawl-delay).