SENSITIVE DATA ALIASING FOR TRANSACTION-CARD AND OTHER APPLICATIONS

• US 20110031309A1
• Filed: 10/15/2010
• Published: 02/10/2011
• Est. Priority Date: 01/27/2006
• Status: Active Grant

• Current Assignee: Appriss Retail Information LLC
• Original Assignee: Aspect Loss Prevention, LLC (Verisk Analytics Incorporated)
• Inventors: DUHAIME, DAVID A., DUHAIME, BRAD J.
• Granted Patent: US 8,473,418 B2
• Time in Patent Office: Days
• US Class Current: 235/380
• CPC Class Codes: G06F 16/122 using management policies backup systems G06F11/1446; file migration policies for HSM systems G06F16/185
• CPC Class Codes: G06F 21/32 using biometric data, e.g. fingerprints, iris scans or voiceprints
• CPC Class Codes: G06F 21/602 Providing cryptographic facilities or services
• CPC Class Codes: G06F 21/606 by securing the transmission between two devices or processes
• 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/6254 by anonymising data, e.g. decorrelating personal data from the owner's identification
• CPC Class Codes: G06F 2221/2101 Auditing as a secondary aspect
• CPC Class Codes: G06Q 20/356 Aspects of software for card payments
• CPC Class Codes: G06Q 20/383 Anonymous user system
• CPC Class Codes: H04L 9/0625 with splitting of the data block into left and right halves, e.g. Feistel based algorithms, DES, FEAL, IDEA or KASUMI
• CPC Class Codes: H04L 9/0631 Substitution permutation network [SPN], i.e. cipher composed of a number of stages or rounds each involving linear and nonlinear transformations, e.g. AES algorithms
• CPC Class Codes: H04L 9/0643 Hash functions, e.g. MD5, SHA, HMAC or f9 MAC

Abstract

Database management and security is implemented in a variety of embodiments. In one such embodiment, data sets containing retail transaction information are analyzed using aliases representing transaction card identifiers. In another embodiment, the transaction card identifiers are stored in an encrypted form for use from a secure access, while the alias identifier is available for standard access.

Claims

1. A method of using data sets associated with transaction card identifiers directed for use in a retail environment, the method being implemented by a computer-based circuit configured and software-programmed to perform the steps of:

accessing, by the computer-based circuit, alias identifiers that represent the transaction card identifiers;

associating the alias identifiers to encrypted forms of the transaction card identifiers;

using the alias identifiers to analyze retail-environment aspects of the data sets, and generating user-directed output therefrom, independent of the transaction card identifiers and the encrypted forms of the transaction card identifiers;

maintaining the association between the alias identifiers and the transaction card identifiers for secured access and decoding, in response to and using disparately processed data, one of;

the alias identifiers, and

the transaction card identifiers.

2. The method of claim 1, wherein the encrypted forms of the transaction card identifiers are formatted to represent displayable characters, wherein the alias identifiers are used to prevent unauthorized access to the transaction card identifiers.

3. The method of claim 1, further including the step of providing secure access to the encrypted forms of the transaction card identifiers.

4. The method of claim 1, wherein the data sets contain at least one of a cash register identifier, an employee identifier, a transaction date, a customer Internet Protocol address, a customer email address, a purchased goods identifier, and a transaction value.

5. The method of claim 1, wherein the alias identifiers are randomly generated.

6. The method of claim 5, wherein a portion of the transaction card identifiers is added to the alias identifiers.

7. The method of claim 1, further including the step of appending a portion of a transaction card identifier to an alias identifier that is associated with said transaction card identifier.

8. The method of claim 1, wherein decoding includes

decrypting the encrypted forms of the transaction card identifiers;

subsequently encrypting the transaction card identifiers using a second encryption method.

9. The method of claim 6, wherein the portion of the transaction card identifiers identifies a financial service provider.

10. The method of claim 2, wherein the encrypted forms of the transaction card identifiers are formatted using uuencode or base 64.

11. The method of claim 10, further including the steps of:

decrypting the encrypted forms of the transaction card identifiers using a first encryption key; and

encrypting the decrypted transaction card identifiers using a second encryption key.

12. The method of claim 1, wherein the transaction card identifiers are first received in an inverted form and where the transaction card identifiers are recovered and subsequently encrypted.

13. The method of claim 1, further including the steps of:

transferring encrypted access information to an application that is used for accessing the data sets;

decrypting the encrypted access information; and

using the decrypted access information to configure access restrictions to the data sets.

14. The method of claim 1, further including the steps of:

restricting access to the transaction card identifiers to a set of authorized users; and

using the alias identifiers in place of the transaction card identifiers for a set of standard users, where at least some of the standard users are not included in the set of authorized users.

15. The method of claim 13, further including the step of decrypting encrypted forms of the transaction card identifiers for use by the set of authorized users.

16. The method of claim 13, further including the step of providing an alias identifier to an authorized user wherein said alias identifier corresponds to a transaction card identifier that has been indicated by said authorized user.

17. The method of claim 13, including the step of creating a log of access attempts by the authorized users and the standard users.

18. The method of claim 1, wherein:

each alias identifier is associated with exactly one transaction card identifier; and

at least one transaction card identifier is associated with multiple data sets.

19. The method of claim 1, wherein decoding includes formatting the transaction card, or the alias, identifiers to represent displayable characters.

20. The method of claim 1, including the steps of:

storing the alias identifiers in a first database;

storing the transaction card identifiers in a second database; and

wherein the first and second database have different secure access requirements.