So, in configuring NOD32, I see there is an option to adjust the scanners to only scan extensions that can actually execute code. This is supposed to speed up systems greatly by reducing the overhead of scanning every file. Eset provides a default list of about 40 extensions to include. More can be added/removed.
I am kinda leaning towards this, but a the same time a little unsure and worried. 1. It will speed up my systems. 2. Probably will have fewer circumstances in which I am scanning an extension that I shouldn't be... (MDF, LDF, VMDKs, etc...) 3. I won't have to manually white list exclusions for the scanners... (See above). The list can be quite extensive, especially for servers. Obviously, I will still have to set up the path/folder level exclusions... Thoughts on this? I imagine this is a feature on many AV products. I wish I could figure out how to list of default exclusions so I could it share it. Thanks! Happy Friday. -Sam ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
