Tokenization (data security)

Tokenization, when applied to data security, is the process of substituting a sensitive <a href="/facts/Data_element/jtyoAIAd">data element</a> with a non-sensitive equivalent, referred to as a <a href="/facts/Security_token/0V55fErB">token</a>, that has no intrinsic or exploitable meaning or value. The token is a reference (i.e. identifier) that maps back to the sensitive data through a tokenization system. The mapping from original data to a token uses methods that render tokens infeasible to reverse in the absence of the tokenization system, for example using tokens created from <a href="/facts/Random_number_generation/RtXEfbzd">random numbers</a>. A one-way cryptographic function is used to convert the original data into tokens, making it difficult to recreate the original data without obtaining entry to the tokenization system's resources. To deliver such services, the system maintains a vault database of tokens that are connected to the corresponding sensitive data. Protecting the system vault is vital to the system, and improved processes must be put in place to offer database integrity and physical security.
The tokenization system must be secured and validated using security best practices applicable to sensitive data protection, secure storage, audit, authentication and authorization. The tokenization system provides data processing applications with the authority and interfaces to request tokens, or detokenize back to sensitive data. 
The security and risk reduction benefits of tokenization require that the tokenization system is logically isolated and segmented from data processing systems and applications that previously processed or stored sensitive data replaced by tokens. Only the tokenization system can tokenize data to create tokens, or detokenize back to redeem sensitive data under strict security controls. The token generation method must be proven to have the property that there is no feasible means through direct attack, <a href="/facts/Cryptanalysis/7CPEQlJI">cryptanalysis</a>, side channel analysis, token mapping table exposure or brute force techniques to reverse tokens back to live data.
Replacing live data with tokens in systems is intended to minimize exposure of sensitive data to those applications, stores, people and processes, reducing risk of compromise or accidental exposure and unauthorized access to sensitive data. Applications can operate using tokens instead of live data, with the exception of a small number of trusted applications explicitly permitted to detokenize when strictly necessary for an approved business purpose. Tokenization systems may be operated in-house within a secure isolated segment of the data center, or as a service from a secure service provider.
Tokenization may be used to safeguard sensitive data involving, for example, <a href="/facts/Bank_account/qh4L451P">bank accounts</a>, <a href="/facts/Financial_statement/c6EUpGtV">financial statements</a>, <a href="/facts/Medical_record/M6L26mk8">medical records</a>, <a href="/facts/Criminal_record/nq6qeS6h">criminal records</a>, <a href="/facts/Driver%2527s_license/hFQycTwB">driver's licenses</a>, <a href="/facts/Loan/bPaAc9HT">loan</a> applications, stock <a href="/facts/Trade_(financial_instrument)/3ACTHbqp">trades</a>, <a href="/facts/Voter_registration/3HtLevwR">voter registrations</a>, and other types of <a href="/facts/Personally_identifiable_information/384PbBg5">personally identifiable information</a> (PII). Tokenization is often used in credit card processing. The <a href="/facts/Payment_Card_Industry_Data_Security_Standard/SLdbE4q0">PCI Council</a> defines tokenization as "a process by which the <a href="/facts/Primary_account_number/g9C3edYe">primary account number</a> (PAN) is replaced with a surrogate value called a token. A PAN may be linked to a reference number through the tokenization process. In this case, the merchant simply has to retain the token and a reliable third party controls the relationship and holds the PAN. The token may be created independently of the PAN, or the PAN can be used as part of the data input to the tokenization technique. The communication between the merchant and the third-party supplier must be secure to prevent an attacker from intercepting to gain the PAN and the token.
De-tokenization is the reverse process of redeeming a token for its associated PAN value. The security of an individual token relies predominantly on the infeasibility of determining the original PAN knowing only the surrogate value". The choice of tokenization as an alternative to other techniques such as <a href="/facts/Encryption/16q29Fdv">encryption</a> will depend on varying regulatory requirements, interpretation, and acceptance by respective auditing or assessment entities. This is in addition to any technical, architectural or operational constraint that tokenization imposes in practical use.

Tokenization (data security) open-in-new

Tokenization (data security)