Connecting to a remote instance of SQL Server via SSMS can expose you to security risks

We routinely use SSMS to connect to various instances of SQL Server some local and some remote without thinking twice and often forgetting that the sensitive information being passed back and forth between the client and the server can be captured and exploited by the evil forces out there. They can get your usernames and passwords and then they can have a "feast" on your database.

So, what are we to do?

The solution is very simple, Microsoft was prudent enough to include an option that allows you to encrypt the communication between the client and the server. Yes, there is an overhead (that's why it is optional) but when you are going over the public network it is a good idea to opt for the encrypted communication.

How can I encrypt the communication

When you are connecting to a remote SQL Server instance, before clicking on the Connect button pay attention to that innocent "Options" button on the bottom right corner - click there and look for the "Encrypt Connection" checkbox. It only takes a second but it will make you feel (and you will truly be) a lot safer so don't overlook this little detail.

Click here to go back to the SQL Server content index page.