Forcing Secure Connect to use TLS protocol

Rapid Recovery since version 6.0.1 use TLS 1.2 by default, which protocol do you want to use? 

I'd like to still use 1.2 but it's an issue with the one specific Cipher Suite, so I wanted to change Cipher Suites (specifically 3DES) 

I'd like to still use 1.2 but it's an issue with the one specific Cipher Suite, so I wanted to change Cipher Suites (specifically 3DES) 

I see, this article might be helpful How to Resolve Security, Vulnerability and Compliance concerns with Rapid Recovery (230703) (quest.com) 

Thanks Victor, this is exactly what I was looking for in regards to the Sweet32 attack. 

So I did this along with a new vulnerability scan and it still shows up on our internal scans.  Is there another fix or alternative measures? 

Here is another KB article that may work for you: Nessus Scanner identifies certain Cipher Suits as a possible vulnerability (260289)

If it still shows up, I recommend contacting support for further investigation.