In the classic asymmetric encryption tiered-server scenario, the front-end (or middle tier) application would have...
access to the public key and use this to encrypt the data. Then, a second system (presumably more secure) would have access to the private key for accessing this data (such as the SSN info). In this way, if the front end was compromised and the data was extracted from the database, the data would be useless without the private key. Since it does not exist on the front end nor the database, the attacker would still need to find this "secure" server with the private key in order to access the data.
Dig Deeper on SQL Server Security
Related Q&A from Steven Andres
Learn how to set a SQL Server password to an SA login and why you can not set this account for access to separate SQL Server databases. Continue Reading
Learn how to create a SQL Server user authentication schema having password and tracked data changes requirements and how it involves Windows ... Continue Reading
Learn why SQL Server 2000 connection is lost on the client side when database administrator changes 'SA' password on the SQL Server domain. Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.