13th Asian Test Symposium
DOI: 10.1109/ats.2004.48
|View full text |Cite
|
Sign up to set email alerts
|

High Level Fault Injection for Attack Simulation in Smart Cards

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
14
0

Publication Types

Select...
7
2

Relationship

1
8

Authors

Journals

citations
Cited by 32 publications
(14 citation statements)
references
References 4 publications
0
14
0
Order By: Relevance
“…In our work, an executable model is produced using SystemC with the TLM extensions [8]. SystemC has been used to produce a methodology to simulate security attacks on smart cards with fault injection [9] and it has also been used to create an environment for design verification of smart cards using security attack simulation [10]. In TLM, communication among computation components is modelled by channels and transaction requests go on by calling interface functions of these channel models [11].…”
Section: Related Workmentioning
confidence: 99%
“…In our work, an executable model is produced using SystemC with the TLM extensions [8]. SystemC has been used to produce a methodology to simulate security attacks on smart cards with fault injection [9] and it has also been used to create an environment for design verification of smart cards using security attack simulation [10]. In TLM, communication among computation components is modelled by channels and transaction requests go on by calling interface functions of these channel models [11].…”
Section: Related Workmentioning
confidence: 99%
“…In this process, an important issue is to identify objects susceptible to threats (e.g., access ports), sensitive information within the system and possible paths of accessing or modifying it [55]. We should also take into account the problem of security compromises as a consequence of other faults in the system (e.g., transient disturbances) and checking if they do not increase the probability of security threats, data leakage, open access paths to sensitive data, reveal passwords, create side channels for attacks, etc.…”
Section: Fault Injection Methods [52]mentioning
confidence: 99%
“…1: Seamless error effect simulation intrusive approach. The effort for rewiring the VP to introduce additional saboteur modules, like in [2], [3] should be avoided. Approaches based on compiler modifications [4] provide one solution.…”
Section: Introductionmentioning
confidence: 98%