When we had gpa 5.2.6 and cb v220.127.116.11xx only the defintion was broken. When cb went to 18.104.22.1681 the real time scanning broke. With gpa 5.2.9-35 for us, it fixed the real time scan and the definition when using cb 22.214.171.1241. Seems every time cb makes a version , opswat needs to make changes that affects their clients like cisco anyconnect and palo alto
what's happening is that GPA 5.2.5 recognized CARBON BLACK's Carbon Black Defense Sensor, but then VMWare bought out CB and renamed it as VMWare Carbon Black Cloud Sensor. All GPA versions 5.2.6+ onward couldn't recognize where VMWare placed their definitions. You can connect GPA, go to Settings, Host Profile, highlight each Anti-Malware item and look to see it has the name, version , BUT the definition is either blank or 01/01/1970 default. We've been working with Palo for over 2 months on this and the fault lies with their subvendor OPSWAT who handles the detection. They've been working on it as well. We've been testing Palo's beta versions so we could help Palo out. We finally got 5.2.9 beta2 to work so VMware CB Cloud Sensor will pickup correctly but Microsoft Defender ATP was still broken. Palo plans to release 5.2.9 but date unknown.
We tested the new release gpa 5.2.9-35 on cb ver 126.96.36.1991 and it detected ms defender atp, carbon black cloud sensor and windows defender properly in version, real time, engine, def ver, and definition date. I hear now cisco anyconnect is having a carbon black real time issue when on cb 188.8.131.521.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!