What's new in the 10.0 release Releases can introduce new features and enhancements or update platform support. Note: McAfee® Web Gateway 10.0 is provided as a controlled release. For information about how to install it, see the McAfee Web Gateway Installation Guide. Use of ICAP server supported in Proxy HA mode When Web Gateway has been set up in Proxy High Availability (HA) mode, use of ICAP servers for processing web traffic can also be configured in this network mode. For more information, see the Proxy HA mode section in the Proxies chapter of the McAfee Web Gateway Product Guide. New authentication and encryption methods for SNMP configuration When users are set up that are allowed to view monitoring information provided under SNMPv3, new methods can be configured for authenticating these users, as well as new methods for encrypting the information. A hash value for use in authenticating users can now be calculated using one of the following digests in addition to the existing: SHA-224, SHA-256, SHA-384, and SHA-512. Information can be encrypted using one of these ciphers in addition to the existing: AES-128, AES-192, and AES-256. The net-snmp package has also been updated. Note: Due to implementing a solution to an issue with the engine IDs that are provided as part of the SNMP information, existing engine IDs have changed for all Web Gateway appliances that have SNMP configured. For more information, see the Event monitoring with SNMP section in the Monitoring chapter of the McAfee Web Gateway Product Guide. New VMware version for virtual appliances A new version of the VMware that is used when Web Gateway is run as a virtual appliance is now supported. This version is ESXi 7.0. For more information, see the System requirements for a virtual appliance section in the System requirements chapter of the McAfee Web Gateway Installation Guide. New Luna client version for use in HSM solution The version of the Luna client that is used as component when a Hardware Security Module (HSM) solution is implemented to run along with Web Gateway to protect private certificate keys has been updated. The new version is 7.4. The driver that is required for this solution has also been updated. For more information about the HSM solution, see the Hardware Security Module section in the Web filtering chapter of the McAfee Web Gateway Product Guide. New version of DLP/CSF filter The DLP/CSF filter that is used on Web Gateway in preventing data leakage has been updated. Extraction of DMG files improved When handling DMG files with unused sectors, the Composite Opener module on Web Gateway no longer extracts these sectors, avoiding unnecessary filling up of the opt partition and memory allocation failures. Caching of Geo Location lookups improved Retrieving information on Geo Location through GTI lookups when requests are processed on Web Gateway has been improved by modifying cache behavior. Range of detected media types extended A media type that includes what is known as symbolic files has been added to the range of types that are detected and can be used in media type filtering rules. This media type is: application/sylk. Security for HTTPS logon to user interface enhanced The default TLS version and SSL cipher string have been updated to make HTTPS logon to the Web Gateway user interface even more secure. More secure algorithms for calculating hash values implemented Several SSH and other packages with improved algorithms have been implemented on Web Gateway to make calculating hash values that are used for authenticating users more secure. Additional self-tests run after starting an appliance Several new self-tests are run after a Web Gateway appliance is started in order to check system integrity and stability. This includes the following tests: CPU spike check System Crash check File integrity check MWG service check CPU temperature check (on a physical appliance only) System Fan check (on a physical appliance only) The test reports are generated and stored at /opt/mwg/log/debug/mwg-boot-test.log. File integrity failures are reported at /opt/mwg/log/debug/validate.log. Logging process improved Additional items related to logging have been implemented on Web Gateway as follows: Values of all request and response headers involved in processing web traffic can now be retrieved and stored for use in logging rules. Two new properties of the string type have been created, which can be used for this purpose, as well as for others where request and response headers are involved. Error logging for calls of /usr/bin/event has been added for the Web Gateway user interface. Names of failed processes with their exit values as well as failures to retrieve exit values are now logged.