APM device not supported
Hello All I am new to the F5 so hope not to ask a question that maybe asked already (I did look and not able to see) I have a 3rd party having issues connecting to the F5 remotely so I was wondering the best course of action to troubleshoot the problem. Error I have seen: Executed agent '/Common/messagebox_epsec_device_not_supported_act_message_box_ag_3' return value 0Common 123481494763780fallbackMessage Box Logging15018426122017-08-04 11:30:12 Following rule 'fallback' from item 'Message Box' to item 'Logging'Common 123481494763781Device not supported.15018426122017-08-04 11:30:12 Logging Agent: Device not supported.Common 123481494763782/Common/messagebox_epsec_device_not_supported_act_logging_ag_3015018426122017-08-04 11:30:12 Executed agent '/Common/messagebox_epsec_device_not_supported_act_logging_ag_3' return value 0Common Regards ED
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!
