{"id":3988,"date":"2023-01-07T18:56:44","date_gmt":"2023-01-07T18:56:44","guid":{"rendered":"http:\/\/cad4security.org\/?page_id=3988"},"modified":"2023-07-10T14:14:46","modified_gmt":"2023-07-10T14:14:46","slug":"ch5_hw_trojan_insert","status":"publish","type":"page","link":"http:\/\/cad4security.org\/index.php\/trainings\/hsl\/ch5_hw_trojan_insert\/","title":{"rendered":"Chapter 5: Hardware Trojan Insertion"},"content":{"rendered":"\n<h2 class=\"is-style-subheading wp-block-heading\"><strong>Chapter 5<\/strong><\/h2>\n\n\n\n<h3 class=\"is-style-subheading wp-block-heading\" style=\"font-style:normal;font-weight:100\">Hardware Trojan Insertion<\/h3>\n\n\n\n<p>A Hardware Trojan is a malicious addition or modification of an integrated circuit (IC) which could be inserted at arbitrary stages in the design and fabrication cycle to compromise the security of entire system. In this chapter, readers will gain hands on experience in the hardware Trojan insertion. Readers will learn how a typical hardware Trojan-inserted AES (advanced encryption standard) cryptographic implementation is implemented at RTL (register-transfer level) and triggered through bitstream tampering on an FPGA platform. Also, we demonstrate how to detect the malicious functionality with security property verification methods and present approaches to insert and detect malicious logics on an FPGA device, respectively.<\/p>\n\n\n\n<div class=\"wp-block-buttons is-layout-flex wp-block-buttons-is-layout-flex\">\n<div class=\"wp-block-button\"><a class=\"wp-block-button__link button\" href=\"http:\/\/cad4security.org\/wp-content\/uploads\/Chapter05-HW_Trojan_Trojan-Insertion.zip\">Download chapter files<\/a><\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>Chapter 5 Hardware Trojan Insertion A Hardware Trojan is a malicious addition or modification of an integrated circuit (IC) which could be inserted at arbitrary stages in the design and fabrication cycle to compromise the security of entire system. In this chapter, readers will gain hands on experience in the hardware Trojan insertion. Readers will &hellip;<\/p>\n","protected":false},"author":6,"featured_media":2565,"parent":3964,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_acf_changed":false,"_genesis_hide_title":false,"_genesis_hide_breadcrumbs":false,"_genesis_hide_singular_image":false,"_genesis_hide_footer_widgets":false,"_genesis_custom_body_class":"","_genesis_custom_post_class":"","_genesis_layout":"","footnotes":""},"acf":[],"_links":{"self":[{"href":"http:\/\/cad4security.org\/index.php\/wp-json\/wp\/v2\/pages\/3988"}],"collection":[{"href":"http:\/\/cad4security.org\/index.php\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"http:\/\/cad4security.org\/index.php\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"http:\/\/cad4security.org\/index.php\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"http:\/\/cad4security.org\/index.php\/wp-json\/wp\/v2\/comments?post=3988"}],"version-history":[{"count":5,"href":"http:\/\/cad4security.org\/index.php\/wp-json\/wp\/v2\/pages\/3988\/revisions"}],"predecessor-version":[{"id":4617,"href":"http:\/\/cad4security.org\/index.php\/wp-json\/wp\/v2\/pages\/3988\/revisions\/4617"}],"up":[{"embeddable":true,"href":"http:\/\/cad4security.org\/index.php\/wp-json\/wp\/v2\/pages\/3964"}],"wp:featuredmedia":[{"embeddable":true,"href":"http:\/\/cad4security.org\/index.php\/wp-json\/wp\/v2\/media\/2565"}],"wp:attachment":[{"href":"http:\/\/cad4security.org\/index.php\/wp-json\/wp\/v2\/media?parent=3988"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}