If you encounter problems like incompatibilities with other antivirus software, too many false positive alerts, or excessive storage or CPU usage, you can optimize Elastic Defend to mitigate these issues.
Endpoint artifacts — such as trusted applications and event filters — and Endpoint exceptions let you modify the behavior and performance of Elastic Endpoint, the component installed on each host that performs Elastic Defend’s threat monitoring, prevention, and response actions.
The following table explains the differences between several Endpoint artifacts and exceptions, and how to use them:
Prevents Elastic Endpoint from monitoring a process. Use to avoid conflicts with other software, usually other antivirus or endpoint security applications.
Prevents event documents from being written to Elasticsearch. Use to reduce storage usage in Elasticsearch.
Does NOT lower CPU usage for Elastic Endpoint. It still monitors event data for possible threats, but without writing event data to Elasticsearch.
Prevents known malware from running. Use to extend Elastic Defend’s protection against malicious processes.
NOT intended to broadly block benign applications for non-security reasons.
Prevents Elastic Endpoint from generating alerts or stopping processes. Use to reduce false positive alerts, and to keep Elastic Endpoint from preventing processes you want to allow.
Might also improve performance: Elastic Endpoint checks for exceptions before most other processing, and stops monitoring a process if an exception allows it.