--- title: "Considerations when trusting a third-party certificate" slug: "considerations-when-trusting-a-third-party-certificate" tags: ["Product Usage", "ENS 10.7.x", "Endpoint Security"] updated: 2026-09-14T20:39:21Z published: 2026-09-14T20:39:21Z canonical: "docs.trellix.com/considerations-when-trusting-a-third-party-certificate" 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. # Considerations when trusting a third-party certificate 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] > 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](https://thrive.trellix.com/s/article/KB88029).