Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Perimeter

7/26/2010
10:00 AM
Adrian Lane
Adrian Lane
Commentary
50%
50%

What You Should Know About Tokenization

A week ago Visa released a set of best practices and recommendations for tokenization. Unfortunately, "best practices" leaves plenty of room for poor implementations.

A week ago Visa released a set of best practices and recommendations for tokenization. Unfortunately, "best practices" leaves plenty of room for poor implementations.A few months back I wrote a post about token deployment strategies for meeting PCI compliance. What I did not discuss were some of the differences between the different tokenization technologies on the market.

Token solutions have become popular because they remove credit card data from most processing systems, thus eliminating them from inspection during PCI assessment. For example, if you have a dozen systems (order entry, customer management, payment gateways, general ledger, etc.) and you substitute a token for the Primacy Account Number, then you remove a huge portion of the PCI audit. For a lot of merchants, that means a savings of 50 percent. No credit card numbers, no security threat, so no reason to poke around.

But that assumes the token is secure. The critical part of a token strategy is to ensure the token does not betray the original credit card number. Tokens created via any mathematical function, be it cryptography or hashing, always start with the account number. That means there is a chance they can be reversed back into the original if not carefully implemented or deployed. But we know from experience that poorly implemented algorithms, bad entropy or pseudo-random number generators, or improper use of padding/salting results in tokens that are easy to hack. The only two recommendations made by Visa are for mathematical derivatives, and there is considerable leeway in its guidance. In other words, a solution that meets Visa's criteria can provide poor security.

What does this mean to you? Several things:

1. Visa should have included in its recommendation the use of completely random numbers. This is far more secure because there is simply no way to reverse-engineer the credit card number from the token given there is no mathematical relationship. The only way to gain access to the original data is through the token server itself. I recommend you select this option if it is available from your vendor.

2. If you are looking at a solution that uses cryptographic functions, then you need to understand you will be using some form of a format-preserving encryption to form the token. Despite being based on accepted strong cryptographic algorithms, the format-preserving options are not specifically endorsed by Visa or the PCI Standards Council. Make sure your vendor has had its product professionally reviewed by a noted expert in the field of cryptanalysis. Also, verify that your auditor will remove systems using encryption from the scope of the audit -- otherwise you miss out on cost savings.

3. If you are looking at a solution that uses a hashing variant, then first make sure the method used is acceptable to Visa and PCI. Second, verify that the vendor implementation has been reviewed by the cryptanalysis community. Finally, see if you can locate a product that provides random salt values for each token. Static salt values or salting with a finite set of merchant IDs offers poor security and makes the hashes vulnerable to dictionary attacks.

Take the time to verify these options so you can get full value for your tokenization investment.

Adrian Lane is an analyst/CTO with Securosis LLC, an independent security consulting practice. Special to Dark Reading. Adrian Lane is a Security Strategist and brings over 25 years of industry experience to the Securosis team, much of it at the executive level. Adrian specializes in database security, data security, and secure software development. With experience at Ingres, Oracle, and ... View Full Bio

 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 8/10/2020
Researcher Finds New Office Macro Attacks for MacOS
Curtis Franklin Jr., Senior Editor at Dark Reading,  8/7/2020
Healthcare Industry Sees Respite From Attacks in First Half of 2020
Robert Lemos, Contributing Writer,  8/13/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: It's a technique known as breaking out of the sandbox kids.
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
The Changing Face of Threat Intelligence
The Changing Face of Threat Intelligence
This special report takes a look at how enterprises are using threat intelligence, as well as emerging best practices for integrating threat intel into security operations and incident response. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-20383
PUBLISHED: 2020-08-13
ABBYY network license server in ABBYY FineReader 15 before Release 4 (aka 15.0.112.2130) allows escalation of privileges by local users via manipulations involving files and using symbolic links.
CVE-2020-24348
PUBLISHED: 2020-08-13
njs through 0.4.3, used in NGINX, has an out-of-bounds read in njs_json_stringify_iterator in njs_json.c.
CVE-2020-24349
PUBLISHED: 2020-08-13
njs through 0.4.3, used in NGINX, allows control-flow hijack in njs_value_property in njs_value.c. NOTE: the vendor considers the issue to be "fluff" in the NGINX use case because there is no remote attack surface.
CVE-2020-7360
PUBLISHED: 2020-08-13
An Uncontrolled Search Path Element (CWE-427) vulnerability in SmartControl version 4.3.15 and versions released before April 15, 2020 may allow an authenticated user to escalate privileges by placing a specially crafted DLL file in the search path. This issue was fixed in version 1.0.7, which was r...
CVE-2020-24342
PUBLISHED: 2020-08-13
Lua through 5.4.0 allows a stack redzone cross in luaO_pushvfstring because a protection mechanism wrongly calls luaD_callnoyield twice in a row.