TLS 1.1 and TLS 1.2 Compatibility with SAM

The following details the level of support of Transport Layer Security (TLS) that the SolarWinds Platform requires to be enabled for each version.

SAM 6.2.3 and earlier

TLS 1.0 must be enabled for these versions. If using SAM 6.2.3 or earlier with Framework .NET 4.6.x, SolarWinds recommends upgrading to a later SAM releases with full support for .NET 4.6.x.

SAM 6.2.4

TLS 1.0, 1.1, and 1.2 must be enabled on the SolarWinds Server and all Polling Engines for these versions.

SAM 6.3, 6.4, 6.5, 6.5, and 6.6 supports TLS 1.1 and 1.2

SAM can fall back to TLS 1.1 or  TLS 1.0 for HTTPS website polling and SSL Certificate monitoring if the later version is not working properly in your environment.

SAM 6.6.1+ (everything after 6.6.1 has this feature)

SAM 6.6.1  enables SAM to run on TLS 1.2 only to support organizations that require that type of delivery for security and compliance reasons. See TLS compatibility with Orion Platform products for details.

SAM 2019.4 currently requires at least TLS 1.2 be enabled with these ciphers:
Helpful steps:

1. Download https://www.nartac.com/Downloads/IISCrypto/IISCrypto.exe
2. Open it as Administrator on all affected servers.
3. Go to Second tab: Cipher Suites
4. One of the cipher from this list should be enabled on all affected servers. We recommend to enable one of the TLS_DHE_RSA....

List of ciphers:

{dhe_rsa, aes_256_gcm, aead, sha384},
 {dhe_dss, aes_256_gcm, aead, sha384},
 {dhe_rsa, aes_256_cbc, sha256},
 {dhe_dss, aes_256_cbc, sha256},
 {dhe_rsa, aes_128_gcm, aead, sha256},
 {dhe_dss, aes_128_gcm, aead, sha256},
 {dhe_rsa, aes_128_cbc, sha256},
 {dhe_dss, aes_128_cbc, sha256},

Primary reason for this requirement in all SolarWinds Platform 2019.4 products:

We modified list of ciphers RabbitMQ can use in both modes in order to properly work on FIPS environments in FIPS mode