IP Library › Granted Patent US 10,819,686
Granted Patent B2
US 10,819,686 · App. 16/183,052 · Granted Oct 27, 2020

Methods and systems for securing data in the public cloud

Inventors: Attaullah Baig (Round Rock, TX); Vishal Parikh (Glen Allen, VA)
Assignee: CAPITAL ONE SERVICES, LLC
H04L63/0428G06F21/6254H04L9/0618G06F2212/402
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,819,686
App. No.
16/183,052
Granted
Oct 27, 2020
Kind
B2
Abstract

Computer implemented systems and methods are provided for securing data. In some embodiments, a system for securing data may comprise one or more processors configured to receive a request for data over a network. The one or more processors may be configured to identify one or more confidential portions of data within the requested data. The one or more processors may be further configured to transmit the confidential portions of data to a hardware device configured to secure the confidential portions of data, and receive the secured data from the hardware device.

Claims (72)

1. A system for encrypting field level data, the system comprising:

one or more processors; and

a memory having stored thereon instructions that, when executed by the one or more processors, cause the one or more processors to perform operations comprising:

receiving, from a requesting application, a request for data;

determining whether field-level encryption should be performed on the requested data, the determination being based on

an indication included in a call to secure-data API sent by a requesting device; and

encrypting a portion of the requested data, based on a result of the determination, wherein the encryption comprises:

receiving a portion of the requested data over a network;

verifying that the portion of the requested data conforms to a particular format;

generating random bits of data of a particular length;

transmitting the received portion of the requested data and the generated random bits to an encryption device;

receiving encrypted data from the encryption device;

appending the random bits to the encrypted data; and

appending, to the encrypted data, information identifying an encryption key for the encrypted data.

2. The system of claim 1 , wherein the format is associated with personally identifying information.

3. The system of claim 1 , wherein the encryption device is a hardware security module.

4. The system of claim 1 , wherein the operations further comprise identifying sensitive data within the portion of the requested data.

5. The system of claim 4 , wherein the sensitive data is associated with personally identifying information.

6. The system of claim 1 , wherein transmitting the received portion of the requested data and the generated random bits comprises transmitting the portion of the requested data and the generated random bits to a remotely located encryption device over a secured connection.

7. The system of claim 1 , wherein the operations further comprise:

receiving, over the network, the encrypted data and the information identifying the encryption key;

isolating the information identifying the encryption key from the received encrypted data;

transmitting the received encrypted data to a decryption device; and

receiving decrypted data from the decryption device.

8. The system of claim 7 , wherein the operations further comprise isolating the random bits of data from the decrypted data.

9. The system of claim 1 , wherein verifying that the portion of the requested data conforms to a particular format comprises:

determining the particular format based on a type of the portion of the requested data; and

verifying that the portion of the requested data conforms to the determined particular format.

10. The system of claim 1 , wherein appending the random bits to the encrypted data comprises:

appending the random bits in an unencrypted form to the encrypted data.

11. The system of claim 1 , wherein the information identifying the encryption key comprises one of a numeric identifier or an alphanumeric identifier.

12. A system for encrypting field level data, the system comprising:

one or more processors; and

a memory having stored thereon instructions that, when executed by the one or more processors, cause the one or more processors to perform operations comprising:

receiving, from a requesting application, a request for data;

determining whether field-level encryption should be performed on the requested data, the determination being based on

an indication included in a call to secure-data API sent by a requesting device; and

encrypting a portion of the requested data, based on a result of the determination, wherein the encryption comprises:

receiving a portion of the requested data over a network;

verifying that the portion of the requested data conforms to a particular format;

generating a random string;

transmitting the received portion of the requested data and the generated random string to an encryption device;

receiving encrypted data from the encryption device;

appending the random string to the encrypted data; and

appending, to the encrypted data, information identifying an encryption key for the encrypted data.

13. The system of claim 12 , wherein verifying that the portion of the requested data conforms to a particular format comprises:

determining the particular format based on a type of the portion of the requested data; and

verifying that the portion of the requested data conforms to the determined particular format.

14. The system of claim 12 , wherein appending the random string to the encrypted data comprises:

appending the random string in an unencrypted form to the encrypted data.

15. The system of claim 12 , wherein the encryption device is a hardware security module.

16. The system of claim 12 , wherein the operations further comprise identifying sensitive data within the portion of the requested data.

17. The system of claim 16 , wherein the sensitive data is associated with personally identifying information.

18. The system of claim 12 , wherein transmitting the received portion of the requested data and the generated random string comprises transmitting the portion of the requested data and generated random bits to a remotely located encryption device over a secured connection.

19. The system of claim 12 , wherein the operations further comprise:

receiving, over the network, the encrypted data and the information identifying the encryption key;

isolating the information identifying the encryption key from the received encrypted data;

transmitting the received encrypted data to a decryption device; and

receiving decrypted data from the decryption device.

20. A method for encrypting field level data, comprising:

receiving, from a requesting application, a request for data;

determining whether field-level encryption should be performed on the requested data, the determination being based on

an indication included in a call to secure-data API sent by a requesting device; and

encrypting a portion of the requested data, based on a result of the determination, wherein the encryption comprises:

receiving a portion of the requested data over a network;

determining, based on a type of the received portion of the requested data, a format requirement;

verifying that the portion of the requested data conforms to the format requirement;

generating a random string;

transmitting the received portion of the requested data and the generated random string to an encryption device;

receiving encrypted data from the encryption device;

appending the random string to the encrypted data; and

appending, to the encrypted data, information identifying an encryption key for the encrypted data.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 7, 2018
From: BAIG, ATTAULLAH; PARIKH, VISHAL
To: CAPITAL ONE SERVICES, LLC
Reel/Frame 047437/0832 →
Continuity (4)
Division 15825356 · Nov 29, 2017
Continuation 15378023 · Dec 13, 2016
Provisional Application 62276623 · Jan 8, 2016
Related Publication 20190075087A1 · Mar 7, 2019
Cited By (2)
US 12,197,597 US 12,596,844