Jump to content

Is adding too many exclusions a bad thing?


Go to solution Solved by itman,

Recommended Posts

I was testing Avast Antivirus Free the other day and as I was adding folders that had a lot of . EXE files (my software folder which includes installers and benchmarking tools), Avast popped a message saying that adding too many exclusions would hurt performance.

This has me thinking, is that something particular to Avast or is it a general rule of thumb that one should only add exclusions to a few items that they do not want the antivirus to touch for any reason but not over do it?

Also, what is the difference between Detection Exclusions and Performance Exclusions?

Link to comment
Share on other sites

  • Administrators

While creating many exclusions would not affect performance, each exclusion creates a potential security hole so exclusions should be used only as a last resort if a particular issue cannot be resolved otherwise.

Link to comment
Share on other sites

2 minutes ago, Marcos said:

While creating many exclusions would not affect performance, each exclusion creates a potential security hole so exclusions should be used only as a last resort if a particular issue cannot be resolved otherwise.

what is the difference between Detection Exclusions and Performance Exclusions?

Link to comment
Share on other sites

  • Administrators

Performance exclusions are intended to solve performance issues while detection exclusions address detection exclusions, ie. files are still scanned but excluded detections are ignored.

Link to comment
Share on other sites

  • Solution
Posted (edited)
3 hours ago, Super_Spartan said:

Also, what is the difference between Detection Exclusions and Performance Exclusions?

Per Eset on-line product help;

Quote

Performance exclusions—exclude files and folders from scanning. Performance exclusions are useful to exclude file-level scanning of gaming applications or when causing abnormal system behavior or increased performance.

Detection exclusions—exclude objects from detection using the detection name, path, or its hash. Detection exclusions do not exclude files and folders from scanning as performance exclusions do. Detection exclusions exclude objects only when they are detected by the detection engine and an appropriate rule is present in the exclusion list.

https://help.eset.com/essp/16.1/en-US/idh_exclude.html

Edited by itman
Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...