Systems and methods for decryption as a service via a configuration of read-only databases

• US 10,505,906 B2
• Filed: 12/21/2016
• Issued: 12/10/2019
• Est. Priority Date: 03/19/2014
• Status: Active Grant

• Current Assignee: Bluefin Payment Systems LLC
• Original Assignee: Bluefin Payment Systems
• Inventors: Barnett, Timothy William, Kasatkin, Alexander I., Miyata, Christopher Hozumi, Ruehle, Daniel
• Primary Examiner(s): Okeke, Izunna
• Application Number:
  US15/386,730
• Publication Number:
  US 20170103386A1
• Time in Patent Office: 1,084 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 postage metering system using cryptography G06Q2250/05
• 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 network architectures or network communication protocols for wireless network security H04W12/00
• 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 fast decryption of one or more payloads, the system comprising:

a frontend server for receiving encrypted payloads;

a plurality of read-only databases operatively connected to the frontend server;

a master read-only database operatively connected to each of the plurality of read-only databases; and

a read/write database operatively connected to the master database, the read/write database for transmitting event messages to the master read-only database, wherein the system is configured for;

receiving event information at the read/write database;

upon receiving the event information at the read/write database, automatically transmitting authentication data to the master read-only database, wherein the authentication data has been updated by the event information;

refreshing the read-only master database to include the authentication data; and

refreshing each of the plurality of read-only databases with authentication data matching the refreshed read-only master database, wherein the authentication data is for determining whether a payload has been transmitted by a tampered device.

2. The system of claim 1, wherein the authentication data is data for authenticating a particular payload.

3. The system of claim 2, wherein the authentication data is a serial number or firmware identifier for a particular device configured to transmit the particular payload to the system.

4. The system of claim 3, wherein the authentication data is an indication of a type of firmware running on a particular device configured to transmit the particular payload to the system.

5. The system of claim 2 wherein the authentication data is for authenticating a particular partner associated with the particular payload.

6. The system of claim 5, wherein the particular partner is a third-party payment processor configured to transmit the particular payload to the system.

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

providing a frontend server for receiving encrypted payloads;

providing a plurality of read-only databases operatively connected to the frontend server;

providing a master read-only database operatively connected to each of the plurality of read-only databases;

providing a read/write database operatively connected to the master database, the read/write database for transmitting event messages to the master read-only database;

receiving event information at the read/write database;

upon receiving the event information at the read/write database, automatically transmitting authentication data to the master read-only database, wherein the authentication data has been updated by the event information;

refreshing the read-only master database to include the authentication data; and

refreshing each of the plurality of read-only databases with authentication data matching the refreshed read-only master database, wherein the authentication data is for determining whether a payload has been transmitted by a tampered device.

8. The computer-implemented method of claim 7, wherein the authentication data is data for authenticating a particular payload.

9. The computer-implemented method of claim 8, wherein the authentication data is a serial number or firmware identifier for a particular device configured to transmit the particular payload to the system.

10. The computer-implemented method of claim 8, wherein the authentication data is an indication of a type of firmware running on a particular device configured to transmit the particular payload to the system.

11. The computer-implemented method of claim 8, wherein the authentication data is for authenticating a particular partner associated with the particular payload.

12. The computer-implemented method of claim 11, wherein the particular partner is a third-party payment processor configured to transmit the particular payload to the system.