SentinelOne

This Sentinel One article appears to provide a way.

Sentinel One Whitelist

SentinelOne’s robust exclusion function is easily configured to enable compatibility and remedy interoperability false positives. Exclusions can be applied at the global level, site level and group level for granular control. Blacklisting or whitelisting specific applications is not a requirement in order for the SentinelOne solution to operate. However, it is considered best practices to ensure that no other endpoint security solutions may be conflicting with SentinelOne and thus cause interoperability issues. In such cases, it is advised that customers consider the use of exclusions to deal with 3rd part interoperability conflicts. SentinelOne is happy to discuss mass deployment strategies that include testing for potential interoperability issues and proactively handling them. SentinelOne agent exclusion mechanisms include: • Hash value • Path, path + subfolders, specific executable • Signer certificate identity • File type • Browser type The ability to not monitor certain executables as well as the option to use cascading exclusions. The latter is typically used by shops building code that use known-good compilers. We also have multiple exclusion modes for highly specific (surgical) exclusions. Ability to turn on and off functionality for consideration of different deployment scenarios, including throttling of deployment. All guidelines and knowledge base articles can be access via the online customer portal.