|Publication number||US6587947 B1|
|Application number||US 09/283,062|
|Publication date||Jul 1, 2003|
|Filing date||Apr 1, 1999|
|Priority date||Apr 1, 1999|
|Publication number||09283062, 283062, US 6587947 B1, US 6587947B1, US-B1-6587947, US6587947 B1, US6587947B1|
|Inventors||Amy O'Donnell, George Thangadurai, Anand Rajan|
|Original Assignee||Intel Corporation|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (15), Referenced by (52), Classifications (12), Legal Events (6)|
|External Links: USPTO, USPTO Assignment, Espacenet|
This invention relates to the field of electronics. More particularly, the invention relates to an apparatus and method for integrity verification of code that is stored off-chip.
2. Related Art
Normally, one of the most critical elements for an electronic device is its processor. In general, a processor is an embedded controller that comprises an integrated circuit (IC) including processing logic and on-chip memory. The memory is considered to be “on-chip” if placed on a die forming the IC. For 32-bit Intel® microprocessor architectures (e.g., Intel® IA-32processors), all architecture functionality is implemented on-chip using a combination of hardware and microcode stored in the on-chip memory.
With the development of 64-bit Intel® microprocessor architectures (e.g., Intel® IA-64 processors), some non-performance critical architecture functionality is being considered for implementation in off-chip firmware code. The use of off-chip firmware code provides a few advantages.
One advantage is that the current die size constraints associated with IA-32 processors can be maintained or even reduced for subsequent generation technologies. For instance, additional run-time services can be added without increasing the size of the on-chip memory, and hence, the die size of the processor. Another advantage is that the overall performance of the processor can be enhanced. This is due to the fact that a lesser amount of architecture functionality is required to be placed in on-chip memory so that more die area is available for processing logic.
However, this off-chip firmware code offers disadvantages as well. For instance, when moving architectural functionality off-chip, the firmware code is more susceptible to corruption and other malicious attacks.
Hence, it would be desirable to develop an apparatus and method of operation that ensure that the firmware code is free from corruption or unauthorized replacement. Also, the apparatus and method would ensure that the firmware code originated from a particular source.
Briefly, one embodiment of the invention is an electronic system comprising a memory element to store Processor Abstraction Layer (PAL) code and a processor coupled to the memory element. The processor verifies the integrity of the PAL code prior to execution of the PAL code.
The features and advantages of the present invention will become apparent from the following detailed description of the present invention in which:
FIG. 1 is an illustrative embodiment of an electronic system operating in accordance with a verification scheme.
FIG. 2 is an illustrative embodiment featuring the contents of the memory element of FIG. 1.
FIG. 3 is a first illustrative embodiment of processing unit of the electronic system of FIG. 1.
FIG. 4 is a second illustrative embodiment of the processing unit of the electronic system of FIG. 1.
FIG. 5 is an illustrative diagram of a technique for verifying the PAL code contained in FIG. 2.
FIG. 6 is a more-detailed embodiment of the verification technique of FIG. 5.
The present invention relates to an electronic system and corresponding method for verifying the integrity of code that is stored off-chip. Herein, certain embodiments of the invention are set forth in order to provide a thorough understanding of the invention. These embodiments should not be construed as a restriction on the scope of the invention. Also, to avoid unnecessarily obscuring the present invention, certain well-known hardware and techniques are not set forth in detail.
In the following description, terminology is used to discuss certain features of the present invention. For example, an “electronic system” is defined as any hardware having a processor. Examples of an electronic system include, but are not limited or restricted to the following: a computer (e.g., laptop, desktop, hand-held, server, mainframe, etc.), imaging equipment (e.g., printer, facsimile machine, scanner, digital camera, etc.), a set-top box (e.g., television control box for cable or satellite transmissions), wireless communication equipment (e.g., cellular phone, pager, etc.), a consumer electronic appliance and the like. A “processor” includes logic capable of processing information such as a microprocessor, a microcontroller, a state machine and the like. A “bus” is generally defined as a medium over which information may be transferred such as, for example, one or more electrical wire(s), fiber optic(s), cable(s), plain old telephone system (POTS) line(s), wireless channel(s) (e.g., satellite, radio frequency “RF”, infrared, etc.) or even one or more logical links. “Information” is defined as data, address, control or any combination thereof.
With respect to cryptography related terminology, the term “secure” generally indicates a state where it is extremely difficult for an unauthorized individual to access information in a plain text format. For example, memory is “secure” if it is physically inaccessible when placed in the electronic system or its contents have been previously authenticated. A “key” is generally defined as an encoding and/or decoding parameter usually structured as a sequence of binary data.
A “digital signature” includes digital information signed with a private key of its signatory in accordance with a digital signature function. For clarity sake, one type of digital signature function described herein is a Digital Signature Algorithm (DSA) set forth in a 1998 publication entitled “Federal Information Processing Standards Publication 186-1” (Dec. 15, 1998). A digital signature is used to ensure that the digital information has not been illicitly modified after being digitally signed. This digital information may be provided in its entirety or in part after undergoing a one-way hash function. The “one-way hash function” includes a function, mathematical or otherwise, that converts information from a variable-length to a fixed-length (referred to as a “message digest”). The term “one-way” indicates that there does not readily exist an inverse function to recover any discernible portion of the original information from the fixed-length digest. Examples of a hash function include MD2 or MD5 provided by RSA Data Security of Redwood City, Calif., or Secure Hash Algorithm (SHA-1) as specified a 1995 publication Secure Hash Standard FIPS 180-1 entitled “Federal Information Processing Standards Publication” (Apr. 17, 1995).
In addition, a “digital certificate” includes digital information used to authenticate a sender of information. For example, a digital certificate may include information concerning a person or entity being certified that is encrypted with the private key of a certification authority. Examples of a “certification authority” include an original equipment manufacturer (OEM), a software vendor, a trade association, a governmental entity, a bank or any other trusted business or person.
Referring to FIG. 1, an illustrative embodiment of an electronic system 100 operating in accordance with a verification scheme described in FIG. 5. Electronic system 100 (e.g., a computer) includes a system substrate 110 that controls the overall functionality of electronic system 100. Normally having a printed circuit board form factor, system substrate 110 comprises a memory element 120 and a connector 130.
As shown, memory element 120 comprises non-volatile memory such as Read Only Memory (ROM), any type of erasable programmable ROM (EPROM), flash memory and the like, although various types of volatile memory could be used (e.g., battery-backed random access memory). Memory element 120 is attached to system substrate 110 and is coupled to a bus 140. Bus 140 is routed to connector 130 in order to establish communications between memory element 120 and a processing unit 150 coupled to connector 130. Although connector 130 is shown as a standard female edge connector, any other style of connector may be used (e.g., a socket, lead frame, etc).
As shown in FIG. 2, contents of memory element 120 include Processor Abstraction Layer (PAL) code 200. PAL code 200 comprises firmware that controls functionality of processing unit 150 but is not highly dependent on processor execution speed. For example, PAL code 200 may include (i) a processing unit reset function, (ii) a check function for internal initialization events, (iii) system management interrupt code that allows the electronic system to interrupt processing unit 150 and the like. Before execution of PAL code 200, processing unit 150 would need to verify the integrity of PAL code 200 before its execution.
Referring now to FIG. 3, a first illustrative embodiment of processing unit 150 is shown. In this embodiment, processing unit 150 includes a processor substrate 300 formed from any type of material upon which integrated circuit components (not shown) can be attached through well-known techniques (e.g., solder connection, etc.). Processor substrate 300 includes a processor 310 that is covered by a package 320 in order to protect processor 310 from damage or harmful contaminants. Although a single processor 300 is shown, multiple processors may be placed on processor substrate 300. Processor substrate 300 further includes a connector 330, which protrudes from package 320 and is adapted to establish a mechanical and electrical connection with connector 130 of FIG. 1.
Referring now to FIG. 4, a second illustrative embodiment of processing unit 150 is shown. In this embodiment, processing unit 150 simply includes processor 310 being an integrated circuit (IC) 400 substantially covered by an IC package 410. IC 400 includes processing logic (e.g., processor core) 420 and a local memory 430 (e.g., on-chip memory). IC package 410 is configured to protect IC 400 from damage or harmful contaminants. The structure of IC package 410 is selected for adaptation with connector 130. Local memory 430 contains a first secret key “P(x)” 440, a second secret key (K) 450, a pre-computed message authentication code (MAC) value 460 and a well-known cyclic redundancy check (CRC) MAC function 470 described on page 22 of a 1996 publication entitled “Message Authentication” by Dr. Hugo Krawczyk. Both keys 440 and 450 as well as pre-computed MAC value 460 are securely stored in local memory 430. Security techniques employed may include the use of tamper resistant software to obfuscate P(x) 440, K 450 and MAC value 460, protection mechanisms to damage the memory in the event that physical tampering of memory 430 is detected or to reduce the likelihood of extracting contents from memory 430, and the like.
More specifically, “P(x)” is an irreducible polynomial of degree N, where “N” is equal to sixty-four (64) in this embodiment and K is a randomly chosen word having a bit size equivalent to the degree of P(x). Since P(x) is arranged as a 64 degree polynomial, K is chosen as a random 64-bit word. It is contemplated that if P(x) were an irreducible polynomial of degree 128, K would be a 128-bit word. Pre-computed MAC value 460 is a message digest resulting from PAL code 200 undergoing a one-way hash function. The loading: of the pre-computed MAC value 460 may be done at manufacture or subsequent thereto during an initialization procedure.
Referring now to FIG. 5, an illustrative diagram of a technique to verify PAL code 200 is shown. PAL code 200 is loaded into processor 310 and undergoes operations by CRC MAC function 470 to produce a computed MAC value 500. Internally within processor 310, computed MAC value 500 is compared with pre-computed MAC value 460 via comparison logic or firmware. If there is a match, namely a determination that both values are identical within a predetermined percentage or error (e.g., less than one percent), PAL code has not been modified since the loading of the pre-computed MAC value 460 via comparison logic or firmware. Hence, the integrity of PAL code 200 has been verified. Otherwise, if no match is detected, PAL code 200 has been modified. As a result, a system error is recorded and/or the electronic system is prevented from exiting the processor reset sequence. This may be accomplished by the processor remaining in the reset sequence (i.e., infinite loop), placing the processor into a SLEEP or reduced power mode, etc.
Referring to FIG. 6, a more-detailed embodiment of the verification scheme conducted by processor 310 of FIG. 3, including execution of the CRC MAC function, is shown. In general, the PAL code is generally divided by the first secret key P(x) to produce a residue value “Y(x)” as set forth in equation (1) shown below. The residue value Y(x) is exclusive-OR'ed (XOR'ed) with the second secret key (K) to calculate the MAC value as set forth in equation (2).
(1) Y(x)=M(x) (x64 mod P(x)); where
“M(x)” is PAL code represented as a polynomial
“Y(x)” is a 64-bit word operating as a remainder or residue.
(2) MAC value=Y(x) XOR K
As shown in FIG. 6, in this embodiment, a processor RESET is detected (block 600). In response, the off-chip code verification scheme begins by performing the CRC MAC function. First, control parameters are initialized (block 610). These control parameters include (i) a first counter (COUNT) which is set to the number of 8-byte quantities forming the PAL code, and (ii) a second counter (I) is set to zero. A pointer (ADDRESS) is set to a starting address of the PAL code while a storage parameter (VAL) is set to include an 8-byte quantity of data at ADDRESS.
Next, a bit counter (J) is set to zero (block 620) and BITSET is set to contain the most significant bit for data associated with VAL (block 630). VAL undergoes modulo 2 division through a single-bit left shift operation and the bit value of BITSET is checked (blocks 640 and 650). If BITSET is determined to be active (e.g., a logic “1”), VAL is updated by exclusively OR'ing itself with P(x) and the bit counter (J) is incremented (blocks 660 and 670). Otherwise, if BITSET is not active, the bit counter (J) is merely incremented (block 670). If J<N (N=64 in this embodiment), the division operation continues (block 680) for each bit of the selected 8-bytes of PAL code.
Upon completing the logical division of the first 8-bytes of PAL code, ADDRESS is incremented to point to the next block of PAL code, second counter (I) is incremented and if the CRC MAC function has not been performed on the entire PAL code, the CRC MAC function is performed on the next segment of PAL code (blocks 690 and 700). In the event that the entire PAL code has undergone the CRC MAC function, the remaining value of VAL, equivalent to the residue Y(x), is XOR'ed with the second secret key (K) to produce the computed MAC value (block 710). The computed MAC value is compared with the precomputed MAC value (block 720). If a match is determined, the PAL code is authenticated and the electronic system will proceed with its boot sequence (block 730). Otherwise, the PAL code has been corrupted and the electronic system will not boot (block 740).
While this invention has been described with reference to illustrative embodiments, this description is not intended to be construed in a limiting sense. Various modifications of the illustrative embodiments, as well as other embodiments of the invention, which are apparent to persons skilled in the art to which the invention pertains are deemed to lie within the spirit and scope of the invention.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US4206315||Jan 4, 1978||Jun 3, 1980||International Business Machines Corporation||Digital signature system and apparatus|
|US4215421||Jun 5, 1978||Jul 29, 1980||Compagnie Internationale Pour L'informatique Cii-Honeywell Bull (Societe Anonyme)||Data-processing system which protects the secrecy of confidential data|
|US4271482||May 12, 1978||Jun 2, 1981||Compagnie Internationale Pour L'informatique -Cii-Honeywell Bull||Data processing system which protects the secrecy of confidential data|
|US4462076 *||Jun 4, 1982||Jul 24, 1984||Smith Engineering||Video game cartridge recognition and security system|
|US4578531||Jun 9, 1982||Mar 25, 1986||At&T Bell Laboratories||Encryption system key distribution method and apparatus|
|US4951280||Dec 9, 1988||Aug 21, 1990||Advanced Micro Devices, Inc.||Method and apparatus for configuring data paths within a supernet station|
|US5005200||Mar 7, 1989||Apr 2, 1991||Fischer Addison M||Public key/signature cryptosystem with enhanced digital signature certification|
|US5097505||Oct 19, 1990||Mar 17, 1992||Securities Dynamics Technologies, Inc.||Method and apparatus for secure identification and verification|
|US5142579||Jan 29, 1991||Aug 25, 1992||Anderson Walter M||Public key cryptographic system and method|
|US5214702||May 13, 1992||May 25, 1993||Fischer Addison M||Public key/signature cryptosystem with enhanced digital signature certification|
|US5231666||Apr 20, 1992||Jul 27, 1993||International Business Machines Corporation||Cryptographic method for updating financial records|
|US5323465||Jun 4, 1993||Jun 21, 1994||Racal-Datacom Limited||Access control|
|US5699428||Jan 16, 1996||Dec 16, 1997||Symantec Corporation||System for automatic decryption of file data on a per-use basis and automatic re-encryption within context of multi-threaded operating system under which applications run in real-time|
|US5802277 *||Jul 26, 1996||Sep 1, 1998||International Business Machines Corporation||Virus protection in computer systems|
|US5844986 *||Sep 30, 1996||Dec 1, 1998||Intel Corporation||Secure BIOS|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US6883052 *||Feb 5, 2001||Apr 19, 2005||Tele Atlas N.V.||System for securing data on a data carrier|
|US6922846 *||Apr 9, 2001||Jul 26, 2005||Sony Corporation||Memory utilization for set top box|
|US7162743 *||Oct 4, 2001||Jan 9, 2007||Hewlett-Packard Development Company, L.P.||System and method of limiting access to protected hardware addresses and processor instructions|
|US7171693 *||May 14, 2001||Jan 30, 2007||Xtreamlok Pty Ltd||Information security method and system|
|US7401234||Mar 1, 2004||Jul 15, 2008||Freescale Semiconductor, Inc.||Autonomous memory checker for runtime security assurance and method therefore|
|US7500108||Mar 1, 2004||Mar 3, 2009||Microsoft Corporation||Metered execution of code|
|US7539304 *||Nov 18, 2002||May 26, 2009||Silicon Image, Inc.||Integrated circuit having self test capability using message digest and method for testing integrated circuit having message digest generation circuitry|
|US7555780||Jun 30, 2009||Symantec Corporation||Information security method and system|
|US7698718||Jul 31, 2006||Apr 13, 2010||Stmicroelectronics Limited||Method and system for restricting use of data in a circuit|
|US7996880||Jan 31, 2010||Aug 9, 2011||Silverbrook Research Pty Ltd||Secure updating of integrated circuits|
|US8038239||Dec 2, 2010||Oct 18, 2011||Silverbrook Research Pty Ltd||Controller for printhead having arbitrarily joined nozzle rows|
|US8214830 *||Jan 19, 2005||Jul 3, 2012||Intel Corporation||Performance in a virtualization architecture with a processor abstraction layer|
|US8239688||Jan 7, 2007||Aug 7, 2012||Apple Inc.||Securely recovering a computing device|
|US8250372 *||Sep 29, 2000||Aug 21, 2012||Aristocrat Technologies Australia Pty Ltd.||Gaming security system|
|US8254568||Jan 7, 2007||Aug 28, 2012||Apple Inc.||Secure booting a computing device|
|US8291480||Jan 7, 2007||Oct 16, 2012||Apple Inc.||Trusting an unverified code image in a computing device|
|US8438401 *||Sep 22, 2009||May 7, 2013||Raytheon BBN Technologies, Corp.||Device and method for securely storing data|
|US8560820||Mar 2, 2012||Oct 15, 2013||Apple Inc.||Single security model in booting a computing device|
|US8688967||Jul 25, 2012||Apr 1, 2014||Apple Inc.||Secure booting a computing device|
|US8806221||Aug 3, 2012||Aug 12, 2014||Apple Inc.||Securely recovering a computing device|
|US8826405||Sep 15, 2012||Sep 2, 2014||Apple Inc.||Trusting an unverified code image in a computing device|
|US8832454 *||Dec 30, 2008||Sep 9, 2014||Intel Corporation||Apparatus and method for runtime integrity verification|
|US9026802||Jul 2, 2012||May 5, 2015||Aristocrat Technologies Australia Pty Limted||Gaming security system|
|US9053323||Apr 13, 2007||Jun 9, 2015||Hewlett-Packard Development Company, L.P.||Trusted component update system and method|
|US20020016918 *||May 14, 2001||Feb 7, 2002||David Tucker||Information security method and system|
|US20020147994 *||Apr 9, 2001||Oct 10, 2002||Damien Kessler||Memory utilization for set top box|
|US20030162527 *||Feb 5, 2001||Aug 28, 2003||Claus Dorenbeck||System for securing data on a data carrier|
|US20040199786 *||Dec 2, 2003||Oct 7, 2004||Walmsley Simon Robert||Randomisation of the location of secret information on each of a series of integrated circuits|
|US20050193217 *||Mar 1, 2004||Sep 1, 2005||Case Lawrence L.||Autonomous memory checker for runtime security assurance and method therefore|
|US20050257054 *||Feb 16, 2005||Nov 17, 2005||David Tucker||Information security method and system|
|US20050289511 *||Feb 16, 2005||Dec 29, 2005||David Tucker||Information security method and system|
|US20060075260 *||Feb 16, 2005||Apr 6, 2006||David Tucker||Information security method and system|
|US20060112266 *||Feb 1, 2005||May 25, 2006||Research In Motion Limited||Method and device for authenticating software|
|US20060161917 *||Jan 19, 2005||Jul 20, 2006||Leung Hin L||Performance in a virtualization architecture with a processor abstraction layer|
|US20060265544 *||May 17, 2005||Nov 23, 2006||John Rudelic||Internally authenticated flash remediation|
|US20070180464 *||Jul 31, 2006||Aug 2, 2007||Stmicroelectronics Limited||Method and system for restricting use of data in a circuit|
|US20080086781 *||Apr 30, 2007||Apr 10, 2008||Stephane Rodgers||Method and system for glitch protection in a secure system|
|US20080165952 *||Jan 7, 2007||Jul 10, 2008||Michael Smith||Secure Booting A Computing Device|
|US20080165971 *||Jan 7, 2007||Jul 10, 2008||De Cesare Joshua||Trusting an Unverified Code Image in a Computing Device|
|US20080168275 *||Jan 7, 2007||Jul 10, 2008||Dallas Blake De Atley||Securely Recovering a Computing Device|
|US20100134541 *||Jan 31, 2010||Jun 3, 2010||Silverbrook Research Pty Ltd.||Secure updating of integrated circuits|
|US20100169967 *||Dec 30, 2008||Jul 1, 2010||Khosravi Hormuzd M||Apparatus and method for runtime integrity verification|
|US20110072279 *||Sep 22, 2009||Mar 24, 2011||Bbn Technologies Corp.||Device and method for securely storing data|
|US20140033305 *||Jul 30, 2012||Jan 30, 2014||Marvin D. Nelson||Code validation|
|CN100489805C||Jan 21, 2005||May 20, 2009||飞思卡尔半导体公司||Autonomous memory checker for runtime security assurance and method therefore|
|EP1659472A1 *||Nov 22, 2004||May 24, 2006||Research In Motion Limited||Method and Device for Authenticating Software|
|EP1768408A1 *||Jul 29, 2005||Mar 28, 2007||STMmicroelectronics Ltd.||Integrated circuit, method and system restricting use of decryption keys using encrypted digital signatures|
|EP2137609A1 *||Mar 7, 2008||Dec 30, 2009||Hewlett-Packard Development Company, L.P.||Trusted component update system and method|
|EP2137609A4 *||Mar 7, 2008||Jun 30, 2010||Hewlett Packard Development Co||Trusted component update system and method|
|WO2005091757A2 *||Jan 21, 2005||Oct 6, 2005||Freescale Semiconductor Inc||Autonomous memory checker for runtime security assurance and method therfore|
|WO2008085449A2 *||Dec 20, 2007||Jul 17, 2008||Apple Inc||Secure booting a computing device|
|WO2013062330A1 *||Oct 25, 2012||May 2, 2013||Taejin Info Tech Co., Ltd.||Secure error detection and synchronous data tagging for high-speed data transfer|
|U.S. Classification||713/187, 713/167, 726/30, 713/172, 713/189, 713/161, 713/170|
|Cooperative Classification||G06F21/57, G06F21/64|
|European Classification||G06F21/64, G06F21/57|
|Jul 31, 2001||AS||Assignment|
|Dec 29, 2006||FPAY||Fee payment|
Year of fee payment: 4
|Feb 7, 2011||REMI||Maintenance fee reminder mailed|
|Apr 14, 2011||FPAY||Fee payment|
Year of fee payment: 8
|Apr 14, 2011||SULP||Surcharge for late payment|
Year of fee payment: 7
|Dec 17, 2014||FPAY||Fee payment|
Year of fee payment: 12