2007
DOI: 10.1049/iet-ifs:20060163
|View full text |Cite
|
Sign up to set email alerts
|

Strengthening hardware AES implementations against fault attacks

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
57
0

Year Published

2010
2010
2020
2020

Publication Types

Select...
5
2
1

Relationship

0
8

Authors

Journals

citations
Cited by 64 publications
(57 citation statements)
references
References 12 publications
0
57
0
Order By: Relevance
“…The first step usually involves the usage of some form of spatiotemporal redundancy to detect the occurrence of the fault, while the second phase attempts to either suppress or adequately randomize the effect of the fault so as to render it ineffective in recovering the secret key. Some popular countermeasure techniques in the current literature include the use of redundancy in various forms-temporal [5], spatial [24], information [25], and hybrid to name a few. Infective countermeasures, on the other hand, avoid the usage of comparison (as opposed to detection based countermeasures) by diffusing the effect of the fault to render the ciphertext unexploitable.…”
Section: Countermeasures Against Fault Attacksmentioning
confidence: 99%
“…The first step usually involves the usage of some form of spatiotemporal redundancy to detect the occurrence of the fault, while the second phase attempts to either suppress or adequately randomize the effect of the fault so as to render it ineffective in recovering the secret key. Some popular countermeasure techniques in the current literature include the use of redundancy in various forms-temporal [5], spatial [24], information [25], and hybrid to name a few. Infective countermeasures, on the other hand, avoid the usage of comparison (as opposed to detection based countermeasures) by diffusing the effect of the fault to render the ciphertext unexploitable.…”
Section: Countermeasures Against Fault Attacksmentioning
confidence: 99%
“…This work showed that faults can be induced reliably in accordance with an AES fault model and, more importantly, without permanently damaging the unit under attack. In [42], a practical application of the concepts presented in [26] and [44] is presented which allowed fault injection analysis to retrieve a full AES-128 key by analyzing less than 50 ciphertexts.…”
Section: 43mentioning
confidence: 99%
“…These methods offer a high level of assurance but inevitably impact performance significantly. In [44] the authors propose adding redundancy to the implementation and using a simple comparison to detect faults. The premise is that practical fault injection will not be able to identically affect both redundant elements and that the differences will be detectable at the function's outputs through comparison.…”
Section: 44mentioning
confidence: 99%
“…But as the detection position is related to the data being processed [5], the comparison step itself is prone to fault attacks. The other ones based on infection [6,7]. The idea of infection countermeasures is to make faulty ciphertexts unexploitable by diffusing the effect of a fault.…”
Section: Introductionmentioning
confidence: 99%
“…To overcome the drawbacks in the above works, this paper presents a novel framework for infection mechanism called random infection mechanism to resist fault attacks based on the research of [4] and [6]. We use the encryption/decryption circuit to construct the fault diffusion pattern, so it could avoid under the possibility of double error attacks.…”
Section: Introductionmentioning
confidence: 99%