Bitdefender enforces HTTPS protocol for Security Server updates

Starting July 30th 2020, Bitdefender enforces in GravityZone the use of the HTTPS protocol for Security Server updates from Bitdefender fallback update servers. The fallback location of Bitdefender update servers will only be accessible via HTTPS.

GravityZone Cloud

HTTPS enforcement affects Bitdefender Security Server (Multi-Platform), GravityZone services like Security for Virtualized Environments (SVE) and Security for Storage, and the behavior of the Use Bitdefender Public Update Server as fallback option from the General > Update section in the policy settings.

To comply with this change, make sure that your network firewalls allow traffic to the following addresses:

This change does not affect Security Server updates from Bitdefender Endpoint Security Tools with Relay role.

No security policy reconfiguration is required.

GravityZone On-premises

HTTPS enforcement affects all Bitdefender Security Servers (Multi-Platform, NSX-T and NSX-V) and GravityZone services like Security for Virtualized Environments (SVE) and Security for Storage, and the behavior of the Use Bitdefender Public Update Server as fallback option from the General > Update section in the policy settings.

To comply with this change, make sure that your network firewalls allow traffic to the following addresses:

This change does not affect Security Server updates from local Bitdefender update servers, such as GravityZone virtual appliance with Update Server role and Bitdefender Endpoint Security Tools with Relay role.

No security policy reconfiguration is required.