Email Security - Server (EX) 11.0.1 Release Notes

Prev Next

New features and changes

This section describes new features in the Trellix Email Security - Server release 11.0.1.

  • New virtual appliance for integrated deployments: model EXintgV

    A new virtual system is introduced for Email Security - Server, model EXintgV. This appliance is designed for integrated mode deployments and supports 8-64 GB of RAM, 1-4 TB of disk space, and 4 network interfaces.

  • VM count in EXintgV models

    In Email Security - Server integrated virtual systems, the show version command will now display the maximum running licensed and configured virtual machines.

  • New columns added to Email Quarantine

    • On the Email Quarantine page, you can now view the malicious URLs found in the message or its attachments as well as the MD5 hashes of the email's attachments in the URL and MD5 columns respectively.

    • You can now click the cog icon in the Action column to view the contents of an email or download a copy of the email.

  • View and Download Clean and Riskware Emails

    Starting from release 11.0.1, the Search Email tab now provides the option to View and Download Clean and Riskware emails. Previously, the view option was restricted to malicious emails within the eQuarantine > eAlerts tab.

    Note

    • This feature is available only when the appliance is operating in Block/Drop mode.

    • Access to the view and download functions is restricted to Admin users.

    • For Clean emails exceeding 2 MB, a download link will be provided instead of a direct in-browser view.

  • Option to view processed emails

    You can now use the View Email action on the Processed Emails page to inspect clean emails, with a toggle to switch between a Parsed and Raw view. Use the following CLIs to manage clean emails:

    • Configure the number of days to retain clean emails.

      email-analysis clean-emails keep days <1 - 90>

    • Enable or disable retaining of clean emails.

      [no]<email-analysis clean-emails keep enable>

    • Configure the amount of storage for clean emails in gigabytes

      email-analysis clean-emails keep size <1 - 250>

      You can view the above settings using show email-analysis

  • Delete all added regex being whitelisted

    You can now delete all added regex entries at once when they are in large numbers, using the CLI no email-analysis adv-url-defense rewrite whitelist.

    • To delete added regex entries individually by using their UUIDs through the CLI

      no email-analysis adv-url-defense rewrite whitelist <UUID>

    • To allow users to delete ALL added regex entries at once, eliminating the need for individual deletion

      no email-analysis adv-url-defense rewrite whitelist

  • Sender-based tracking protection

    You can now defang URLs as a part of sender based tracking protection using the CLI [no] email-analysis policy tracking-protection defang enable.

  • Configuring DUA object size

    You can now configure the DUA downloadable object size using the CLI, analysis file max-size dua-file <size>. The default limit of 128 MB has been removed. You can select a size between 1 to 1024 MB. You can also perform static analysis on the partially downloaded objects.

  • FLOSS artifacts updates on eAlerts page

    On the eAlerts page, FLOSS will be shown in the Artifact column whether it is enabled or not. FLOSS artifacts are disabled by default. Disabled FLOSS artifacts will not be displayed in the following situations:

    • On expanding the alert details

    • Inside a triage bundle

    • On downloading artifacts from the API

    Use the following CLIs to configure FLOSS artifacts.

    • [no] analysis artifact floss enable: Enable or disable FLOSS artifact

    • show analysis artifact floss: Display FLOSS artifact

  • Bulk configuration on Health Services tab

    In the Health Services tab, you can select the newly added check box to enable or disable all services/notifications in bulk.

  • LDAP client update

    The LDAP client now supports the automatic fetching of Certificate Revocation Lists (CRLs), along with existing manual updates feature.

  • Synchronization with TAXII

    The TAXII client within the appliance is now correctly routed through the Fenet proxy (if configured), allowing for successful synchronization with the TAXII server.

  • WebUI support to release Quarantined Emails by MD5 or URL

    The EX WebUI now provides the functionality to release quarantined emails using a URL or MD5 hash, significantly improving incident response workflow. This capability was previously exclusive to the command-line interface (CLI) in version 11.0.0.

  • Enhanced mutual TLS (mTLS) support for next-hop mail

    You can now configure the underlying MTA for client-side mutual TLS (mTLS) for next-hop emails. Use the CLI, email-analysis mta options mtls-request-cert, to enable the EX appliance to send its client certificate to a downstream MTA during the STARTTLS SMTP command handshake, facilitating mTLS.

    To use this feature, valid root/intermediate CA certificate, client certificate and client’s private key must be present on the appliance. Also, both the Trellix appliance and the receiving MTA require valid certificates for a successful connection.

    To disable the requirement, use [no]email-analysis mta options mtls-request-cert. The MTA will not request a client certificate allowing standard, one-way TLS connections where only the server's certificate is validated.

Enhancements

This section describes the enhancements implemented in the Trellix Email Security - Server release 11.0.1.

  • TLS 1.3 Support for Appliance Management

    The appliance base components have been upgraded to fully support TLS 1.3 for management protocols, including the web management interface. This enhancement enforces access rules when Web Client Certificate Authentication is enabled, client certificates are now required for all WSAPI calls, and there is no fallback to other authentication methods for Web Portal access.

  • Support local time streaming for events

    The streamingd service now supports the configuration of event timestamps to reflect the local time zone set on the appliance, rather than the default Coordinated Universal Time (UTC).

    • datastreaming submission local-timestamp enable - Enable the streaming of event timestamps in the appliance's local time zone.

    • no datastreaming submission local-timestamp enable - Revert the streaming of event timestamps back to the default UTC format.

    • show datastreaming submission - View the status of this new "Streaming in Local Time" feature, use existing CLI.

  • Enhanced data streaming configuration guidance for TLS Syslog

    You can now follow updated guidance for configuring secure (SSL/TLS) syslog for data streaming. This guide provides the specific settings required to ensure your TLS syslog server (typically on port 6514) is compatible with the standard RFC 5424 format.

    • datastreaming configuration protocol rsyslog consumers <consumer-name> output-type Syslog-TLS: Specifies that the data stream consumer will use the secure Syslog-TLS protocol for output.

    • datastreaming configuration protocol rsyslog consumers <consumer-name> msg-style ietf: Ensures the syslog messages are formatted according to the IETF standard (RFC 5424).

    The CLI, datastreaming configuration protocol rsyslog consumers <consumer-name> ssl ca-list <option>, now has updated CA list options:

    • builtin-only: no supplemental list, can only use built-in one.

    • default-ca-list: default supplemental CA certificate list.

    • undefined: Implements dynamic logic to determine inclusion/exclusion automatically.

    • based on context: For example, configuration defaults to default-ca-list when SSL is disabled.

  • Enhanced certificate authority (CA) list configuration for TLS Syslog

    You can now use enhanced configuration options for managing Certificate Authority (CA) lists when setting up secure (SSL/TLS) rsyslog consumers. This update provides greater control and introduces a dynamic default behavior for including CA certificates.

  • Log manager updates

    The Upload option on the Log Manager page used to upload archived files has been removed.

  • Modified commands

    • The show email analysis command now displays the retention policy for clean emails, including its current status and configured storage limit.

    • You can now delete the entire URL rewrite whitelist, including all RegEx patterns and whitelisted domains, with a single command, [no] email-analysis adv-url-defense rewrite whitelist.

    • In Email Security - Server integrated virtual systems, the show version command now displays the maximum running licensed and configured virtual machines.

    • The configuration jumpstart command now supports both pure IPv6 and dual-stack (IPv4/IPv6) configurations, enabling successful deployment in IPv6-only environments.

    • The output for show analysis config now displays the maximum size of a DUA downloadable object.

Resolved Issues

The following issues were resolved in the Email Security - Server 11.0.1 release.

Tracking number

Summary

COM-62386

Fixes the issue where the appliance included a version of the python3 idna software module associated with CVE-2024-3651. The module is now updated to a non-vulnerable version. This proactively addresses the potential vulnerability even though the appliance did not use the specific vulnerable function.

COM-63130

Removed the diffie-hellman-group14-sha1 Key Exchange (KEX) cipher from our supported CC and FIPS cipher lists.

COM-63373

Fixed the vulnerability CVE-2022-27406 issue by updating the FreeType library

COM-63390

Resolved an issue that caused slogin connections from CMS to other appliances to immediately disconnect after upgrading to version 11.0.

COM-63502

Fixed the autocomplete issue where the autocomplete function is disabled on all password fields to prevent browsers from automatically saving and filling in sensitive data.

COM-63513

Resolved an issue where an error response during login attempts exposed an internal system path.

COM-63528

Resolved an issue where the Email Security - Server appliance's management interface (ether1) was incorrectly attempting to establish connections for sandbox analysis.

COM-63549

Resolved an issue that prevented users from logging in to the PKI/CAC server after upgrading to version 11.0.0.

COM-63695

Resolved an issue where upgrading to v11.0.1 with CC/FIPS+CC enabled caused the appliance to incorrectly report "No" for overall compliance mode. The issue was due to the "LDAP CRL Autofetch" rule not being met.

COM-63703

Resolved an issue where upgrading a CC/FIPS+CC enabled cluster to Abbot-MR1 would incorrectly report a "No" for overall compliance mode. This was due to the "LDAP Certificate SAN RFC-6125" rule not being met.

EMPS-17213

EMPS-18352

On upgrading to 11.0.0, Alert summary count and redirection counts are not consistent for Total Malicious Emails, Malicious URLs, and Malicious Attachments.

EMPS-18295

Fixes an issue where the password in the Remediation settings was unmasked when viewed in the Inspect column.

WEBUI-14964

Fixes an issue in the 3rd Party Feeds tab where any file with STIX type could be uploaded. Now an error occurs on uploading invalid files.

WEBUI-15060

Fixes a missing logs issue on the Create Log Archive page. A message appears on creating a log archive. Also, a success message is displayed when the log archive is created succesfully.

Known issues

The following issues are known in the Email Security - Server 11.0.0 release.

Tracking number

Summary

COM-63593

Upgrading to version 11.0.1 from version 9.1.5 fails to migrate custom MD5 and SHA-256 blacklisted entries.

COM-30656

The negation symbol "!" is not functioning as expected when placed before the hostname or username in the deny user list.

COM-31165

The GI settings API does not currently enforce a limit of 10 inputs for a field.

COM-63612

Threat-information badges may not appear on alerts, even when the hash qualifies the bloom filter.

COM-63635

Compliance mode appliances are logging too much noise with SSL_ERROR_WANT_READ informational status.

COM-63642

COM-63684

FLOSS artifact will be displayed in the Artifact column on eAlerts page whether the FLOSS is disabled or not.

EMPS-17745

Submitting duplicate mdsum, sha256, or URL values to allowed and blocked lists via the Web UI and CLI results in inconsistent output.

EMPS-17820

The downgrade of Email Security - Server to a previous release resulted in the loss of data configured on the "Advanced Rule" tab of the current release.

EMPS-18602

Exchange remediation requests fail to go through the proxy as expected.

EMPS-18682

Following the upgrade to Abbot 11.0.1, a mismatch has been identified between the statistics for Malicious URLs and Total Malicious Emails.

WEBUI-14979

The Service Health Statistics Trend incorrectly displays date and time for weekly and monthly reports.

WEBUI-29818

Introduced a loading indicator for third-party feeds within the Allow/Block lists to enhance user comprehension of data availability status.

WEBUI-30212

When certificate authentication is enabled, deleted certificates reappear after the page is reloaded.

WEBUI-30229

The Alert Summary widget on the Dashboard displays the Malicious URL count based only on body URLs.

Additional information

Disable SAML in a Helix environment

SAML and HelixConnect are mutually exclusive. If the HelixConnect client is enabled on the Email Security - Server appliance, you must disable SAML authentication and authorization. Otherwise, the appliance will not come up after a system reboot.

For more information, see the

Helix Integration Guide for Trellix devices

.

  • In the Software Requirements section, see “HelixConnect Client Software Requirements”.

  • In the HelixConnect Troubleshooting section, see “Disabling SAML Authentication and Authorization”.

Upgrade support

The Trellix Email Security - Server 11.0.1 release requires a reboot for the update to take effect. You can upgrade your EX appliance to 11.0.1 from release 9.1.0 or later.

Created Log archive files on 9.1.x will not be preserved on upgrade to 11.0.1. Please have a backup of logs before upgrade.

Important

When you upgrade an Email Security appliance to 11.0.1, FireEye Advanced URL Defense Engine (FAUDE) and email feature extraction are enabled, even if they were previously disabled. See "Enabling or Disabling Advanced URL Defense" and "Enabling or Disabling Email Feature Extraction Using the CLI" in the

Email Security — Server Edition User Guide

.

Note

After an upgrade to version 11.0.1, certain processes will be in a pending state until new security content is downloaded and installed. See the following section, "Download the security content bundle".

Important

When upgrading an X500 EX running in FIPS/CC compliance mode to version 11.0.1, you must reapply the compliance mode immediately after the upgrade. Use the CLI command compliance apply standard <standard name> and save the configuration using the CLI write memory.

After reapplying compliance mode, ensure that any necessary compliance options overrides are reasserted as needed. In rare instances, the appliance may become unresponsive before compliance can be applied. If this occurs, the appliance may need to be power cycled.

Download the security content bundle

After the upgrade, certain processes will be in a pending state until new security content is downloaded and installed. The security content is downloaded and installed automatically for online customers. Offline customers must manually download and install the new security content after upgrading appliances to release 11.0.1.

Downloading content from the DTI offline update portal

If you download Email Security - Server 11.0.1 security content from the DTI Offline Update Portal, use the SCNET-9.0 channel of the portal.

Caution

Downloading security content from a different channel will result in a loss of detection.

For details, see the Trellix DTI Offline Update Portal User Guide.

YARA rules supported versions

YARA rules support version 4.5.0.

Important

Before you upgrade an Email Security - Server appliance to the 11.0.1 release, modify any custom YARA rules to YARA 4.5.0. For details about YARA 4.5.0, see YARA's Documentation, Release 4.5.0 by Victor Alvarez.