Managing payload decryption via fingerprints

• US 10,382,405 B2
• Filed: 03/16/2018
• Issued: 08/13/2019
• Est. Priority Date: 03/19/2014
• Status: Active Grant

• Current Assignee: Bluefin Payment Systems LLC
• Original Assignee: Bluefin Payment Systems LLC
• Inventors: Barnett, Timothy William, Kasatkin, Alexander I., Miyata, Christopher Hozumi
• Primary Examiner(s): Patel, Haresh N
• Application Number:
  US15/923,330
• Publication Number:
  US 20180211251A1
• Time in Patent Office: 515 Days
• Field of Search: 713189
• CPC Class Codes: G06F 11/0766 Error or fault reporting or storing
• CPC Class Codes: G06F 16/23 Updating
• CPC Class Codes: G06F 16/2379 Updates performed during online database operations; commit processing
• CPC Class Codes: G06F 16/955 using information identifiers, e.g. uniform resource locators [URL]
• CPC Class Codes: G06F 21/44 Program or device authentication
• CPC Class Codes: G06F 21/602 Providing cryptographic facilities or services
• CPC Class Codes: G06F 21/6227 where protection concerns the structure of data, e.g. records, types, queries
• CPC Class Codes: G06F 21/6245 Protecting personal data, e.g. for financial or medical purposes
• CPC Class Codes: G06F 21/73 by creating or determining hardware identification, e.g. serial numbers
• CPC Class Codes: G06F 21/77 in smart cards
• CPC Class Codes: G06Q 10/00 Administration; Management
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G06Q 20/20 Point-of-sale [POS] network systems
• CPC Class Codes: G06Q 20/223 based on the use of peer-to-peer networks
• CPC Class Codes: G06Q 20/382 insuring higher security of transaction
• CPC Class Codes: G06Q 20/3823 combining multiple encryption tools for a transaction
• CPC Class Codes: G06Q 20/401 Transaction verification
• CPC Class Codes: G06Q 20/4014 Identity check for transactions
• CPC Class Codes: G06Q 20/409 Device specific authentication in transaction processing
• CPC Class Codes: G06Q 2220/00 Business processing using cryptography
• CPC Class Codes: G06Q 2220/10 : Usage protection of distributed data files
• CPC Class Codes: G16H 10/60 : for patient-specific data, e.g. for electronic patient records
• CPC Class Codes: H04L 2209/24 : Key scheduling, i.e. generating round keys or sub-keys for block encryption
• CPC Class Codes: H04L 2209/56 : Financial cryptography, e.g. electronic payment or e-cash
• CPC Class Codes: H04L 2209/60 : Digital content management, e.g. content distribution
• CPC Class Codes: H04L 2209/80 : Wireless
• CPC Class Codes: H04L 63/0428 : wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• CPC Class Codes: H04L 63/0435 : wherein the sending and receiving network entities apply symmetric encryption, i.e. same key used for encryption and decryption cryptographic mechanisms or cryptographic arrangements for symmetric key encryption H04L9/06
• CPC Class Codes: H04L 63/061 : for key exchange, e.g. in peer-to-peer networks cryptographic mechanisms or cryptographic arrangements for key agreement H04L9/0838
• CPC Class Codes: H04L 63/08 : for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• 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/12 : Applying verification of the received information cryptographic mechanisms or cryptographic arrangements for data integrity or data verification H04L9/32
• CPC Class Codes: H04L 63/123 : received data contents, e.g. message integrity
• CPC Class Codes: H04L 63/20 : for managing network security; network security policies in general filtering policies H04L63/0227
• CPC Class Codes: H04L 9/0861 : Generation of secret information including derivation or calculation of cryptographic keys or passwords
• CPC Class Codes: H04L 9/0877 : using additional device, e.g. trusted platform module [TPM], smartcard, USB or hardware security module [HSM]
• CPC Class Codes: H04L 9/14 : using a plurality of keys or algorithms
• CPC Class Codes: H04L 9/3226 : using a predetermined code, e.g. password, passphrase or PIN network architectures or network communication protocols for supporting authentication of entities using passwords in a packet data network H04L63/083
• CPC Class Codes: H04L 9/3234 : involving additional secure or trusted devices, e.g. TPM, smartcard, USB or software token network architectures or network communication protocols for supporting authentication of entities using an additional device in a packet data network H04L63/0853

Abstract

Systems and methods for creating fingerprints for encryption devices are described herein. In various embodiments, the system includes an encryption device operatively connected to a device management system. According to particular embodiments, the device management system: 1) receives a first payload from the encryption device, the first payload including data in a particular format; 2) creates a fingerprint for the encryption device, the fingerprint including a section format for each of one or more distinct sections of the particular format; 3) storing a record of the fingerprint for the encryption device and the unique identifier at the at least one database; and 4) comparing a format of each subsequent payload received from the encryption device to the fingerprint for the device to determine whether the device has been compromised.

Claims

1. A point to point encryption management computing system comprising at least one hardware processor operatively coupled to memory, the at least one hardware processor configured to:

receive a first payload from a device, the first payload comprising data in a particular format and a device indicator comprising a unique identifier used for identifying the device;

parse the first payload to extract the unique identifier;

retrieve a unique identifier table from memory;

compare the unique identifier to the unique identifier table to determine whether the unique identifier is included in the unique identifier table;

upon determining that the unique identifier is included in the unique identifier table, create a fingerprint associated with the unique identifier, wherein the fingerprint is created by;

parsing the particular format of the first payload into one or more distinct sections of the particular format;

determining the section format of each of the one or more distinct sections; and

creating a record of the section format of each of the one or more distinct sections; and

compare a format of each subsequent payload received from the device to the fingerprint for the device to determine whether the device has been compromised.

2. The point to point encryption management computing system of claim 1, wherein the at least one hardware processor is further configured to, upon determining that the device has been compromised, change a state of the device to indicate the device is compromised.

3. The point to point encryption management computing system of claim 2, wherein the at least one processor is further configured to only decrypt payloads of devices with states indicating they have not been compromised.

4. The point to point encryption management computing system of claim 1, wherein comparing the format of each subsequent payload received from the device to the fingerprint for the device to determine whether the device has been compromised comprises:

receiving a second payload from the device, the second payload comprising second data in a second particular format and a second device indicator, the second device indicator comprising a second unique identifier used for identifying the device;

retrieving the fingerprint from at least one database based on the second device indicator; and

comparing the second particular format to the fingerprint to determine whether the device has been compromised.

5. The point to point encryption management computing system of claim 4, wherein comparing the second particular format to the fingerprint to determine whether the device has been compromised comprises comparing the second format of each of one or more distinct sections of the second particular format to the section format for each of one or more distinct sections of the fingerprint.

6. The point to point encryption management computing system of claim 5, wherein the at least one processor is further configured to, upon determining that the device has been compromised, transmit a message to a user indicating that the device has been compromised.

7. The point to point encryption management computing system of claim 6, wherein the at least one processor is further configured to, upon determining that the device has been compromised, disregard the second payload without decrypting any data.

8. The point to point encryption management computing system of claim 1, wherein the at least one hardware processor receives the first payload via a cloud-based communication system.

9. The point to point encryption management computing system of claim 8, wherein the at least one hardware processor receives each subsequent payload received from the device from the cloud-based communication system.

10. A point to point encryption management computing system comprising at least one hardware processor operatively coupled to memory, the at least one hardware processor configured to:

receive an initial payload from one or more devices, each initial payload comprising encrypted and unencrypted data in a format;

parse each initial payload to extract a unique identifier;

retrieve a unique identifier table from memory;

compare each of the unique identifiers to the unique identifier table to determine whether each of the unique identifiers are included in the unique identifier table;

upon determining that each of the unique identifiers are included in the unique identifier table, create a fingerprint associated with each unique identifier, wherein each fingerprint is created by;

parsing the format of each initial payload into one or more distinct sections;

determining a section format of each of the one or more distinct sections; and

creating a record of the section format of each of the one or more distinct sections; and

compare the format of each subsequent payload from the one or more devices to the fingerprint associated with the unique identifier for the one or more devices; and

upon determining that the format of a particular payload of the subsequent payloads received from a particular device does not match the fingerprint associated with the unique identifier for the particular device, decline to decrypt any encrypted data of the particular payload and transmit a notification of declining to decrypt the encrypted data to a user computing system.

11. The point to point encryption management computing system of claim 10, wherein the at least one hardware processor is further configured to, upon determining that the format of the particular payload does not match the fingerprint associated with the unique identifier for the particular device, changing a status associated with the particular device from active to tampered.

12. The point to point encryption management computing system of claim 10, wherein each payload from the particular device includes one or more segments of data in a particular order.

13. The point to point encryption management computing system of claim 12, wherein each of the one or more segments of data included in each payload from the particular device is in a particular format.

14. The point to point encryption management computing system of claim 13, wherein the particular format for a particular segment of the one or more segments is a character format.

15. The point to point encryption management computing system of claim 14, wherein the particular format for a second particular segment of the one or more segments is a hexadecimal format.

16. The point to point encryption management computing system of claim 10, wherein the at least one hardware processor receives the initial payload via a cloud-based communication system.

17. The point to point encryption management computing system of claim 16, wherein the at least one hardware processor receives each subsequent payload from the one or more devices via the cloud-based communication system.

18. A computer-implemented method for managing payload decryption via a computing system operatively coupled to an encryption device, the method comprising:

receiving, by at least one processor, a first payload from the encryption device, the first payload comprising data in a particular format, a unique identifier used for identifying the encryption device, and encrypted data;

extracting the unique identifier from the first payload;

comparing the unique identifier to a unique identifier table retrieved from memory to determine whether the unique identifier is included in the unique identifier table;

upon determining that the unique identifier is included in the unique identifier table, creating, by a fingerprint creation means, a fingerprint for the encryption device, by;

parsing the particular format into one or more distinct sections of the particular format;

determining the section format of each of the one or more distinct sections; and

creating a record of the section format of each of the one or more distinct sections;

storing a record of the fingerprint and the unique identifier in memory and changing a state of the encryption device to active by the at least one processor;

comparing, by the at least one processor, a second particular format of a subsequent payload received from the encryption device to the fingerprint for the encryption device to determine whether the encryption device has been compromised; and

upon determining that the encryption device has not been compromised, decrypting encrypted data of the subsequent payload.

19. The computer-implemented method of claim 18, the method further comprising the steps of:

receiving, by the at least one processor, the subsequent payload from the encryption device, the subsequent payload comprising data in the second particular format and the unique identifier; and

retrieving, by the at least one processor, the fingerprint from memory for comparing the second particular format to the fingerprint.

20. The computer-implemented method of claim 19, the method further comprising the steps of, upon determining that the encryption device has been compromised, declining, by the at least one processor, to decrypt the encrypted data of the subsequent payload.