{"id":16334,"date":"2015-08-25T00:00:08","date_gmt":"2015-08-25T00:00:08","guid":{"rendered":"https:\/\/www.rambus.com\/?p=16334"},"modified":"2019-03-15T09:13:12","modified_gmt":"2019-03-15T17:13:12","slug":"use-cases-debug-access-control","status":"publish","type":"post","link":"https:\/\/www.rambus.com\/use-cases-debug-access-control\/","title":{"rendered":"Use Cases: Debug Access Control"},"content":{"rendered":"

When chips are shipped into the field, it is required that test features, needed to test the chip during manufacturing, must be securely disabled (see Figure 1 below). If left enabled in the field, these test and debug ports could provide a back door into the device that could be used maliciously to read sensitive keys and other sensitive data from the device. These test features must be disabled when the part ships into the field, but must also be securely enabled later when defective parts are returned through the RMA (Return Merchandise Authorization) channel for failure analysis.<\/p>\n

To prevent misuse of debug modes (e.g. BIST, scan, JTAG), the CryptoManager Root of Trust can be connected to the debug mode enable, which defaults to an off (safe) setting. The Root of Trust can selectively enable debug features as needed, for example:<\/p>\n