Security Server Multi-Platform

Internal fixes.

Internal fixes.

Addressed an issue that caused the Update Task to generate inconsistent responses in GravityZone when the update to the Security Server failed.

Security fixes.

Internal fixes.

Security fixes.

Improved resource usage when sending product status notifications to GravityZone.

Updated third party libraries for better communication with GravityZone.

Improved the resource usage when sending product status notifications to GravityZone.

Addresses an issue with configuring static IPs for network interfaces when their names were different than eth0.

Fixed an issue where the Security Server was not automatically updated when the root password expired.

Added support for Open SSL version 1.1.1t.

Fixed an issue that caused the Internet Content Adaptation Protocol (ICAP) to disconnect due to the limited number of connections to the Security Server. The limit has been increased.

Improved resource usage on the Security Server when network connectivity problems occurred on Bitdefender Endpoint Security Tools while running Central Scan.

The JSON parsing issues during UTF-16 encodings have been fixed.

The password security requirement has been increased. It must contain at least 8 characters, one digit, at least one upper case character, at least one lower case character, one special character and must be changed every 3 months.

The thick provisioning pre-allocation storage for Security Server Multi-Platform has been set to 40 GB.

You can now download the Microsoft Hyper-V Gen 2 Security Server image from GravityZone.

The number of concurrent connections per client IP has been limited to reduce denial-of-service and distributed denial-of-service attacks.

Fixed an issue that prevented the OS Upgrade Task status from being updated in GravityZone.

Fixed an issue that caused floppy disk kernel errors to be displayed in System logs.

Fixed a proxy configuration issue in the setup interface.

Fixed an issue that prevented the Communication Server from being configured.

Fixed an issue that prevented the GravityZone loopback IP address from being displayed correctly for the Security Server role.

Security fixes.

Applied the changes to reflect the new Company hash label, formely known as Company ID. For more information, refer to Release notes for GravityZone Cloud version 6.26.2-2.

Added an additional local interface in the the Security Server console. You can use this interface to view more information about the Security Server, as well as configuring it without using the sva-setup command.

Fixed an issue that prevented DNS entries from remaining saved after a reboot.

Fixed an issue that prevented the applied HVI policy from being displayed.

Fixed an issue that caused the ubuntu user to be overwritten during a manual installation.

Fixed an issue that caused DNS entries to change after a Security Server reboot.

Fixed an issue that prevented the Security Server role from being installed on GravityZone, when it was deployed on Amazon AWS or Azure.

The Communication Server configuration options have been renamed to better reflect the used Cloud instances, based on your browser's URL:

When you configure the Communication Server parameters on the Security Server for GravityZone Cloud, you can select your cloud region from a drop-down menu.

Some Security Server have lost their static DNS configuration. If you have encountered this issue, use the sva-setup command to manually correct them.