--- title: "How Trellix DLP Network Monitor – SaaS inspects live network traffic" slug: "how-trellix-dlp-network-monitor-saas-inspects-live-network-traffic" tags: ["Product Usage", "SaaS"] updated: 2026-09-01T09:27:59Z published: 2026-09-01T09:27:59Z canonical: "docs.trellix.com/how-trellix-dlp-network-monitor-saas-inspects-live-network-traffic" --- > ## 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. # How Trellix DLP Network Monitor – SaaS inspects live network traffic You can register on-premises ePO - SaaS to apply the Trellix DLP – SaaS policies. Use the Trellix DLP Network Monitor – SaaS policies to learn about the quantity and types of data transferred across the network and to monitor network traffic. Trellix DLP Network Monitor – SaaS doesn't block or change network traffic, so you can integrate it into a production environment without impacting live traffic. 1. The router receives network packets from internal users and servers. 2. Trellix DLP Network Monitor – SaaS connects to either a Switched Port Analyzer (SPAN) port or a network tap to passively monitor live traffic received from the router. 3. Trellix DLP Network Monitor – SaaS receives copies of network packets and analyzes them. Sends incidents to ePO - SaaS . 4. ePO - SaaS sends policy to Trellix DLP Network Monitor – SaaS. 5. Registered documents server defines sensitive information to protect it from being distributed in unauthorized ways. ![GUID-B5CCF026-C9F8-4753-A10E-D5AFC4991BEE-low.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-bdc37236-d49c-f558-3deb-b2ffc119a34a.png?sv=2026-02-06&spr=https&st=2026-11-22T14%3A09%3A30Z&se=2026-11-22T15%3A09%3A30Z&sr=c&sp=r&sig=Ak6iv2%2BORU%2Bh4ypZsSguVMB%2FqwQGcrWgmqPLLzRf77M%3D) ### Types of protection rules Trellix DLP Network Monitor – SaaS can apply one of these Trellix DLP – SaaS protection rules to your network traffic. - **Email Protection** — By default, Trellix DLP Network Monitor – SaaS inspects SMTP traffic using email protection rules, which incorporate protocol-specific information such as sender and recipient email addresses. - **Web Protection** — By default, Trellix DLP Network Monitor – SaaS inspects HTTP and FTP traffic using web protection rules, which incorporate protocol-specific information such as the URL. - **Network Communication Protection** — Trellix DLP Network Monitor – SaaS can inspect all supported traffic using network communication protection rules, which do not incorporate any protocol-specific information. If you don't want to analyze SMTP, HTTP, or FTP traffic with email and web protection rules, you can configure Trellix DLP Network Monitor – SaaS to use network communication protection rules. To disable analysis of SMTP, HTTP, and FTP traffic, go to **Menu** → **Policy Catalog** → **DLP Appliance Management** → **Trellix DLP Network Monitor Settings** and deselect the options in the **Protocol Rule Application** field. > [!NOTE] > Note > > Using **Email Protection** and **Web Protection** rules allows you to share rules with Trellix DLP Network Prevent – SaaS. ### Supported protocols - SMTP* - IMAP* - POP3* - HTTP - LDAP - Telnet - FTP - IRC - SMB** Trellix DLP Network Monitor – SaaS can also analyze traffic that is encapsulated in SOCKS. * These protocols support STARTTLS (plain text initial connection converted to TLS/SSL after STARTTLS command). These protocols are treated as encrypted and does not analyze them if STARTTLS is used. ** Data transferred using SMB might be encrypted depending on the version of the protocol and your configuration. > [!NOTE] > Note > > The content of encrypted connections is not analyzed directly. You can use a dedicated gateway (for example, the SSL Tap feature in Web Gateway), to intercept the encrypted connection and send the decrypted data to Trellix DLP Network Monitor – SaaS for analysis. See the documentation for your gateway for information. If Trellix DLP Network Monitor – SaaS can't classify a connection as a known protocol, it shows the connection as unknown.