US 6,915,430 B2Grant

Reliably identifying information of device generating digital signatures

Issue Date:2005-07-05

•29 Claims

•23 Drawing Sheets

Abstract

Information of a device that generates digital signatures is reliably identified by (a) for each of a plurality of devices manufactured in an environment, (i) creating a public-private key pair within the environment, (ii) linking within the environment in a secure manner the public key with other information associated with the device, and (iii) before release of the device from the environment, storing the private key within the device for generating a digital signature for an electronic message, and (b) thereafter, when a said linked public key successfully authenticates a digitally signed message, identifying the other information associated with said linked public key as pertaining to the device to which belongs the private key utilized in digitally signing the message. Manufacturing the devices includes creating a public-private key pair within the secure environment, and storing the private key within the device against the possibility of divulgement thereof by the device.

Metadata

Assignee

First Data Corporation

Inventors

Anne M. Wheeler
Lynn Henry Wheeler

Application Information

Application Number:US 10/248,625

Filing Date:2003-02-01

Priority Date:2000-08-04

Art Unit:2132

Patent Drawings (23 sheets)

Description

Cross Reference to Related Applications

[0001] The present application is a continuation of and claims priority under 35 U.S.C. § 120 to U.S. patent application Ser. No. 09/923,213 filed Aug. 6, 2001, which is the nonprovisional of and claims priority under 35 U.S.C. 119(e) to the benefit of the filing date of Wheeler et al. U.S. provisional patent application Ser. No. 60/223,076 filed on Aug. 4, 2000, both of which are incorporated herein by reference. This application also incorporates herein by reference each of four international patent applications and two U.S. patent application to Anne and Lynn Wheeler filed in the U.S. Patent & Trademark Office on Aug. 6, 2001, and bearing serial No. PCT/US01/41587 (titled “Person-Centric Account-Based Digital Signature System”) and Ser. No. 09/923,179 (titled “Account-Based Digital Signature (ABDS) System”); serial No. PCT/US01/41562 (titled “Entity Authentication in Electronic Communications by Providing Verification Status of Device”) and Ser. No. 09/923,075 (titled “Modifying Message Data and Generating Random Number Digital Signature Within Computer Chip”); serial No. PCT/US01/24572 (titled “Linking Public Key of Device to Information During Manufacture”); and serial No. PCT/US01/24563 (titled “Trusted Authentication Digital Signature (TADS) System”).

Background of Invention

[0002] The present invention generally relates to electronic communications and, in particular, to devices that generate digital signatures associated with electronic communications.

[0003] As used herein, an electronic communication (“EC”) is considered to be any communication in electronic form. ECs have become an integral part of transacting business today, especially with the growth of the Internet and e-commerce. An EC can represent, for example, a request for access to information or a physical area, a financial transaction, such as an instruction to a bank to transfer funds, or a legal action, such as the delivery of an executed contract.

[0004] Over recent years, digital signatures also have become an important part of e-commerce. The origination of a digital signature generally comprises: (1) the calculation of a message digest-such as a hash value; and (2) the subsequent encryption of the message digest. The message digest is encrypted by an electronic device generally using a private key of a key pair used in public-private key cryptography (also known as asymmetric cryptography). The resulting ciphertext itself usually constitutes the digital signature, which typically is appended to the message to form the EC. The second part of originating the digital signature-encrypting with a private key—is referred to herein as “generating” the digital signature, and the combination of the two steps is referred to herein as “originating” the digital signature. Furthermore, while the generation of the digital signature is conventionally understood as the encryption of the message digest, it is contemplated herein that generating the digital signature also may include simply encrypting the message rather than the message digest. Digital signatures are important because any change whatsoever to the message in an EC is detectable from an analysis of the message and the digital signature. In this regard, the digital signature is used to “authenticate” a message contained within the EC (herein referred to as “Message Authentication”).

[0005] For example, a message digest may be calculated by applying a hashing algorithm to the message. The hashing algorithm may be applied either within the device or external to the device with the resulting hash value then being transmitted to the device for generation of the digital signature. In order to perform the Message Authentication in this example, the recipient of the EC must know or be able to obtain both the identity of the hashing algorithm applied to the message as well as the public key (“PuK”) corresponding to the private key used to encrypt the message digest. With this knowledge, the recipient applies the appropriate hashing algorithm to the message to calculate a hash value, and the recipient decrypts the digital signature using the public key. If the hash value calculated by the recipient equals the hash value of the decrypted digital signature, then the recipient determines that the content of the message contained in the EC was not altered in transmission, which necessarily would have changed the hash value.

[0006] In performing Message Authentication, the recipient also authenticates the sender of the EC, in so much as the recipient thereby confirms that the sender of the EC possessed the private key corresponding to the public key used successfully to authenticate the message. This is one type of entity authentication and is based on what the sender “has” (herein referred to as “Factor A Entity Authentication”). Factor A Entity Authentication is useful when the recipient of the EC has trusted information regarding the identity of the owner of the private key. Such trusted information may arise from a digital certificate issued by a trusted third-party that accompanies the EC and binds the identity of the private key owner with the public key. This trusted knowledge also may comprise actual knowledge of the identity of the private key owner, such as in the case where the recipient itself has issued the, private key or the device containing the private key to the owner.

[0007] As will be appreciated, trust in the digital signature system depends upon the legitimate possession and use of the private key, i.e., upon the sender of the EC actually being the private key owner. A fraudulent use of a private key to generate a digital signature of an EC currently cannot be detected through the above-described Message Authentication and Factor A Entity Authentication procedures. The digital signature system therefore is susceptible to fraud if a private key of a device is stolen, either by physical theft of the device containing the private key, or by discovery of the private key therein and subsequent copying and use in another device capable of generating digital signatures.

[0008] To guard against fraudulent use of a device through theft of the device itself, a personal identification number (PIN), password, or passphrase (collectively referred to herein as “Secret”) is typically prestored within the device and must be input into the device before it will operate to generate digital signatures. Alternatively, the Secret is shared with the recipient beforehand and, when the EC later is sent to the recipient, the Secret also is sent to the recipient in association with the message. In the first case, verification of the Secret authenticates the user of the device (herein “User Authentication”), and in the second case, verification of the Secret authenticates the sender of the EC (herein “Sender Authentication”). In either case, confirmation of the Secret represents entity authentication based on what the user or sender “knows” (herein “Factor B Entity Authentication”). Another security feature that guards against fraudulent use of the device through physical theft include the verification of a biometric characteristic—like a fingerprint—of the user of the device or sender of the EC. This type of authentication is based on what the user or sender “is” (herein “Factor C Entity Authentication”). As with the Secret, a biometric value is either maintained within the device for User Authentication, or is shared with the recipient beforehand for Sender Authentication by the recipient. To guard against discovery of a private key and subsequent copying and use in another device, devices are manufactured with electronic shielding, zeroization, auditing, tamper evidence and tamper response, and other security features that serve to safeguard the private key (and other protected data) contained therein.

[0009] Such security features of devices include hardware, software, and firmware, and are well known in the art of manufacturing secure computer chips and other devices having cryptographic modules. The requirements of such security features are specified, for example, in Federal Information Processing Standards Publication 140-1, Security Requirements for Cryptographic Modules, US DOC/NBS, Jan. 11, 1994 (herein “FIPS PUB 140-1”), which is incorporated herein by reference and which is available for download at http://csrc.nist.gov/publications/fips; and Federal Information Processing Standards Publication 140-2, Security Requirements for Cryptographic Modules, US DOC/NBS, May 25, 2001 (herein “FIPS PUB 140-2”), which is incorporated herein by reference and which is available for download at http://csrc.nist.gov/publications/fips. FIPS PUB 140-1 and 140-2 also define security levels that may be met by a device based on the device's security features, with each of these defined security levels generally representing a various level of difficulty—in terms of time and money—that would be encountered in attempting to discern a private key of a device. Currently, four security levels are defined with security level 4 being the highest level of security available.

[0010] Specifications for such security features also are set forth in Trusted Computing Platform Alliance Trusted Platform Module Protection Profile Version 0.45, TRUSTED COMPUTING PLATFORM ALLIANCE, September 2000; Trusted Platform Module (TPM) Security Policy Version 0.45, TRUSTED COMPUTING PLATFORM ALLIANCE, October 2000; and TCPA PC Implementations Specification Version 0.95, TRUSTED COMPUTING PLATFORM ALLIANCE, Jul. 4, 2001, which are incorporated herein by reference (collectively “TCPA Documents”), and which are available for download at http://www.trustedpc.com; and Common Criteria for Information Technology Security Evaluation, Smart Card Protection Profile, Draft Version 2.1d, SMART CARD SECURITY USER GROUP, Mar. 21, 2001, which is incorporated herein by reference (hereinafter “Smart Card Protection Profile”), and which is available for download at http://csrc.nist.gov.

[0011] The particular features of a device that safeguard against discovery of a private key and other protected data are referred to herein as “security characteristics” of the device. The particular features of a device that safeguard against unauthorized use of the device by authenticating the user are referred to herein as “authentication capabilities” of the device. The “security features” of a device (including a cryptographic module or TPM) comprise the security characteristics and authentication capabilities as well as other security features of the device, the requirements of which are specified in the above cited references.

[0012] Unfortunately, while the aforementioned security features generally reduce the risk of fraud within the digital signature system overall, a recipient of any one particular EC including a digital signature may be unfamiliar with the device used to generate the digital signature and, therefore, be unable to gauge the risk of whether the digital signature was generated fraudulently, either through theft of the device or discovery of the private key.

[0013] Of course, if the recipient possesses a shared secret or a biometric value of the sender for performing Sender Authentication, then the recipient may determine that the digital signature was not fraudulently generated assuming that the shared secret or biometric value was not stolen. However, this type of protection by the recipient has significant drawbacks and is not always used by the recipient. For example, if the Secret or biometric value is communicated to the recipient in association with a Platform Alliance Trusted Platform Module Protection Profile Version 0.45, TRUSTED COMPUTING PLATFORM ALLIANCE, September 2000; Trusted Platform Module (TPM) Security Policy Version 0.45, TRUSTED COMPUTING PLATFORM ALLIANCE, October 2000; and TCPA PC Implementations Specification Version 0.95, TRUSTED COMPUTING PLATFORM ALLIANCE, Jul. 4, 2001, which are incorporated herein by reference (collectively “TCPA Documents”), and which are available for download at http://www.trustedpc.com; and Common Criteria for Information Technology Security Evaluation, Smart Card Protection Profile, Draft Version 2.1 d, SMART CARD SECURITY USER GROUP, Mar. 21, 2001, which is incorporated herein by reference (hereinafter “Smart Card Protection Profile”), and which is available for download at http://csrc.nist.gov.

[0014] The particular features of a device that safeguard against discovery of a private key and other protected data are referred to herein as “security characteristics” of the device. The particular features of a device that safeguard against unauthorized use of the device by authenticating the user are referred to herein as “authentication capabilities” of the device. The “security features” of a device (including a cryptographic module or TPM) comprise the security characteristics and authentication capabilities as well as other security features of the device, the requirements of which are specified in the above cited references.

[0015] Unfortunately, while the aforementioned security features generally reduce the risk of fraud within the digital signature system overall, a recipient of any one particular EC including a digital signature may be unfamiliar with the device used to generate the digital signature and, therefore, be unable to gauge the risk of whether the digital signature was generated fraudulently, either through theft of the device or discovery of the private key.

[0016] Of course, if the recipient possesses a shared secret or a biometric value of the sender for performing Sender Authentication, then the recipient may determine that the digital signature was not fraudulently generated assuming that the shared secret or biometric value was not stolen. However, this type of protection by the recipient has significant drawbacks and is not always used by the recipient. For example, if the Secret or biometric value is communicated to the recipient in association with a message for Sender Authentication by the recipient, then the Secret or biometric value first must have been shared with the recipient beforehand and safeguarded by the recipient as part of an established, preexisting relationship; consequently, a recipient having no prior existing relationship with the sender is unable to perform Sender Authentication.

[0017] Another drawback is that the sharing of the Secret or biometric value with the recipient exposes the recipient to liability and exposes the Secret or biometric value itself to a greater risk of theft and dissemination. The transmission of the Secret or biometric value for verification carries with it the risk of interception and discovery during transit. Upon receipt, the Secret or biometric value must be safeguarded by the recipient, which inherently gives rise to a risk of theft from the recipient. This is especially significant in the corporate context where a rogue employee may steal the safeguarded Secret or biometric value (insider fraud historically has been the greatest threat). The potential damages also are extensive when the Secret or biometric value is stolen. Since it is difficult for an individual to remember multiple Secrets for multiple recipients, it is common for the same Secret to be used with different recipients. The theft of the Secret from one recipient thereby compromises the Sender Authentication performed by all of the recipients, at least until the Secret is changed for each recipient. In the case of the theft of a biometric value, the damages are even more severe, as a sender's biometric characteristic cannot be changed and, once lost, potentially compromises any future Sender Authentication therewith.

[0018] Accordingly, a recipient generally is unable to gauge the risk of whether a digital signature was generated fraudulently when no secret or biometric value is shared between the sender and the recipient. Instead, a recipient must rely upon blind trust in accepting that the device used to generate the digital signature has not been stolen and in accepting that the device used to generate the digital signature has sufficient safeguards to protect its private key from discovery and use.

[0019] A need therefore exists for a method by which a recipient may reliably identify a risk of whether a digital signature has been generated fraudulently using a stolen private key (whether stolen by physical theft of the device or discovery of the private key itself), whereby the recipient may protect itself against fraud. In this regard, a need also exists for a method by which a recipient of an EC including a digital signature may reliably determine at any given time the current level of security of the device to which belongs the private key used to generate the digital signature. A need also exists for a method by which a recipient of an EC may reliably determine the safeguards of such device that protect against fraudulent use thereof.

Summary of Invention

[0020] The present invention generally comprises the linking in a reliable manner of a public key of a device that generates digital signatures using asymmetric cryptography to other information regarding the device within an environment in which the device is manufactured. As used herein, the “other information” comprises at least one of security features and manufacturing history of the device, and preferably includes both security features and manufacturing history of the device (herein collectively referred to as “Security Profile”).

[0021] As used herein, the “authentication capabilities” of the device include those components that perform either or both of Factors B and C Entity Authentication with regard to authentication of the user of the device. Furthermore, the “manufacturing history” of the device preferably includes a recording of manufacturing attributes of the device, such as the manufacturer of the device; all specifications applicable to the device; manufacture date of the device; location of manufacture; batch identifier of the device; serial number or part number of the device; security of the manufacturing facility; physical instantiation of the device regarding layout and process geometry; software identification and release date; operating parameters of the device, including voltage and frequency ranges; and identification of all enabled hardware and software security features of the device. The manufacturing history of the device also preferably includes the cryptographic characteristics, key generation characteristics, and random number generator characteristics of the device.

[0022] A. First Aspect of the Present Invention/Identifying PuK-Linked Information of Device Generating Digital Signatures

[0023] A first aspect of the present invention includes the linking of a public key of a device with other information within the environment of its manufacture and then the later identifying of the other information regarding the device after the release of the device from the manufacturing environment based upon its public key. By considering such information later identified, a recipient is able to gauge a risk or likelihood of whether a digital signature using the private key belonging to the device was generated fraudulently.

[0024] In accordance with the preferred methods of the first aspect of the present invention, the device is manufactured in a secure environment (i.e., an environment having a sufficient security rating so as not to compromise the security level of any device manufactured in such environment). Furthermore, the information linked with the public key of the device comprises the Security Profile of the device. Accordingly, the recipient is able to determine a current security level of the device based on the identified security features of the device. The recipient also is able to gauge a risk of whether the private key of the device was compromised based on the identified security characteristics of the device, and the recipient is able to gauge a risk of whether the device containing the private key was fraudulently used based on the identified authentication capabilities of the device. Finally, the recipient is able to evaluate the stated security features of the device based upon the identified manufacturing history of the device.

[0025] In preferred methods of the first aspect of the present invention, before a manufactured device is removed from the secure environment, a public-private key pair is created within the device and the public key is exported and linked to the Security Profile of the device within one or more databases maintained within the secure environment (herein collectively “secure database”). In particular, one of the keys—the public key—is recorded in the secure database by the device manufacturer or other trustworthy entity (“Secure Entity”), and the other key—the private key—is preferably retained within the manufactured device and safeguarded against discovery. The public key also is retained within the device and is exportable upon demand. The Security Profile of the manufactured device is recorded in the secure database, and the record therefor is indexed or mapped to the corresponding public key, thereby reliably linking together both the public key and Security Profile of the device. In this case, the unique identifier is stored within the device and is exportable upon demand. Moreover, since each public key is unique—at least to a high degree of probability—the mapping in the secure database is one-to-one. Alternatively, the public key and Security Profile are indexed to a unique identifier of the device within the secure database, thereby reliably linking together the public key and Security Profile of the device, whereby an assurance level of the device may be determined.

[0026] Subsequently, when an EC is received by a recipient that includes a digital signature generated by a suspect device and the message is authenticated utilizing a suspect public key, the recipient identifies the Security Profile linked to the suspect public key as pertaining to the actual manufactured device to which belongs the private key used to generate the digital signature of the EC (herein “genuine device”). Then, whether the digital signature was generated fraudulently can be gauged by the recipient based upon the known Security Profile for the genuine device. Specifically, the risk of whether the private key retained within the manufactured device has been compromised—and thus whether the suspect device is the genuine device—can be gauged based on the identified security characteristics of the genuine device, and the risk of whether the genuine device has been fraudulently used can be gauged based on the identified authentication capabilities of the genuine device. These evaluations also can be qualified based on the identified manufacturing history of the device, as appropriate.

[0027] In alternative preferred methods of the first aspect of the present invention, a public-private key pair is created and the public key of the device is linked to the Security Profile of the device by combining the public key with the Security Profile into a record that then is digitally signed by the Secure Entity. The record and digital signature together form a “Security Certificate,” which also is imported into the device for safekeeping with the private key. The digital signing of the record by the Secure Entity in the secure environment reliably links the Security Profile of the manufactured device and its public key.

[0028] Subsequently, when a digital signature is generated by the device for inclusion in an EC, the Security Certificate also is included in the EC. Upon receipt and successful authentication of the message using the suspect public key set forth in the Security Certificate, the recipient authenticates the Security Certificate in the EC utilizing a public key of the Secure Entity. Upon successful authentication thereof, the recipient reliably identifies the Security Profile of the genuine device to which belongs the private key used in generating the digital signature of the EC. Then, whether the digital signature was generated fraudulently can be gauged by the recipient based upon the known Security Profile for the genuine device. Specifically, the risk of whether the private key retained within the manufactured device has been compromised—and thus whether the suspect device is the genuine device—can be gauged based on the identified security characteristics of the genuine device, and the risk of whether the genuine device has been fraudulently used can be gauged based on the identified authentication capabilities of the genuine device. These evaluations also can be qualified based on the identified manufacturing history of the device, as appropriate.

[0029] B. Second Aspect of the Present Invention/Establishing PuK-Linked Account Database

[0030] A second aspect of the present invention includes establishing an initial PuK-linked account database. A method in accordance with this aspect of the present invention includes manufacturing devices that generate digital signatures and, for each manufactured device before it is released from the environment of its manufacture: creating a pair of keys used in asymmetric cryptography; storing one of the keys within the manufactured device for utilization in generating a digital signature for an electronic message; and recording the other key and other information in a database maintained within the environment such that the information is linked with the key in the database. The manufactured devices then are distributed to a plurality of users. The users to which the manufactured devices are distributed may comprise existing customers as well as potential customers of a third-party. Thereafter, the database records of the distributed manufactured devices are identified to the third-party as the initial PuK-linked account database of the users.

[0031] In accordance with the preferred methods of this aspect of the present invention, the information with which each key of a device is linked comprises the Security Profile of the respective device, and the devices for which the Security Profiles are identified are manufactured in a secure environment. The database also preferably comprises a secure database. Furthermore, the keys of each device preferably are generated and are retained within the device, with the public key preferably being exportable on demand.

[0032] In preferred methods of this aspect of the present invention, the identifying of the database records includes communicating from the secure environment in a secure manner the database records for the distributed manufactured devices as the initial PuK-linked account database of the third-party. In this regard, the database records are communicated in a manner having a security rating greater than the security level of any manufactured device to which the database records pertain. Indeed, the security rating should be proportional to the aggregate risk presented by all of the individual devices to which the database records pertain. Such a manner includes generating a digital signature for the database records and then communicating the database records and digital signature to the third-party.

[0033] When the third-party receives the PuK-linked database as the initial PuK-linked account database of the users, it may be updated with specific information of the users that is provided by each user. In associating information specific to a user with a record of the initial PuK-linked account database, Factor A Entity Authentication preferably is used based on the user digitally signing a message with the private key of the manufactured device. Alternatively, the initial PuK-linked account database may be merged with a preexisting account database of the users maintained by the third-party that contains user-specific information, or the initial PuK-linked account database may be maintained separately from but indexed with such a preexisting account database of the users. In such case, the third-party preferably authenticates each user as being the correct user for the respective records of the user in the account databases before such association is made. Accordingly, Factor A Entity Authentication preferably is used with respect to the record of the user in the PuK-linked account database, and other entity authentication techniques are used for authenticating the user with respect to the record in the account database. Such other techniques may include questioning the user about specific-account information in the record or requiring the user to provide a Secret, such as the maiden name of the mother of the user.

[0034] C. Third Aspect of the Present Invention/Establishing Initial PuK-Linked Account Database Record

[0035] A third aspect of the present invention includes establishing an initial PuK-linked account database record of a user with a plurality of accounts maintained by different third-parties. A method in accordance with this aspect of the present invention includes manufacturing devices that generate digital signatures and, for each manufactured device before it is released from the environment of its manufacture: creating a pair of keys used in asymmetric cryptography; storing one of the keys within the manufactured device for utilization in generating a digital signature for an electronic message; and recording the other key and other information in a database maintained within the environment such that the information is linked with the key in the database. One of the manufactured devices then is distributed to the user. Thereafter, the database record of the distributed device is identified to each of the third-parties as being the initial PuK-linked account database record of the user. The user may be a customer or potential customer of each third-party.

[0036] In accordance with the preferred methods of this aspect of the present invention, the information with which the key of the device is linked comprises the Security Profile of the device, and the device is manufactured in a secure environment. The database in which the key and Security Profile are linked also preferably comprises a secure database. Furthermore, the keys preferably are generated and are retained within the device, with the public key preferably being exportable on demand.

[0037] In preferred methods of this aspect of the present invention, the identifying of the initial PuK-linked database record includes communicating from the secure environment in a secure manner the database record for the device of the user to a third-party at which an account of the user is or will be maintained. In this regard, the database records are communicated in a manner having a security rating greater than the security level of the manufactured device to which the database record pertains. Such a manner includes generating a digital signature for the database record by the Secure Entity and then communicating the database record and digital signature to the third-party.

[0038] When the third-party receives the PuK-linked database record as the initial PuK-linked account database record of the user, it may be updated with specific information of the user as provided by the user. In associating user-specific information with the initial PuK-linked account database record of the user, Factor A Entity Authentication preferably is used for the initial PuK-linked account database record based on the user digitally signing a message with the private key of the manufactured device. Alternatively, the initial PuK-linked account database record may be merged with a preexisting account database record of the user maintained by the third-party that contains user-specific information, or the initial PuK-linked account database record may be maintained separately from but indexed with such a preexisting account database record of the user. In such case, the third-party preferably authenticates the user as being the correct user for both account records before such association. Accordingly, Factor A Entity Authentication preferably is used in conjunction with other entity authentication techniques for authenticating a user with respect to the account database record. Such other techniques may include questioning the user about specific-account information in the record or requiring the user to provide a Secret, such as the maiden name of the mother of the user.

[0039] D. Fourth Aspect of the Present Invention/Insuring EC for a Transaction Based on Identified PuK-Linked Information of Device Generating Digital Signatures

[0040] Yet a fourth aspect of the present invention includes the insuring of a transaction based, at least in part, on the identified information of a manufactured device that generates digital signatures in accordance with the first aspect of the present invention. In particular, a preferred method in accordance with the fourth aspect of the present invention includes the steps of manufacturing devices in a secure environment and, for each manufactured device before it is released from the secure environment: creating a pair of keys used in asymmetric cryptography; storing one of the keys within the manufactured device for utilization in generating a digital signature for an electronic message; and linking together in a secure manner the other key and the Security Profile of the manufactured device. The manufactured devices then are released from the secure environment.

[0041] Thereafter, an electronic communication representing the transaction is sent with a digital signature generated with a suspect device. The electronic communication includes an electronic message and a digital signature generated for the electronic message utilizing the key stored in one of the manufactured devices. Upon receipt, the message is authenticated using a public key. The Security Profile linked to the public key successfully authenticating the message then is identified as the Security Profile of the genuine device to which belongs the private key used in generating the digital signature, and a monetary guarantee is provided that the digital signature for the electronic message was not generated fraudulently. The monetary guarantee, i.e., the insurance, is provided in exchange for a premium that is based, at least in part, upon an evaluation of the identified security features of the genuine device and further may be based on an evaluation of the manufacturing history of the device. In this regard, the preferred method further includes assigning a defined risk level to the EC based on the identified Security Profile, with each defined risk level corresponding to a different premium rate that is charged for the provision of the monetary guarantee.

[0042] E. Fifth Aspect of the Present Invention/Gauging Whether EC on Account is Fraudulent Based on PuK-Linked Information of Device Generating Digital Signatures

[0043] A fifth aspect of the present invention includes gauging a risk of whether an EC including a digitally signed message representing a transaction on an account is fraudulent based not only on information linked with the public key of a device used to generate the digital signature, but also on a transactional history of the account as recorded by the recipient and, in particular, a history of transactions on the account that were digitally signed (herein “transactional history”).

[0044] In a feature of this aspect of the present invention, a plurality of manufactured devices are distributed to or acquired by a user and the database record for each distributed device is provided to the recipient and associated with the account of the user. Subsequently, for ECs for transactions on the account that are received by the recipient and that include digital signatures generated by one of the devices, the recipient records the particular details regarding each such transaction in the account. However, rather than generally associating the transaction details with the overall account, the recipient associates the transaction details with the linked public key used to successfully authenticate the message of the EC. Accordingly, for each EC received, the recipient evaluates the potential for a fraudulent EC based not only on the information linked with the public key identified in accordance with the first aspect of the present invention, but also on the transactional history of digitals signatures authenticated using such key as recorded by the recipient. In yet an additional feature, the environment in which the digital signature of an EC is generated, if such information is discernable from the EC or otherwise obtainable, also preferably is considered in gauging a risk of whether the EC is fraudulent. For instance, an I/O support element may also digitally sign an EC, and information regarding the I/O support element linked to the public key of the I/O support element may be identified in accordance with the first aspect of the present invention. Furthermore, in another feature, the authentication techniques performed (if any) when a linked public key was associated with the account of the user are recorded in the account record and are considered in gauging a risk of whether a particular EC is fraudulent.

[0045] F. Sixth Aspect of the Present Invention/Service for Disseminating PuK-Linked Information of Device Generating Digital Signatures

[0046] In accordance with a sixth aspect of the present invention, an entity (herein “Central Key Authority”) maintains PuK-linked account registration information for a user (herein “Registration Information”). The Registration Information includes the public key and one or more of the following types of information relating to a particular device of the user that generates digital signatures: the identity of third-parties with which the user has PuK-linked accounts for the device; information linked with the public key of the device in accordance with the first aspect of the present invention; user-specific information; and, if applicable, the authentication techniques that were employed in verifying the user-specific information maintained by the Central Key Authority.

[0047] In accordance with this aspect of the present invention, the Central Key Authority disseminates some or all of the Registration information, as appropriate, to a third-party. Registration information is disseminated when the user has an account with a third-party—or desire to establish an account with a third-party—and desires to send ECs with messages representing transactions on the account that are digitally signed using the device. The dissemination of the Registration information also occurs, for example, when Registration information with a third-party has become outdated for a particular account. Furthermore, the dissemination of the Registration information may be in accordance with the third aspect of the present invention.

Brief Description of Drawings

[0048] Further features and benefits of these aspects of the present invention will be apparent from a detailed description of preferred embodiments thereof taken in conjunction with the following drawings, wherein like references refer to like elements.

[0049] FIG. 1 illustrates a preferred system in which a first preferred method of the first aspect of the present invention is practiced.

[0050] FIG. 2 illustrates a flowchart of steps performed within a secure environment in accordance with the first preferred method of the first aspect of the present invention.

[0051] FIG. 3 illustrates a communication sequence in identifying a Security Profile of a device in accordance with the first preferred method of the first aspect of the present invention.

[0052] FIG. 4 illustrates a flowchart of steps performed by a suspect device originating a digital signature in an EC in accordance with the first preferred method of the first aspect of the present invention.

[0053] FIG. 5 illustrates a flowchart of steps performed by a recipient in accordance with the first preferred method of the first aspect of the present invention.

[0054] FIG. 6 illustrates a flowchart of steps performed by a Secure Entity in accordance with the first preferred method of the first aspect of the present invention.

[0055] FIG. 7 illustrates a flowchart of steps performed within the secure environment in accordance with a second preferred method of the first aspect of the present invention.

[0056] FIG. 8 illustrates a communication sequence in identifying a Security Profile of a device in accordance with the second preferred method of the first aspect of the present invention.

[0057] FIG. 9 illustrates a flowchart of steps performed by a suspect device originating a digital signature in an EC in accordance with the second preferred method of the first aspect of the present invention.

[0058] FIG. 10 illustrates a flowchart of steps performed by a recipient in accordance with the second preferred method of the first aspect of the present invention.

[0059] FIG. 11 illustrates a flowchart of steps performed by a Secure Entity in accordance with the second preferred method of the first aspect of the present invention.

[0060] FIG. 12 illustrates a flowchart of steps performed within the secure environment in accordance with a third preferred method of the first aspect of the present invention.

[0061] FIG. 13 illustrates a communication sequence in identifying a Security Profile of a device in accordance with the third preferred method of the first aspect of the present invention.

[0062] FIG. 14 illustrates a flowchart of steps performed by a suspect device originating a digital signature in an EC in accordance with the third preferred method of the first aspect of the present invention.

[0063] FIG. 15 illustrates a flowchart of steps performed by a recipient in accordance with the third preferred method of the first aspect of the present invention.

[0064] FIG. 16 illustrates a flowchart of steps performed by a Secure Entity in accordance with the third preferred method of the first aspect of the present invention.

[0065] FIG. 17 illustrates a system related to the second aspect of the present invention in which a third-party provides goods and/or services to customers and maintains a customer account database in conjunction therewith.

[0066] FIG. 18 illustrates a preferred system in which a preferred method of the second aspect of the present invention is practiced.

[0067] FIG. 19 illustrates database records of an initial PuK-linked account database in accordance with the preferred method of the second aspect of the present invention.

[0068] FIG. 20 illustrates a PuK-linked account database of customers comprising the database records of FIG. 19 after having been updated and/or merged by the third-party representing an Internet service provider.

[0069] FIG. 21 illustrates a PuK-linked account database of customers comprising the database records of FIG. 19 after having been updated and/or merged by the third-party representing a financial institution.

[0070] FIG. 22 illustrates a preferred system in which a preferred method of the third aspect of the present invention is practiced.

[0071] FIG. 23 illustrates a preferred system in which a first preferred method of the fourth aspect of the present invention is practiced.

[0072] FIG. 24 illustrates a communication sequence in accordance with the first preferred method of the fourth aspect of the present invention.

[0073] FIG. 25 illustrates a flowchart of steps performed by a suspect device originating a digital signature of an EC in accordance with the first preferred method of the fourth aspect of the present invention.

[0074] FIG. 26 illustrates a flowchart of steps performed by a Financial Institution in accordance with the first preferred method of the fourth aspect of the present invention.

[0075] FIG. 27 illustrates a flowchart of steps performed by an Insuring Entity in accordance with the first preferred method of the fourth aspect of the present invention.

[0076] FIG. 28 illustrates a flowchart of steps performed by a Secure Entity in accordance with the first preferred method of the fourth aspect of the present invention.

[0077] FIG. 29 illustrates a communication sequence in accordance with a second preferred method of the fourth aspect of the present invention.

[0078] FIG. 30 illustrates a flowchart of steps performed by a suspect device originating a digital signature in an EC in accordance with the second preferred method of the fourth aspect of the present invention.

[0079] FIG. 31 illustrates a flowchart of steps performed by a Financial Institution in accordance with the second preferred method of the fourth aspect of the present invention.

[0080] FIG. 32 illustrates a flowchart of steps performed by an Insuring Entity in accordance with the second preferred method of the fourth aspect of the present invention.

[0081] FIG. 33 illustrates a flowchart of steps performed by a Secure Entity in accordance with the second preferred method of the fourth aspect of the present invention.

[0082] FIG. 34 illustrates a communication sequence in accordance with a third preferred method of the fourth aspect of the present invention.

[0083] FIG. 35 illustrates a flowchart of steps performed by a suspect device originating a digital signature in an EC in accordance with the third preferred method of the fourth aspect of the present invention.

[0084] FIG. 36 illustrates a flowchart of steps performed by a Financial Institution in accordance with the second preferred method of the fourth aspect of the present invention.

[0085] FIG. 37 illustrates a flowchart of steps performed by an Insuring Entity in accordance with the second preferred method of the fourth aspect of the present invention.

[0086] FIG. 38 illustrates a flowchart of steps performed by a Secure Entity in accordance with the second preferred method of the fourth aspect of the present invention.

[0087] FIG. 39 illustrates a communication sequence in accordance with a fourth preferred method of the fourth aspect of the present invention.

[0088] FIG. 40 illustrates a flowchart of steps performed by a suspect device originating a digital signature in an EC in accordance with the fourth preferred method of the fourth aspect of the present invention.

[0089] FIG. 41 illustrates a flowchart of steps performed by a Financial Institution in accordance with the fourth preferred method of the fourth aspect of the present invention.

[0090] FIG. 42 illustrates a flowchart of steps performed by an Insuring Entity in accordance with the fourth preferred method of the fourth aspect of the present invention.

[0091] FIG. 43 illustrates a flowchart of steps performed by a Secure Entity in accordance with the fourth preferred method of the fourth aspect of the present invention.

[0092] FIG. 44 illustrates an established PuK-linked account database of customers of a third-party representing a financial institution in accordance with a preferred method of a fifth aspect of the present invention.

[0093] FIG. 45 illustrates a flow chart for considering whether to perform a transaction on an account in accordance with a preferred method of the fifth aspect of the present invention.

[0094] FIG. 46 illustrates an account database of a Central Key Authority in accordance with a sixth aspect of the present invention.

[0095] FIG. 47 illustrates a communication sequence in accordance with a preferred method of the sixth aspect of the present invention.

[0096] FIG. 48 illustrates a flowchart of steps performed by a user in accordance with the preferred method of the sixth aspect of the present invention of FIG. 47.

[0097] FIG. 49 illustrates a flowchart of steps performed by a Central Key Authority in accordance with the preferred method of the sixth aspect of the present invention of FIG. 47.

[0098] FIG. 50 illustrates a flowchart of steps performed by a first Account Authority in accordance with the preferred method of the sixth aspect of the present invention of FIG. 47.

[0099] FIG. 51 illustrates a flowchart of steps performed by a second Account Authority in accordance with the preferred method of the sixth aspect of the present invention of FIG. 47.

Detailed Description

[0100] As a preliminary matter, it readily will be understood by those persons skilled in the art that, in view of the following detailed description of the devices, systems, and methods of the present invention, the present invention is susceptible of broad utility and application. Many embodiments and adaptations of the present invention other than those herein described, as well as many variations, modifications, and equivalent arrangements, will be apparent from or reasonably suggested by the present invention and the following detailed description thereof, without departing from the substance or scope of the present invention. Furthermore, those of ordinary skill in the art will understand and appreciate that although steps of various processes may be shown and described in some instances as being carried out in a preferred sequence or temporal order, the steps of such processes are not necessarily to be limited to being carried out in such particular sequence or order. Rather, in many instances the steps of processes described herein may be carried out in various different sequences and orders, while still falling within the scope of the present invention. Accordingly, while the present invention is described herein in detail in relation to preferred embodiments, it is to be understood that this detailed description only is illustrative and exemplary of the present invention and is made merely for purposes of providing a full and enabling disclosure of the present invention. The detailed description set forth herein is not intended nor is to be construed to limit the present invention or otherwise to exclude any such other embodiments, adaptations, variations, modifications and equivalent arrangements of the present invention, the present invention being limited solely by the claims appended hereto and the equivalents thereof.

[0101] A. Overview of the Present Invention

[0102] The present invention generally comprises the linking in a reliable manner of a public key of a device that generates digital signatures using public-private key cryptography to other information regarding the device within an environment in which the device is manufactured. The public-private key pair preferably is generated within the device during its manufacture; thereafter, the private key is retained securely within the device and never exported, and the public key may be retained within the device and exportable upon demand whenever needed.

[0103] In accordance with all of the aspects of the present invention, the device comprises hardware or firmware and, specifically, comprises a computer chip, an integrated circuit, a computer-readable medium having suitable software therein, or a combination thereof. The device further may comprise a physical object such as a hardware token or an embedded token, the token containing such a computer chip, integrated circuitry, or software, or combination thereof. If the device is a hardware token, it preferably takes the form of a ring or other jewelry; a dongle; an electronic key; a card, such as an IC card, smart card, debit card, credit card, ID badge, security badge, parking card, or transit card; or the like. If the device is an embedded token, it preferably takes the form of a cell phone; a telephone: a television; a personal digital assistant (PDA); a watch; a computer; computer hardware; or the like. The device preferably includes a device interface comprising a port-including a wireless communications port, a serial port, a USB port, a parallel port, or an infrared port-or some other physical interface for communicating with an external electronic apparatus, whether contact or contactless. The device also may include a trusted platform module (TPM) comprising hardware and software components providing increased trust in a platform, as set forth and described in the TCPA Documents cited above.

[0104] Some of these devices require use of an I/O support element to enable the device to receive data representing a message, a Secret, or a biometric characteristic. Some of the devices require an I/O support element to receive specific types of data but not others. Some of the devices require use of an I/O support element to transmit information including digital signatures and messages to recipients. Some of the devices are self-contained and can generate and transmit messages and digital signatures without the use external apparatuses; some devices, although self-contained, are capable of interacting with such external apparatuses, such as an I/O support element, if desired. An I/O support element may take the form of any number of different apparatuses, depending upon the particular application in which it is used and depending upon the type of device with which interacts.

[0105] For applications of a device requiring high security, the device—or the device in combination with an I/O support element—preferably includes the following components: a keypad (alphanumeric), interactive display, or other type of user data entry mechanism (collectively referred to herein as “User Interface”) that allows a user to compose or modify a message; a User Interface for inputting data representing a Secret (it should be noted that the User Interface for generating or modifying a message may, but does not have to, be the same as the User Interface for the entry of the data representing a Secret); a display for showing the message and/or Secret to the user; a scanner or reader for receiving at least one type of biometric data for a biometric characteristic of the user; memory for securely storing the Secret of the authorized user, biometric data of the authorized user, and the private key; a processor or circuitry for verifying input of the Secret of biometric data as being that of the authorized user: a processor or circuitry for generating or originating digital signatures; and a means for outputting from the device and transmitting information including the message and digital signature therefor. Preferably, the device also includes memory for storing and exporting the public key associated with the particular private key, and for storing types of user information such as account information, user ID, and the like. For lower security applications, not all of the above elements are necessary.

[0106] The public key linked information in the preferred embodiments of the present invention includes the Security Profile of the device. As defined above, the Security Profile preferably includes the security features of the device (including characteristics and authentication capabilities), as well as the manufacturing history of the device. It is important to know the security features of a device—rather than simply a stated security level of the device—as technologies are developed over time that reduce the effectiveness of such security features and, consequently, result in the decrease of the actual security level of the device. Unless upgrades are made, the security features of a device are permanent while the security level of the device eventually will decrease over time. By knowing the security features, the appropriate security level of a device may be determined at any given time. Furthermore, by knowing the security characteristics of the device, a recipient is able to gauge a likelihood of whether the private key of the device has been compromised, and by knowing the authentication capabilities of the device (or lack thereof), a recipient is able to gauge a likelihood of whether someone other than the authorized user utilized the device to generate a digital signature. Finally, by knowing the manufacturing history of a device, the security features of the device may be revised as errors, omissions, flaws, security breaches, or possible improprieties and the like are discovered as having occurred during the manufacturing of the device.

[0107] A. Identifying PuK-Linked Information of Device Generating Digital Signatures

[0108] 1. First Preferred Embodiment

[0109] In accordance with the first aspect of the present invention, and with reference to FIG. 1, a first preferred embodiment is practiced within a first preferred system 100 that includes a secure manufacturing facility 102, devices manufactured at the facility 102 as represented by device 104, the world 106, a recipient 108, and a secure database 110 maintained by a Secure Entity 112. The facility 102 and the secure database 110 are located within a secure environment 114, which represents any and all locations having a sufficient security rating so as not to compromise the security level of the device 104 manufactured in the facility 102. As will be apparent, the facility 102 and the secure database 110 need not be co-located at the same physical location in order to be within the secure environment 114. Nor must the manufacturer of the device 102 be the Secure Entity 112 that maintains the secure database 110, although such possibility is within the scope of the present invention.

[0110] The relevant manufacturing steps that are performed within the secure environment 114 are set forth in FIG. 2. With reference to both FIGS. 1 and 2, a public-private key pair is generated (Step 202) within the device 104 during its manufacture in the facility 102 and before the device 104 is released from the secure environment 114. Preferably the public-private key pair is created with a random number generator disposed within the device 104 itself. The private key 116 (PrK) is retained within the device 104, while the corresponding public key (PuK) 118 is exported (Step 204) from the device 104 and recorded (Step 206) in the secure database 110 before the device 104 is released from the secure environment 114. If desired, the public key 118 also may be retained (not shown) within the device 104 for later export upon demand after release of the device 104 from the secure environment 114. The private key 116 is utilized, for example, in generating a digital signature (DS) for a message (M) that is communicated to the recipient 108. In addition to the public key 118, a Security Profile 120 of the device 104 is compiled and recorded (Step 208) in the secure database 110 and indexed to the public key 118, whereby the Security Profile 120 is retrievable from the secure database 110 based on knowledge of the public key 118. The public key 118 and Security Profile 120 are thereby securely linked together.

[0111] Following population of the secure database 110 with the public key 118 and Security Profile 120 of the device 104, the device 104 is released from the secure environment 114 into the world 106. The secure database 110, however, is maintained (Step 210) in the secure environment 114 to preserve the integrity of the data recorded therein. Furthermore, following manufacture the security rating of the secured environment 114 is maintained at a level that is at least as comparable to, and preferably greater than, the security level of each device 104 manufactured at the facility 102 for which the public key 118 and Security Profile 120 are maintained in the secure database 110.

[0112] With reference now to FIGS. 3-6, a digital signature (DS) is originated (Step 402) for a message (M) somewhere in the world 106 with a suspect device. The suspect device may be the genuine device 104 manufactured at the facility 102 of FIG. 1 that is legitimately used, the genuine device 104 that is fraudulently used, or a counterfeit device having a replica of the private key 116 of the genuine device 104. The digital signature then is combined (Step 404) with the message to form an EC 122, which is sent (Step 406) to the recipient 108 over any conventional secure or insecure electronic communications network, such as the Internet or a private network.

[0113] The recipient 108 receives the EC 122 (Step 502) and attempts to authenticate (Step 504) the message using a suspect device public key 124. The suspect device public key 124 is provided to the recipient 108 and, preferably, is included within the EC 122 that is received by the recipient 108, whereby the recipient 108 may readily attempt authentication of the message. Alternatively, the suspect device public key 124 is identified to the recipient 108 before or after receipt of the EC 122 in such a manner that the recipient 108 is able to associate the suspect device public key 124 with the EC 122.

[0114] In any event, if the message successfully authenticates using the suspect device public key 124, and if the message is the first message authenticated using the suspect device public key 124, then the recipient 108 sends (Step 506) the suspect device public key 124 to the Secure Entity 112 that manages the secure database 110 and requests a Security Profile associated with that public key 124. Communications between the recipient 108 and the Secure Entity 112 are by way of any conventional secure or insecure electronic communications network, such as the Internet or a private network.

[0115] When the Secure Entity 112 receives (Step 604) the suspect device public key 124 from the recipient 108, the Secure Entity 112 compares (Step 606) the suspect device public key 124 against the exported public keys maintained in the secure database 110 to determine if there is a match. If a match is found, then the Security Profile associated with the matching exported public key is retrieved and, for the purpose of maintaining the integrity of the information during transit, digitally signed (Step 608) by the Secure Entity 112. The Security Profile and digital signature therefor create a “Security Certificate” (SC) 126 that then is forwarded (Step 610) to the recipient 108. Preferably, the public key 118 of the manufactured device 104 matching the suspect device public key 124 is included in the Security Certificate 126 for confirmation by the recipient 108 of the public key 118 to which the Security Certificate 126 pertains.

[0116] Upon receipt (Step 508) of the Security Certificate 126 from the Secure Entity 112, the authenticity of the Security Certificate 126 is checked (Step 510) using a public key 128 (SE PuK) of the Secure Entity 112, which preferably has been communicated (Step 602) to the recipient 108 beforehand. Subsequently, upon a successful authentication, the Security Profile contained in the authenticated Security Certificate 126 is identified as the Security Profile 120 of the genuine device 104 to which belongs the private key 116 used to digitally sign the message of the EC 122.

[0117] Thereafter, the recipient 108 gauges the risk of whether the use of the private key 116 of the genuine device 104 to digitally sign the message of the EC 122 was fraudulent based on the identified Security Profile. The Security Certificate 126 also is recorded by the recipient 108 in an “in-house” database maintained by the recipient 108, whereby the same suspect device public key 124 used to authenticate future ECs may be referenced against this in-house database for identifying the appropriate Security Profile, rather than again sending a request for the Security Profile to the Secure Entity 112. Accordingly, another request need not be made unless and until the Security Profile has been updated by the Secure Entity 112.

[0118] 2. Second Preferred Embodiment

[0119] Briefly described, in a second preferred embodiment of the first aspect of the present invention a Secure Entity generates a reference containing device public keys and corresponding Security Profiles linked thereto for a plurality of devices manufactured at a secure manufacturing facility and communicates the reference to a recipient. The reference is embodied in print or electronic media and includes a list of Security Profiles of manufactured devices indexed by their respective public keys. Furthermore, the reference preferably is digitally signed by the Secure Entity, whereby the recipient may securely rely upon the information contained in the reference when successfully authenticated with a public key of the Secure Entity. Thereafter, the recipient only need compare each suspect device public key that successfully authenticates a message against the device public keys included in the reference, rather than actually send each suspect device public key to the Secure Entity for a Security Profile. The recipient thereby is readily able to identify the Security Profile of the genuine device to which belongs the private key used to digitally sign the message.

[0120] With particular reference to FIG. 7, and in accordance with this second preferred embodiment, a public-private key pair is created (Step 702) within each device during its manufacture and before the devices are removed from a secure environment 714. The respective private key of each device is retained securely within the device, and the respective public key is exported from each device (Step 704) and recorded (Step 706) in a secure database together with the respective Security Profile of each device. The respective public key may also be retained within each device and be exportable upon demand. Each Security Profile is indexed with the exported public key (Step 708) of the respective device, whereby the Security Profile of the device is retrievable from the secure database based on the public key. Following population of the secure database with the public key and Security Profile of the device, the Secure Entity creates and preferably digitally signs (Step 710) a reference including the Security Profiles and public keys linked therewith for the respective devices. As will be appreciated by one of ordinary skill in the art, all of the Steps 702-710 occur within the secure environment 714.

[0121] Following release of the devices from the secure environment 714, and with reference now to FIGS. 8-11, a digital signature is originated (Step 902) for a message (M) somewhere in the world 806 with a suspect device, and the digital signature is combined (Step 904) with the message to form an EC 822, which is then sent (Step 906) to the recipient 808. The recipient 808 receives the EC 822 (Step 1004) and attempts to authenticate (Step 1006) the message using a suspect device public key sent within the EC 822 or otherwise provided to the recipient 808.

[0122] Upon successful authentication of the message, the recipient 808 compares the suspect device public key against the public keys included in the reference 830 created by the Secure Entity 812. The reference 830 is forwarded (Step 1106) to the recipient 808 and received and authenticated (Step 1002) by the recipient 808 preferably before the receipt of the EC 822. Also, in order that the recipient 808 may authenticate the reference 830, the public key 828 (SE PuK) of the Secure Entity 812 also preferably is communicated (Step 1102) in a secure manner beforehand. Then, if the suspect device public key matches a public key in the reference 830, the Security Profile of the genuine device to which belongs the private key used to digitally sign the message is identified. Subsequently, the recipient 808 is able to gauge, based on the identified Security Profile, a risk that the private key of the genuine device was fraudulently used to digitally sign the message of the EC 822.

[0123] 3. Third Preferred Embodiment

[0124] In a third preferred method, a Security Certificate is incorporated into a manufactured device itself prior to its release from the secure environment of its manufacture. In this regard, and with reference to FIG. 12, a pair of keys are created (Step 1202) within the device during its manufacture and before its release from a secure environment 1214. The private key is securely retained within the device, and the public key is exported (Step 1204) from the device and may also be retained within the device and be exportable upon demand. The exported public key is combined with a Security Profile of the device and digitally signed (Step 1206) by the Secure Entity to form the Security Certificate. The Security Certificate then is imported (Step 1208) into the device itself and is exportable from the device with a digital signature for inclusion in an EC.

[0125] Thereafter, with reference to FIGS. 13-16, a suspect device originates (Step 1402) a digital signature for a message (M) somewhere in the world 1306. The digital signature and Security Certificate of the device are then exported from the device and combined (Step 1404) with the message to form an EC 1322, which then is sent (Step 1406) to the recipient 1308. Upon receipt (Step 1504) of the EC 1322 by the recipient 1308, the suspect device public key identified in the Security Certificate is used to authenticate (Step 1506) the message, and the Secure Entity's public key 1328—which preferably is communicated (Step 1602) by the Secure Entity 1312 and received (Step 1502) by the recipient 1308 beforehand—is used to authenticate (Step 1508) the Security Certificate. Upon successful authentication, the Security Profile of a genuine device to which belongs the private key used to generate the digital signature is thereby identified to the recipient 1308. Based on the identified Security Profile, the recipient 1308 is able to gauge the risk that the private key of the genuine device was fraudulently used to digitally sign the message of the EC 1322. Furthermore, because the public key is bound with the Security Profile in the Security Certificate during the manufacture of the device in the secure environment, the recipient 1308 is able to rely upon the Security Certificate corresponding, in fact, to the genuine device.

[0126] Benefits of the third preferred embodiment of the first aspect of the present invention include the elimination of the requirement that the recipient 1308 transmit a suspect device public key to the Secure Entity 1312, and the elimination of the requirement that the Secure Entity 1312 transmit the a Security Profile directly to the recipient 1308. Of course, a disadvantage to this preferred method is that the entire system is compromised if the Secure Entity's private key used to digitally sign Security Certificates is compromised.

[0127] 4. Variations of the Preferred Embodiments

[0128] In the first and second preferred embodiments of the first aspect of the present invention set forth above, the Security Profile of each device is indexed in the secure database to the public key of the device and is retrievable from the secure database based on the public key. In a variation of these two preferred embodiments (not shown), the Security Profile and public key of each device is recorded in the secure database and are indexed to a unique device identifier, which may comprise, for example, an account number written into the device during its manufacture, a serial number manufactured within the device during its manufacture, or the like. The device identifier is exportable from the device for inclusion with each digital signature generated by the device. Upon receipt of an EC including the digital signature and device identifier, a recipient then obtains the suspect device public key by cross-referencing the device identifier with a known database or reference for public keys and Security Profiles linked therewith. In this regard, the recipient forwards the device identifier to a Secure Entity for identifying the suspect device public key and Security Profile therefor, or the recipient compares the device identifier in a reference published by the Secure Entity that includes public keys and linked Security Profiles indexed by device identifiers. The methodology is similar to that described above for the first and second preferred embodiments, the primary difference being that the recipient must contact the Secure Entity or check a reference prior to attempting to authenticate a received message. In the first and second preferred embodiments in which the Security Profile of each device is indexed to its public key, the recipient only need contact the Secure Entity or check a reference if the message first authenticates using the suspect device public key included with the message.

[0129] In a variation of the first, second, and third preferred embodiments of this aspect of the present invention, the Secure Entity receives the EC and, itself, identifies the Security Profile of the genuine device to which belongs the private key used to digitally sign the message. Furthermore, the EC in this case either may be sent directly to the Secure Entity or may be forwarded to the Secure Entity by a recipient for gauging of the risk that the private key of the genuine device was fraudulently used to digitally sign the message.

[0130] Preferably, the steps set forth above with regard to FIGS. 5-6; FIGS. 10-11; and FIGS. 15-16 are computer automated, and the entire sequence of events of each respective group of figures occurs within a small time interval on the order of magnitude of minutes, if not seconds.

[0131] In view of the foregoing detailed description of preferred embodiments of the first aspect of the present invention, it will be apparent to those having ordinary skill in the art that by: creating the respective public-private key pair of each device within the device itself before release from the secure environment of its manufacture; exporting only the public key from the device and retaining the private key within the device against the possibility of export; and securely linking the exported public key of the device with other information within the secure environment of manufacture of the device, each device is thereby rendered unique with respect to all of the other devices. Moreover, because of the secure environment in which the devices are manufactured and the secure linking of the public key with the other information, the uniqueness of the devices may be relied upon by third-parties—such as future Account Authorities even though such third-parties may not have had any control or involvement in the actual manufacturing of the devices. The secure binding of the public key with each device within the environment of the manufacture of the device provides the required trust for relying upon the uniqueness of the devices, as each device may be authenticated based upon the private key retained therein, and only therein. Accordingly, the present invention further includes this manufacturing process for devices.

[0132] A benefit this manufacturing process is that it provides the ability to transport devices from their place of manufacture to additional processing facilities where the devices are initialized with regard to particular Account Authorities without high levels of security otherwise conventionally utilized. For example, armored cars and guards are routinely used to protect the delivery of credit card and IC card supplies to a processing facility for initialization for a particular financial institution. Indeed, as a result of the manufacturing process of the present invention, a facility at which additional processing takes place on behalf of a particular Account Authority now may authenticate each device prior to its initialization and independent of the transport of the device from the manufacturing facility. Moreover, because of the ability to authenticate a particular device immediately following its manufacture and thereafter, the system of using of a single device for making transactions on multiple accounts maintained with different Account Authorities is now enabled with higher levels of trust not otherwise found in the conventional art.

[0133] B. Establishing Initial PuK-Linked Account Database

[0134] The second aspect of the present invention includes establishing an initial PuK-linked account database and is based partially upon the first aspect of the present invention. In this regard, the establishment of a database for a plurality of manufactured devices as described above-wherein each device has a unique record including its public key and other information regarding the device-represents a database that may be built upon in creating an initial PuK-linked account database for plurality of customers and/or consumers (generically referred to herein as “customers”) of a third-party.

[0135] Specifically, with reference to FIG. 17, a third-party 1732 provides services and/or goods 1734 to each of a plurality of customers 1736 and, in connection therewith, maintains a database 1738 of account records for the customers 1736. For example, and without limitation, the third-party 1732 (herein referred to as an “Account Authority”) may be a financial institution including a bank, finance company, or insurance company, merchant; Internet service provider; telecommunication provider; medical provider; government entity; or utility company. The account database 1738 typically is established one account at a time on a per customer basis is each customer 1736 engages the Account Authority 1732, and each database record for the customer 1736 typically is indexed within the database 1738 by a unique account number.

[0136] In accordance with the second aspect of the present invention, and with reference to FIG. 18, a predetermined number of devices 1804 are manufactured in a secure environment 1814 in accordance with the first and second preferred embodiments of the first aspect of the present invention. In accordance with the second aspect of the present invention, the devices 1804 are earmarked for the Account Authority 1732, and database records 1840 in the secure database 1810 corresponding to the devices 1804 are communicated in a secure manner 1814′ to the Account Authority 1732. The earmarked devices 1804 also are distributed to the customers 1736 of the Account Authority 1732.

[0137] Upon receipt of the PuK-linked database records 18440 by the Account Authority 1732, the database records 1840 represent an initial PuK-linked account database for the Account Authority 1732. The database records 1840 preferably include the public keys 1818 of the devices 1804 and the Security Profiles 1820 of the devices 1804 as described above with respect to the first and second preferred embodiments of the first aspect of the present invention. Moreover, the database records 1840 are preferably digitally signed by the Secure Entity 1812 for security in transit from the Secure Entity 1812 to the Account Authority 1732.

[0138] An example of the preferred database records 1840 are shown in FIG. 19. As set forth in the background section above, the Security Profile includes security features of the device—specifications for which are set forth for example in FIPS PUBS 140-1 and 140-2—as well as a manufacturing history of the device as specified, for example, in Smart Card Protection Profile. Moreover, in accordance with the preferred embodiments of the present invention the security features of the Security Profile include security characteristics and authentication capabilities of the device.

[0139] Once received, the Account Authority 1732 updates the PuK-linked account database records with specific information of the customers 1736 and their accounts. However, before such an association is made between a particular customer's account and a record of the initial PuK-linked account database, the particular customer 1736 preferably is authenticated to the Account Authority 1732 with respect to that customer's account. Accordingly, entity authentication techniques are used for authenticating the customer 1736 with respect to a record in the account database. Such authentication techniques may include questioning the particular customer 1736 about specific-account associated information in the record or requiring the particular customer 1736 to provide a Secret or other entity information, such as the maiden name of the mother of the customer (Factor B Entity Authentication).

[0140] Additionally, the Account Authority 1732 preferably verifies that a customer 1736 has received the correct device 1804. The device 1804 received by a customer 1736 is identified by having the customer 1736 digitally sign a message with the private key of the device 1804 and transmit the message and digital signature in a respective EC 1822 that is sent to the Account Authority 1732 for Factor A Entity Authentication. The Account Authority 1732 authenticates the message using a public key of the device 1804 that preferably is included in the EC 1822. Furthermore, upon a successful authentication of the message, the Account Authority 1732 identifies the record in the initial PuK-linked account database corresponding to the public key successfully authenticating the message for association with the account of the customer 1736.

[0141] If additional security is required, each device may include an initialization PIN that first must be entered by a customer before functioning. Upon the correct entry of the initialization PIN, each customer preferably then enters a personalization PIN that must be entered, for example, each time the device is used thereafter. The initialization PINs preferably are distributed to the customers separately from the devices. Moreover, the use of an initialization PIN and a personalization Pin in each device preferably is included in each database record as part of the authentication capabilities of the respective device.

[0142] A number of alternative techniques for verifying that the customers received the correct cards also could be used. For example, each customer could be required to call a particular number from his or her home and input over the telephone a number printed on each respective device in order to effect association of the device with the customer's account.

[0143] Once sufficient authentication is completed, the customer-specific information may be associated with the PuK-linked account database record in various ways. First, the initial PuK-linked account database record may be merged with a preexisting account database of the customer maintained by the Account Authority, which contains the customer-specific information. Second, the initial PuK-linked account database may be maintained separately from but indexed by an identifier with a preexisting account database of the customer containing the customer-specific information. Third, the Account Authority simply may obtain the customer-specific information from the customer following authentication and update the PuK-linked account database record accordingly.

[0144] This second aspect of the present invention also is useful in establishing accounts for new customers of the Account Authority. In this regard, devices are distributed in the same manner as set forth in FIG. 18, but to potential customers of the Account Authority rather than to existing customers. However, in this scenario entity authentication with respect to preexisting accounts is not required, as new accounts are established by the potential customers. Nevertheless, Factor A Entity Authentication remains important in associating a customer with one of the particular PuK-linked records.

[0145] With respect to the establishment of new accounts, under an “anonymous” framework the manufactured devices are distributed to the customers, and the goods and/or services are provided to the customers without regard to any customer-specific information, i.e., the goods and/or services are provided on a per device basis as identified by the public key of the device, and are not necessarily on a per customer basis. Thus, upon successful authentication with a public key of a message digitally signed by one of the devices, the account identified by the public key is activated and nothing further is required.

[0146] On the other hand, under a “personalized” framework each new customer provides customer-specific information to the Account Authority, and the Account Authority updates the initial PuK-linked account database by associating the customer-specific information with the respective PuK-linked database record of that customer's device (as identified by the public key of that device). Again, the Account Authority in this situation does not need to authenticate the new customer with respect to any existing account.

[0147] An example of a new business method of establishing a initial PuK-linked account database in accordance with the second aspect of the present invention comprises establishing new customers for an Internet service provider (ISP). First, a number of manufactured devices such as dongles, for instance, are manufactured in accordance with the first aspect of the present invention and mailed to a plurality of prospective customers of the ISP. Each dongle is packaged with a CD-ROM including software for setting up and connecting to the ISP and the Internet from a potential customer's computer. The dongle and CD-ROM also may be distributed as an insert in a magazine, for example. Upon receipt, the prospective customer installs the software in his or her computer and attaches the dongle to an appropriate port of the computer. Then, when the computer connects with the ISP, an EC is communicated to the ISP that includes a digital signature generated utilizing a private key retained within the dongle as well as a public key retained within and exported from the dongle. Upon receipt of the EC, the ISP authenticates the message using the public key included with the message. Upon authentication, then the ISP compares for a match the public key received with the linked public keys in the initial PuK-linked account database and activates the account having the matching public key. The account record may include a credit of 100 hours of free internet surfing, for example, as a promotional introduction to the ISP. In this example, no customer-specific information is required and the account is setup under an anonymous framework.

[0148] Alternatively, the ISP may require customer-specific information in order to activate the new account, including billing and credit card information from the customer. Upon receipt thereof, the identified record in the PuK-linked account database is updated with this customer-specific information and the account is activated. A resulting updated PuK-linked account database 2040 of the ISP after activation of several accounts might resemble, for instance, that of FIG. 20.

[0149] Upon activation of the account, the account preferably is assigned a unique account identifier that is included with each message sent to the ISP for identifying the account to which the message relates. A User ID or account number may serve as the account identifier. The public key is recorded in the PuK-linked account database whereby, upon identifying the appropriate account record with the account identifier, the digitally signed message is authenticated with the associated public key. Alternatively, the public key itself may serves as the account identifier. In either case, access is granted to its network and the Internet by the ISP upon a successful authentication of a digitally signed message (Factor A Entity Authentication).

[0150] Another example of a new business method utilizing the aforementioned establishment of a initial PuK-linked account database of this second aspect of the present invention comprises setting up existing customers of a financial institution with IC cards to be used as check cards. In this example, a number of IC cards are manufactured in accordance with the first aspect of the present invention and mailed to a plurality of existing customers of the financial institution who have requested the IC cards. Each manufactured IC card includes a respective initialization PIN that must be sent to the financial institution for activation of the IC card for use on the account. The respective initialization PIN is mailed to each customer separately from the corresponding IC card. Furthermore, each IC card includes recorded therein the account number of the customer to which it is mailed.

[0151] The database records of the IC cards recorded in the secure database are transmitted to the financial institution in a secure manner. Upon receipt, the database records represent the initial PuK-linked account database which then are updated and/or merged with the records of the customers in a preexisting account database maintained by the financial institution, the resulting database being a PuK-linked account database. A resulting PuK-linked account database 2140 might resemble, for instance, that of FIG. 21.

[0152] Upon separate receipt by each customer of the IC card and initialization PIN, the customer first uses the IC card at an ATM machine of the financial institution by entering the initialization PIN and then communicating to the financial institution an EC including the PIN from the customer and account number from the IC Card digitally signed with the IC card. Upon receipt of the EC, the financial institution authenticates the sender of the EC by retrieving the authorized PIN from the identified account number in the EC and comparing the authorized PIN with the PIN transmitted in the EC. The financial institution similarly authenticates the message with the public key associated with the identified account number. Upon successful verification of the PIN and successful message authentication, the financial institution activates the IC card within the record for use as a check card on the account. Furthermore, after activation of the IC card, messages in ECs representing transactions on the account need only be digitally signed with the IC card and include the account number of the customer. Such ECs need not include any personal information of the customer, such as the customer's name, billing address, a PIN, etc.

[0153] C. Establishing Multiple Third-party Accounts with PuK-Linked Database Record

[0154] The third aspect of the present invention includes establishing multiple third-party accounts with a PuK-linked database record and is based partially upon the first and second preferred embodiments of the first aspect of the present invention. In this regard, and with reference to FIG. 22, a device 2204 that generates digital signatures is manufactured within a secure environment 2214. Before the device 2204 is released from the secure environment 2214, the public key 2218 of the device 2204 plus some other information is recorded as a database record 2275 in a secure database 2210; preferably, the other information includes the Security Profile 2220 of the device 2204, as described above with respect to the first aspect of the present invention. The device 2204 then is distributed to a customer 2232 and the customer 2232 establishes a respective account with each one of a plurality of desired Account Authorities 2242,2244,2246.

[0155] In accordance with the third aspect of the present invention, each PuK-linked account of the customer 2232 is established based upon, at least in part, a communication of the PuK-linked database record 2248 from the secure database 2210 to each of the desired Account Authorities 2242,2244,2246. As set forth above, the PuK-linked database record 2248 preferably includes the public key 2218 and Security Profile 2220 of the device 2204 linked thereto by the Secured Entity 2212. Furthermore, the database record 2248 is communicated in a secure manner 2214′ so as to preserve the integrity of the database record 2248.

[0156] When received by a respective Account Authority 2242,2244,2246, the public key 2218 linked to the Security Profile 2220 of the database record 2248 represents an initial PuK-linked account database record of the customer 2232 with the respective Account Authority and, if the customer 2232 is an existing customer of the respective Account Authority, then the initial PuK-linked account database record 2248 preferably is associated with the existing account database record of the customer 2232. However, the association of the PuK-linked account database record 2248 received from the Secure Entity 2212 with the existing account database record of the customer 2232 preferably is performed only after the receipt of the correct device 2204 by the customer 2232 has been verified through one or more of the aforementioned authentication techniques with regard to the second aspect of the present invention.

[0157] If the initial PuK-linked account database record represents the only account database record for the customer 2232 (i.e., if the customer is new to an Account Authority), then under a personalized framework the customer 2232 supplies customer-specific information to the Account Authority for recording with the initial PuK-linked account database record of the customer 2232. Under an anonymous framework, no customer-specific information need be provided.

[0158] Also under the personalized framework, the device 2204 is activated for use on each account when the customer 2232 sends a message digitally signed using the device 2204 in a respective EC 2222 to each Account Authority 2242,2244,2246, and when the digitally signed message is authenticated by the respective Account Authority 2242,2244,2246 using the public key associated with the respective PuK-linked account database record 2248.

[0159] Under the anonymous framework, each respective account established with an Account Authority 2242,2244,2246 is activated when the customer 2232 sends a message digitally signed using the device 2204 in a respective EC 2222 to each Account Authority 2242,2244,2246, and when the digitally signed message is authenticated by the respective Account Authority 2242,2244,2246 using the public key associated with the respective PuK-linked account database record 2248.

[0160] D. Insuring Transactions Based on Identified Security Characteristics of a Device That Generates Digital Signatures

[0161] The fourth aspect of the present invention includes the insuring of a transaction represented by an EC that is digitally signed. Furthermore, the insurance preferably is provided on a per transaction basis. For instance, a recipient represented for example by a financial institution that receives an EC instructing it to make a wire transfer of $250,000 out of an account of one of its customers, and that is authenticated, nevertheless may desire to insure that the EC is not fraudulent.

[0162] Reliable knowledge of security features of the device to which belongs the private key used to generate the digital signature of the EC conventionally has been lacking when such a transaction is insured. An entity insuring the transaction (“Insuring Entity”), which gauges the risk that the EC was fraudulently sent and which calculates the premium to be charged based on such risk, therefore would be forced to err on the high side in insuring such transaction.

[0163] Now, in view of the first aspect of the present invention, security features of the device to which belongs the private key used to generate the digital signature of the EC can be reliably identified. Moreover, the manufacturing history of the device also can be reliably identified at the same time. Accordingly, the risk that a particular digitally signed EC has been fraudulently sent can be gauged with greater accuracy, and it is believed that the premium charged for such insurance may be lowered based on this greater knowledge and the consequent reduced risk of the transaction. Additionally, this greater knowledge gives rise to a more targeted premium structure for insuring a plurality of transactions, wherein different rates are based, at least in part, on the varying identified security features of devices generating digital signatures.

[0164] A system in which preferred embodiments of this fourth aspect of the present invention are implemented is illustrated in FIG. 23, wherein a plurality of devices 2304 are manufactured at a secure manufacturing facility 2302 in a secure environment 2314 in accordance with the first aspect of the present invention. Each of the devices 2304 includes a private key retained therein for which a public key 2318 corresponding thereto is linked with a Security Profile 2320 thereof in a secure database 2310 maintained by a Secure Entity 2312. After manufacture, the devices 2304 are released from the secure environment 2314 into the world 2306, with one of the devices ultimately reaching a customer of a Financial Institution 2350 and becoming associated with an account of the customer maintained at the Financial Institution 2350.

[0165] In accordance with a first preferred embodiment of this fourth aspect of the present invention, and as illustrated in FIGS. 24-28, a digital signature is generated (Step 2502) for a message including a request for a wire transfer of $250,000 from the account of the customer maintained at the financial institution 2350. The digital signature is combined (Step 2504) with the message for the wire transfer to form an EC 2322 that is then sent (Step 2506) from somewhere in the world 2306 to the Financial Institution 2350. The EC 2322 preferably includes the number for the account from which the transfer is to be made.

[0166] Upon receipt (Step 2602) of the EC 2322, the Financial Institution 2350 authenticates (Step 2604) the message of the EC 2322 using the public key associated with the account identified in the EC 2322, and then determines whether to honor the instruction contained in the EC 2322 and, if so, whether to insure the transaction represented by the EC 2322. The determination of whether to honor the instruction preferably is based, at least in part, upon the security features and manufacturing history identified in accordance with the first aspect of the present invention.

[0167] Upon an affirmative determination to insure the transaction represented by the EC 2322, the Financial Institution 2350 forwards (Step 2606) the EC 2322 to the Insuring Entity 2352 together with the public key. Upon receipt (Step 2702), the Insuring Entity 2352 authenticates (Step 2704) the message of the EC 2322 with the public key to confirm authentication of the message and, upon successful authentication, the Insuring Entity 2352 sends (Step 2706) the public key to the Secure Entity 2312.

[0168] Upon receipt (Step 2804) of the public key, the Secure Entity 2312 compares (Step 2806) for a match the public key against the linked public keys maintained in the secure database 2310. If a match is found, then the Security Profile linked with the matching public key is retrieved (Step 2808) and, for the purpose of maintaining the integrity of the information during transit, digitally signed (also in Step 2808) by the Secure Entity 2312 to form a Security Certificate 2326. The Security Certificate 2326 then is sent (Step 2810) to the Insuring Entity 2352. Preferably, the matching public key is included in the Security Certificate 2326 for confirmation by the Insuring Entity 2352 of the public key to which the Security Certificate 2326 pertains. Upon receipt (Step 2708) of the Security Certificate 2326 by the Insuring Entity 2352, the authenticity of the Security Certificate 2326 is confirmed (also Step 2708) using a public key 2428 (SE PuK) of the Secure Entity 2321, which preferably is communicated (Step 2802) to the Insuring Entity 2352 beforehand. Subsequently, the Security Profile contained in the authenticated Security Certificate 2326 is identified by the Insuring Entity 2352 as the Security Profile of the manufactured device to which belongs the private key used in digitally signing the message of the EC 2322.

[0169] Based on the identified Security Profile, the Insuring Entity 2352 is able to gauge a risk that the private key of the manufactured device was fraudulently used in digitally signing the message of the EC 2322 and, in turn, the Insuring Entity 2352 is able to classify the transaction thereof for a corresponding premium rate. The corresponding premium rate for the particular classification of the transaction then is applied to the monetary value of the transaction for which insurance is sought (i.e., to the $250,000 in the present wire transfer example), and the actual premium to be charged for the particular transaction in question is calculated. Confirmation 2354 of insurance coverage then is sent (Step 2710) by the Insuring Entity 2352 to the Financial Institution 2350. The coverage confirmation 2354 preferably includes the identified Security Profile, applicable premium rate, and calculated premium to be charged to the Financial Institution 2350 for the particular transaction represented by the EC 2322. The coverage confirmation 2354 also is preferably digitally signed by the Insuring Entity 2352 to preserve the integrity of the coverage confirmation 2354 during transit. Upon receipt and authentication (Step 2608) of the coverage confirmation 2354, the Financial Institution 2350 makes (Step 2610) the requested wire transfer 2356.

[0170] As in the first preferred embodiment, in the second preferred embodiment of the fourth aspect of the present invention, a plurality of devices are manufactured at a secure manufacturing facility in a secure environment. Each of the devices includes a private key retained therein for which a public key corresponding thereto is linked with a Security Profile thereof in a secure database maintained by a Secure Entity. After manufacture, the devices are released from the secure environment into the world, with one of the devices ultimately reaching a customer of a Financial Institution and becoming associated with an account of the customer maintained at the Financial Institution.

[0171] Unlike the first preferred embodiment, and as illustrated in FIGS. 29-33, the second preferred embodiment differs from the first preferred embodiment of the fourth aspect of the present invention in that the Secure Entity 2912 creates and communicates a reference 2930 containing public keys and corresponding Security Profiles of manufactured devices to the Insuring Entity 2952, rather than sending a Security Certificate for a particular one of the manufactured devices as in the first preferred embodiment of FIGS. 24-28. Nor does the Insuring Entity 2952 send a public key to the Secure Entity 2912 for identifying a Security Profile from a secure database 2910.

[0172] With particular regard to the sequence of events, the Secure Entity 2912 generates (Step 3304) the reference 2930 containing public keys and linked security features for all of the devices associated with the accounts of the Financial Institution 2950, and then forwards (Step 3306) the reference 2930 to the Insuring Entity 2952. The information regarding which devices are associated with the accounts of the Financial Institution 2950 is known by the Secure Entity 2912 in the second and third aspects of the present invention and, alternatively, is identified to the Secure Entity 2912 by either the Financial Institution 2950 or by the insuring Entity 2952. The reference 2930 preferably is compiled in accordance with the first aspect of the present invention as illustrated in FIGS. 7-11, and preferably is digitally signed by the Secure Entity 2912 to preserve the integrity of the information therein during transit and storage. A public key 2928 of the Secure Entity 2912 is preferably communicated (Step 3302) in a secure manner to the Insuring Entity 2952 beforehand. Upon receipt thereof (Steps 3202 and 3204), the Insuring Entity 2952 authenticates (Step 3206) the reference 2930 with the public key 2928 of the Secure Entity 2912.

[0173] Thereafter, a digital signature is originated (Step 3002) for and combined (Step 3004) with a message that includes a wire transfer request for a particular account number maintained at the Financial Institution 2950 to form an EC 2922. The EC 2922 then is sent (Step 3006) to the Financial Institution 2950. Upon receipt (Step 3102) of the EC 2922, the Financial Institution 2950 authenticates (Step 3104) the message of the EC 2922 using the public key associated with the account identified in the EC 2922, and then determines whether to honor the instruction contained in the EC 2922 and, if so, whether to insure the transaction represented by the EC 2922. The determination of whether to honor the instruction preferably is based, at least in part, upon the security features and manufacturing history identified in accordance with the first aspect of the present invention.

[0174] Upon an affirmative determination to insure the transaction represented by the EC 2922, the Financial Institution 2950 forwards (Step 3106) the EC 2922 to the Insuring Entity 2952 together with the public key. Upon receipt (Step 3208) of the EC 2922, the Insuring Entity 2952 authenticates (Step 3210) the message of the EC 2922 with the public key to confirm authentication of the message and, upon successful authentication, the Insuring Entity 2952 compares for a match the public key against the linked public keys in the reference 2930 to identify (Step 3212) a matching public key and the Security Profile linked therewith. The Security Profile thereby identified represents the Security Profile of the manufactured device to which belongs the private key used in digitally signing the message of the EC 2922.

[0175] Based on the identified Security Profile, the Insuring Entity 2952 is able to gauge a risk that the private key of the manufactured device was fraudulently used in digitally signing the message of the EC 2922 and, in turn, the Insuring Entity 2952 is able to classify the transaction thereof for a corresponding premium rate. The corresponding premium rate for the particular classification of the transaction then is applied to the monetary value of the transaction for which insurance is sought (i.e., to the $250,000 in the present wire transfer example), and the actual premium to be charged for the particular transaction in question is calculated. Confirmation 2954 of insurance coverage is then sent (Step 3214) by the Insuring Entity 2952 to the Financial Institution 2950. The coverage confirmation 2954 preferably includes the identified Security Profile, applicable premium rate, and premium to be charged to the Financial Institution 2950 for the particular transaction of the EC 2922. The coverage confirmation 2954 also is preferably digitally signed by the Insuring Entity 2952 to preserve the integrity of the coverage confirmation 2954 during transit. Upon receipt and authentication (Step 3108) of the coverage confirmation 2954, the Financial Institution 2950 makes (Step 3110) the requested wire transfer 2956.

[0176] In a variation of this second preferred method of the fourth aspect of the present invention, as illustrated in FIGS. 34-38, a Secure Entity 3412 communicates a reference 3430 to a Financial Institution 3450 rather than to an Insuring Entity 3452. The reference 3430 then is forwarded to the Insuring Entity 3452 by the Financial Institution 3450. Otherwise, the steps are the same as those described with reference to the second method of the fourth aspect of the present invention illustrated in FIGS. 29-33.

[0177] In particular, the Secure Entity 3412 creates (Step 3802) the reference 3430 including the public keys and linked security features for all of the devices associated with the accounts of the Financial Institution 3450, and then sends (Step 3804) the reference 3430 to the Financial Institution 3450. Upon receipt (Step 3602), the Financial Institution 3450 sends (Step 3604) the reference 3430 to the Insuring Entity 3452 and, in turn, the Secure Entity 3412 sends (Step 3806) its public key 3428 to the Insuring Entity 3452 in a reliable manner. Upon receipt of the reference 3430 (Step 3702) and the public key 3428 of the Secure Entity 3412 (Step 3704), the Insuring Entity 3452 authenticates (Step 3706) the reference 3430.

[0178] Thereafter, a digital signature is originated (Step 3502) for and combined (Step 3504) with a message regarding the wire transfer to form an EC 3422. The EC 3422 is then sent (Step 3506) to the Financial Institution 3450. Upon receipt (Step 3606) of the EC 3422, the Financial Institution 3450 authenticates (Step 3608) the message of the EC 3422 using the public key associated with the account identified in the EC 3422 from which the transfer is to be made, and then determines whether to honor the instruction contained in the EC 3422 and, if so, whether to insure the transaction represented by the EC 3422. The determination of whether to honor the instruction preferably is based, at least in part, upon the security features and manufacturing history identified in accordance with the first aspect of the present invention.

[0179] Upon an affirmative determination to insure the transaction represented by the EC 3422, the Financial Institution 3450 forwards (Step 3610) the EC 3422 to the Insuring Entity 3452 together with the public key. Upon receipt (Step 3708) of the EC 3422, the Insuring Entity 3452 authenticates (Step 3710) the message of the EC 3422 with the public key to confirm authentication of the message and, upon successful authentication, the Insuring Entity 3452 compares for a match the public key against the linked public keys in the reference 3430 to identify (Step 3712) a matching public key and the Security Profile linked therewith. The Security Profile thereby identified represents the Security Profile of the manufactured device to which belongs the private key used in digitally signing the message of the EC 3422.

[0180] Based on the identified Security Profile, the Insuring Entity 3452 is able to gauge a risk that the private key of the manufactured device was fraudulently used in digitally signing the message of the EC 3422 and, in turn, the Insuring Entity 3452 is able to classify the transaction thereof for a corresponding premium rate. The corresponding premium rate for the classification of the transaction then is applied to the monetary value of the transaction for which insurance is sought (i.e., to the $250,000 in the present wire transfer example), and the actual premium to be charged for the particular transaction at question is calculated. Confirmation 3454 of insurance coverage then is sent (Step 3714) by the Insuring Entity 3452 to the Financial Institution 3450. The coverage confirmation 3454 preferably includes the identified Security Profile, applicable premium rate, and premium to be charged to the Financial Institution 3450 for the particular transaction of the EC 3422. The coverage confirmation 3454 also is preferably digitally signed by the Insuring Entity 3452 to preserve the integrity of the coverage confirmation 3454 during transit. Upon receipt and authentication (Step 3612) of the coverage confirmation 3454, the Financial Institution 3450 makes (Step 3614) the requested wire transfer 3456.

[0181] In a third preferred method of the fourth aspect of the present invention, a Security Certificate is incorporated into the manufactured device itself prior to the release of the device from the secure environment in accordance with the third preferred embodiment of the first aspect of the present invention. Accordingly, as illustrated in FIGS. 39-43, when a suspect device originates (Step 4002) a digital signature somewhere in the world 3906, the Security Certificate is included (Step 4004) with the digital signature and message in an EC 3922, which then is sent (Step 4006) to a Financial Institution 3950. Upon receipt (Step 4102) of the EC 3922 by the Financial Institution 3950, the public key identified in the Security Certificate is used to authenticate (Step 4104) the message. Thereafter, if insurance is desired for the transaction, the Financial Institution 3950 forwards (Step 4106) the EC 3922 to the Insuring Entity 3952. The determination of whether to honor the instruction preferably is based, at least in part, upon the security features and manufacturing history identified in the Security Certificate in accordance with the first aspect of the present invention.

[0182] Upon receipt (Step 4204), the Insuring Entity 3952 authenticates (Step 4206) the message with the public key set forth in the Security Certificate to confirm authentication of the message. The Insuring Entity 3952 also authenticates (Step 4208) the Security Certificate with the public key 3928 of the Secure Entity 3912, which preferably is communicated (Step 4302) by the Secure Entity 3912 and received (Step 4202) by the Insuring Entity 3952 beforehand. The Security Profile of the manufactured device to which properly belongs the private key used in generating the digital signature for the message of the EC 3922 thereby is identified to the Insuring Entity 3952.

[0183] Based on the identified Security Profile, the Insuring Entity 3952 is able to gauge a risk that the private key of the manufactured device was fraudulently used in digitally signing the message of the EC 3922 and, in turn, the Insuring Entity 3952 is able to classify the transaction thereof for a corresponding premium rate. The corresponding premium rate for the classification of the transaction then is applied to the monetary value of the transaction for which insurance is sought (i.e., to the $250,000 in the present wire transfer example), and the actual premium to be charged for the particular transaction at question is calculated. Confirmation 3954 of insurance coverage then is sent (Step 3714) by the Insuring Entity 3952 to the Financial Institution 3950. The coverage confirmation 3954 preferably includes the identified Security Profile, applicable premium rate, and premium to be charged to the Financial Institution 3950 for the particular transaction of the EC 3922. The coverage confirmation 3954 also is preferably digitally signed by the Insuring Entity 3952 to preserve the integrity of the coverage confirmation 3954 during transit. Upon receipt and authentication (Step 3612) of the coverage confirmation 3954, the Financial Institution 3950 makes (Step 3614) the requested wire transfer 3956.

[0184] Under any of the preferred methods of the fourth aspect of the present invention, the actual billing of the premium by an insuring entity to a Financial Institution preferably is performed on a regularly scheduled period, such as monthly. Furthermore, the premium rates for each transaction classification preferably are determined in accordance with a prearranged insurance contract entered into between the Financial Institution and Insuring Entity. In this regard, the greater the security level met by a device at the time of the transaction, the lower the premium rate should be. Furthermore, the coverage confirmations of all insured transactions for a time period received by the Financial Institution readily may be utilized by the Financial Institution to keep a running tab on the amount of the premium to be billed by the Insuring Entity for such time period.

[0185] Preferably, the steps set forth above with regard to FIGS. 26-28; FIGS. 31-33; FIGS. 36-38; and FIGS. 41-43 are computer automated, and the entire sequence of steps for each respective group of figures occurs within a small time interval on the order of magnitude of at least minutes, if not seconds.

[0186] As opposed to insurance provided on a per transaction basis, insurance also may be provided on a per device basis, possibly subject to certain limits. In this case, each EC would not be sent to the Insuring Entity as in the preferred methods in which insurance is provided on a per transaction basis. Rather, under this scenario insurance preferably is provided to an Account Authority (such as a financial institution) for transactions of the Account Authority's customers who send digitally signed messages. In accordance with the fourth aspect of the present invention, each message is digitally signed with a retained private key of a device manufactured in accordance with the first aspect of the present invention, i.e., a manufactured device for which information preferably such as the Security Profile reliably is identified. For example, a financial institution that maintains a PuK-linked account database of its customers that is established under either of the second or third aspects of the present invention, and which includes the identified Security Profiles in the PuK-linked account database records, may obtain insurance for all devices of its customers in accordance with the fourth aspect of the present invention. The insurance is provided for each device at a premium that is based, at least in part, on the identified Security Profile of the device to which the device's public key is linked. The ability reliably to know the Security Profile of each device as provided by the first aspect of the present invention permits differentiation in premiums charged as between the devices to reflect the different levels of risk that may be associated with the devices.

[0187] E. Gauging Whether EC on Account is Fraudulent Based on PuK-Linked Information of Device Generating Digital Signatures

[0188] A fifth aspect of the present invention includes gauging the risk of whether a message of an EC representing a transaction on an account and digitally signed with a device is fraudulent and, based thereon, determining whether to perform the transaction. Gauging of the risk is based on identified information that was securely linked with a public key of the device at the time of its manufacture, including the security features and manufacturing history of the device, and preferably incorporates the first aspect of the present invention. Gauging of the risk also is based on additional factors, including the transactional account history of digital signatures authenticated using the public key, the environment in which the digital signature for the EC was originated, and other account or business-specific factors, such as whether the transaction is even capable of being performed on the account.

[0189] An example of an account database maintained by an Account Authority for a plurality of user accounts in accordance with the fifth aspect of the present invention is illustrated in FIG. 44. This account database corresponds with that of FIG. 21 with “Transactional History” and “PuK-to-Account Authentication” information for each account being added to the account records in conjunction with the Security Profile to form “Risk Management Information.” The security features and manufacturing history of the device, as well as the public key linked therewith, are associated with the account and may be obtained by an Account Authority as set forth above with respect to the first, second, or third aspects of the present invention, or through any other process considered trustworthy by the Account Authority.

[0190] The transactional account history is recorded on the account by the Account Authority, preferably as digitally signed ECs are received. In particular, the Account Authority records the transaction details of each EC in a record of the account. The transactional history may include such factors as the geographic locations of use, amounts of transaction, and frequency of transactions, all of which may be tracked and evaluated by the Account Authority in monitoring for possible fraud. Information such as the number of incorrect entries of data representing a Secret or biometric characteristic used to authenticate a user of the device also may be monitored by the Account Authority, which also may serve to indicate possible fraud.

[0191] The PuK-to-Account Authentication is the authentication technique employed when the public key and PuK-linked information were associated with the account maintained by the Account Authority. This information is important in evaluating the risk to be accorded the initial association of the public key and PuK-linked information with the account.

[0192] Also in accordance with the fifth aspect of the present invention, the Account Authority notes any factors known about the environment in which the digital signature for the message was originated. Indeed, the environment in which the device is used often is communicated within the EC itself. For example, in financial transactions involving credit charges, an Account Authority—such as an issuing bank—is able to determine whether a card was present at a point of sale for a transaction, or whether the charge occurred otherwise, such as over the Internet. The former scenario is believed to involve a risk of fraud that is substantially less than that of the later scenario. In another example, when an external apparatus such as an I/O support element is used in conjunction with a device to compose a message and originate a digital signature, information regarding the I/O support element is preferably included in the environmental information communicated in the EC. For instance, an I/O support element also may digitally sign an EC, and information regarding the I/O support element linked to the public key of the I/O support element preferably is identified in accordance with the first aspect of the present invention. Indeed, the device may include a card reader comprising hardware and software components designed in accordance with the technical specifications published by CEN/ISSS as a result of the well-known Financial Transactional IC Card Reader Project (known commonly as “FINREAD”).

[0193] A preferred embodiment in accordance with this aspect of the present invention is illustrated in FIG. 45, wherein an Account Authority receives (Step 4502) an EC including a message and a digital signature therefor. The digitally signed message includes an instruction therein representing a transaction on a particular account as identified in the EC by a unique account number. Upon receipt, the Account Authority retrieves (Step 4504) a public key associated with the particular account and then attempts to authenticate (Step 4506) the message of the EC using the public key. If the message does not authenticate in Step 4508, then the Account Authority rejects (Step 4510) the message. If the message authenticates in Step 4508, then the Account Authority further processes (Step 4512) the message.

[0194] Further processing (Step 4512) of the message includes consideration (Step 4514) of numerous factors that are used by the Account Authority to gauge the risk that the digital signature was fraudulently generated and, ultimately, to determine whether to perform the transaction on the account. The consideration (Step 4514) includes an evaluation (Step 4516) of the security features and manufacturing history of the device linked with the public key of the device within the environment of the manufacturing of the device and, as applicable: an evaluation (Step 4518) of entity authentication provided by the sender of the EC or user of the device; an evaluation (Step 4520) of environmental factors surrounding the origination of the EC; an evaluation (Step 4522) of the transactional history of the device on the account; and an evaluation (Step 4524) of other account or business-specific factors. At a more fundamental level, the PuK-to-Account Authentication also may be considered in gauging the risk of fraud.

[0195] Whether the Account Authority considers some or all of the above factors, how much weight the Account Authority applies to any particular factor, and what order the Account Authority makes these evaluations may vary; and the Account Authority uses its own business rules and judgment to determine (Step 4526), based on its own considerations in Step 4514, whether to perform the transaction on the account. If the determination in Step 4526 is negative, then the Account Authority rejects (Step 4510) the message. If the determination in Step 4526 is positive, then the Account Authority performs (Step 4528) the transaction on the account and updates (Step 4530) the account record accordingly. Alternatively, the Account Authority may choose to execute only a limited portion of the instruction (not shown) based on its considerations (Step 4514), or the Account Authority may require additional information from the sender of the EC prior to performing the transaction (not shown).

[0196] In a feature of the present invention, a plurality of different devices are associated with the same user account maintained with the Account Authority. In this situation, the risk of a fraudulent transaction preferably is gauged not on an overall account basis, but rather, on a device-by-device basis for each account. Specifically, the transactional history of digital signatures on the account preferably is recorded and later considered on a device-by-device basis.

[0197] Of course, the actual rule base or business logic used by each Account Authority is subjective and necessarily will vary as between Account Authorities. Nevertheless, the reliable identification of the security features and manufacturing history of a device—when combined with evaluations of the transactional account history of digital signatures generated by the device, environmental factors in which the digital signature is originated, and other account or business-specific factors—provides added security against fraudulent transactions not otherwise realized.

[0198] F. Disseminating PuK-Linked Information of Device Generating Digital Signatures

[0199] In accordance with a sixth aspect of the present invention, an entity (herein “Central Key Authority”) maintains certain PuK-linked account information of a user (herein “Registration Information”) for disseminating to one or more Account Authorities. The Registration Information includes the public key (PuK) of a device of the user that generates digital signatures and one or more of the following types of information: the identity of Account Authorities with which the user has PuK-linked accounts for the device and respective account identifiers that identify each PuK-linked account of the user to the respective Account Authority; information linked with the public key of the device in accordance with the first aspect of the present invention; user-specific information, such as the user's mailing address, credit card information, age, etc.; and, as desired, the authentication techniques that were employed in verifying the user-specific information maintained by the Central Key Authority. Furthermore, the Central Key Authority preferably indexes the Registration Information of the user to a unique account identifier such that the Registration Information may be retrieved based on the account identifier. In this regard, but not shown, the public key may serve as the unique account identifier. An example of a PuK-linked account database 4640 of a Central Key Authority is illustrated in FIG. 46.

[0200] In accordance with this aspect of the present invention, the Central Key Authority disseminates some or all of the Registration Information, as appropriate, to Account Authorities. Registration Information is disseminated when the user has an account with an Account Authority—or desires to establish an account with an Account Authority—and desires to send ECs with messages each containing an instruction that represents a transaction on the account, each such message being digitally signed using the device. The dissemination of the Registration Information occurs, for example, when Registration Information maintained by an Account Authority has become outdated for a particular account. Furthermore, the dissemination of the Registration Information may be in accordance with the third aspect of the present invention wherein the PuK-linked account database record is obtained from the Central Key Authority if the Central Key Authority is considered to have sufficient security measures and protocols so as to qualify to be a Secure Entity.

[0201] The Registration Information maintained by the Central Key Authority is obtained in various ways. For example, the public key and information linked therewith preferably is obtained from a Secure Entity in accordance with the first, second, or third aspects of the present invention. The identity of the Account Authorities with which the user has PuK-linked accounts for the device, and the account identifier that identifies the PuK-linked account of the user to each such Account Authority, preferably is obtained from the user, and is obtained when the user registers with the Central Key Authority; when, at the instruction of the user, the Central Key Authority establishes an account on behalf of the user with an Account Authority; or when the third-party, at the instruction of the user, acquires Registration Information from the Central Key Authority.

[0202] An example of efficiency and convenience that may be provided by the Central Key Authority in accordance with this sixth aspect of the present invention comprises the updating of PuK-linked accounts of a user with a new device of the user in place of the user's old (and possibly outdated) device as represented by the respective public keys of the devices. With reference to FIGS. 47-51, such an update preferably is accomplished by a user 4758 by the mere sending (Step 4806) of an EC 4722 to a Central Key Authority 4760 with which the user 4758 has previously registered with an old device as represented by the old public key (PuK1).

[0203] The EC 4722 includes a message (M) having an instruction to associate a new public key (PuK2) included in the message with accounts of the user 4758 maintained by certain Account Authorities 4762,4764, which preferably are on register with the Central Key Authority 4760. The message is digitally signed (Step 4802) using the private key (PrK1), and the digital signature (DS) therefor is included (Step 4804) with the message in the EC 4722. The EC 4722 also includes the account identifier (CKA#) for the account maintained by the Central Key Authority 4760.

[0204] Upon receipt (Step 4902) of the EC 4722, the Central Key Authority 4760 authenticates (Step 4904) the message (M) of the EC 4722 using the public key (PuK1) associated with the account of the user 4758 maintained by the Central Key Authority 4760 as identified by the unique account identifier (CKA#).

[0205] Upon successful authentication, the Central Key Authority 4760 updates (Step 4906) the Registration Information with the new public key (PuK2) and sends (Step 4908) a respective EC 4766,4768 to each of the Account Authorities 4762,4764 identified by the user 4758. Each EC 4762,4764 includes a respective request of the Account Authorities 4762,4764 to associate the new public key (PuK2) with the accounts of the user 4758. The Central Key Authority 4760 also preferably obtains the Security Profile linked with the new public key (PuK2) in accordance with the first aspect of the present invention, and includes the Security Profile with the new public key (PuK2) in the respective request sent to the Account Authorities 4762,4764.

[0206] The request preferably is digitally signed (Step 4908) using a private key of the Central Key Authority 4760 for authentication of the request and information therein by each Account Authority 4762,4764, and may include the original EC 4722 received by the Central Key Authority 4760 from the user 4758. Each respective request also preferably includes the appropriate account identifier for the account that is to be updated by each Account Authority 4762,4764, which information is part of the Registration Information maintained by the Central Key Authority 4760.

[0207] Upon receipt (Step 5002) of the EC 4766 by Account Authority 4762, the request (R1) is authenticated (Step 5004) using a public key of the Central Key Authority 4760, which preferably is obtained by the Account Authority 4762 beforehand. The Account Authority 4762 also may authenticate the original message (M) in EC 4722, as desired. Upon successful authentication, the Account Authority 4762 updates (Step 5006) the account identified by the account identifier (Acc#) in the EC 4766 by associating the new public key (PuK2) with the account.

[0208] Similarly, upon receipt (Step 5102) of the EC 4768 by Account Authority 4764, the request (R2) is authenticated (Step 5104) using the public key of the Central Key Authority 4760, which preferably is obtained by the Account Authority 4764 beforehand. The Account Authority 4764 also may authenticate the original message (M) in EC 4722, as desired. Upon successful authentication, the Account Authority 4764 updates (Step 5106) the account identified by the account identifier (Acc#) in the EC 4768 by associating the new public key (PuK2) with the account.

[0209] As will be appreciated by those having ordinary skill in the art, while two Account Authorities have been illustrated in the preferred method of FIGS. 47-51, any number of Account Authorities may be sent a respective EC by the Central Key Authority as appropriate and desired. Indeed, the more Account Authorities that are contacted, the more efficient and convenient the preferred method in accordance with the sixth aspect of the present invention.

[0210] Accordingly, it readily will be understood by those persons skilled in the art that, in view of the above detailed description of preferred embodiments, devices, and methods of the present invention, the present invention is susceptible of broad utility and application. Many methods, embodiments, and adaptations of the present invention other than those herein described, as well as many variations, modifications, and equivalent arrangements, will be apparent from or reasonably suggested by the present invention and the following detailed description thereof, without departing from the substance or scope of the present invention. Furthermore, those of ordinary skill in the art will understand and appreciate that although steps of various processes may be shown and described in some instances as being carried out in a preferred sequence or temporal order, the steps of such processes are not necessarily to be limited to being carried out in such particular sequence or order. Rather, in many instances the steps of processes described herein may be carried out in various different sequences and orders, while still falling within the scope of the present invention. Accordingly, while the present invention is described herein in detail in relation to preferred methods and devices, it is to be understood that this detailed description only is illustrative and exemplary of the present invention and is made merely for purposes of providing a full and enabling disclosure of the invention. The detailed description set forth herein is not intended nor is to be construed to limit the present invention or otherwise to exclude any such other embodiments, adaptations, variations, modifications and equivalent arrangements of the present invention, the present invention being limited solely by the claims appended hereto and the equivalents thereof.

[0211] For instance, the roles set forth above with respect to the Secure Manufacturing Facility, the Secure Entity, the Account Authority, the Financial Institution, the Insuring Entity, and the Central Key Authority, may all be performed by a single entity or affiliated entities, or any combination thereof, in accordance with the present invention. Moreover, any of the aforementioned entities also may be a recipient of an EC.

[0212] Additionally, it should be apparent that the devices described above with regard to the present invention encompass, for example, devices of merchants and other commercial entities that generate digital signatures, and are not limited to devices of individual consumers that generate digital signatures. For instance, a device in accordance with the present invention includes an I/O support element comprising, for example, an IC card reader used to read IC cards of individual consumers in establishing secure financial transactions if such IC card reader itself generates digital signatures. In this regard, such device may include a trusted platform module.

Claims

1. A method in which information of a device that generates digital signatures is reliably identified, comprising the steps of,

(a) for each of a plurality of devices manufactured in a secure manufacturing environment,

(i) creating, within the secure manufacturing environment, a public-private key pair,

(ii) linking, within the secure manufacturing environment, the public key with other information associated with the device, wherein the other information comprises at least one of security features and manufacturing history of the device and wherein the other information defines a relative security level of the device, and

(iii) before release of the device from the secure manufacturing environment, storing the private key within the device for utilization in generating a digital signature for an electronic message,

(b) recording the linked public key and other information in a database and maintaining the database in a secure environment having a security rating at least comparable to the security level of the device for which the public key thereof is linked,

(c) thereafter, when a public key linked in step (a)(ii) successfully authenticates a digitally signed message outside of the secure manufacturing environment, identifying from the database the other information to which the public key was linked in step (a)(ii) as pertaining to the device to which belongs the private key utilized in digitally signing the message without use of a digital certificate.

2. The method of claim 1, wherein the other information is identified by a recipient of the digitally signed message.

3. The method of claim 1, wherein the other information is identified to a recipient of the digitally signed message.

4. The method of claim 1, further comprising gauging a risk that the private key was fraudulently used to digitally sign the message based at least in part on said identified other information of step (b).

5. The method of claim 1, wherein, for each device, the other information comprises security characteristics of the device.

6. The method of claim 5, wherein the security characteristics of a respective manufactured device include an algorithm used by the device in originating digital signatures.

7. The method of claim 1, wherein, for each device, the other information comprises authentication capabilities of the device.

8. The method of claim 7, wherein the authentication capabilities include whether the device performs authentication based on a Secret and authentication based on a biometric characteristic.

9. The method of claim 1, wherein, for each device, the other information comprises all of the security features of the device.

10. The method of claim 1, wherein the secure environment includes multiple physical locations.

11. The method of claim 1, wherein the electronic message represents a financial transaction.

12. The method of claim 1, wherein the electronic message represents a legal action.

13. The method of claim 1, wherein the electronic message represents a request for access to information.

14. The method of claim 1, wherein the electronic message represents a request for access to a physical location.

15. The method of claim 1, wherein, for each of the plurality of manufactured devices, the public-private key pair is generated within each respective device.

16. The method of claim 15, wherein only the public key of each pair is exportable from the respective device.

17. The method of claim 15, wherein the private key is not exportable from the respective device.

18. A method of manufacturing devices that generate digital signatures such that each device may be reliably and uniquely identified without use of a digital certificate, the devices being manufactured within a secure manufacturing environment, comprising the steps of, for each respective device:

(a) creating, within the secure manufacturing environment, a public-private key pair,

(b) before release of the device from the secure manufacturing environment, storing the private key within the device for utilization in generating a digital signature for an electronic message, the private key being stored within the device against the possibility of divulgement thereof by the device,

(c) securely linking, within the secure manufacturing environment, the public key with other information, wherein the other information comprises at least one of security features and manufacturing history of the device and wherein the other information defines a relative security level of the device, and

(d) recording the linked public key and other information in a database and maintaining the database in a secure environment having a security rating at least comparable to the security level of the device for which the public key thereof is linked.

19. The method of claim 18, wherein the public-private key pair is created within the device based on a random number produced by a random number generator disposed within the device.

20. The method of claim 19, wherein the random number generator is a high quality random number generator.

21. The method of claim 19, wherein only the public key is exportable from the device.

22. The method of claim 19, wherein each digital signature generated by each device is a random number.

23. The method of claim 18, wherein the other information comprises security characteristics of the device.

24. The method of claim 18, further comprising identifying a particular manufactured device by authenticating a message using one of said linked public keys, a digital signature for the message having been generated by the particular manufactured device.

25. A method in which information of a device that generates digital signatures is reliably identified, comprising the steps of:

(a) for each of a plurality of devices manufactured in a secure manufacturing environment, before release of the device from the secure manufacturing environment:

(i) creating a public-private key pair;

(ii) storing the private key within the device for utilization in generating digital signatures for electronic messages; and

(iii) linking the public key with other information associated with the device, wherein the other information defines a relative security level of the device;

(b) for each of the plurality of devices manufactured in the secure manufacturing environment:

(i) originating a digital signature for a reference, the reference including the public key and the other information of the device, the digital signature for the reference generated by a private key of a Secure Entity;

(ii) publishing the reference and digital signature therefor, and;

(iii) maintaining the private key of the Secure Entity in a secure environment outside of the device, wherein the secure environment has a security rating that is at least comparable to the security level of the device to which the reference pertains; and

(c) thereafter, when a public key linked in step (a)(iii) successfully authenticates a digitally signed message, identifying the other information to which the public key was linked in step (a)(iii) as pertaining to the device to which belongs the private key utilized in digitally signing the message based on a successful authentication of the reference.

26. The method of claim 25 wherein the other information comprises at least one of security features and manufacturing history of the device.

27. The method of claim 25 wherein the Secure Entity is the manufacturer of the device.

28. The method of claim 25 wherein the Secure Entity is not the manufacturer of the device.

29. The method of claim 25, wherein the secure environment includes multiple physical locations.

Patent Citations (125)

Patent	Date	Inventor	Cited By
US3962539(A)	1976-06-01	Ehrsam et al.	Applicant
US4200770(A)	1980-04-01	Hellman et al.	Applicant
US4218582(A)	1980-08-01	Hellman et al.	Applicant
US4405829(A)	1983-09-01	Rivest et al.	Applicant
US4408203(A)	1983-10-01	Campbell	Applicant
US4424414(A)	1984-01-01	Hellman et al.	Applicant
US4734564(A)	1988-03-01	Boston et al.	Applicant
US4748668(A)	1988-05-01	Shamir et al.	Applicant
US4797920(A)	1989-01-01	Stein	Applicant
US4823388(A)	1989-04-01	Mizutani	Applicant
US4825050(A)	1989-04-01	Griffith	Applicant
US4850017(A)	1989-07-01	Matyas	Applicant
US4868877(A)	1989-09-01	Fischer	Applicant
US4885788(A)	1989-12-01	Takaragi et al.	Applicant
US5018196(A)	1991-05-01	Takaragi et al.	Applicant
US5029208(A)	1991-07-01	Tanaka	Examiner
US5097504(A)	1992-03-01	Camion et al.	Applicant
US5140634(A)	1992-08-01	Guillou	Applicant
US5214703(A)	1993-05-01	Massey	Applicant
US5225978(A)	1993-07-01	Petersen et al.	Applicant
US5231668(A)	1993-07-01	Kravitz	Applicant
US5422953(A)	1995-06-01	Fischer	Examiner
US5453601(A)	1995-09-01	Rosen	Applicant
US5455865(A)	1995-10-01	Perlman	Applicant
US5502766(A)	1996-03-01	Boebert et al.	Examiner
US5509071(A)	1996-04-01	Petrie Jr.	Applicant
US5534855(A)	1996-07-01	Shockley et al.	Applicant
US5539828(A)	1996-07-01	Davis	Applicant
US5557518(A)	1996-09-01	Rosen	Applicant
US5563946(A)	1996-10-01	Cooper et al.	Applicant
US5577120(A)	1996-11-01	Penzias	Applicant
US5586036(A)	1996-12-01	Pintsov	Applicant
US5590197(A)	1996-12-01	Chen et al.	Applicant
US5604801(A)	1997-02-01	Dolan et al.	Applicant
US5606609(A)	1997-02-01	Houser	Applicant
US5615266(A)	1997-03-01	Altschuler	Applicant
US5623637(A)	1997-04-01	Jones et al.	Applicant
US5625690(A)	1997-04-01	Michel et al.	Applicant
US5636280(A)	1997-06-01	Kelly	Applicant
US5659616(A)	1997-08-01	Sudia	Applicant
US5671258(A)	1997-09-01	Newman	Applicant
US5671279(A)	1997-09-01	Elgamal	Applicant
US5677953(A)	1997-10-01	Dolphin	Applicant
US5677955(A)	1997-10-01	Doggett et al.	Applicant
US5694471(A)	1997-12-01	Chen et al.	Applicant
US5708780(A)	1998-01-01	Levergood	Applicant
US5715314(A)	1998-02-01	Payne	Applicant
US5721779(A)	1998-02-01	Funk	Applicant
US5724424(A)	1998-03-01	Gifford	Applicant
US5745886(A)	1998-04-01	Rosen	Applicant
US5751813(A)	1998-05-01	Dorenbos	Applicant
US5778072(A)	1998-07-01	Samar	Applicant
US5817723(A)	1998-07-01	Yee	Applicant
US5790677(A)	1998-08-01	Fox et al.	Applicant
US5796840(A)	1998-08-01	Davis	Applicant
US5812666(A)	1998-09-01	Baker et al.	Applicant
US5825884(A)	1998-10-01	Zdepski et al.	Examiner
US5848161(A)	1998-12-01	Luneau et al.	Applicant
US5862327(A)	1999-01-01	Kwang et al.	Applicant
US5870475(A)	1999-02-01	Allan et al.	Examiner
US5878142(A)	1999-03-01	Caputo	Applicant
US5883810(A)	1999-03-01	Franklin et al.	Examiner
US5887131(A)	1999-03-01	Angelo	Applicant
US5903882(A)	1999-05-01	Asay	Applicant
US5910988(A)	1999-06-01	Ballard	Applicant
US5910989(A)	1999-06-01	Naccache	Applicant
US5919574(A)	1999-07-01	Hoagland	Applicant
US5928298(A)	1999-07-01	Matsuoka et al.	Applicant
US5943423(A)	1999-08-01	Muftic	Applicant
US5949881(A)	1999-09-01	Davis	Applicant
US5956404(A)	1999-09-01	Schneier et al.	Applicant
US5963648(A)	1999-10-01	Rosen	Applicant
US5970147(A)	1999-10-01	Davis	Applicant
US6000522(A)	1999-12-01	Johnson	Applicant
US6000832(A)	1999-12-01	Franklin	Applicant
US6009177(A)	1999-12-01	Sudia	Applicant
US6021202(A)	2000-02-01	Anderson et al.	Examiner
US6023509(A)	2000-02-01	Herbert et al.	Applicant
US6029150(A)	2000-02-01	Kravitz	Applicant
US6044154(A)	2000-03-01	Kelly	Applicant
US6061794(A)	2000-05-01	Angelo et al.	Examiner
US6061799(A)	2000-05-01	Eldridge et al.	Examiner
US6070154(A)	2000-05-01	Tavor et al.	Applicant
US6084969(A)	2000-07-01	Wright	Applicant
US6092202(A)	2000-07-01	Veil et al.	Applicant
US6102287(A)	2000-08-01	Matyas	Applicant
US6104815(A)	2000-08-01	Alcorn et al.	Applicant
US6105012(A)	2000-08-01	Chang	Applicant
US6108644(A)	2000-08-01	Goldschlag	Applicant
US6111956(A)	2000-08-01	Field	Applicant
US6134325(A)	2000-10-01	Vanstone	Applicant
US6144949(A)	2000-11-01	Harris	Applicant
US6154543(A)	2000-11-01	Baltzley	Applicant
US6161180(A)	2000-12-01	Matyas et al.	Applicant
US6161181(A)	2000-12-01	Haynes et al.	Applicant
US6167518(A)	2000-12-01	Padgett et al.	Applicant
US6189096(B1)	2001-02-01	Haverty	Applicant
US6192130(B1)	2001-02-01	Otway	Applicant
US6192405(B1)	2001-02-01	Bunnell	Applicant
US6199052(B1)	2001-03-01	Mitty et al.	Applicant
US6202151(B1)	2001-03-01	Musgrave	Applicant
US6205437(B1)	2001-03-01	Gifford	Applicant
US6213391(B1)	2001-04-01	Lewis	Examiner
US6230269(B1)	2001-05-01	Spies	Applicant
US6233565(B1)	2001-05-01	Lewis et al.	Applicant
US6240091(B1)	2001-05-01	Ginzboorg	Applicant
US6243812(B1)	2001-06-01	Matyas et al.	Applicant
US6253027(B1)	2001-06-01	Weber et al.	Examiner
US6263447(B1)	2001-07-01	French	Applicant
US6279112(B1)	2001-08-01	O'Toole, Jr. et al.	Applicant
US6282522(B1)	2001-08-01	Davis et al.	Applicant
US6285991(B1)	2001-09-01	Powar	Applicant
US6299062(B1)	2001-10-01	Hwang	Applicant
US6314519(B1)	2001-11-01	Davis et al.	Applicant
US6324525(B1)	2001-11-01	Kramer et al.	Applicant
US6373950(B1)	2002-04-01	Rowney	Applicant
US6510516(B1)	2003-01-01	Benson et al.	Examiner
US6523067(B2)	2003-02-01	Mi et al.	Examiner
US6532451(B1)	2003-03-01	Schell et al.	Examiner
US6565000(B2)	2003-05-01	Sehr	Examiner
US6571339(B1)	2003-05-01	Danneels et al.	Examiner
US6587837(B1)	2003-07-01	Spagna et al.	Examiner
US2001/0000535(A1)	2001-04-01	Lapsely et al.	Applicant
US2002/0120846(A1)	2002-08-01	Stewart	Applicant
CA2271178	1999-07-01		Applicant

Non-Patent Literature (84)

PKCS #9, Selected Object Classes and Attribute Types Version 2.0, RSA Laboratories, Redwood City, CA, pp 1-42.Applicant
Digital Signature Guidelines Tutorial ; ABA Network, (web site at http://www.abanet.org/scietech/ec/isc/dsg-tutorial.html), date of capture Feb. 18, 2003, pp 1-7.Applicant
Gerck, Ed, Overview of Certication Ssytems: x.509, PKIX, CA, PCP & SKIP—Do you understand digital certificates? Do you know what they warrant? Jul. 18, 2000; pp. 1-18.Applicant
Linn, John, Trust Models and Management in Public-Key Infrastructures; RSA Laboratories, Nov. 6, 2000, pp 1-13.Applicant
PKCS #5, v2.0: Password-Based Cryptography Standard, RSA Laboratories, Redwood City, CA; Mar. 25, 1999; pp 1-30.Applicant
PKCS #9, v2.0: Selected Object Classes and Attribute Types, RSA Laboratories, Redwood City, CA; Feb. 25, 2000; pp. 1-34.Applicant
PKCS #10, v1.7: Certificate Request Syntax Standard, RSA Laboratories, Redwood City, CA; May 26, 2000; pp. 1-10.Applicant
PCKS #12, V1.0: Personal Information Excahnge Syntax, RSA Laboratories, Redwood City, CA; Jun. 24, 1999; pp. 1-23.Applicant
PCKS #15: Conformance Profile Specification; RSA Laboratories, Redwood City, CA; Aug. 1, 2000; pp 1-8.Applicant
Pepe, Michel; Smart Cards Gaining Traction; CRN.com—Point of Sale: Trends, Markets and Technologies; Dec. 31, 2002, (web site at http://crn.channelsupersearch.com/news/crn/39163.asp) captured on Feb. 18, 2003; pp. 1-2.Applicant
Guide to Internet Security; Public Key Cryptography (web ite at http://www.e-certify.com/library/pkc_guide.htm) captured on Feb. 18, 2003.Applicant
Private Server Product Description; (web site at http://www.bnn.com.tr/assets/cserver_prodesc.html), date of capture Feb. 18, 2003; pp 1-11.Applicant
Cylink atm encryptor (web site at http://securitytools.hypermart.net/security_1/cylink_atm_encryptor.html), date of capture Feb. 18, 2003, p. 1.Applicant
BAL's PGP Public Key Server; The Computer Law Resource 1996; (web site at http://www.complaw.com/pgp/webkeyserver.html) date of capture Feb. 18, 2003; pp 1-2.Applicant
Baltimore; Solutions; A New Era in Secure and Trusted E-Business; (web site at http://www.baltimore.com/solutions/index.asp) date of capture Feb. 18, 2003; p 1Applicant
(PGP) Pretty Good Privacy; What's? com; Dec. 27, 2000; (web site at http://whatis.techtarget.com/WhatIs_Definition_Page/0,4152,214292,00.html) date of capture Dec. 27, 2000; pp 1-3.Applicant
An Introduction to Cryptography; Network Associates, Inc. PGP, Version 6.5.1; Jun. 1999, pp. 1-88.Applicant
Turnbill, Jim; “Cross-Certification and PKI Policy Networking”; Entrust, Inc; Aug. 2000; pp 1-10.Applicant
Some Suggestions for Automatic Encryption and Identity Verification in the IBM Computing Network; Dec. 28, 1985; pp 1-13.Applicant
Arthur, Dwight; AADS Option for Buyer Authentication; Response to NACHA/IC ANT 2 RFI; Sep. 14, 1998; pp 1-3.Applicant
Internet Counsel; Consumer Internet Purchases Using ATM Cards Successfully Processed by NACHA Pilot Participants; Feb. 23, 2003lpp 1-4.Applicant
Internet Counsel; NACHA to Test ATM Card Payments for Consumer Internet PUrchases; Feb. 23, 2003; pp 1-3.Applicant
News Release: Digital Signatures Can Secure ATM Card Payments on the Internet, NACHA Pilot Concludes; Jul. 23, 2001; pp 1-2.Applicant
Kutler, Jeffrey; Privacy Broker; Likely Internet Role for Banks? Digital Frontiers; Oct. 8, 1998; pp 1-6.Applicant
Hettinga, Bob, Hettiga's Best of the Month, Journal of Internet Banking and Commerce; Array Development. Mar. 31, 1999, web site at http://www.arraydev.com/commerce/JIBC/9801-20.htm, pp 1-4.Applicant
Denny, Stephanie, The Electric Commerce Challenge, Journal of Internet Banking and Commerce; Array Development, Mar. 31, 1999, web site at http://www.arraydev.com/commerce/JIB9811-06.htm, pp 1-2.Applicant
Burton S. Kaliski, Jr., Some Examples of the PKCS Standards, An RSA Laboratories Technical Note, Nov. 1, 1993, RSA Laboratories, Redwood City, CA, pp. 1-15.Applicant
Burton S. Kaliski, Jr., A Layman's Guide to a Subset of ASN.1, BER, and DER, An RSA Laboratories Technical Note, Nov. 1, 1993, RSA Laboratories, Redwood City, CA, pp. 1-36.Applicant
PKCS Editor, PKCS #1 v2.1: RSA Cryptography Standard, RSA Laboratories, Draft 2, Jan. 5, 2001, RSA Laboratories, Bedfor, MA, pp. 1-60.Applicant
PKCS #3: Diffie-Hellman Key-Agreement Standard, An RSA Laboratories Technical Note, Version 1.4, Nov. 1, 1993, RSA Laboratories, Redwood City, CA, pp. 1-8.Applicant
PKCS #6: Extended-Certificate Syntax Standard, An RSA Laboratories Technical Note, Nov. 1, 1993, Version 1.5, RSA Laboratories, Redwood City, CA, pp. 1-11.Applicant
PKCS #8: Private-Key Information Syntax Standard, An RSA Laboratories Technical Note, Nov. 1, 1993, Version 1.2, RSA Laboratories, Redwood City, CA, pp. 1-5.Applicant
Michael J. Wiener, Performance Comparison of Public-Key Cryptosystems, The Technical Newsletter of RSA Laboratories, a division of RSA Data Security, Inc., Summer 1998, vol. 4, No. 1, RSA Laboratories, San Mateo, CA, pp. 1-23.Applicant
George Apostolopoulos, et al., Securing Electronic Commerce: Reducing the SSL Overhead, IEEE Network, Jul./Aug. 2000, vol. 14, Issue 4, pp. 1-16.Applicant
Ueli Maurer, Modelling a Public-Key Infrastructure, Sep. 1996, Proc. 1996 European Symposium on Research in Computer Security, Lecture Notes in Computer Science, Berlin: Springer-Verlag, Rome, Italy, Department of Computer Science, Swiss Federal Institute of Technology, Zürich, Switzerland, pp. 1-26.Applicant
Security Requirements for Cryptographic Modules, Federal Information Processing Standards Publication 140-1, Jan. 11, 1994, pp. 1-45, CSL Bulletin For FIPS 140-1 pp. 1-6, Validated FIPS 140-1 Cryptographic Modules 2001, 2000, 1999, 1998, 1997-95, pp. 1-14.Applicant
Mark Heroux, A Private Key Storage Server for DCE—Functional Specification, Open Software Foundation Request for Comments: 94.1, Nov. 1996, (web site at http://www.opengroup.org/rfc/mirror-rfc/rfc94.1.txt), date of capture Jun. 13, 2001, pp. 1-73.Applicant
Peter Cox, Bench-Marking SmartGate, Establishing the Scaleability of V-ONE's SmartGate Security System, Internet SmartWare Ltd., Jul. 24, 1997, pp. 1-7.Applicant
Answers to Frequently Asked Questions about Today's Cryptography, RSA Data Security, Inc., Oct. 5, 1993, Revision 2.0, pp. 1-44.Applicant
Announcing the Standard for Digital Signature Standard (DSS), Federal Information Processing Standards Publication 186, May 19, 1994, pp. 1-18.Applicant
Sharon Boeyen, Certificate Policies and Certification Practice Statements, Entrust Technologies White Paper, Feb. 1997, Version 1.0, pp. 1-7.Applicant
Public-Key Infrastructure (PKI)—The VeriSign Difference, Feb. 3, 2001, Copyright 1999, VeriSign, Inc., pp. 1-21.Applicant
Thierry Moreau, Thirteen Reasons to Say ‘No’ to Public Key Cryptography, Draft paper, Mar. 4, 1998, CONNOTECH Experts-Conseils, Inc., Montréal, Québec, Canada, pp. 1-5.Applicant
“X9 Overview,” American Bankers Association web page (web site at http://www.x9.org/aboutX9.htm), 1998, date of capture Jan. 11, 1999, 3 pp.Applicant
July 1997 Meeting Report, Electronic Payments Forum (web site at http://www.epf.net/PrevMtngs/July97Mtng/July97Report.htm), date of capture Jan. 11, 1999, 2 pp.Applicant
Hettinga's Best of the Month, Journal of Internet Banking and Commerce, Jan. 5, 1998, (web site at wysiwyg://10/http://www.arraydev.com/commerce/JIBC/9801-20.htm), date of capture Jan. 11, 1999, 6 pp.Applicant
Burton S. Kaliski Jr., An Overview of the PKCS Standards, An RSA Laboratories Technical Note, Nov. 1, 1993, RSA Data Security, Inc. Public-Key Cryptography Standards (PKCS), pp. 1-27.Applicant
Public Key Cryptography, NIST Special Publication 800-2, Apr. 1991, reprinted at http://csrc.nist.gov/publications/nistpubs/800-2/800-2.txt, pp. 1-138.Applicant
Guideline for Implementing Cryptography in the federal Government, NIST Special Publication 800-21, Nov. 1999, pp. 1-138.Applicant
Guideline for the Use of Advanced Authentication Technology Alternatives, FIPS Publication 190, Sep. 28, 1994, reprinted at http://csrc.nist.gov/publications/fips/fips190/fip190.txt, pp. 1-55.Applicant
Building A Foundation of Trust in the PC, The Trusted Computing Platform Alliance, Jan. 2000 (web site at http://www.trustedpc.org), pp. 1-9.Applicant
Trusted Platform Module (TPM) Security Policy (A Part of the “TCPA Security Policy”), Version 0.45, Oct. 2, 2000, pp. 1-13.Applicant
Trusted Platform Module Protection Profile (TPMPP) (A Part of the “TCPA Security Policy”), Version 0.45, Sep. 14, 2000, pp. 1-151.Applicant
TCPA PC Specific Implementation Specification, Version 0.95, Jul. 4, 2001, pp. 1-70.Applicant
Common Criteria for Information Technology Security Evaluation, Smart Card Security User Group, Smart Card Protection Profile, draft Version 2.1d, Mar. 21, 2001, pp. 1-194.Applicant
X9.84-2000, Biometric Information Management and Security for the Financial Services Industry, draft version, Dec. 2000, pp. 1-141.Applicant
Security Requirements for Cryptographic Modules, FIPS Publication 140-2, May 25, 2001, pp. 1-62.Applicant
Secure Hash Standard, FIPS Publication 180-1, Apr. 17, 1995, pp. 1-24.Applicant
Digital Signature Standard (DSS), FIPS Publication 186-2, Jan. 27, 2000, pp. 1-72.Applicant
Entity Authentication Using Public Key Cryptography, FIPS Publication 196, Feb. 18, 1997, pp. 1-52.Applicant
Computer Data Authentication, FIPS Publication 113, May 30, 1985, (web site at www.itl.nist.gov/fipspubs/fip113,htm), date of capture Jan. 16, 2001, pp. 1-7.Applicant
Hettinga's Best of the Month, Journal of Internet Banking and Commerce, Mar. 31, 1999, (web site at http://www.arraydev.com/commerce/JIBC/9801-20.htm), pp. 1-4.Applicant
The Electronic Commerce Challenge, Journal of Internet Banking and Commerce, Mar. 31, 1999, (web site at http://www.arraydev.com/commerce/JIBC/9811-06.htm), pp. 1-2.Applicant
Sales Brochure for APPROVEIT, electronic approval management software, by SilanisTechnology, Inc., Jul. 18, 2000, pp. 1-12.Applicant
Public Key Infrastructure, An NSS Group White Paper, by Bob Walder, undated, reprinted from website http://www.nss.co.uk/WhitePapers/PublicKeyInfrastructure.htm on Jan. 25, 2001, pp. 1-18.Applicant
Smart Card & Security Basics, Cardlogix, Inc. brochure, Ref. date: Q1-Q2 2000, pp. 3-36.Applicant
Understanding Public Key Infrastructure (PKI), Technology White Paper, by RSA Security, Inc., 1999, pp. 1-10.Applicant
An Overview of Smart Card Security, Chan, Siu-cheng Charles, Aug. 17, 1997, reprinted from website http://home.hkstar.com/˜alanchan/papers/smartCardSecurity/ on Jan. 27, 2001, pp. 1-7.Applicant
Technical Introduction to CIP 3.0, Taschler, Scott, Sep. 30, 1997, reprinted from website http://www.datakey.com/cardpage/cip.htm on Jan. 25, 2001, pp. 1-6.Applicant
Smart Cards: Enabling Smart Commerce in the Digital Age, CREC/KPMG White Paper (Draft), May 1998, pp. 1-22.Applicant
Hettinga, Bob, Hettinga's Best of the Month, Journal of Internet Banking and Commerce; Array Development, Mar. 31, 1999, web site at http://www.arraydev.com/commerce/JIBC/9801-20.htm, pp. 1-4.Applicant
List Serve Posting dated Dec. 29, 1999 regarding Attacks on PKI.Applicant
List Serve Posting dated Dec. 30, 1999 regarding Attacks on PKI.Applicant
List Serve Posting dated Feb. 7, 2000 regarding Questions about PKI.Applicant
List Serve Posting dated Feb. 14, 2000 regarding RealNames Hacked—Firewall Issues.Applicant
List Serve Posting dated Dec. 3, 1998 regarding EU Digital Signature Initiative Stalled.Applicant
List Serve Posting dated Dec. 12, 1999 regarding QC Bio-Info Leak?Applicant
List Serve Posting dated Apr. 2, 2000 regarding Biometrics and Electronic Signatures.Applicant
List Serve Posting dated Dec. 11, 1998 regarding AADS Strawman.Applicant
List Serve Posting dated May 24, 1999 regarding [ECARM] Cardtech / Securetech & CA PKI.Applicant
List Serve Posting dated May 25, 1999 regarding [ECARM] Cardtech / Securetech & CA PKI.Applicant
List Serve Posting dated May 30, 1999 regarding [ECARM] Cardtech / Securetech & CA PKI.Applicant
List Serve Posting dated Jul. 16, 1999 regarding Common Misconceptions, was Re: KISS for PKIX.Applicant
List Serve Posting dated Aug. 15, 1999 regarding Risk Management in AA / draft X9.59.Applicant

Abstract