2011IEEE 10th International Conference on Trust, Security and Privacy in Computing and Communications 2011
DOI: 10.1109/trustcom.2011.82
|View full text |Cite
|
Sign up to set email alerts
|

Design Comparison to Identify Malicious Hardware in External Intellectual Property

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
13
0

Year Published

2012
2012
2021
2021

Publication Types

Select...
3
3
2

Relationship

1
7

Authors

Journals

citations
Cited by 22 publications
(13 citation statements)
references
References 20 publications
0
13
0
Order By: Relevance
“…One way to alleviate this issue is the concept of using design diversity in order to identify differences between designs [26]. Two recent studies [27,28] provide frameworks for addressing the issue of software Trojans hidden in Systemon-Chips (SoCs), and developing hardware/software codesign techniques to use two untrusted IPs in order to create secure implementations for SoCs.…”
Section: B Further Work Addressing Third-party Ipmentioning
confidence: 99%
See 1 more Smart Citation
“…One way to alleviate this issue is the concept of using design diversity in order to identify differences between designs [26]. Two recent studies [27,28] provide frameworks for addressing the issue of software Trojans hidden in Systemon-Chips (SoCs), and developing hardware/software codesign techniques to use two untrusted IPs in order to create secure implementations for SoCs.…”
Section: B Further Work Addressing Third-party Ipmentioning
confidence: 99%
“…The primary concept behind Design Comparison is to logically compare two untrusted hardware designs with similar functionality, identifying wherever their outputs differ in order to verify a design pre-fabrication [26]. As Trojan triggers are designed to have astronomically low odds to prevent accidental triggering, the odds are even less that two Trojans would have the same Trigger and the same payload.…”
Section: Design Comparisonmentioning
confidence: 99%
“…But those techniques may not be complete or optimal. For instance, in [51], the authors make the primary outputs of the designs as functions of only primary inputs during equivalence checking. However, in most of the designs, it is impossible to make the outputs independent of the state variables.…”
Section: Motivationmentioning
confidence: 99%
“…This can be done by a fully trusted third party or by the buyer oneself. The other way is to use a second untrusted third-party IP assuming that even if both circuits have malicious inclusions, the chances of both Trojans being at the same place, and having same trigger conditions and same functional effect is very unlikely [51]. Our technique assumes that the reference circuit is an unoptimized (potentially much larger) circuit free from malicious insertions prepared in a trusted environment.…”
Section: Random Simulation and Equivalence Checkingmentioning
confidence: 99%
“…Figure 1 illustrates possible points of insertion in an example production cycle [3]. Depending on the method through which a Trojan is inserted, possible detection methods can vary [4][5][6].…”
Section: Introductionmentioning
confidence: 99%