Our IT shop uses the Pulse Secure ESAP 2.8.8 software, which runs a "host checker" to verify anti-virus software on a user's home computer. SAV for Mac version 9.x is on the supported software list available here: https://www.pulsesecure.net/techpubs/pulse-connect-secure/esap/2.8.x
Unfortunately, our IT support for the VPN connections is very limited because IT policy prevents them from setting anything up on a user's personal equipment. I've been able to help most of our PC users get up and running, but I'm having trouble with the Mac OS X users because it does not have a free built-in AV client like Windows Defender. Sophos has a stellar reputation, so I recently suggested it to a user, but she is having some difficulties getting the system to detect that a full scan was completed.
The Pulse Secure Host Checker tells her that she needs to complete a successful full system scan:
Here are the scan setting she is using:
The scan says that it completed:
She reviewed her scan logs and they show 0 items detected, but 7 issues were identified. Maybe she needs to address these issues before the Host Checker will pass her? She can't figure out how to address these corrupt files, and I don't know enough about Macs to help her.
I'm hopeful that someone out there has experience getting this to work with the Pulse Secure VPN. In my mind, possible causes of the failure could be:
1. She is not performing the complete system scan correctly. I found a guide for doing this in Windows, but is there something similar for the Mac version?
2. She must address the 7 corrupted files. Any ideas on how to address this?
3. She must somehow authorize Pulse Secure to communicate with SAV. It is possible that SAV is not allowing Pulse Secure to access the scan completion information. This was something we were able to do in a Windows 8 + Windows Defender environment, but I don't know if such a thing is possible in OS X.
Thank you for your help. If I broke any forum protocols with the large post, please accept my apologies.
Thanks,
Brook
This thread was automatically locked due to age.
