Device-level authentication with unique device identifiers

• US 9,602,292 B2
• Filed: 09/11/2015
• Issued: 03/21/2017
• Est. Priority Date: 07/25/2015
• Status: Active Grant

• Current Assignee: Confia Systems, Inc.
• Original Assignee: Confia Systems, Inc.
• Inventors: Ramatchandirane, Nadaradjane
• Primary Examiner(s): CHIANG, JASON
• Application Number:
  US14/852,284
• Publication Number:
  US 20170026187A1
• Time in Patent Office: 557 Days
• US Class Current: 1/1
• CPC Class Codes: G06F 21/305 by remotely controlling device operation
• CPC Class Codes: G06F 21/44 Program or device authentication
• CPC Class Codes: G06F 21/6218 to a system of files or objects, e.g. local or distributed file system or database
• CPC Class Codes: H04L 63/0823 using certificates cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263
• CPC Class Codes: H04L 63/0876 based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
• CPC Class Codes: H04L 63/166 at the transport layer
• CPC Class Codes: H04L 9/3268 using certificate validation, registration, distribution or revocation, e.g. certificate revocation list [CRL]

Abstract

An embodiment may include transmitting a manufacturer security certificate to a provisioning server device, and establishing, with the provisioning server device, a secure connection based on the manufacturer security certificate. The embodiment may also involve transmitting, over the secure connection, device data that characterizes the client device, and receiving, over the secure connection, a server security certificate. The embodiment may further include obtaining a unique client device identifier, where the unique client device identifier is stored in a secure memory element of the client device. The embodiment may additionally include, possibly based on the server security certificate and the unique client device identifier, accessing protected information available to a particular pre-validated server device.

Claims

1. A method comprising:

receiving, by a provisioning server device, a manufacturer security certificate from a client device, wherein the manufacturer security certificate is associated with a manufacturer of the client device;

establishing, between the client device and the provisioning server device, a secure connection, wherein the secure connection is established based on the manufacturer security certificate;

receiving, by the provisioning server device over the secure connection, device data that characterizes the client device;

transmitting, by the provisioning server device over the secure connection, a server security certificate, wherein the server security certificate identifies secure communication parameters of one or more pre-validated server devices, wherein the pre-validated server devices do not include the provisioning server device;

randomly generating, by the provisioning server device, a representation of a unique client device identifier, wherein the unique client device identifier is associated with the client device and is configured to support, for the client device, secure access to the pre-validated server devices;

transmitting, by the provisioning server device over the secure connection, the unique client device identifier, wherein reception of the unique client device identifier causes the client device to store the unique client device identifier in a tamper-resistant secure memory element of the client device; and

based on the representation of the unique client device identifier, registering, by the provisioning server device, the client device, wherein the registration associates the representation of the unique client device identifier with policies that allow the client device to securely access, by way of the secure communication parameters, protected information available to the one or more pre-validated server devices, wherein the accessing the protected information comprises (i) establishing, between the client device and a particular pre-validated server device, a second secure connection, wherein the second secure connection is established based on the server security certificate, (ii) after establishing the second secure connection, transmitting, by the client device over the second secure connection, a representation of the unique client device identifier, and (iii) receiving, by the client device over the second secure connection, the protected information, wherein the second secure connection involves mutual authentication between the client device and the particular pre-validated server device, and wherein accessing the protected information occurs without the client device transmitting security credentials that identify a user of the client device to the one or more pre-validated server devices.

2. The method of claim 1, further comprising:

generating a hash of the unique client device identifier, wherein the hash is a one-way cryptographic function;

comparing the hash to other hashes associated with other unique client device identifiers; and

verifying that the hash is unique amongst the other hashes.

3. The method of claim 1, further comprising:

instructing, by the provisioning server device over the secure connection, the client device to perform a secure test transaction with a particular pre-validated server device, wherein security of the secure test transaction is based on the secure communication parameters.

4. The method of claim 1, wherein at least one of the secure connection or the second secure connection is established, at least in part, by a web browser application operating on the client device.

5. The method of claim 1, wherein the secure connection is based on Secure Sockets Layer (SSL) or Transport Layer Security (TLS) protocols.

6. The method of claim 1, wherein storing the unique client device identifier in the tamper-resistant secure memory element comprises locking the tamper-resistant secure memory element with the unique client device identifier stored therein.

7. An article of manufacture including a non-transitory computer-readable medium, having stored thereon program instructions that, upon execution by a provisioning server device, cause the provisioning server device to perform operations comprising:

receiving, by the provisioning server device, a manufacturer security certificate from a client device, wherein the manufacturer security certificate is associated with a manufacturer of the client device;

establishing, between the client device and the provisioning server device, a secure connection, wherein the secure connection is established based on the manufacturer security certificate;

receiving, by the provisioning server device over the secure connection, device data that characterizes the client device;

transmitting, by the provisioning server device over the secure connection, a server security certificate, wherein the server security certificate identifies secure communication parameters of one or more pre-validated server devices, wherein the pre-validated server devices do not include the provisioning server device;

randomly generating, by the provisioning server device, a representation of a unique client device identifier, wherein the unique client device identifier is associated with the client device and is configured to support, for the client device, secure access to the pre-validated server devices;

transmitting, by the provisioning server device over the secure connection, the unique client device identifier, wherein reception of the unique client device identifier causes the client device to store the unique client device identifier in a tamper-resistant secure memory element of the client device; and

based on the representation of the unique client device identifier, registering, by the provisioning server device, the client device, wherein the registration associates the representation of the unique client device identifier with policies that allow the client device to securely access, by way of the secure communication parameters, protected information available to the one or more pre-validated server devices, wherein the accessing the protected information comprises (i) establishing, between the client device and a particular pre-validated server device, a second secure connection, wherein the second secure connection is established based on the server security certificate, (ii) after establishing the second secure connection, transmitting, by the client device over the second secure connection, a representation of the unique client device identifier, and (iii) receiving, by the client device over the second secure connection, the protected information, wherein the second secure connection involves mutual authentication between the client device and the particular pre-validated server device, and wherein accessing the protected information occurs without the client device transmitting security credentials that identify a user of the client device to the one or more pre-validated server devices.

8. The article of manufacture of claim 7, wherein the operations further comprise:

generating a hash of the unique client device identifier, wherein the hash is a one-way cryptographic function;

comparing the hash to other hashes associated with other unique client device identifiers; and

verifying that the hash is unique amongst the other hashes.

9. The article of manufacture of claim 7, wherein the operations further comprise:

instructing, by the provisioning server device over the secure connection, the client device to perform a secure test transaction with a particular pre-validated server device, wherein security of the secure test transaction is based on the secure communication parameters.

10. The article of manufacture of claim 7, wherein at least one of the secure connection or the second secure connection is established, at least in part, by a web browser application operating on the client device.

11. The article of manufacture of claim 7, wherein the secure connection is based on Secure Sockets Layer (SSL) or Transport Layer Security (TLS) protocols.

12. The article of manufacture of claim 7, wherein storing the unique client device identifier in the tamper-resistant secure memory element comprises locking the tamper-resistant secure memory element with the unique client device identifier stored therein.

13. A provisioning server device comprising:

a processor;

memory; and

program instructions, stored in the memory, that upon execution by the processor cause the provisioning server device to perform operations comprising;

receiving, by the provisioning server device, a manufacturer security certificate from a client device, wherein the manufacturer security certificate is associated with a manufacturer of the client device;

establishing, between the client device and the provisioning server device, a secure connection, wherein the secure connection is established based on the manufacturer security certificate;

receiving, by the provisioning server device over the secure connection, device data that characterizes the client device;

transmitting, by the provisioning server device over the secure connection, a server security certificate, wherein the server security certificate identifies secure communication parameters of one or more pre-validated server devices, wherein the pre-validated server devices do not include the provisioning server device;

randomly generating, by the provisioning server device, a representation of a unique client device identifier, wherein the unique client device identifier is associated with the client device and is configured to support, for the client device, secure access to the pre-validated server devices;

transmitting, by the provisioning server device over the secure connection, the unique client device identifier, wherein reception of the unique client device identifier causes the client device to store the unique client device identifier in a tamper-resistant secure memory element of the client device; and

based on the representation of the unique client device identifier, registering, by the provisioning server device, the client device, wherein the registration associates the representation of the unique client device identifier with policies that allow the client device to securely access, by way of the secure communication parameters, protected information available to the one or more pre-validated server devices, wherein the accessing the protected information comprises (i) establishing, between the client device and a particular pre-validated server device, a second secure connection, wherein the second secure connection is established based on the server security certificate, (ii) after establishing the second secure connection, transmitting, by the client device over the second secure connection, a representation of the unique client device identifier, and (iii) receiving, by the client device over the second secure connection, the protected information, wherein the second secure connection involves mutual authentication between the client device and the particular pre-validated server device, and wherein accessing the protected information occurs without the client device transmitting security credentials that identify a user of the client device to the one or more pre-validated server devices.

14. The provisioning server device of claim 13, wherein the operations further comprise:

generating a hash of the unique client device identifier, wherein the hash is a one-way cryptographic function;

comparing the hash to other hashes associated with other unique client device identifiers; and

verifying that the hash is unique amongst the other hashes.

15. The provisioning server device of claim 13, wherein the operations further comprise:

instructing, by the provisioning server device over the secure connection, the client device to perform a secure test transaction with a particular pre-validated server device, wherein security of the secure test transaction is based on the secure communication parameters.

16. The provisioning server device of claim 13, wherein at least one of the secure connection or the second secure connection is established, at least in part, by a web browser application operating on the client device.

17. The provisioning server device of claim 13, wherein the secure connection is based on Secure Sockets Layer (SSL) or Transport Layer Security (TLS) protocols.

18. The provisioning server device of claim 13, wherein storing the unique client device identifier in the tamper-resistant secure memory element comprises locking the tamper-resistant secure memory element with the unique client device identifier stored therein.