In some environments, it may be necessary to require SQL server connections originating from an Enterprise Vault (EV) server to be made over TLS -- providing encryption in transit.
EV does not have any encryption-related settings that control the behavior, but SQL Server and/or SQL client components can be used to turn on encryption in transit.
One of two methods can be used. Method 1 can be done at the SQL server level. Method 2 can be done per EV server.
This method enforces TLS encryption at the SQL Server level, affecting all client connections to the SQL instance.
Fig 1

This method enforces TLS encryption specifically for SQL connections originating from EV servers, without affecting other clients.
Open the Windows Registry Editor (regedit.exe) on the EV server.
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\MSSQLServer\Client\SNI18.0\GeneralFlags\Flag1
Change the Value of Flag1 to 1 (Mandatory encryption). (Fig 2)
Flag2: Optionally configure this key to control whether the server certificate is trusted (e.g., set to 1 to trust the server certificate).
Fig 2

Run the SQL Server Client Network Utility (cliconfg.exe) on the EV server. Both settings may be required.
For 64-bit systems: %systemroot%\system32\cliconfg.exe
For 32-bit systems: %systemroot%\syswow64\cliconfg.exe
Fig 3
