SQL Azure "Remember to encrypt your connection"

“SQL Azure doesn’t support unencrypted connections. If you try to request a connection via SQL Server Management Studio that’s unencrypted, SQL Azure signals SQL Server Management Studio to establish an encrypted connection. Likewise, you need to specify in your connection strings that you want to encrypt the connection. If you copy & paste connection string […]

“SQL Azure doesn’t support unencrypted connections. If you try to request a connection via SQL Server Management Studio that’s unencrypted, SQL Azure signals SQL Server Management Studio to establish an encrypted connection. Likewise, you need to specify in your connection strings that you want to encrypt the connection. If you copy & paste connection string from SQL Azure portal this’s done for you. For ADO.NET you add: Encrypt=True | For ODBC you add: Encrypt=yes . This handshake for encryption is done in PRELOGIN stream of the Tabular Data Stream(TDS) Protocol which’s required by any client communicating with SQL Server and SQL Azure including: SQL Server Management Studio and SQL Client and ADO.Net. You can read more about how client and server handle encryption negotiation here,” write David. However, there’s a potential for Man-In-The-Middle attack when requesting connection. “A Man-In-The-Middle attack is the type of attack where attackers intrude into an existing connection to intercept exchanged data and inject false information. It involves eavesdropping on a connection and intercepting messages.”

More info: securely connecting to SQL Azure