Has anybody managed to successfully deploy Sophos Enterprise 5.5.1 while using the TLS1.2 database connectivity?

Hello Redfern,

I am in the process of updating from 5.4.1 and have outcome all but the stated instance support error. I too am on 2012 SP4 /w CU 10. I've tried many different things after ensuring it was not anything to do with an encrypted connection to the SQL server.

So I decided to log a ticket with Sophos to get their explanation on the issue. I'm wondering if it is simply checking for a version number that is different, below mine is stated as 11.4.7001.0 which might identify express version over other versions.

SQL Server 2012      codename Denali

11.0.2100.60

11.0.3000.0 or 11.1.3000.0

11.0.5058.0 or 11.2.5058.0

11.0.6020.0 or 11.3.6020.0

11.0.7001.0 or 11.4.7001.0

In your case the cert issue is that you will need to configure a certificate for use with the SQL Server. We have an enterprise CA so it's quite straightforward for me (just remember to configure all the alternate names you might be using). Sophos link below if you haven't already seen it.

community.sophos.com/.../127521

Can let you know what they reply.

Cheers,

Grant

Hi Grant. 

Thanks for this. 

Did you get a helpful Reply? 

Would be grateful if you can share it with us. 

Cheers. 

Shahid 

Hi guys,

not much to add to the Friday afternoon wrap up, other than I've been told that the incident has gone to GES engineers, who, "are the highest technical tier within support and are responsible for interacting with our development teams".

Should have some better information next week.

have a good weekend.

Grant

So ?

Paul Jr 

Hi guys,

sorry for the delay but this has turned into a bit of an annoyance. Anyway, long story short I upgraded to 2017 without any change in behaviour, I identified the client connections to the SQL box and realised Sophos was using 2 different client libraries (of which one is not TLS 1.2 compliant). So now I am trying to figure out if there is TLS 1.2 support for this driver, or that Sophos needs to update the parts of the application that is using SQL OLE DB connection strings as per this article from Microsoft tech team.

https://blogs.msdn.microsoft.com/sqlreleaseservices/released-microsoft-ole-db-driver-for-sql-server/

At this point I’m not sure as I do not know the exact provider they are using.

It's worth noting that this was done in a DEV environment and I ran up a fresh Windows 2016 with SEC 5.5.1 and got exactly the same behaviour.

Below are some notes I made to get to this point.

--------------------------------------------------------------------------

R&D team’s answer to support is to follow the articles and to speak to Microsoft and SQL experts:

-----------------------------------------
Article ID: 127521
Title: Enterprise Console - Database connection check
URL: https://sophos.com/kb/127521 
-----------------------------------------

-----------------------------------------
Article ID: 131698
Title: Sophos Enterprise Console - How to create the required certificate package to allow TLS 1.2 connection to the database
URL: https://sophos.com/kb/131698 
-----------------------------------------

Sound familiar?

Okay, so from here I decided to upgrade to SQL 2017.

Next time to find out exactly what are the connections to the database by application and driver.

Sp_who2

This shows applications accessing the Sophos DB and if we follow SPID 57 & 60 we see 1 is SQLNCLI and the other is “Sophos EndPoint Management”. So lets follow those 2 into the activity monitor.

Activity monitor reveals the same information ass sp_who2 and now we follow the session ID to find out what drivers are being used by the applications.

Using this article we find the driver versions:
https://www.mssqltips.com/sqlservertip/2198/determine-which-version-of-sql-server-data-access-driver-is-used-by-an-application/

Now we can see that session ID 57 and 60 are using different client libraries as per this article

https://msdn.microsoft.com/en-us/library/dd339982.aspx

So now using SQL profiler, the trace reveals that both these session ID’s come from the same ClientProcessID 2112

Now task manager will show us what process 2112 actually is:

So it appears that MgntSvc.exe or “Sophos Management Service” is making SQL connections using 2 different client libraries. Of which the “SQL 2000” driver connection made by the application name of “Sophos EndPoint  Management “ does not support TLS 1.2.

It would appear that this connection is a SQL OLE DB TLS 1.0 connection as illustrated when using a test connection and generating the same error.

Do Sophos need to update the connection string as per this article?
https://blogs.msdn.microsoft.com/sqlreleaseservices/released-microsoft-ole-db-driver-for-sql-server/

At this point I’m not sure as I do not know the exact provider they are using, will pose question to tech support.

Have you run the CheckDBconnection.exe -a to setup the SQLNLI connection string

The tool has two working mode. The default is checking the system for TLS 1.2 compatibility (system check mode). The second performs the database settings modification (apply mode: -a).

Hi Dominic,

Where have you been all this time! No I did not see that a tool called CheckDBconnection.exe is used to change the SQL provider. I've just gone back to check that article and can now see that they have it in the guts of the tool info.

Looks like a real silly place to put it to me as I missed it entirely. Not sure why it is in a list of a parameters for an article called DB connection check. Not sure why there is nothing in the setup to tell you that you need to convert the connection string, or even clear steps in that article outlining;

1. upgrade

2. db check

3. convert connection string

Thank you, you've saved me a lot of grief as I knew it had to be that, now that I realise this tool is not to check, but to change the SQL connection string I will go back and do exactly that.

And just like that, I've disabled TLS 1.0 & 1.1 after changing the connection string and everything works as expected.

Really not a fan of that documentation. 

Many thanks again!!!

Grant

Hello

There have been many mentions to many articles.  When you write "that article", I am not sure which one you refer to ...

Paul Jr

Hi Paul,

This is one below the main culprit for me, as I'm never one to read details parameters of application unless I think I need the functionality. I really did not expect that the convert string would be found in a db check tool.

-----------------------------------------
Article ID: 127521
Title: Enterprise Console - Database connection check
URL: https://sophos.com/kb/127521 
-----------------------------------------

Anyway, time to continue, I've spent way too much time on this already and life's too short.

Big thanks again to Dominic for showing me what I had missed.

Best wishes to all,

Grant

No problem Grant,

Agree the single line in the document is not particularly obvious or that it is required to run the connectivity tool in -a mode to migrate the console over to TLS 1.2

Surely going forward the functionality will be built into the Installer/Console itself, and would be the recommended default on install. 

I have tried that tools many times.  It does just nothing.  The -a switch does nothing more ...

Not sure I get it ...

Paul Jr

Hi Paul,

The goal of the tool is to merely convert the sql connection string used by the Sophos app to a SQL client library that supports TLS 1.2. I kept the output of the process which I'll paste below, and yours should look similar. Double check against mine below.

C:\sourceRepository\Sophos\Sophos Enterprise Console\sec_551\ServerInstaller\CheckDBConnection>CheckDBconnection.exe -a -c -l
Sophos Connectivity Verifier
5.5.1.955

Copyright 2000-2018 Sophos Limited. All rights reserved.
Sophos and Sophos Anti-Virus are registered trademarks of Sophos Limited and Sop
hos Group. All other product and company names mentioned are trademarks or regis
tered trademarks of their respective owners.

UpdateConnectionString 64 bit system
UpdateConnectionString :
Registry Key: Software\Wow6432Node\Sophos\EE\Management Tools
Value: DatabaseConnectionMS
Trust cert: True

Found: Provider=SQLOLEDB;Integrated Security=SSPI;Initial Catalog=SOPHOS551;Data Source=(hostname)\SOPHOS;

Testing: Provider=SQLNCLI11;Trusted_Connection=Yes;Database=SOPHOS551;Server=(hostname)\SOPHOS;Encrypt=yes;TrustServerCertificate=true;

TestDatabaseConnectionWithConnectionString 'Provider=SQLNCLI11;Trusted_Connection=Yes;Database=SOPHOS551;Server=(hostname)\SOPHOS;Encrypt=yes;TrustServerCertificate=true;'

NewConnStr 'Trusted_Connection=Yes;Database=SOPHOS551;(hostname)\SOPHOS;Encrypt=yes;TrustServerCertificate=true;;'

Test successfull, writing reg key
UpdateConnectionString :
Registry Key: Software\Sophos\ServerSecurity
Value: DatabaseConnection
Trust cert: True

Found: Integrated Security=SSPI;Initial Catalog=SophosSecurity;Data Source=(local)\SOPHOS;

Testing: Provider=SQLNCLI11; Trusted_Connection=Yes;Database=SophosSecurity;Server=(hostname)\SOPHOS;Encrypt=yes;TrustServerCertificate=true;

TestDatabaseConnectionWithConnectionString 'Provider=SQLNCLI11; Trusted_Connection=Yes;Database=SophosSecurity;(hostname)\SOPHOS;Encrypt=yes;TrustServerCertificate=true;'

NewConnStr ' Trusted_Connection=Yes;Database=SophosSecurity;(hostname)\SOPHOS;Encrypt=yes;TrustServerCertificate=true;;'

Test successfull, writing reg key
UpdateConnectionString :
Registry Key: Software\Wow6432Node\Sophos\ServerSecurity
Value: DatabaseConnection
Trust cert: True

Found: Integrated Security=SSPI;Initial Catalog=SophosSecurity;Data Source=(local)\SOPHOS;

Testing: Provider=SQLNCLI11; Trusted_Connection=Yes;Database=SophosSecurity;Server=(hostname)SOPHOS;Encrypt=yes;TrustServerCertificate=true;

TestDatabaseConnectionWithConnectionString 'Provider=SQLNCLI11; Trusted_Connection=Yes;Database=SophosSecurity;Server=(hostname)\SOPHOS;Encrypt=yes;TrustServerCertificate=true;'

NewConnStr ' Trusted_Connection=Yes;Database=SophosSecurity;Server=(hostname)\SOPHOS;Encrypt=yes;TrustServerCertificate=true;;'

Test successfull, writing reg key
UpdateConnectionString :
Registry Key: Software\Sophos\Patch
Value: SophosPatchConnectionString
Trust cert: True

Found: Data Source=(local)\SOPHOS;Initial Catalog=SOPHOSPATCH52;Integrated Security=SSPI;Connect Timeout=60

Testing: Provider=SQLNCLI11; Server=(hostname)\SOPHOS;Database=SOPHOSPATCH52;Trusted_Connection=Yes;Timeout=60;Encrypt=yes;TrustServerCertificate=true;

TestDatabaseConnectionWithConnectionString 'Provider=SQLNCLI11; Server=(hostname)\SOPHOS;Database=SOPHOSPATCH52;Trusted_Connection=Yes;Timeout=60;Encrypt=yes;TrustServerCertificate=true;'

NewConnStr ' Server=(hostname)\SOPHOS;Database=SOPHOSPATCH52;Trusted_Connection=Yes;Timeout=60;Encrypt=yes;TrustServerCertificate=true;;'

Test successfull, writing reg key
Database connection settings modified successfully

best wishes,

Grant

Hi Paul,

The goal of the tool is to merely convert the sql connection string used by the Sophos app to a SQL client library that supports TLS 1.2. I kept the output of the process which I'll paste below, and yours should look similar. Double check against mine below.

C:\sourceRepository\Sophos\Sophos Enterprise Console\sec_551\ServerInstaller\CheckDBConnection>CheckDBconnection.exe -a -c -l
Sophos Connectivity Verifier
5.5.1.955

Copyright 2000-2018 Sophos Limited. All rights reserved.
Sophos and Sophos Anti-Virus are registered trademarks of Sophos Limited and Sop
hos Group. All other product and company names mentioned are trademarks or regis
tered trademarks of their respective owners.

UpdateConnectionString 64 bit system
UpdateConnectionString :
Registry Key: Software\Wow6432Node\Sophos\EE\Management Tools
Value: DatabaseConnectionMS
Trust cert: True

Found: Provider=SQLOLEDB;Integrated Security=SSPI;Initial Catalog=SOPHOS551;Data Source=(hostname)\SOPHOS;

Testing: Provider=SQLNCLI11;Trusted_Connection=Yes;Database=SOPHOS551;Server=(hostname)\SOPHOS;Encrypt=yes;TrustServerCertificate=true;

TestDatabaseConnectionWithConnectionString 'Provider=SQLNCLI11;Trusted_Connection=Yes;Database=SOPHOS551;Server=(hostname)\SOPHOS;Encrypt=yes;TrustServerCertificate=true;'

NewConnStr 'Trusted_Connection=Yes;Database=SOPHOS551;(hostname)\SOPHOS;Encrypt=yes;TrustServerCertificate=true;;'

Test successfull, writing reg key
UpdateConnectionString :
Registry Key: Software\Sophos\ServerSecurity
Value: DatabaseConnection
Trust cert: True

Found: Integrated Security=SSPI;Initial Catalog=SophosSecurity;Data Source=(local)\SOPHOS;

Testing: Provider=SQLNCLI11; Trusted_Connection=Yes;Database=SophosSecurity;Server=(hostname)\SOPHOS;Encrypt=yes;TrustServerCertificate=true;

TestDatabaseConnectionWithConnectionString 'Provider=SQLNCLI11; Trusted_Connection=Yes;Database=SophosSecurity;(hostname)\SOPHOS;Encrypt=yes;TrustServerCertificate=true;'

NewConnStr ' Trusted_Connection=Yes;Database=SophosSecurity;(hostname)\SOPHOS;Encrypt=yes;TrustServerCertificate=true;;'

Test successfull, writing reg key
UpdateConnectionString :
Registry Key: Software\Wow6432Node\Sophos\ServerSecurity
Value: DatabaseConnection
Trust cert: True

Found: Integrated Security=SSPI;Initial Catalog=SophosSecurity;Data Source=(local)\SOPHOS;

Testing: Provider=SQLNCLI11; Trusted_Connection=Yes;Database=SophosSecurity;Server=(hostname)SOPHOS;Encrypt=yes;TrustServerCertificate=true;

TestDatabaseConnectionWithConnectionString 'Provider=SQLNCLI11; Trusted_Connection=Yes;Database=SophosSecurity;Server=(hostname)\SOPHOS;Encrypt=yes;TrustServerCertificate=true;'

NewConnStr ' Trusted_Connection=Yes;Database=SophosSecurity;Server=(hostname)\SOPHOS;Encrypt=yes;TrustServerCertificate=true;;'

Test successfull, writing reg key
UpdateConnectionString :
Registry Key: Software\Sophos\Patch
Value: SophosPatchConnectionString
Trust cert: True

Found: Data Source=(local)\SOPHOS;Initial Catalog=SOPHOSPATCH52;Integrated Security=SSPI;Connect Timeout=60

Testing: Provider=SQLNCLI11; Server=(hostname)\SOPHOS;Database=SOPHOSPATCH52;Trusted_Connection=Yes;Timeout=60;Encrypt=yes;TrustServerCertificate=true;

TestDatabaseConnectionWithConnectionString 'Provider=SQLNCLI11; Server=(hostname)\SOPHOS;Database=SOPHOSPATCH52;Trusted_Connection=Yes;Timeout=60;Encrypt=yes;TrustServerCertificate=true;'

NewConnStr ' Server=(hostname)\SOPHOS;Database=SOPHOSPATCH52;Trusted_Connection=Yes;Timeout=60;Encrypt=yes;TrustServerCertificate=true;;'

Test successfull, writing reg key
Database connection settings modified successfully

best wishes,

Grant

Hello

I get the exact same output as you with the command "CheckDBconnection.exe -a -c -l".  But running C:\sec_551\ServerInstaller\CheckDBConnection\CheckDBConnection.exe without switches afterward, you get this:

C:\sec_551\ServerInstaller\CheckDBConnection>CheckDBConnection.exe
Sophos Connectivity Verifier
5.5.1.955

Copyright 2000-2018 Sophos Limited. All rights reserved.
Sophos and Sophos Anti-Virus are registered trademarks of Sophos Limited and Sophos Group. All other product and company names mentioned are trademark
s or registered trademarks of their respective owners.

(/) Operating system is ready to use TLS 1.2
(/) Installed .NET Framework supports TLS 1.2
Connection to the SQL Server established
(x) SQL Server instance does not support TLS 1.2
(x) SQL Server TCP/IP protocol detection failed
(/) There is a certificate installed that can be used with SQL Server
(/) SQL Server Native Client library supports TLS 1.2
Encrypted connection to the SQL Server cannot be established

C:\sec_551\ServerInstaller\CheckDBConnection>

My version of SQL clearly support TLS 1.2.  And TCP/IP is clearly enabled.

Paul Jr Robitaille

My version of SQl is: 

Product Version: 11.0.7469.6
Product Name: SQL Server 2012
Product Level: SP4
Product Edition: Express Edition (64-bit)

Which clearly supports TLS1.2

Paul Jr

Hi Paul,

I'd probably start with SQL Server configuration manager and make sure that the TCP/IP connections are accepted.

Grant

Sorry for awaking a dead thread, however I am experiecing some issues with my upgrade to 5.5.2 from 5.5.0 I followed all the steps in here and still I am receiving the following. Any advice will be appreciated as this seems as the best thread on the matter since support isn't of much help. Thanks

C:\sec_552\ServerInstaller\CheckDBConnection>checkdbconnection -s .\sophos
Sophos Connectivity Verifier
5.5.2.700

Copyright 1989-2020 Sophos Limited. All rights reserved.
Sophos and Sophos Anti-Virus are registered trademarks of Sophos Limited and Sop
hos Group. All other product and company names mentioned are trademarks or regis
tered trademarks of their respective owners.

(/) Operating system is ready to use TLS 1.2
(/) Installed .NET Framework supports TLS 1.2
Connection to the SQL Server established
(!) SQL Server instance can be configured to use TLS 1.2
(/) SQL Server TCP/IP protocol is enabled
(/) There is a certificate installed that can be used with SQL Server
(/) SQL Server Native Client library supports TLS 1.2
Encrypted connection to the SQL Server cannot be established

C:\sec_552\ServerInstaller\CheckDBConnection>CheckDBconnection.exe -a -c -l
Sophos Connectivity Verifier
5.5.2.700

Copyright 1989-2020 Sophos Limited. All rights reserved.
Sophos and Sophos Anti-Virus are registered trademarks of Sophos Limited and Sop
hos Group. All other product and company names mentioned are trademarks or regis
tered trademarks of their respective owners.

WMI namespace to use: root\Microsoft\Sqlserver\ComputerManagement14
TestDatabaseConnectionWithConnectionString 'Server=.\SOPHOS;Database=master;Time
out=3;Trusted_Connection=Yes;TrustServerCertificate=true;'

NewConnStr 'Server=.\SOPHOS;Database=master;Timeout=3;Trusted_Connection=Yes;Tru
stServerCertificate=true;;'

WMI namespace to use: root\Microsoft\Sqlserver\ComputerManagement14
WMI namespace to use: root\Microsoft\Sqlserver\ComputerManagement14
WMI namespace to use: root\Microsoft\Sqlserver\ComputerManagement14
WMI namespace to use: root\Microsoft\Sqlserver\ComputerManagement14
TestDatabaseConnectionWithConnectionString 'Server=.\SOPHOS;Database=master;Time
out=3;Trusted_Connection=Yes;Encrypt=yes;TrustServerCertificate=true;'

NewConnStr 'Server=.\SOPHOS;Database=master;Timeout=3;Trusted_Connection=Yes;Enc
rypt=yes;TrustServerCertificate=true;;'

UpdateConnectionString 64 bit system
UpdateConnectionString :
Registry Key: Software\Wow6432Node\Sophos\EE\Management Tools
Value: DatabaseConnectionMS
Trust cert: True

Found: Provider=SQLOLEDB;Integrated Security=SSPI;Initial Catalog=SOPHOS550;Data
Source=(local)\SOPHOS;

Testing: Provider=SQLNCLI11;Trusted_Connection=Yes;Database=SOPHOS550;Server=sop
hos.starlight.com\SOPHOS;Encrypt=yes;TrustServerCertificate=true;

TestDatabaseConnectionWithConnectionString 'Provider=SQLNCLI11;Trusted_Connectio
n=Yes;Database=SOPHOS550;Server=sophos.starlight.com\SOPHOS;Encrypt=yes;TrustSer
verCertificate=true;'

NewConnStr 'Trusted_Connection=Yes;Database=SOPHOS550;Server=sophos.starlight.co
m\SOPHOS;Encrypt=yes;TrustServerCertificate=true;;'

Test successful, writing reg key
UpdateConnectionString :
Registry Key: Software\Sophos\ServerSecurity
Value: DatabaseConnection
Trust cert: True

Found: Integrated Security=SSPI;Initial Catalog=SophosSecurity;Data Source=(loca
l)\SOPHOS;

Testing: Provider=SQLNCLI11;Trusted_Connection=Yes;Database=SophosSecurity;Serve
r=sophos.starlight.com\SOPHOS;Encrypt=yes;TrustServerCertificate=true;

TestDatabaseConnectionWithConnectionString 'Provider=SQLNCLI11;Trusted_Connectio
n=Yes;Database=SophosSecurity;Server=sophos.starlight.com\SOPHOS;Encrypt=yes;Tru
stServerCertificate=true;'

NewConnStr 'Trusted_Connection=Yes;Database=SophosSecurity;Server=sophos.starlig
ht.com\SOPHOS;Encrypt=yes;TrustServerCertificate=true;;'

Test successful, writing reg key
UpdateConnectionString :
Registry Key: Software\Wow6432Node\Sophos\ServerSecurity
Value: DatabaseConnection
Trust cert: True

Found: Integrated Security=SSPI;Initial Catalog=SophosSecurity;Data Source=(loca
l)\SOPHOS;

Testing: Provider=SQLNCLI11;Trusted_Connection=Yes;Database=SophosSecurity;Serve
r=sophos.starlight.com\SOPHOS;Encrypt=yes;TrustServerCertificate=true;

TestDatabaseConnectionWithConnectionString 'Provider=SQLNCLI11;Trusted_Connectio
n=Yes;Database=SophosSecurity;Server=sophos.starlight.com\SOPHOS;Encrypt=yes;Tru
stServerCertificate=true;'

NewConnStr 'Trusted_Connection=Yes;Database=SophosSecurity;Server=sophos.starlig
ht.com\SOPHOS;Encrypt=yes;TrustServerCertificate=true;;'

Test successful, writing reg key
UpdateConnectionString :
Registry Key: Software\Sophos\Patch
Value: SophosPatchConnectionString
Trust cert: True

Found: Data Source=(local)\SOPHOS;Initial Catalog=SOPHOSPATCH52;Integrated Secur
ity=SSPI;Connect Timeout=60

Testing: Provider=SQLNCLI11;Server=sophos.starlight.com\SOPHOS;Database=SOPHOSPA
TCH52;Trusted_Connection=Yes;Timeout=60;Encrypt=yes;TrustServerCertificate=true;

TestDatabaseConnectionWithConnectionString 'Provider=SQLNCLI11;Server=sophos.sta
rlight.com\SOPHOS;Database=SOPHOSPATCH52;Trusted_Connection=Yes;Timeout=60;Encry
pt=yes;TrustServerCertificate=true;'

NewConnStr 'Server=sophos.starlight.com\SOPHOS;Database=SOPHOSPATCH52;Trusted_Co
nnection=Yes;Timeout=60;Encrypt=yes;TrustServerCertificate=true;;'

Test successful, writing reg key
(/) Operating system is ready to use TLS 1.2
(/) Installed .NET Framework supports TLS 1.2
Connection to the SQL Server established
(!) SQL Server instance can be configured to use TLS 1.2
(/) SQL Server TCP/IP protocol is enabled
(/) There is a certificate installed that can be used with SQL Server
(/) SQL Server Native Client library supports TLS 1.2
Encrypted connection to the SQL Server is established

Database connection settings modified successfully

OS version information:
Microsoft Windows Server 2012 R2 Standard - 6.3.9600 - 0

SQL Server version:
SOPHOS - 14.0.3335.7 - RTM - CU21

SQL Server protocol information:
Sm: True
Np: True
Tcp: True

SQL Server Certificates:
Sophos-CA Sophos-CA

Client Library information:
sm - SQLNCLI11 - 11.0.7493
tcp - SQLNCLI11 - 11.0.7493
np - SQLNCLI11 - 11.0.7493
tcp - SQLNCLI11 - 11.0.7493.4

C:\sec_552\ServerInstaller\CheckDBConnection>CheckDBconnection.exe -s .\sophos
Sophos Connectivity Verifier
5.5.2.700

Copyright 1989-2020 Sophos Limited. All rights reserved.
Sophos and Sophos Anti-Virus are registered trademarks of Sophos Limited and Sop
hos Group. All other product and company names mentioned are trademarks or regis
tered trademarks of their respective owners.

(/) Operating system is ready to use TLS 1.2
(/) Installed .NET Framework supports TLS 1.2
Connection to the SQL Server established
(!) SQL Server instance can be configured to use TLS 1.2
(/) SQL Server TCP/IP protocol is enabled
(/) There is a certificate installed that can be used with SQL Server
(/) SQL Server Native Client library supports TLS 1.2
Encrypted connection to the SQL Server cannot be established