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
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.