When is it better to use tokenization instead of encryption?
top of page
Forum
We all come from different backgrounds. Many of us have the same story. We want to know yours.
Not ready to share yet? That's okay. Maybe you're still trying to figure out how you feel about your changing beliefs. Or maybe you live in a place where apostasy is punishable by death. Whether you just want to read, contribute anonymously, or engage in respectful debate, we hope you find comfort connecting with the growing community of others who dared to doubt.
For safety's sake, log-in is required to post in the forum. You may remain anonymous and you are not required to participate. Only to respect your fellow doubters. We’re all in varying stages of questioning and withdrawal. Those who faith-shame or fear-monger may be asked to leave. Help keep our community supportive and safe!
bottom of page
I wondered is tokenization the same as encryption? And found the answer in https://www.verygoodsecurity.com/blog/posts/tokenization-vs-encryption-vs-aliasing-how-to-truly-minimize-compliance . Tokenization is best used when it is necessary to save data, since it replaces confidential information with a protected token. This makes it more secure than encryption because it is invulnerable to the same types of attacks, such as brute force attacks. Tokenization also requires less computational overhead than encryption and can be more cost-effective. In addition, tokenization is better suited for situations where data must be protected, but at the same time remain accessible, for example, when storing payment information.