Column level encryption
Column Level Encryption
Column level encryption is a form of database encryption method that encrypts sensitive information stored in the columns.
Understanding the concept of encryption would require a basic conceptualization of database structure. Generally, a database can be stored into tables, files, and even columns, with each rows having specific data or information inputted. To correctly identify an individual, personal information is collected like data of birth, social security number, address, work place, etc. To ensure that these set of private information is transferred and stored safely, data is encoded to be illegible to the common readers or receivers, but can only be decoded by person who holds the decryption key. The concept of encoding data is known as encryption. Encryption software companies adopts different encryption algortihms like Blowfish, AES RC4, RC5, and combine those with in-house technology, thus allowing encryption to be possible in different layers of a database. (Redirected from Database encryption)
Encryption algorithm are basically mathematical algorithm coded to store data in cipher modes that can only be deciphered if access is provided to the user. In a database, encryption can take place at the file-level, table-level and even column-levels with each method having different advantages and disadvantages.
Advantages of column-level encryption[1]:
- Flexibility in data to encrypt. The application can be written to control when, where, by whom, and how data is viewed
- Transparent encryption is possible
- More secure as each column can have its own unique encryption key within the database
- Encryption is possible when data is active and not just “at rest”
- Retrieval speed is maintained because there’s less encrypted data
Aside from column level encryption, there are other encryption methods like file level encryption, disk encryption, and database encryption.
References
- ^ "Differences Between Whole Database and Column Encryption". NetLib Security. 2016-01-21. Retrieved 2018-07-30.