DXLData Exchange Layer client
ePOAPI integration
MD5/SHAFile reputations
CEFInto Trellix Helix
The short answer

Trellix and OneFirewall are complementary. Trellix detects and blocks on endpoints and in network traffic, using Trellix intelligence and local reputations held in TIE. OneFirewall adds an independent, Alliance-validated source of malicious file hashes to that reputation fabric, and blocks known attacker IPs at the firewall before they reach Trellix-protected hosts.

How Trellix works

ENS, TIE and DXL under ePO

Trellix (the former McAfee Enterprise and FireEye) protects endpoints with Endpoint Security (ENS), managed from ePolicy Orchestrator (ePO). Threat Intelligence Exchange (TIE) holds file and certificate reputations for the organisation, and the Data Exchange Layer (DXL) is the real-time message fabric that lets ENS, TIE, network sensors and third-party tools share those reputations instantly.

Trellix also offers network security, email security, Helix SIEM and its XDR platform. Third-party tools join the fabric as authenticated DXL clients, using a broker CA bundle and a client certificate.

  • Strong endpoint protection with central ePO management
  • TIE reputations decide whether a file can run, organisation-wide
  • DXL shares updates across every connected product in real time
  • Reputations come from Trellix intelligence and your own environment
The integration

The WCF Agent as a DXL client

Trellix is an agent-based integration. The WCF Agent connects to your DXL fabric and the ePO API with credentials and certificates you issue.

STEP 1

Issue certificates

In ePO, provision a DXL client certificate for the WCF Agent and export the broker CA bundle, client certificate and private key.

STEP 2

Configure the agent

Fill in the trellix section of the WCF Agent configuration: ePO API endpoint, integration user, file list path and the three certificate files.

STEP 3

Share reputations

On each sync the agent publishes Alliance-confirmed malicious file hashes (MD5, SHA1, SHA256) to the Trellix fabric, so endpoints treat them as known-malicious.

STEP 4

Send events to Helix (optional)

Point the agent's CEF syslog output at Trellix Helix so OneFirewall blocks and detections appear alongside your Trellix telemetry.

What the configuration looks like

// WCF Agent config.json: Trellix connects as a DXL client + ePO API
"ips": {
  "trellix": {
    "active": true,
    "api": "https://<epo-server>:8443",
    "username": "ofa-integration",
    "password": "********",
    "fileslist_file": "/opt/onefirewall/feeds/files.txt",
    "broker_ca_bundle": "/opt/onefirewall/dxl/ca-bundle.crt",
    "cert_file": "/opt/onefirewall/dxl/client.crt",
    "private_key": "/opt/onefirewall/dxl/client.key"
  }
}

In parallel, the same WCF Agent pushes attacker IPs to your firewalls, IPS and WAFs, so the network layer and the endpoint layer act on the same Alliance intelligence.

Side by side

Trellix and OneFirewall, capability by capability

CapabilityTrellixOneFirewall
Where it actsEndpoints, network sensors, email, Helix SIEMAt the perimeter, plus file reputations shared into the Trellix fabric
Reputation sourceTrellix intelligence and your local TIE decisionsIndicators confirmed by 290+ organisations across vendors
Integration mechanismDXL and ePOAuthenticated DXL client and ePO API; CEF to Helix
Indicator typesFile and certificate reputations, network signaturesIP, domain, URL and file hashes, each with a Crime Score
Stale indicatorsManaged in TIE and ePODecay automatically when no longer reported
ScopeTrellix productsThe same intelligence reaches firewalls, cloud WAFs and other SIEMs
The added value

What OneFirewall adds to Trellix

A second source of file reputation

Hashes confirmed by other Alliance members reach your endpoints over DXL without anyone importing a list.

Perimeter blocking Trellix endpoints don't need to handle

Known attacker IPs are dropped at the firewall before they can deliver anything to a host.

One intelligence source, two layers

Network and endpoint act on the same scored indicators, which keeps policy consistent across teams.

Where Trellix is still the right tool
  • Malware prevention, exploit protection and EDR on endpoints
  • Organisation-wide reputation decisions in TIE
  • Network, email and sandbox detection
  • Investigation and correlation in Helix and Trellix XDR

OneFirewall feeds the Trellix fabric; it doesn't replace any Trellix product.

FAQ

OneFirewall and Trellix: FAQ

How does OneFirewall connect to Trellix?

The WCF Agent connects as a DXL client using a broker CA bundle, client certificate and private key, and uses the ePO API with an integration user.

What does OneFirewall share with Trellix?

Malicious file hashes (MD5, SHA1, SHA256) confirmed by the Alliance, so Trellix endpoints treat them as known-malicious.

Can OneFirewall events go to Trellix Helix?

Yes. The agent's CEF syslog output can be sent to Helix like any other CEF source.

Is this an agent-based integration?

Yes. The WCF Agent runs on a separate VM with Docker; nothing extra is installed on endpoints.

See what Trellix lets through today.

A free Proof of Value runs against your own traffic. Nothing leaves your perimeter.

Start a Free PoV