The need for declarative properties in digital IC security

Mohamed El Massad, Frank Imeson, Siddharth Garg, Mahesh Tripunitara

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

Abstract

We emphasize the need to articulate precise, declarative properties in the context of securing Digital ICs. We do this by discussing two pieces of our work on securing Digital ICs. In one, we discuss a seemingly compelling approach to protecting Intellectual Property | IC camouaging. We demonstrate that an adversary can carry out a decamouaging attack, in practice, much more efficiently than previously thought. Underlying our attack is strong foundations: an identification of the computational-complexity of the problems an attacker faces, and how they can be addressed using off-the-shelf constraint solvers. We identify the lack of a precise characterization of 'security' in this context as an issue. In the other piece of work, we present an example of the articulation of such a security property for 3D IC technology, in the context of securing a supply-chain. The property is articulated declaratively, with explicit assumptions that underlie the threat model.

Original languageEnglish (US)
Title of host publicationGLSVLSI 2017 - Proceedings of the Great Lakes Symposium on VLSI 2017
PublisherAssociation for Computing Machinery
Pages333-338
Number of pages6
ISBN (Electronic)9781450349727
DOIs
StatePublished - May 10 2017
Event27th Great Lakes Symposium on VLSI, GLSVLSI 2017 - Banff, Canada
Duration: May 10 2017May 12 2017

Publication series

NameProceedings of the ACM Great Lakes Symposium on VLSI, GLSVLSI
VolumePart F127756

Other

Other27th Great Lakes Symposium on VLSI, GLSVLSI 2017
Country/TerritoryCanada
CityBanff
Period5/10/175/12/17

Keywords

  • Computational complexity
  • Declarative properties

ASJC Scopus subject areas

  • Engineering(all)

Fingerprint

Dive into the research topics of 'The need for declarative properties in digital IC security'. Together they form a unique fingerprint.

Cite this