IP Library Granted Patent US 12,292,999
Granted Patent B2
US 12,292,999 · App. 17/460,007 · Granted May 6, 2025

Token-based data security systems and methods for structured data

Inventor: Walter Hughes Lindsay (Phoenix, AZ)
Assignee: OPEN TEXT HOLDINGS, INC.
G06F21/6254G06F16/93G06F21/6218G06F21/6227G06F40/103G06F40/166G06F40/284G06F2221/2141
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 12,292,999
App. No.
17/460,007
Granted
May 6, 2025
Kind
B2
Abstract

A tokenization system receives a request for data anonymization, the request referencing structured data containing values of interest. Responsively, the tokenization system performs a tokenization operation on the structured data, generates a corresponding token, and replaces a value of interest with the corresponding token to produce an anonymized version of the structured data. The tokenization system stores the value of interest with the corresponding token in a secure data vault. Subsequently, the tokenization system may receive a request for revealing the anonymized version of the structured data containing the corresponding token. In response, the tokenization system can perform a reveal operation on the anonymized version of the structured data by querying the secure data vault for the corresponding token and retrieving the value of interest from the secure data vault using the corresponding token. The reveal operation produces a detokenized version of the structured data containing the value of interest.

Claims (59)

1. A method for securing data, the method comprising:

receiving, by a tokenization system from a first client computing system, a request for data anonymization, the request referencing data containing values of interest;

performing, by the tokenization system, a tokenization operation on the data, the tokenization operation comprising:

splitting a value of interest in a data field in the data into multiple regions, each region of the multiple regions corresponding to a subfield of the data field;

generating, for a respective region of the multiple regions of the value of interest in the data, a corresponding token based on the respective region of the multiple regions of the value of interest; and

placing the corresponding token in the subfield of the data field, thereby producing an anonymized version of the data;

storing, by the tokenization system, the value of interest, with the respective region having the corresponding token in the subfield of the data field, in a secure data vault, wherein the respective region of the value of interest is stored with the corresponding token in the secure data vault as a token-value pair, wherein the corresponding token is one of a plurality of format-preserving tokens generated for the values of interest in the data;

communicating, by the tokenization system, the anonymized version of the data to the first client computing system;

receiving, by the tokenization system from the first client computing system or a second client computing system, a request for revealing the anonymized version of the data containing the corresponding token;

performing, by the tokenization system, a reveal operation on the anonymized version of the data, the reveal operation comprising:

querying the secure data vault for the corresponding token; and

retrieving the respective region of the value of interest from the secure data vault using the corresponding token,

the reveal operation producing a detokenized version of the data containing the value of interest; and

communicating, by the tokenization system, the detokenized version of the data to the first client computing system or to the second client computing system.

2. The method according to claim 1 , wherein the data comprises a single field of data, a form, a table, a database record, a document having multiple data fields, a credit card number, a social security number, a single element in an extensible markup language file, or a single column in a comma separated values file.

3. The method according to claim 1 , wherein the multiple regions comprise a head portion, a body portion, and a tail portion, wherein the corresponding token preserves a format and a length of the head portion, the body portion, or the tail portion.

4. The method according to claim 1 , wherein the multiple regions comprise a head portion, a body portion, and a tail portion, and wherein the corresponding token for the head portion, the body portion, or the tail portion comprises a format-preserving token.

5. The method according to claim 1 , wherein the reveal operation further comprises concatenating the multiple regions retrieved from the secure data vault into the value of interest.

6. The method according to claim 1 , wherein the respective region of the value of interest is stored with the corresponding token in the secure data vault as a token-value pair.

7. The method according to claim 1 , wherein the corresponding token is one of a plurality of format-preserving tokens generated for the values of interest in the data.

8. A tokenization system for securing data, the tokenization system comprising:

a processor;

a non-transitory computer-readable medium; and

stored instructions translatable by the processor for:

receiving, from a first client computing system, a request for data anonymization, the request referencing data containing values of interest;

performing a tokenization operation on the data, the tokenization operation comprising;

splitting a value of interest in a data field in the data into multiple regions, each region of the multiple regions corresponding to a subfield of the data field;

generating, for a respective region of the multiple regions of the value of interest in the data, a corresponding token based on the respective region of the multiple regions of the value of interest; and

placing the corresponding token in the subfield of the data field, thereby producing an anonymized version of the data;

storing the value of interest, with the respective region having the corresponding token in the subfield of the data field, in a secure data vault, wherein the respective region of the value of interest is stored with the corresponding token in the secure data vault as a token-value pair, wherein the corresponding token is one of a Plurality of format-preserving tokens generated for the values of interest in the data;

communicating the anonymized version of the data to the first client computing system;

receiving, from the first client computing system or a second client computing system, a request for revealing the anonymized version of the data containing the corresponding token;

performing a reveal operation on the anonymized version of the data, the reveal operation comprising:

querying the secure data vault for the corresponding token; and

retrieving the respective region of the value of interest from the secure data vault using the corresponding token, the reveal operation producing a detokenized version of the data containing the value of interest; and

communicating the detokenized version of the data to the first client computing system or to the second client computing system.

9. The tokenization system of claim 8 , wherein the data comprises a single field of data, a form, a table, a database record, a document having multiple data fields, a credit card number, a social security number, a single element in an extensible markup language file, or a single column in a comma separated values file.

10. The tokenization system of claim 8 , wherein the multiple regions comprise a head portion, a body portion, and a tail portion, wherein the corresponding token preserves a format and a length of the head portion, the body portion, or the tail portion.

11. The tokenization system of claim 8 , wherein the multiple regions comprise a head portion, a body portion, and a tail portion, and wherein the corresponding token for the head portion, the body portion, or the tail portion comprises a format-preserving token.

12. The tokenization system of claim 8 , wherein the reveal operation further comprises concatenating the multiple regions retrieved from the secure data vault into the value of interest.

13. The tokenization system of claim 8 , wherein the respective region of the value of interest is stored with the corresponding token in the secure data vault as a token-value pair.

14. The tokenization system of claim 8 , wherein the corresponding token is one of a plurality of format-preserving tokens generated for the values of interest in the data.

15. A computer program product comprising a non-transitory computer-readable medium storing instructions translatable by a processor of a tokenization system for:

receiving, from a first client computing system, a request for data anonymization, the request referencing data containing values of interest;

performing a tokenization operation on the data, the tokenization operation comprising:

splitting a value of interest in a data field in the data into multiple regions, each region of the multiple regions corresponding to a subfield of the data field;

generating, for a respective region of the multiple regions of the value of interest in the data, a corresponding token based on the respective region of the multiple regions of the value of interest; and

placing the corresponding token in the subfield of the data field, thereby producing an anonymized version of the data;

storing the value of interest, with the respective region having the corresponding token in the subfield of the data field, in a secure data vault, wherein the respective region of the value of interest is stored with the corresponding token in the secure data vault as a token-value pair, wherein the corresponding token is one of a plurality of format-preserving tokens generated for the values of interest in the data;

communicating the anonymized version of the data to the first client computing system;

receiving, from the first client computing system or a second client computing system, a request for revealing the anonymized version of the data containing the corresponding token;

performing a reveal operation on the anonymized version of the data, the reveal operation comprising:

querying the secure data vault for the corresponding token; and

retrieving the respective region of the value of interest from the secure data vault using the corresponding token, the reveal operation producing a detokenized version of the data containing the value of interest; and

communicating the detokenized version of the data to the first client computing system or to the second client computing system.

16. The computer program product of claim 15 , wherein the data comprises a single field of data, a form, a table, a database record, a document having multiple data fields, a credit card number, a social security number, a single element in an extensible markup language file, or a single column in a comma separated values file.

17. The computer program product of claim 15 , wherein the multiple regions comprise a head portion, a body portion, and a tail portion, wherein the corresponding token preserves a format and a length of the head portion, the body portion, or the tail portion.

18. The computer program product of claim 15 , wherein the multiple regions comprise a head portion, a body portion, and a tail portion, and wherein the corresponding token for the head portion, the body portion, or the tail portion comprises a format-preserving token.

19. The computer program product of claim 15 , wherein the reveal operation further comprises concatenating the multiple regions retrieved from the secure data vault into the value of interest.

Assignments (2)
MERGER Recorded Jun 23, 2026
From: OPEN TEXT HOLDINGS, INC.
To: OPEN TEXT INC.
Reel/Frame 075054/0783 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 11, 2021
From: LINDSAY, WALTER HUGHES
To: OPEN TEXT HOLDINGS, INC.
Reel/Frame 057756/0124 →
Continuity (2)
Provisional Application 63071618 · Aug 28, 2020
Related Publication 20220067205A1 · Mar 3, 2022
References Cited (61)
US 8458487B1 · Palgon · 2013 [cited by examiner]
US 8806204B2 · Chambers et al. · 2014 [cited by applicant]
US 8949371B1 · Shrowty · 2015 [cited by applicant]
US 10691728B1 · Masson et al. · 2020 [cited by applicant]
US 11720548B1 · Opincariu et al. · 2023 [cited by applicant]
US 11893136B2 · Lindsay · 2024 [cited by applicant]
US 11947706B2 · Lindsay · 2024 [cited by applicant]
US 20090006645A1 · Cui et al. · 2009 [cited by applicant]
US 20120321078A1 · Chambers et al. · 2012 [cited by applicant]
US 20120324223A1 · Chambers et al. · 2012 [cited by applicant]
US 20130024433A1 · Amit et al. · 2013 [cited by applicant]
US 20130312107A1 · Agrawal et al. · 2013 [cited by applicant]
US 20140143844A1 · Goertzen · 2014 [cited by applicant]
US 20160070917A1 · Rozenberg · 2016 [cited by examiner]
US 20160379010A1 · Farkash · 2016 [cited by examiner]
US 20170147828A1 · Kurian et al. · 2017 [cited by applicant]
US 20170255867A1 · Ramachandran et al. · 2017 [cited by applicant]
US 20170272472A1 · Adhar · 2017 [cited by applicant]
US 20180189502A1 · Kumar et al. · 2018 [cited by applicant]
US 20180285591A1 · Thayer et al. · 2018 [cited by applicant]
US 20180285597A1 · Mahonin · 2018 [cited by examiner]
US 20190057222A1 · Bradley · 2019 [cited by applicant]
US 20200272762A1 · Dawkins et al. · 2020 [cited by applicant]
US 20200327252A1 · Mcfall · 2020 [cited by examiner]
US 20200334376A1 · Bragdon et al. · 2020 [cited by applicant]
US 20200401446A1 · Kodali et al. · 2020 [cited by applicant]
US 20210382770A1 · Lu et al. · 2021 [cited by applicant]
US 20220019784A1 · Wen et al. · 2022 [cited by applicant]
US 20220067184A1 · Lindsay · 2022 [cited by applicant]
US 20220067206A1 · Lindsay · 2022 [cited by applicant]
US 20220067207A1 · Lindsay · 2022 [cited by applicant]
US 20220075796A1 · Lindsay · 2022 [cited by applicant]
US 20220156300A1 · Paruchuri et al. · 2022 [cited by applicant]
US 20240143839A1 · Lindsay · 2024 [cited by applicant]
US 20240184923A1 · Lindsay · 2024 [cited by applicant]
WO WO2022047250 · 2022 [cited by applicant]
International Search Report and Written Opinion issued for International PCT Application No. PCT/US21/48085 < mailed Dec. 1, 2021, 14 pages. [cited by applicant]
Nubridges, Tokenizing Sensitive Data [retrieved from <<https://web.archive.org/web/20090928203420/http://www.nubridges.com/solutions/tokenization/>> Sep. 28, 2009, 2 pages. [cited by applicant]
Office Action issued by the U.S. Patent and Trademark Office for U.S. Appl. No. 17/460,092, mailed on Feb. 27, 2023, 19 pages. [cited by applicant]
International Preliminary Report on Patentability (IPRP), issued by the International Bureau for International PCT Application No. PCT/US2021/048085, mailed Mar. 9, 2023, 13 pages. [cited by applicant]
Office Action issued by the U.S. Patent and Trademark Office for U.S. Appl. No. 17/460,040, mailed on Apr. 28, 2023, 14 pages. [cited by applicant]
“OneTrust Acquires Redacted.ai for Data Redaction,” Mar. 1, 2021, downloaded from <<https: //www.onetrust.com/blog/onetrust-acquires-redacted-ai/>> on Aug. 27, 2021, 3 pages. [cited by applicant]
2. Z.C Nxumalo et al., “Towards Privacy with Tokenization as a Service,” V. 2015, IEEE International Conference on Adaptive Science and Technology, ICAST, downloaded from <<https://www.researchgate.net/publication/28310… [cited by applicant]
“Voltage Secure Stateless Tokenization Advances Data Security for Enterprises, Merchants and Payment Processors,” Voltage Security, Press Releases, Dec. 18, 2012, downloaded from <<https://www.coalfire.com/medialib/asse… [cited by applicant]
“Software Testing Validation and Verification,” Arbour Group, downloaded from <<https: //www.arbourgroup.com/services/validation-compliance/software-testing-validation-and-verification/?utm_source=google&utm_medium=cpc&… [cited by applicant]
N. Lomas, “Researchers Spotlight the Lie of ‘Anonymous’ Data,” Jul. 24, 2019, downloaded from <<https://techcrunch.com/2019/07/24/researchers-spotlight-the-lie-of-anonymous-data/>> on Aug. 27, 2021, 9 pages. [cited by applicant]
“Effective Personal-Identity and Metadata Redaction Techniques for Subsequent E-Filing,” downloaded from <<https://www.azd.uscourts.gov/sites/default/files/documents/redaction.pdf>> on Aug. 27, 2021, 1 page. [cited by applicant]
“OpenText Brava! Securely View, Annotate and Redact Virtually Any Type of File,” Open Text, downloaded from <<https://www.opentext.com/products-and-solutions/products/enterprise-content-management/opentext-brava >> on A… [cited by applicant]
8. B. Sondhi, “Comforte SecurDPS: Enterprise Solution for GDPR,” White Paper, Published by Coalfire Systems, Inc., Jun. 2020, 21 pages. [cited by applicant]
Notice of Allowance issued by the U.S. Patent and Trademark Office (USPTO) for U.S. Appl. No. 17/460,040, mailed Nov. 15, 2023, 13 pages. [cited by applicant]
Notice of Allowance issued by the U.S. Patent and Trademark Office (USPTO) for U.S. Appl. No. 17/460,092, mailed Dec. 8, 2023, 10 pages. [cited by applicant]
Corrected Notice of Allowability issued by the U.S. Patent and Trademark Office (USPTO) for U.S. Appl. No. 17/460,040, mailed Dec. 11, 2023, 4 pages. [cited by applicant]
Notice of Allowance issued by the U.S. Patent and Trademark Office (USPTO) for U.S. Appl. No. 17/460,092, mailed Aug. 21, 2023, 8 pages. [cited by applicant]
Office Action issued by the U.S. Patent and Trademark Office (USPTO) for U.S. Appl. No. 17/460,094, mailed Oct. 25, 2023, 16 pages. [cited by applicant]
Office Action issued by the U.S. Patent and Trademark Office for U.S. Appl. No. 17/460,094, mailed Apr. 18, 2024, 22 pages. [cited by applicant]
Office Action issued by the U.S. Patent and Trademark Office (USPTO) for U.S. Appl. No. 18/395,013, mailed Jul. 18, 2024, 21 pages. [cited by applicant]
Extended European Search Report issued by the European Patent Office for European Patent Application No. 21862883.2, mailed Aug. 22, 2024, 7 pages. [cited by applicant]
Office Action issued by the U.S. Patent and Trademark Office (USPTO) for U.S. Appl. No. 17/460,094, mailed Sep. 30, 2024, 15 pages. [cited by applicant]
Office Action issued by the U.S. Patent and Trademark Office (USPTO) for U.S. Appl. No. 18/443,171, mailed Oct. 24, 2024, 33 pages. [cited by applicant]
Office Action issued for U.S. Appl. No. 18/395,013, mailed Jan. 15, 2025, 28 pages. [cited by applicant]
Office Action issued by the U.S. Patent and Trademark Office (USPTO) for U.S. Appl. No. 17/460,094, mailed Mar. 14, 2025, 16 pages. [cited by applicant]
Cited By (3)
US 12,561,476 US 12,619,778 US 12,645,832