Bad news. It has been over a month and we are still having the issue with Ivanti Secure Connect not recognizing Sophos 2022.2.1.9. We have been escalated, sent multiple logs, and even installed on proposed fix (ESAP version 4.0.5). We are waiting for OPSWAT to put out a new ESAP module now, but our Helpdesk has had to resort to removing the approved and centrally managed virus scanning solution (Sophos) and installing Avast until we can get a ESAP module that correctly identifies the version of Sophos we use.    If we had more users using VPN this would have been worse. But as you can all imagine, the users that do access the VPN perform very important functions for our organization. Hopefully the end is near.    Mark Fleming ... View more

Just another update to my personal journey in (Product-to-Product interoperability).    Ivanti's developers have identified a fix and had it validated by OPSWAT. So they know what was wrong and have found a fix. Their development SDK will be updated by tomorrow, August 16. A new ESAP module will be out by Friday, August 19th. So, the end is nigh.  ... View more

We have tried Pulse Secure client versions 5.3.x up until 9.1.16 and the newest Ivanti Client. None of them seem to be able to verify that Sophos Endpoint 2022.2.1.9 is a valid anti virus agent. But as soon as we remove Sophos, users can connect to the VPN again.   We initially updated our appliance from 9.1R11 to 9.1R16 and our ESAP to 4.0.4 because we though the newer version of Sophos just wasn't in the older versions we were running. An issue we have seen in the past. Ivanti has confirmed to us that the issue runs deeper and their developers are working on the issue now.     Pulse Secure Article: KB45380 - Sophos Core Agent 2022.2.1.9 failing compliance with ESAP 4.0.4 ... View more

My organization has been seeing the same issue with ESAP 4.0.4 and Sophos 2022.2.1.9. Case was escalated to developers, but haven't heard anything since.  ... View more