Routing aware and runtime detection for infected network-on-chip routers

Luka Daoud, Nader Rafla

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

18 Scopus citations

Abstract

Network-on-Chip (NoC) architecture is the communication heart of the processing cores in Multiprocessors System-on-Chip (MPSoC), where messages are routed from a source to a destination through intermediate nodes. Therefore, NoC has become a target to security attacks. By experiencing outsourcing design, NoC can be infected with a malicious Hardware Trojans (HTs) which potentially degrade the system performance or leave a backdoor for secret key leaking. In this paper, we propose a HT model that applies a denial of service attack by misrouting the packets, which causes deadlock and consequently degrading the NoC performance. We present a secure routing algorithm that provides a runtime HT detection and avoiding scheme. Results show that our proposed model has negligible overhead in area and power, 0.4% and 0.6%, respectively.

Original languageEnglish
Title of host publication2018 IEEE 61st International Midwest Symposium on Circuits and Systems, MWSCAS 2018
PublisherInstitute of Electrical and Electronics Engineers Inc.
Pages775-778
Number of pages4
ISBN (Electronic)9781538673928
DOIs
StatePublished - 2 Jul 2018
Event61st IEEE International Midwest Symposium on Circuits and Systems, MWSCAS 2018 - Windsor, Canada
Duration: 5 Aug 20188 Aug 2018

Publication series

NameMidwest Symposium on Circuits and Systems
Volume2018-August
ISSN (Print)1548-3746

Conference

Conference61st IEEE International Midwest Symposium on Circuits and Systems, MWSCAS 2018
Country/TerritoryCanada
CityWindsor
Period5/08/188/08/18

Keywords

  • Hardware Trojan
  • Malicious-tolerant Routing Algorithm
  • Network-on-Chip
  • NoC
  • Secure Routing Algorithm

Fingerprint

Dive into the research topics of 'Routing aware and runtime detection for infected network-on-chip routers'. Together they form a unique fingerprint.

Cite this