Put Your Sensitive DB2 Data Under Lock and Key

ackers are trying to find some way to get into your database. If you think they're not, you're just deluding yourself. The news stories about compromised credit card numbers are proof that the best way to lose face with your customers is to let a hacker steal their sensitive data. Customers want their credit card numbers, medical histories, etc. kept under lock and key. Go figure!

You can use technologies such as Secure Sockets Layer (SSL) and Secure HTTP to securely transport confidential user information across network connections (i.e., in transit). But how do you go about storing your customers' confidential data securely? Sadly, in many large organizations, you can't even trust your own staff to have access to such confidential information.

IBM DB2 Universal Database offers a solution. Since version 7.2, it has provided built-in facilities for encrypting the data you persist. Using this encryption and decryption functionality is a straightforward process that you can employ to safeguard sensitive data. In particular, this tutorial demonstrates how to use DB2's ENCRYPT, DECRYPT_BIN, DECRYPT_CHAR, and GETHINT functions.

How do you store your customers' confidential data securely when hackers are constantly trying break into your DB2 database?



Use DB2's built-in functions (ENCRYPT, DECRYPT_BIN, DECRYPT_CHAR, and GETHINT) to encrypt the data you persist.