2017
DOI: 10.1007/s41635-017-0006-1
|View full text |Cite
|
Sign up to set email alerts
|

Fault Tolerant Infective Countermeasure for AES

Abstract: Infective countermeasures have been a promising class of fault attack countermeasures. However, they have been subjected to several attacks owing to lack of formal proofs of security and improper implementations. In this paper, we first provide a formal information theoretic proof of security for one of the most recently proposed state of the art infective countermeasures against DFA, under the assumption that the adversary does not change the flow sequence or skip any instruction. Subsequently, we identify we… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
13
0

Year Published

2018
2018
2022
2022

Publication Types

Select...
5
3
1

Relationship

0
9

Authors

Journals

citations
Cited by 37 publications
(13 citation statements)
references
References 21 publications
0
13
0
Order By: Relevance
“…Software countermeasures against fault attacks can be generally divided into two main groups: instruction-level and algorithmlevel techniques [12]. Instruction-based countermeasures include instruction duplication or triplication, and fault-tolerant instruction sequences, where an instruction is replaced by functionally equivalent sequence of more secure instructions [13]. This technique was recently extended to a new approach, called intra-instruction redundancy [14].…”
Section: Countermeasuresmentioning
confidence: 99%
“…Software countermeasures against fault attacks can be generally divided into two main groups: instruction-level and algorithmlevel techniques [12]. Instruction-based countermeasures include instruction duplication or triplication, and fault-tolerant instruction sequences, where an instruction is replaced by functionally equivalent sequence of more secure instructions [13]. This technique was recently extended to a new approach, called intra-instruction redundancy [14].…”
Section: Countermeasuresmentioning
confidence: 99%
“…As an example for infection-based countermeasures, we consider the infective countermeasure presented by Tupsamudre et al at CHES 2014 [TBM14] as an extension of an infective countermeasure presented by Gierlichs et al [GST12]. Patranabis et al [PCM15] give a formal proof for this countermeasure against differential fault analysis using a single fault injection under the assumption that the sequence of executed instructions is neither skipped, nor altered. The only attacks on this countermeasure so far are attacks that either skip or alter instructions [BG16].…”
Section: Infective Countermeasurementioning
confidence: 99%
“…The infection countermeasure by Patranabis et al [PCM15] can be seen as an extended version of the one described in subsubsection 2.1.2. Hence, we limit our description solely to the actual differences between both designs.…”
Section: Infection By Patranabis Et Almentioning
confidence: 99%
“…Therefore, [PYGS16,LCFS17]. Another approach is a technique called infective countermeasure that tries to distribute the fault evenly to the whole cipher state so that the attacker does not get any usable information about the secret key [PCM15]. Each of these countermeasures has some assumptions, e.g.…”
Section: Countermeasuresmentioning
confidence: 99%