Design, Automation &Amp; Test in Europe Conference &Amp; Exhibition (DATE), 2013 2013
DOI: 10.7873/date.2013.092
|View full text |Cite
|
Sign up to set email alerts
|

Comprehensive Analysis of Software Countermeasures against Fault Attacks

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
7
0

Year Published

2014
2014
2024
2024

Publication Types

Select...
5
3

Relationship

0
8

Authors

Journals

citations
Cited by 14 publications
(7 citation statements)
references
References 0 publications
0
7
0
Order By: Relevance
“…Fault countermeasures can be implemented at different abstraction levels within a device. Classic redundancy-based countermeasures can be employed, which protect the program flow and guarantee data integrity [44]. These countermeasures can be employed at higher protocol levels or even at the logic level.…”
Section: Surveymentioning
confidence: 99%
“…Fault countermeasures can be implemented at different abstraction levels within a device. Classic redundancy-based countermeasures can be employed, which protect the program flow and guarantee data integrity [44]. These countermeasures can be employed at higher protocol levels or even at the logic level.…”
Section: Surveymentioning
confidence: 99%
“…For the sake of designing countermeasures, several research studies have been conducted based only on a single level of fault characterization, such as Instruction-Set Architecture (ISA) level in [14,15] or RTL [16]. However, because of the incomplete fault model, this could lead to either under-engineer or over-engineer the protections.…”
Section: Institute Of Engineering Univ Grenoble Alpesmentioning
confidence: 99%
“…For the second experiment of Program 1, one might think that duplicating CMP will work as a countermeasure for APSR corruption since instruction duplication could work as a software countermeasure as described in [7,28]. However, it did not as the injection affects two instructions in most cases, which might be related to the microarchitectural possibility to fetch two instructions at the same time.…”
Section: On the Difficulty Of Analyzing The Program Flow Faultsmentioning
confidence: 99%
“…Such a model provides a theoretical set of faults an attacker could produce. Since performing practical experiments on software countermeasures may require some advanced fault injection means and can be very time-consuming, fault models are also used to perform fault injection simulations (Theissing et al 2013) or formal proofs (Moro, Heydemann, et al 2014). Those simulations help to provide stronger guarantees about the efficiency of the tested countermeasures.…”
Section: Software Countermeasuresmentioning
confidence: 99%