Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Tokenization (data security)
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
== The tokenization process == The process of tokenization consists of the following steps: * The application sends the tokenization data and authentication information to the tokenization system. It is stopped if authentication fails and the data is delivered to an event management system. As a result, administrators can discover problems and effectively manage the system. The system moves on to the next phase if authentication is successful. * Using one-way cryptographic techniques, a token is generated and kept in a highly secure data vault. * The new token is provided to the application for further use.<ref>{{Cite journal |last=Ogigau-Neamtiu |first=F. |date=2016 |title=Tokenization as a data security technique |url=http://yadda.icm.edu.pl/baztech/element/bwmeta1.element.baztech-7680b362-6a77-420a-aff6-9409bfb9efe6 |journal=Zeszyty Naukowe AON |language=EN |volume=2 |issue=103 |issn=0867-2245}}</ref> Tokenization systems share several components according to established standards. # Token Generation is the process of producing a token using any means, such as mathematically reversible cryptographic functions based on strong encryption algorithms and key management mechanisms, one-way nonreversible cryptographic functions (e.g., a hash function with strong, secret salt), or assignment via a randomly generated number. Random Number Generator (RNG) techniques are often the best choice for generating token values. # Token Mapping β this is the process of assigning the created token value to its original value. To enable permitted look-ups of the original value using the token as the index, a secure cross-reference database must be constructed. # Token Data Store β this is a central repository for the Token Mapping process that holds the original values as well as the related token values after the Token Generation process. On data servers, sensitive data and token values must be securely kept in encrypted format. # Encrypted Data Storage β this is the encryption of sensitive data while it is in transit. # Management of Cryptographic Keys. Strong key management procedures are required for sensitive [[data encryption]] on Token Data Stores.<ref name=":1">{{Cite journal |last1=Ozdenizci |first1=Busra |last2=Ok |first2=Kerem |last3=Coskun |first3=Vedat |date=2016-11-30 |title=A Tokenization-Based Communication Architecture for HCE-Enabled NFC Services |journal=Mobile Information Systems |language=en |volume=2016 |pages=e5046284 |doi=10.1155/2016/5046284 |issn=1574-017X|doi-access=free |hdl=11729/1190 |hdl-access=free }}</ref>
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)