Trojan Taxonomy in Quantum Computing

Research output: Chapter in Book/Report/Conference proceedingConference contribution

Abstract

Quantum computing introduces unfamiliar security vulnerabilities demanding customized threat models. Hardware and software Trojans pose serious concerns needing rethinking from classical paradigms. This paper develops the first structured taxonomy of Trojans tailored to quantum information systems. We enumerate potential attack vectors across the quantum stack from hardware to software layers. A categorization of quantum Trojan types and payloads is outlined ranging from reliability degradation, functionality corruption, backdoors, and denial-of-service. Adversarial motivations behind quantum Trojans are analyzed. By consolidating diverse threats into a unified perspective, this quantum Trojan taxonomy provides insights guiding threat modeling, risk analysis, detection mechanisms, and security best practices customized for this novel computing paradigm.

Original languageEnglish (US)
Title of host publication2024 IEEE Computer Society Annual Symposium on VLSI
Subtitle of host publicationEmerging VLSI Technologies and Architectures, ISVLSI 2024
EditorsHimanshu Thapliyal, Jurgen Becker
PublisherIEEE Computer Society
Pages644-649
Number of pages6
ISBN (Electronic)9798350354119
DOIs
StatePublished - 2024
Event2024 IEEE Computer Society Annual Symposium on VLSI, ISVLSI 2024 - Knoxville, United States
Duration: Jul 1 2024Jul 3 2024

Publication series

NameProceedings of IEEE Computer Society Annual Symposium on VLSI, ISVLSI
ISSN (Print)2159-3469
ISSN (Electronic)2159-3477

Conference

Conference2024 IEEE Computer Society Annual Symposium on VLSI, ISVLSI 2024
Country/TerritoryUnited States
CityKnoxville
Period7/1/247/3/24

All Science Journal Classification (ASJC) codes

  • Hardware and Architecture
  • Control and Systems Engineering
  • Electrical and Electronic Engineering

Fingerprint

Dive into the research topics of 'Trojan Taxonomy in Quantum Computing'. Together they form a unique fingerprint.

Cite this