The Sorcerer's Apprentice Guide to Fault Attacks
By H. Bar-El, Hamid Choukri, David Naccache, Michael Tunstall, Claire Whelan. Proceedings of the IEEE, 2006
978 citations recorded by the source corpus.
Subfields: Artificial Intelligence, Electrical and Electronic Engineering, Hardware and Architecture
View Paper: https://www.semanticscholar.org/paper/9dd15f3ff339de35865c3230211abf797c8814e5
How researchers see this paper
The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.
In Artificial Intelligence
- Jo Van Bulck
- Frank Piessens
- Daniel Gruss
- Simha Sethumadhavan
- Salvatore J. Stolfo
- Adrian Tang
- Debdeep Mukhopadhyay
- Ramesh Karri
In Electrical and Electronic Engineering
- Ramesh Karri
- A. Calvez
- Frank Piessens
- Daniel Gruss
- Masoud Rostami
- Pierre Vanhauwaert
- Paolo Maistri
- Farinaz Koushanfar
In Hardware and Architecture
- Ramesh Karri
- A. Calvez
- Debdeep Mukhopadhyay
- Frank Piessens
- Salvatore J. Stolfo
- Daniel Gruss
- Masoud Rostami
- Pierre Vanhauwaert
Citations in the corpus
- Statistical fault injection: Quantified error and confidence (2009, background): “The computation of the required number of faults to inject in order to achieve a given confidence and error interval is also discussed.”
- Differential Fault Analysis of the Advanced Encryption Standard Using a Single Fault (2011, methodology): “Other methods for fault injection include variations in the power supply to create a glitch or spike [5], characteristics of the supplied clock [2], laser light [3] and eddy currents [27].”
- A Primer on Hardware Security: Models, Methods, and Metrics (2014, background): “Fault attacks can be launched using lasers, glitches in power supplies and clocks, and X-rays [80].”
- Plundervolt: Software-based Fault Injection Attacks against Intel SGX (2020, background): “a) Fault-Resistant Cryptographic Primitives: There is a large body of work regarding fault injection countermeasures for cryptographic algorithms, including (generic) temporal and/or spatial redundancy [26] and algorithm-specific approaches such as performing the inverse operation or more advanced t”
- CLKSCREW: Exposing the Perils of Security-Oblivious Energy Management (2017, methodology): “Several software-only defenses propose compiling code with checksum integrity verification and execution redundancy (executing sensitive code multiple times) [13, 15].”