MétaCan
Menu
Back to cohort
Record W2952663436 · doi:10.1109/dtis.2019.8735085

Hardware Trojan Prevention Through Limiting Access to the Active Region

2019· article· en· W2952663436 on OpenAlexaff
Tareq Muhammad Supon, Mahsasadat Seyedbarhagh, Rashid Rashidzadeh, Roberto Muscedere

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicPhysical Unclonable Functions (PUFs) and Hardware Security
Canadian institutionsUniversity of Windsor
Fundersnot available
KeywordsTrojanHardware TrojanLimitingComputer scienceEmbedded systemRouting (electronic design automation)Block (permutation group theory)Hardware security moduleChipComputer securityComputer hardwareComputer networkCryptographyEngineeringTelecommunications

Abstract

fetched live from OpenAlex

Hardware Trojan (HT) has become a serious threat to the semiconductor industry. Many solutions have been developed to detect Trojans and address hardware security concerns. However, due to the wide range of possible Trojans, specific solutions for certain Trojans have been presented and a comprehensive solution is yet to be developed. Trojan prevention methods have also been explored to ensure hardware security. This paper presents a new technique for HT prevention in which attackers are deprived of the resources to route their Trojans and connect them to the active region of the chip. In the proposed solution, the empty space of the die is filled with polysilicon to block unauthorized die connection by attackers. This will deprive attackers of the routing resources to layout their Trojan circuitry. A readout circuit is used to determine that the polysilicon layer is intact, and it has not been tampered with. Simulation results indicate that with proper design, even a reduction of around 14.85 $\mu m^{2}$ polysilicon can be detected. This technique can ensure 100% utilization of the empty spaces in the polysilicon layer.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

How this classification was reachedexpand

Full frame machine prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.001
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Bench or experimental · Consensus signal: Bench or experimental
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.002
Threshold uncertainty score0.005

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0000.001
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.001
Open science0.0010.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0020.001

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.043
GPT teacher head0.292
Teacher spread0.248 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designBench or experimental
Domainnot available
GenreEmpirical

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations4
Published2019
Admission routes1
Has abstractyes

Explore more

Same topicPhysical Unclonable Functions (PUFs) and Hardware SecurityFrench-language works237,207