--- title: "tapsender certificate name <certificateName>" slug: "tapsender-certificate-name-certificatename" tags: ["Reference", "CMS 11.x", "EX 11.x", "HX 10.x", "FX 11.x", "AX 11.x", "NX 11.x", "IVX 11.x", "Customer", "Network Security"] updated: 2026-08-04T17:22:36Z published: 2026-08-04T17:22:36Z canonical: "docs.trellix.com/tapsender-certificate-name-certificatename" stale: true --- > ## 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. # tapsender certificate name <certificateName> Configures a certificate to authenticate the Evidence Collector module to TAP. The public certificate and private key must be imported before configuring the certificate for the Evidence Collector module. For details about how to import the public certificate and private key, refer to the "TAP Integration" section in the "Integrating with Other Tools " chapter of the Network Security User Guide. > [!NOTE] > Note > > TAP integration is not supported on the NX x3xx appliances and the NX 10000 appliance. > [!WARNING] > Important > > After you applied the certificate to enable authentication, use the `tapsender enable` command to enable the Evidence Collector module. ### Syntax `tapsender certificate name <certificateName>` ### Parameters `<certificateName>` A name that you already configured to uniquely identify the certificate for the Evidence Collector module. ### Example The following example applies the uploaded "tapsender" certificate to the Evidence Collector module for authentication to TAP: ``` hostname (config) # tapsender certificate name tapsender ``` ### User role Admin or Operator ### Command mode Config ### Supported appliances This command is supported on the following appliances running the specified releases or later: - **Network Security:** Release 7.9.3