[AV Check] How to disable checking if Windows Defender is up-to-date during client-side check
Hello DevCentral users, I am currently trying to figure out how to avoid running into issues when one of my users has eSet Endpoint Security installed on their Windows 10 devices. When a user installs eSet Endpoint Security it automatically disables the built-in Windows Defender. This disabled Windows Defender however is being found by the antivirus client-side check in my Access Policy. The user is then not able to log into my SSL-VPN. I would like to know how to built an antivirus client-side check into my Access Policy where it doesn't matter which AV product a user has as long as its virus definitions have been updated at least 7 days ago, like this: I've added Windows Defender as a second AV but when I do get it to work (no check on if the definitions are up-to-date) it won't suffice for users who only have Windows Defender installed. Does anyone have any tips or tricks on how to set this up? Thanks in advance!
APM :: EPSEC / OPSWAT :: Dealing with Unsupported Antivirus Applications
How do folks deal with unsupported antivirus applications when requiring passing of this check prior to logging in? For example, some users have repackaged applications from their ISPs, and it is typically something they either pay for or comes with their subscription. They generally aren't too keen on moving to something else because of that. I would entertain the idea of a bypass... but EPSEC doesn't even see it. Removing the troublesome AV suite and enabling/updating Defender would work and get them in... but again, they're generally not too keen on removing something they pay for. And giving the ISP-specific nature of it... I doubt OPSWAT is going to accommodate an update in that regard? Anyway... Does anybody have any tricks for this in their environment? Thanks!
