OPSWAT v3 software EOL

[DaveG]

Hi all,

I just noticed we're still using OPSWAT v3 and not V4.

If we migrate to V4, does anyone know if clients will be impacted? They all use the Pulse Secure Client and VPN tunnelling? Or does it only update the standalone host checker?

Thanks!

[[email protected]]

@DaveG Please prepare a test-plan before migrating from OPSWAT v3 to v4 SDK in your production setup as it might cause some unexecpted issues like AV not being supported, detected, failure to parse correct information, etc. Hence, please test the setup by activating the newer SDK on a test environment with handful number of testers.

Below KBs should provide some of the key highlights when it comes to OPSWAT SDK migration:

https://kb.pulsesecure.net/articles/Pulse_Secure_Article/KB40318/?kA1j0000000WywG

Process based Host Check for unsupported software -- https://kb.pulsesecure.net/articles/Pulse_Secure_Article/KB22348/?kA1j0000000FjLL

[DaveG]

Hi [email protected] , thank you.

Do you know if it would cause clients to update their Pulse connection or would they see any message when connecting?

[zanyterp · Accepted solution]

the pulse client connection would not be updated by "simply" updating ESAP
there should be no visible change to the users; they may see a notification that host checker is downloading…but you would need to confirm for your deployment (as mentioned by [email protected]