Field level security system for securing sensitive data

1. A field level security system for tokenizing field level data, comprising:

one or more memory devices storing instructions; and

one or more processors configured to execute the instructions to perform operations comprising:

receiving, via a secure connection, a request for data directed to the field level security system, the request comprising a call to a secure-data Application Program Interface (API), the call requesting tokenization of a particular portion of the requested data;

obtaining field level data based on the request;

identifying, based on the particular portion, sensitive field level data for tokenization within the field level data;

determining, based on the request for the tokenization, whether the identified sensitive field level data will be tokenized;

generating a token representing the identified sensitive field level data, based on:

a process integrated into the field level security system; and

a result of a determination that the identified sensitive field level data will be tokenized;

associating the generated token with the identified sensitive field level data;

storing the identified sensitive field level data in a database; and

providing the requested data with the generated token over a network, the generated token constituting a replacement for the identified sensitive field level data.

2. The field level security system of claim 1 , wherein the identified sensitive field level data includes at least one of a credit card number, a bank routing number, an account number, a social security number, a patient identification number, or personally identifying pieces of information.

3. The field level security system of claim 1 , wherein generating the token comprises generating the token using at least one of tokenization logic implemented in software, specialized hardware, or a combination of software and hardware.

4. The field level security system of claim 1 , wherein generating the token comprises generating the token based on an algorithm which comprises format-preserving encryption.

5. The field level security system of claim 1 , the operations further comprise storing the association between the generated token and the identified sensitive field level data in the database.

6. The field level security system of claim 1 , wherein the operations further comprise encrypting the identified sensitive field level data prior to storing the identified sensitive field level data.

7. The field level security system of claim 6 , wherein encrypting the field level data comprises:

generating random bits of data of a specified length;

transmitting the identified sensitive field level data and the 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.

8. The field level security system of claim 1 , wherein encrypting the identified sensitive field level data comprises encrypting the identified sensitive field level data using at least one of software or a hardware device.

9. A field level security system for detokenizing field level data, comprising:

one or more memory devices storing instructions, and

one or more processors configured to execute the instructions to perform operations comprising:

receiving, via a secure connection, a request for data directed to the field level security system, the request comprising a call to a secure-data Application Program Interface (API), the call requesting detokenization of a portion of the requested data;

determining, based on the request for detokenization, that detokenization is to be performed for the requested data;

receiving a token over a network;

identifying, based on the token, sensitive field level data for detokenization within the data;

retrieving the identified sensitive field level data; and

providing the retrieved sensitive field level data to the application.

10. The field level security system of claim 9 , wherein identifying sensitive field level data comprises identifying stored associations between the token and the sensitive field level data stored in a database.

11. The field level security system of claim 9 , wherein retrieving the identified sensitive field level data comprises retrieving the identified sensitive field level data from a database storing token data.

12. The field level security system of claim 9 , wherein the retrieved sensitive field level data is encrypted.

13. The field level security system of claim 12 , wherein the operations further comprise decrypting the encrypted sensitive field level data by transmitting the encrypted sensitive field level data to a decryption device.

14. The field level security system of claim 9 , wherein the retrieved sensitive field level data comprises at least one of a credit card number, a bank routing number, an account number, a social security number, a patient identification number, or personally identifying pieces of information.

15. The field level security system of claim 9 , the operations further comprising determining that decryption should be performed on the requested data.

16. The field level security system of claim 15 , wherein determining that decryption should be performed on the requested data comprises determining that decryption should be performed on the requested data based on at least one of an indication received as part of the call to the API, a policy in place for providing data to requesting application, or a specific policy for the requested data.

17. The field level security system of claim 9 , wherein receiving the request for data comprises receiving the request for data via an API.

18. The field level security system of claim 17 , wherein the API comprises an API requiring mutual authentication.

19. The field level security system of claim 9 , wherein retrieving the sensitive field level data comprises retrieving the sensitive field level data over the secure connection.