Database Encryption – Part 1
This is a topic I love to review every once in a while. Encryption is a big enough task; but, wrap a database around it, and you have a bigger can of worms.
Why would you want your database encrypted?
- Database backups take offsite may be restored easily if they are not encrypted
- If a hacker gains access to your database server, if the database files are encrypted they can’t acces any of the contents easily without also hacking into an SQL Account
- Sensitive data may be stored in your database such as Credit Card Numbers, BirthDates or other personal identification information that may be used to establish credit
- You may have data contained in your database having a restricted access list due to company, best practices, or even regulations of some sort
- Your database may interact with End Points exposed outside your firewall, and require encryption entering and leaving the database
Of course you have lots of options for how your data is encrypted. We can discuss some of those tomorrow In the meantime, share your encryption stories and experience by joining the discussion below, or sending an email to btaylor@sswug.org.
Cheers,
Ben
$$SWYNK$$
Featured Article(s)
SQL Server 2012 Linked Servers Optimization Tips
In this article, you can find some useful tips to use SQL Server 2012 linked servers.