Systems and methods for decryption as a service via a hardware security module

• US 10,044,686 B2
• Filed: 05/17/2017
• Issued: 08/07/2018
• 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, Ruehle, Daniel
• Primary Examiner(s): Okeke, Izunna
• Application Number:
  US15/597,402
• Publication Number:
  US 20170257350A1
• Time in Patent Office: 447 Days
• 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/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: G06Q 10/10 Office automation; Time management
• 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/401 Transaction verification
• CPC Class Codes: G06Q 20/4014 Identity check for transactions
• CPC Class Codes: G06Q 2220/00 Business processing using cryptography
• CPC Class Codes: G16H 10/60 for patient-specific data, e.g. for electronic patient records
• CPC Class Codes: G16H 70/00 ICT specially adapted for the handling or processing of medical references
• CPC Class Codes: G16H 70/60 relating to pathologies
• CPC Class Codes: H04L 2209/56 Financial cryptography, e.g. electronic payment or e-cash
• 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/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/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 decryption of payloads are disclosed herein. In various embodiments, systems and methods herein are configured for decrypting thousands of transactions per second. Further, in particular embodiments, the systems and methods herein are scalable, such that many thousands of transactions can be processed per second upon replicating particular architectural components.

Claims

1. A system for decryption of one or more payloads, the system comprising:

a hardware security module implemented by at least one processor for decrypting encrypted elements of received payloads, the hardware security module operatively connected to at least one decryption server;

the at least one decryption server, wherein the at least one decryption server is configured to

transmit the particular payload to the hardware security module for decryption of at least one encrypted element;

at least one read-only database, the at least one read-only database configured to store authentication data for decrypting encrypted elements of the received payloads;

a frontend server operatively connected to the at least one read-only database, the frontend server configured to;

     1) retrieve authentication data associated with a particular received payload; and

     2) compare the authentication data to the particular received payload to authenticate the particular received payload before the particular received payload is transmitted to the hardware security module; and

a master read-only database operatively connected to the at least one read-only database, the master read-only database configured for refreshing the authentication data stored at the at least one read-only database.

2. The system of claim 1, further comprising:

at least one decryption server operatively connected to the hardware security module, wherein the at least one decryption server is configured to;

receive the particular received payload, the particular received payload comprising at least one encrypted element;

transmit the particular received payload to the hardware security module for decryption of the at least one encrypted element;

upon receiving the particular received payload from the hardware security module, parse the particular received payload to determine whether the at least one encrypted element has been decrypted by the hardware security module;

upon determining that the at least one encrypted element has not been decrypted by the hardware security module, transmit an error message to a read/write database operatively coupled to the frontend server.

3. The system of claim 1, wherein the system further comprises a read/write database operatively connected to the master database, the read/write database configured for transmitting updated authentication data to the master database.

6. The system of claim 2, wherein the at least one decryption server is further configured to, upon determining that the at least one encrypted element has been decrypted by the hardware security module, transmitting the particular received payload to a third-party partner.

7. The system of claim 1, wherein the hardware security module is operatively connected to the frontend server via the at least one decryption server.

8. The system of claim 1, wherein the at least one read-only database is a slave read only database.

9. The system of claim 6, wherein the at least one encrypted element comprises an identifier associated with a source of the particular received payload.

10. The system of claim 9, wherein the source of the particular received payload is any of the following:

a particular point of interaction device, a mobile payments system, or an electronic health records system.

11. The system of claim 10, wherein the at least one encrypted element is in any of the following formats:

3DES, DUKPT, BPS, base64, hexadecimal encoded, or encrypted value name.

12. The system of claim 3, wherein the read/write database is a P2PE manager.

4. A computer-implemented method for decryption of one or more payloads, the method comprising:

providing a hardware security module implemented by at least one processor for decrypting encrypted elements of received payloads, the hardware security module operatively connected to at least one decryption server;

providing at least one read-only database, the at least one read-only database configured to store authentication data for decrypting encrypted elements of the received payloads;

providing a frontend server operatively connected to the at least one read-only database, the frontend server configured to;

     1) retrieve authentication data associated with a particular received payload; and

     2) compare the authentication data to the particular received payload to authenticate the particular received payload before the particular received payload is transmitted to the hardware security module; and

providing a master read-only database operatively connected to the at least one read-only database, the master read-only database configured for refreshing the authentication data stored at the at least one read-only database

providing the at least one decryption server;

transmitting the particular payload to the hardware security module for decryption of at least one encrypted element.

5. The computer-implemented method of claim 4, wherein the computer-implemented method further comprises the step of providing a read/write database operatively connected to the master database, the read/write database configured for transmitting updated authentication data to the master database.

13. The computer-implemented method of claim 4, further comprising:

providing the at least one decryption server operatively connected to the hardware security module;

receiving the particular received payload, the particular received payload comprising at least one encrypted element;

retrieving authentication data associated with the particular received payload;

comparing the particular received payload authentication data to the particular received payload to authenticate the particular received payload;

transmitting the particular received payload to the hardware security module for decryption of the at least one encrypted element;

upon receiving the particular received payload from the hardware security module, parsing the particular received payload to determine whether the at least one encrypted element has been decrypted by the hardware security module; and

upon determining that the at least one encrypted element has not been decrypted by the hardware security module, transmitting an error message to a read/write database operatively coupled to the frontend server.

14. The computer-implemented method of claim 4, wherein the hardware security module is operatively connected to the frontend server via the at least one decryption server.

15. The computer-implemented method of claim 4, wherein the at least one read-only database is a slave read only database.

16. The computer-implemented method of claim 13, wherein the computer-implemented method further comprises the step of, upon determining that the at least one encrypted element has been decrypted by the hardware security module, transmitting the particular received payload to a third-party partner.

17. The computer-implemented method of claim 5, wherein the read/write database is a P2PE manager.

18. The computer-implemented method of claim 16, wherein the at least one encrypted element comprises an identifier associated with a source of the particular received payload.

19. The computer-implemented method of claim 18, wherein the source of the particular received payload is any of the following:

a particular point of interaction device, a mobile payments system, or an electronic health records system.

20. The computer-implemented method of claim 19, wherein the at least one encrypted element is in any of the following formats:

3DES, DUKPT, BPS, base64, hexadecimal encoded, or encrypted value name.