ARCHIVED CONTENT
You are viewing ARCHIVED CONTENT released online between 1 April 2010 and 24 August 2018 or content that has been selectively archived and is no longer active. Content in this archive is NOT UPDATED, and links may not function.By Michael Higashi
When it comes to protecting your sensitive customer and corporate data in the cloud, encryption and tokenization will no doubt be two of the most important weapons in your arsenal. But before you can begin applying them (along with your other cloud data protection tools) to your data, you’ll need to know where to encrypt and where to tokenize, and why.
No matter which cloud you’re adopting, your cloud data protection best practices will remain the same: the first step will always be to identify and classify which data must be protected. Encrypting or tokenizing everything going to the cloud would be far too resource-intensive and unwieldy an endeavor, ultimately causing more problems than it solves: there’s no reason to invest in the protection of data that is of no value to competitors or cybercriminals. Instead, determine which data must be protected, and how strongly.
Read the complete article at: Cloud Data Protection 101: Data Classification