--- title: "Configuring event filter rules" slug: "configuring-event-filter-rules" tags: ["Product Usage", "EX 11.x", "FX 11.x", "AX 11.x", "NX 11.x", "Network Security"] updated: 2026-09-12T20:42:26Z published: 2026-09-12T20:42:26Z canonical: "docs.trellix.com/configuring-event-filter-rules" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Configuring event filter rules This section covers the following information: - [Configuring event filter rules using the Web UI](/network-and-platform/docs/configuring-event-filter-rules-using-the-web-ui) - [Configuring event filter rules using the CLI](/network-and-platform/docs/configuring-event-filter-rules-using-the-cli) ### About event filter rules When you enable integration between Helix and the Network Security appliance, the appliance passes events to Helix for further analysis. If you have events that you do not want to analyze further, you can set event filter rules so that events that match the filter criteria are not sent to Helix. Several event filter rules are set by default and you can add custom event filter rules. You can delete default and custom rules if you want to stop filtering out the events affected by those rules. You can configure event filter rules using the CLI or API. For information on using the API, see the *Trellix API Reference Guide*. ### Usage guidelines Follow these usage guidelines when you configure the event filter rules: - A maximum of 64 custom filter rules can be configured for each event type. - A back slash (\) in a regular expression is always the escape character. ### Prerequisites - Administrator or Operator access to the Network Security appliance - A connection to the Dynamic Threat Intelligence (DTI) Cloud - An active subscription to Helix - Verify that you have specified a valid hostname for the VPC within an AWS endpoint. For details about how to configure the VPC within an AWS endpoint, see [Configuring the VPC within an AWS endpoint using the Web UI](/network-and-platform/docs/configuring-the-vpc-within-an-aws-endpoint-using-the-web-ui) or [Configuring the VPC within an AWS endpoint Using the CLI](/network-and-platform/docs/configuring-the-vpc-within-an-aws-endpoint-using-the-cli) . The following table lists the event types and some of the associated filter fields. | Event Type | Description | Filter Field Examples | | --- | --- | --- | | `http` | HTTP events | `http.hostname` `http.url` `http.http_user_agent` | | `smtp` | SMTP events | `smtp.mail_from` `email.status` | | `dnp3` | DNP3 events | `dnp3.type` `dnp3.control.dir` `dnp3.control.pri` `dnp3.control.fcb` `dnp3.control.fcv` `dnp3.control.function_code` `dnp3.src` `dnp3.dst` `dnp3.application.control.fir` `dnp3.application.control.fin` `dnp3.application.control.con` `dnp3.application.control.uns` `dnp3.application.control.sequence` `dnp3.application.function_code` `dnp3.application.complete` | | `dns` | DNS events | `src_ip dns.rrname` `src_port` `dest_ip` `dest_portdns.rdata` `proto` `dns.version` `dns.type` `dns.id` `dns.flags` `dns.qr` `dns.rd` `dns.ra` `dns.rrname` `dns.rrtype` `dns.tx_id` `dns.tx_id` `dns.rcode` `dns.ttl` `dns.rdata` `answers.rrname` `answers.rrtype` `answers.ttl` `answers.rdata` | | `dcerpc` | Distributed Computing Environment Remote Procedure Call (DCE-RPC) events | `dcerpc.interface.uuid` `dcerpc.interface.version` `dcerpc.interface.minor-version` | | `fileinfo` | File information events | `fileinfo.filename` `fileinfo.md5` `fileinfo.stored` | | `flow` | Flow events | `app_proto` `flow.pkts_toserver` `flow.pkts_toclient` | | `imap` | Internet Message Access Protocol (IMAP) events | `email.status` `email.from` | | `pop3` | POP3 (Post Office Protocol) events | `email.status` `email.from` | | `irc` | Internet Relay Chat (IRC) events | `irc.user` `irc.prefix` `irc.cmd` | | `modbus` | Modbus events | `modbus.transaction_id` `modbus.protocol_id` `modbus.unit_id` `modbus.function_code` `modbus.function_category` `modbus.exception_code` `modbus.diag_subfunction` `modbus.mei` `modbus.response` `modbus.read.address` `modbus.read.quantity` `modbus.write.address` `modbus.write.quantity` `modbus.write.count` | | `rdp` | Remote Desktop Protocol (RDP) events | `src_ip` `src_port` `dest_ip` `dest_port` `proto` `rdp.event_type` `rdp.client.version` `rdp.client.desktop_width` `rdp.client.desktop_height` `rdp.client.color_depth` `rdp.client.keyboard_layout` `rdp.client.build` `rdp.client.client_name` `rdp.client.keyboard_type` `rdp.client.function_keys` `rdp.client.product_id` `rdp.client.capabilities` `rdp.client.id` `rdp.channels` | | `rtsp` | Real Time Streaming Protocol (RTSP) events | `rtsp.request.type` `rtsp.request.accept` `rtsp.response.content_type` | | `smb` | Server Message Block (SMB) events | `smb.command` `smb.command_str` `smb.status` | | `smb2` | SMB2 events | `smb2.status` `smb2.session_setup.type` `smb2.session_setup.authenticate.domain` | | `ssh` | Secure Shell (SSH) events | `ssh.client.proto_version` `ssh.client.software_version` `ssh.server.proto_version` | | `ftp` | File Transfer Protocol (FTP) events | `ftp.user` `ftp.pass` `ftp.port` | | `tls` | TLS events | `tls.subject` `tls.version` `tls.notbefore` | | `mysql` | MySQL events | `mysql.command` `mysql.arguments` `mysql.success` `mysql.rows_affected` `mysql.response_error` | | `krb5` | Kerberos (KRB5) events | `krb5.request_type` `krb5.client` `krb5.client_realm` `krb5.server` `krb5.server_realm` `krb5.from` `krb5.till` `krb5.cipher` `krb5.forwardable` `krb5.renewable` `krb5.success` `krb5.error_code` | | `socks` | SOCKS events | `socks.ver4.request.command` `socks.ver4.request.remote_port` `socks.ver4.request.remote_address` `socks.ver4.request.username` `socks.ver4.request.remote_V4A_domain_name` `socks.ver4.response.result` `socks.ver4.response.port` `socks.ver4.response.address` `socks.ver5.request.method_count` `socks.ver5.request.method_0` `socks.ver5.request.method_1` `socks.ver5.request.method_2` `socks.ver5.request.method_3` `socks.ver5.request.method_4` `socks.ver5.request.method_5` `socks.ver5.request.method_mismatch` `socks.ver5.request.username_length` `socks.ver5.request.username` `socks.ver5.request.password_length` `socks.ver5.request.password` `socks.ver5.request.command` `socks.ver5.request.address_type` `socks.ver5.request.remote_address` `socks.ver5.request.remote_port` `socks.ver5.request.remote_name` `socks.ver5.request.remote_name_length_field` `socks.ver5.request.remote_name_length` `socks.ver5.response.accepted_method` `socks.ver5.response.unexpected_method` `socks.ver5.response.status` `socks.ver5.response.result` `socks.ver5.response.address_type` `socks.ver5.response.remote_name_length` `socks.ver5.response.remote_address` `socks.ver5.response.remote_port` | | `all` | All event types | None | | `radius` | RADIUS (Remote Authentication Dial-In User Service) events | `radius.request.code` `radius.request.username` `radius.request.remote.ip` `radius.request.remote.port` `radius.request.remote.port.type` `radius.request.remote.port_id` `radius.request.service_type` `radius.request.Called_MAC` `radius.reply.code` `radius.success` | | `dhcp` | DHCP events | `src_ip` `src_port` `dest_ip` `dest_port` `proto` `dhcp.type` `dhcp.id` `dhcp.client_mac` `dhcp.assigned_ip` `dhcp.client_ip` `dhcp.relay_ip` `dhcp.next_server_ip` `dhcp.dhcp_type` `dhcp.subnet_mask` `dhcp.routers` `dhcp.hostname` `dhcp.lease_time` `dhcp.renewal_time` `dhcp.rebinding_time` `dhcp.client_id` `dhcp.dns_servers` | | `sip` | SIP Protocols | `src_ip` `src_port` `dest_ip` `dest_port` `proto` `sip.method` `sip.uri` `sip.version` `sip.request_line` `sip.code` `sip.reason` `sip.response_line` |