New features
This Trellix Intrusion Prevention System release does not include any new features.
Enhancements
This Trellix Intrusion Prevention System release includes the following enhancements:
Enhanced security measures for proxy-based SSL/TLS decryption
Starting with this release of 11.1, enhanced security measures have been implemented to bolster both inbound and outbound proxy-based SSL/TLS decryption. The new features include the following:
IPS-VM5000-SSL, IPS-VM600-SSL, and IPS-VM600-VSS-SSL Sensors are introduced for virtual and cloud deployments.
Support for jumbo frame parsing.
SSL decryption exclusions apply to both inbound and outbound SSL decryption.
Support for 4096-bit RSA and up to 521-bit ECDSA certificates.
Note
The re-signing CA certificate must be created for server authentication and added to the browser as a trusted authority without purpose limitations.
The "Outbound" Block Flow configuration will apply to "Inbound" and may block inbound flow if an internal web server uses expired/untrusted CA certificates. Thus, an exception rule with the specific internal web server IP should be added to allow inbound flow without decryption when block flow is configured.
Once Inbound proxy is enabled, all Inbound traffic will be decrypted; However, it is recommended to create a proxy rule for Inbound SSL decryption.
License requirements for proxy-based SSL decryption
Model | System license | SSL license | Virtual license |
|---|---|---|---|
IPS-VM5000-SSL, IPS-VM600-SSL, and IPS-VM600-VSS-SSL Sensors | NA | NA | Requires one or more SSL-enabled virtual Sensor licenses (IPS-VM1000-SSL-CLD-SUB) depending on the Sensor or cluster capacity. Example:
|
For more information, see Managing licenses for proxy based SSL decryption in Trellix Intrusion Prevention System 11.1.x Product Guide
Supported models and platforms
The following table lists the supported models and platforms for the proxy-based inbound and outbound SSL decryption:
Models | Platform |
|---|---|
IPS-VM5000-SSL and IPS-VM600-SSL | ESX and KVM |
IPS-VM600-VSS-SSL | AWS and Azure |
Important
IPS-VM5000-SSL, IPS-VM600-SSL, and IPS-VM600-VSS-SSL Sensors are compatible with signature set version 11.10.28.4 and above.
A new command show ssl proxy is included to support the SSL enhancements.
For more information, see SSL decryption support for NS-series and Virtual IPS Sensors in Trellix Intrusion Prevention System 11.1.x Product Guide
Support for SMB and DCERPC layer 7 data collection and SmartVision attack related L7 metadata and alerts export to Trellix Network Investigator
Starting with this release of 11.1, Trellix IPS supports collecting layer 7 data for SMB (SMBv1 and SMBv2) and DCERPC protocols (over TCP). It also exports the SmartVision attack related L7 metadata related to these protocols from IPS Sensors and alerts from IPS Manager, when the integration between Trellix IPS and Trellix NI is enabled. The SmartVision alerts and L7 metadata collected for SMB and DCERPC protocol traffic and exported to NI further enhances its SmartVision capabilities for detecting malicious activities, such as malware lateral movement, data exfiltration, and beaconing.
Consider the following if you want to enable the detection and export of SmartVision attacks related L7 metadata and alerts related to SMB and DCERPC protocols to NI:
You need to use Manager and Sensor(s) running on 11.1 Update 8 and later, along with a compatible signature set (11.10.28.4 and above) that includes SMB and DCERPC related attack signatures.
Manager running on 11.1 Update 8 and later includes additional L7 data fields for SMB (under the netbios-ss section) and DCERPC protocols in the → → → → → → page. These L7 fields related to SMB and DCERPC protocols are applicable only for Sensors running on 11.1 Update 8 version or later and can be customized accordingly.
Note
DCERPC L7 data collection is supported over TCP only.
When Trellix IPS and Trellix NI is integrated, Manager sends all relevant alert data (including SmartVision attacks) to NI. For SMB and DCERPC protocols, Sensors running on version 11.1 Update 8 or later send only SmartVision attack-related L7 metadata to NI.
For more information on layer 7 data collection, see Enable Layer 7 Data Collection for an interface or sub-interface in Trellix Intrusion Prevention System 11.1.x Product Guide.
For more information on SmartVision attacks, see Harnessing SmartVision attacks for effective threat detection and response in Trellix Intrusion Prevention System 11.1.x Product Guide.
Configuring and managing packet capture rules for member Sensors in the cloud cluster
Starting with this release of 11.1, you can configure and manage packet capture rules for member Sensors directly from the Devices tab.
Configure packet capture: Go to → → → → → → → → .
Manage captured file: Go to → → → → → → → → .
You can also view the summary details for a selected member Sensor from the Devices tab. Go to → → → → → → .
For more information, see View member Sensor summary details in Trellix Virtual Intrusion Prevention System 11.1.x Product Guide.
Database pruning enhancements in the Manager
With this release of 11.1, a few enhancements have been made in the Trellix IPS Manager to speed up and optimize the task of database pruning. From this release onwards, the Manager creates and maintains a separate (active) partition for iv_alert_data, iv_alert, and iv_packetlog tables that stores alert and packet log data based on user configuration (that is, number of days or number of alerts configured). When the alert pruning activity is triggered (as per the configuration performed on → → → → page), all data is deleted at once, thus speeding up the database pruning process.
Support for script files for advanced malware detection
Starting with this release of 11.1, Trellix IPS supports script files to be scanned while configuring an advanced malware policy. It is available for configuration under the File Scanning Options section in the → → → → page. To know the list of advanced malware file extensions supported by signature sets, refer to KB96988.
After configuring the advanced malware policy, you need to assign it to the required Sensor monitoring resources such as ports, interfaces, and sub-interfaces. You must do a configuration and signature set update for any changes in the policy to take effect.
For more information, see Add an Advanced Malware policy in Trellix Intrusion Prevention System 11.1.x Product Guide.
Enhancements around SSL key push failure in the Manager
Previously, the reason for SSL key push failure was undetermined. With this release of 11.1, a thorough analysis revealed that the failures were due to missing or corrupted certificates. Additionally, SSL key push would fail when a new shared secret key was issued. This enhancement provides a clear resolution in the Manager, displaying the reason for the SSL key push failure.
For more information, see Deploy pending changes to a device in Trellix Intrusion Prevention System 11.1.x Product Guide.
Enhanced support for latency troubleshooting
With this release of 11.1, Trellix IPS introduces a significant improvement to latency troubleshooting, providing a streamlined solution for diagnosing performance-related issues. It addresses common latency-related problems such as slow application response, packet drops, network slowdowns, and delayed file transfers/database operations.
You can use the latency-troubleshooting command to add, delete, list the configured commands, modify the frequency of execution, and collect logs from the trace in debug mode.
The following commands are available:
Parameter | Syntax | Description | |
|---|---|---|---|
start |
| Start latency troubleshooting | |
status |
| Check the current status of latency troubleshooting | |
stop |
| Stop latency troubleshooting | |
command | add |
| Add a command to the list |
delete |
| Delete a command from the list | |
list |
| Lists all added commands | |
run |
| Run latency troubleshooting once | |
set | frequency |
| Modify the frequency of run |
rollover_limit |
| Sets the number of logs to retain | |
For more information, see latency-troubleshooting in Trellix Intrusion Prevention System 11.1.x Product Guide
Terminology updates in the UI
Navigation Path | Prior to 11.1.7.121 | 11.1.7.121 and later |
|---|---|---|
→ → | The Synchronize Policies menu Policy tab shows the synchronization status for all the Managers added to your Central Manager. | The Policy tab from → → → shows the synchronization status for all the Managers added to your Central Manager. |
→ → | The Synchronize Faults menu from → → → allows automatic synchronization of faults between the Managers and the Central Manager. | The Faults tab from → → → allows automatic synchronization of faults between the Managers and the Central Manager. |
→ → → | On clicking
| On clicking
|
→ → → |
|
|
→ → → | One of the fields available is User Name. | The field is renamed to Login Name. |
→ → → | The Preferences page includes the following:
| The Preferences page includes the following:
|
→ → → | During the configuration of any report:
| During the configuration of any report:
|
→ → → |
|
|
→ → → | A note regarding customized message appears in the Message Preference field. | A tooltip regarding customized message appears in the Message Preference field. |
Apart from the terminology updates mentioned above, this release of Manager (11.1.7.121 and later) displays the following changes:
The following pages have been removed, and consequently, all associated UI configuration options, buttons, and related dashboards have been removed from the other pages in the Manager:
Network Forensics page (in → )
Endpoint Executables page (in → )
NTBA Quarantine Events page (in → → → )
Related dashboards that have been removed: Top Applications (NTBA), Top Destinations (NTBA), Top Endpoint Executables (NTBA), Top Files (NTBA), Top Sources (NTBA), and Top URLs (NTBA).
The Reconnaissance Policy configuration report has been removed from → → → page.
Updated platform, environment, or operating system support
This release provides the following enhancements related to platforms, environments, or operating systems:
Apache Solr upgrade
Starting with this release, the IPS Manager uses Apache Solr version 8.11.4 that includes additional security against new vulnerabilities and bug fixes.
JDK upgrade
Starting with this release of 11.1, the IPS Manager uses JDK version 1.8u432-b06 which includes additional security against new vulnerabilities.
Apache Tomcat server upgrade
Starting with this release of 11.1, the Tomcat server used in the Manager is upgraded to version 9.0.102. This server update provides a collection of security fixes.
.png)
.png)
.png)
.png)
.png)