Forcing Secure Connect to use TLS protocol

Hi,

I'm running version 6.6.0 for our RR and I wanted to see how to update and force the connection using an updated TLS protocol. We've ran security scans and RR comes back with an vulnerability. I've tried to follow this guide here but as it's an older version I don't have anything in the directory for sc_server.properties in the following directory:

Open file explorer and navigate to C:\Program Files\AppRecovery\Core\CoreService\SecureConnect

I was hoping to get an updated answer or be pointed to the most up to date knowledge base for 6.6.0.268

Thanks,

Nik

Top Replies

Victor.Portillo over 3 years ago in reply to n lagnese +1

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

0 Victor.Portillo over 3 years ago

Rapid Recovery since version 6.0.1 use TLS 1.2 by default, which protocol do you want to use?
- 0 n lagnese over 3 years ago in reply to Victor.Portillo
  
  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)
  - 0 Victor.Portillo over 3 years ago in reply to n lagnese
    
    I see, this article might be helpful How to Resolve Security, Vulnerability and Compliance concerns with Rapid Recovery (230703) (quest.com)
  - 0 n lagnese over 3 years ago in reply to Victor.Portillo
    
    Thanks Victor, this is exactly what I was looking for in regards to the Sweet32 attack.
  - 0 n lagnese over 3 years ago in reply to Victor.Portillo
    
    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?
  - 0 Luciano.Guerra over 3 years ago in reply to n lagnese
    
    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.