McAfee and Juniper have done it again: SSL-VPN stopped working

[SF_Dan_]

It seems to fix it if you change the AV definition check from:

Virus Definition files should not be older than X Updates.

to:

Virus Definition files should not be older than X Days.

[scoutt_]

that won't work for me Dan, I also see Real Time Protection is not running. I was told today that OPSWAT will have a fix by the end of the month, April.

I was also thinking that what if we looked for the service to see if it is running like some had to on Security Essentials 4.x. Just have Host checker look for it. But not sure if that woudl really work.

[PaddleFace_]

We at OPSWAT are aware that consumption of OESIS Framework updates by Juniper (and other partners) for inclusion in Hostchecker features released to end customers can be painful for Juniper and for its customers. 

We are committed to releasing OESIS more frequently (currently weekly, with a goal of daily updates by end of 2014) and to make it easier for Juniper to validate OESIS releases and incorporate into their packages.

In addition, OPSWAT recently released a configurable client, GEARS, which auto-updates OESIS and stores endpoint device compliance status in the Windows Registry or Mac OS p-list.

The Host Checker can access and use this information through implementing either a (1) the  default Antivirus Rule or (2)  a  custom process / registry checks.

A Hostchecker-GEARS configuration guide is posted at http://files.cdn.opswat.com/www.opswat.com/files/gears-integration/integrate-juniper-ssl-vpn-opswat-...

Using GEARS together with Hostchecker should reduce the number of issues you encounter with your end users being blocked due to their running an unrecognized endpoint security application.

Attachments:

integrate-juniper-ssl-vpn-opswat-gears.pdf ‏1003 KB