The new docs.trellix.com features a modernized UI and AI-powered conversational search. Content is currently available in English, with additional languages launching in mid-October 2026. We hope you enjoy the updated experience.

Press CTRL+K to open search

Considerations when trusting a third-party certificate

  • Published on Sep 14, 2026
  • 1 minute(s) read
Prev Next

Trusting a third-party certificate can result in increased security risks.

The security implications of trusting a third-party certificate include:

  • Code signed by the third-party certificate is trusted to interact with Trellix processes, files, registry, and all other Trellix-protected objects.

  • File activity generated by processes signed with the third-party certificate might not be scanned.

  • Any product or code releases from the same vendor using the same digital certificate automatically inherit the same trust or untrusted state.

  • Any product or code releases from the same vendor using a different digital certificate must be trusted.

Tip

If the Endpoint Security Platform stops running, a third-party injection into Trellix code might be the cause. For information about troubleshooting this error, see KB88029.

Related articles
  • Considerations when trusting a third-party certificate
    Endpoint Security (ENS) > Trellix Endpoint Security (ENS) 10.7.x Product Guide - Windows > Configuring with Trellix ePO - On-prem > Configuring common features > Protecting Trellix processes from third-party DLLs
  • Validation failures
    Endpoint Security (ENS) > Trellix Endpoint Security (ENS) 10.7.x Product Guide - Windows > Configuring with Trellix ePO - On-prem > Configuring common features > Protecting Trellix processes from third-party DLLs
  • Validation failures
    Endpoint Security (ENS) > Trellix Endpoint Security (ENS) 26.x Product Guide - Windows > Configuring with Trellix ePO - On-prem > Configuring common features > Protecting Trellix processes from third-party DLLs