Submitting file samples to IVX Cloud

Prev Next

(Optional component) If a file's reputation is unknown in the TIE services and Trellix GTI, an endpoint requests to IVX Cloud through DXL local broker for sandboxing.

IVX Cloud detects zero-day malware and combines antivirus signatures, reputation, and real-time emulation defenses. You can send files automatically from the TIE services to IVX Cloud through DXL local broker based on their reputation level and file size. File reputation information sent from IVX Cloud is added to TIE services database.

You can make the DXL local broker optional for IVX Cloud file submissions by enabling the Bypass DXL Local Broker for file submissions to IVX Cloud. Even if a DXL local broker is configured, enabling this option for IVX Cloud takes precedence, and files are submitted directly to the IVX Cloud server.

Caution

Before you uninstall the DXL local broker, ensure all endpoints are running Trellix Endpoint Security (ENS) Update 19 or later.

When you bypass the DXL local broker, you lose access to these existing capabilities:

  • Caching at the DXL local broker level

  • File type filtering

  • Sandbox failure tracking

IVX Cloud workflow

  1. An endpoint requests a file reputation to the TIE services through DXL local broker.

  2. The endpoint receives all reputations available. If the reputation is unknown, the endpoint requests IVX Cloud for sandboxing.

  3. The endpoint analyzes the content rules based on the response and determines file should be submitted for sandboxing.

    Note

    By default file's local reputation must be unknown and the file size less than 5 MB.

  4. The endpoint submits the binary file to DXL local broker.

  5. DXL local broker sends the binary file request to IVX Cloud for sandboxing.

  6. IVX Cloud sends the response back to DXL streaming databus.

  7. TIE consumes the response from the DXL streaming databus and updates the local database.