XDR Network Security Virtual Appliance

Internal fixes.

Security fixes.

Updated third party libraries for better communication with GravityZone.

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

The network sensor is only going to allow one configured monitored network address per appliance. This is needed to ensure that the detections generated by this sensor are accurate. Existing network sensor configurations that have already been deployed are not going to be affected by this change.

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.

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.

Reduced the network traffic consumption of the Network Probe module.

Fixed an issue that caused the XDR Network Security Virtual Appliance services to run before the network module.

You can now add multiple subnets for the monitoring interface.

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

The default Dynamic Host Configuration Protocol (DHCP) client has been removed from the Switched Port Analyzer (SPAN) network. To accommodate this, the Security Server setup has been modified.

The XDR Network Security Virtual Appliance has been integrated into the GravityZone Sensors Management.

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

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.