V-256841
AvePoint Compliance Guardian Security Technical Implementation Guide
Title
Compliance Guardian must use TLS 1.2, at a minimum, to protect the confidentiality of sensitive data during electronic dissemination using remote access.
Description
<VulnDiscussion>Using older unauthorized versions or incorrectly configuring protocol negotiation makes the gateway vulnerable to known and unknown attacks that exploit vulnerabilities in this protocol. This requirement applies to Transport Layer Security (TLS) gateways (also known as Secure Sockets Layer [SSL] gateways), web servers, and web applications and is not applicable to virtual private network (VPN) devices. Application protocols such as HTTPS and DNSSEC use TLS as the underlying secu...
Fix Text (Documentation Requirement)
Consult Microsoft documentation and ensure the .Net Framework on Compliance Guardian servers is a version that supports TLS 1.2. Update if necessary. Configure the Compliance Guardian servers to enable TLS 1.2 protocol only. - On the Compliance Guardian servers, open "Registry Editor". - Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols. - Disable TLS 1.0, TLS 1.1, and any SSL protocols, if present. Configure the Compliance Guardian servers to enable strong cryptography settings. - On the Compliance Guardian servers, open "Registry Editor". - Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319 and verify: "SystemDefaultTlsVersions" = dword:00000001 "SchUseStrongCrypto" = dword:00000001