![]() While in the beginning there was a strong focus on signatures / patterns of known malware, this topic has recently become less and less important, because the viruses have been mutating for some time (like real viruses) and do so much faster than the vendors can update their signatures. Due to the spread of Windows, this has been an ongoing issue since the 90s. Virus scanners such as Microsoft Defender AV (MDAV) have the job of detecting malware and neutralizing it. What is an Exclusion and why should I care? So in this blog I will try to show what kinds of exclusions there are, what risks they entail and how to implement them in a practical way. However, it is always good to know your enemy and have a plan in case you are forced to use exclusions. To be clear, my recommendation is to use every opportunity to get rid of (old) exceptions and not migrate anything that has not been proven to cause problems with the new solution. ![]() Nevertheless, I have only come across a few companies that did not have exclusions and it is always assumed to be a project risk not to migrate them when it comes to switching to a new solution. Usually, it was always quickly agreed that the best way to deal with exclusions is not to use them □. Whenever I’ve had to deal with AV solutions in recent years, the topic of exclusions has always come up at some point.
0 Comments
Leave a Reply. |