December 8, 2025 at 4:51 pm
hi for the 2 years i've been here I believe we've had "encryption" turned off in what i only know as the way we tell ssms to communicate with our sql servers ...and i've always thought meant also the server itself relaxing how it communicates back to whatever client is asking for data.
recently an OO programmer asked why we are communicating to / from sql server without ssl. i told him its been like that and i'd investigate what the downside is either way knowing we havent heard of any breeches.
also recently, our dba turned on (for test purposes in response to the OO programmer's question) a service called TDE on a vm. All sorts of problems started happening including a need to trust the cert if contacting that server from a local instance of ssms and timeouts from/on one of our web apps (connection) trying thru java connectors to insert records onto a db on that server. shutting down that service made our current problems disappear.
so the questions are 1) what risk have we had all this time not encrypting, and 2) what other gotchyas will we see in an environment where ssis, ssrs, pbi , excel pivots etc are used bumping up against sql engines and cubes built off that engine?
Viewing post 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply