--- title: "Routing malware definition update requests through a reverse proxy" slug: "routing-malware-definition-update-requests-through-a-reverse-proxy" tags: ["Endpoint Security (HX)", "Product Usage"] updated: 2026-09-23T17:25:03Z published: 2026-09-23T17:25:03Z canonical: "docs.trellix.com/routing-malware-definition-update-requests-through-a-reverse-proxy" --- > ## 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. # Routing malware definition update requests through a reverse proxy You can use the CLI commands in this procedure to route your malware definition update requests through a reverse proxy before going to avupdate.fireeye.com when your Malware Protection Source is set to **HX Preferred** or **HX Only**. ### Note The upstream server must be a reverse proxy. A forward proxy is not supported. To route your malware definition update requests to a proxy: 1. Go to CLI configuration mode: `hostname > enable hostname # configure terminal` 2. View your current malware proxy parameters: `hostname (config) # show hx server mal` 3. Enable malware proxy support: `hostname (config) # hx server mal proxy forward enable` 4. Configure the URL you will use to forward the malware definitions: `hostname (config) # hx server mal proxy forward url http://IPXXX:PORTXXX/` ### Note You must use the IP address of the proxy. If you use the fully qualified domain name of the proxy, then validation will fail. 5. (Optional) Choose one of the following two authorization methods: `hostname (config) # hx server mal proxy forward auth-header "Basic XXXXXXXXXXXXXX=="` `hostname (config) # hx server mal proxy forward auth-header "Bearer XXXXXXXXXXXXX=="` ### Note If you do not indicate an authorization method, then the default option (which sets the Authorization header to null) is used. `hostname (config) # hx server mal proxy forward auth-header ""` 6. Save your changes: `hostname (config) # write mem` :