METHOD FOR TRIGGERING AND DETECTING A MALICIOUS CIRCUIT IN AN INTEGRATED CIRCUIT DEVICE
First Claim
1. A method for triggering and detecting a malicious circuit on an integrated circuit device, the method comprising:
- providing a first run of test patterns to logic circuits on the integrated circuit device, the first run of test patterns comprising a plurality of test patterns, each test pattern of the first run of test patterns comprising a plurality of bits, a first portion of the plurality of bits being bits that do not influence a value of a resulting first test output vector, and a second portion of the plurality of bits being bits that will influence the value of the first test output vector;
outputting the first test output vector from the first run of test patterns;
comparing the value of the first test output vector to first expected values;
changing bit values of the first portion of the plurality of bits for each test pattern of the first run of test patterns to generate a second run of test patterns;
providing the second run of test patterns to the logic circuits on the integrated circuit device;
outputting a second test output vector resulting from the second run of test patterns; and
comparing a value of the second run of test patterns to second expected values.
1 Assignment
0 Petitions
Accused Products
Abstract
A method for triggering and detecting a malicious circuit on an integrated circuit device is provided. A first run of test patterns is provided to logic circuits on the integrated circuit device. Each test pattern of the first run of test patterns includes a plurality of bits, a first portion of the plurality of bits being bits that do not influence a value of a resulting first test output vector, and a second portion of the plurality of bits being bits that will influence the value of the first test output vector. The value of the first test output vector is compared to first expected values. Bit values of the first portion of the plurality of bits for each test pattern of the first run of test patterns are changed to generate a second run of test patterns. The second run of test patterns is provided to the logic circuits on the integrated circuit device. A value of the second run of test patterns is compared to second expected values.
-
Citations
16 Claims
-
1. A method for triggering and detecting a malicious circuit on an integrated circuit device, the method comprising:
-
providing a first run of test patterns to logic circuits on the integrated circuit device, the first run of test patterns comprising a plurality of test patterns, each test pattern of the first run of test patterns comprising a plurality of bits, a first portion of the plurality of bits being bits that do not influence a value of a resulting first test output vector, and a second portion of the plurality of bits being bits that will influence the value of the first test output vector; outputting the first test output vector from the first run of test patterns; comparing the value of the first test output vector to first expected values; changing bit values of the first portion of the plurality of bits for each test pattern of the first run of test patterns to generate a second run of test patterns; providing the second run of test patterns to the logic circuits on the integrated circuit device; outputting a second test output vector resulting from the second run of test patterns; and comparing a value of the second run of test patterns to second expected values. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8)
-
-
9. A method for triggering and detecting a malicious circuit on an integrated circuit device, the method comprising:
-
scanning in a first run of test patterns to logic circuits on the integrated circuit device using logic built-in self-test (LBIST), the first run of test patterns comprising a plurality of test patterns, each test pattern of the first run of test patterns comprising a plurality of bits, a first portion of the plurality of bits being bits that do not influence a value of a resulting first test output vector, and a second portion of the plurality of bits being bits that will influence the value of the first test output vector; scanning out the first test output vectors from the first run of test patterns; comparing the value of the first test output vectors to first expected values; changing bit values of the first portion of the plurality of bits for each test pattern of the first run of test patterns to generate a second run of test patterns; scanning in the second run of test patterns to the logic circuits on the integrated circuit device; scanning out the second test output vectors resulting from the second run of test patterns; and comparing a value of the second run of test patterns to second expected values. - View Dependent Claims (10, 11, 12)
-
-
13. A method for triggering and detecting a malicious circuit on an integrated circuit device, the method comprising:
-
scanning in a first run of test patterns to logic circuits on the integrated circuit device using logic built-in self-test (LBIST), the first run of test patterns comprising a plurality of test patterns, each test pattern of the first run of test patterns comprising a plurality of bits, a first portion of the plurality of bits being bits that do not influence a value of a resulting first test output vector, and a second portion of the plurality of bits being bits that will influence the value of the first test output vector; scanning out the first test output vectors from the first run of test patterns; comparing the value of the first test output vectors to first expected values; changing bit values of the first portion of the plurality of bits for each test pattern of the first run of test patterns to generate a second run of test patterns; scanning in the second run of test patterns to the logic circuits on the integrated circuit device; scanning out the second test output vectors resulting from the second run of test patterns; comparing a value of the second run of test patterns to second expected values; and detecting the malicious hardware in response to comparing the values of the first and second test output vectors. - View Dependent Claims (14, 15, 16)
-
Specification