Carbon black incomplete definition data

[SammiSolmonson]

When matching HIP objects for definitions updated within 30 days a majority of my users failed. I noticed carbon black does not show the data I need under definition version or data. Has anyone else seen this?

[vathreya]

What GP App Version are your users using?

[yan]

Did anyone figure out how to check for carbon black definition using hip object?

[SammiSolmonson]

I updated the GP client from a 5.0.0 version to 5.2.3 and it fixed the issue for me.

[yan]

Thanks. i had version 5.2.6 and their TAC saw my oswalt (palo program)  wasn't pulling in the CB info anymore. they say 5.2.7 which is coming soon, will have the patch to fix that... i hope.

[yan]

patch 5.2.7 didn't work. it sees the CB definition and fills it 01/01/1970, if you look at host profile in settings of the GPA, open CB and see antimalware definition. Developers are taking another look

[orlandos]

The same problem happens in version 5.2.8-23. Has anyone found a solution?

[yan]

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.

[SLesseos]

We are having the same issue. Version 5.2.9 was just released but still detecting definition date incorrectly as 01/01/1970. 

[yan]

We tested the new release gpa 5.2.9-35 on cb ver 3.7.0.1411 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 3.7.0.1411.

[yan · Accepted solution]

When we had gpa 5.2.6 and cb v3.6.0.2xx only the defintion was broken. When cb went to 3.7.0.1411 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 3.7.0.1411.  Seems every time cb makes a version , opswat needs to make changes that affects their clients like cisco anyconnect and palo alto

[yan]

Test GPA 5.2.9 on CB 3.6.0.2076 and it passes all 3 types of Host Profile data - Defender ATP, Carbon BLack Cloud Sensor, Windows Firewall

[peppywoll]

I had a similar problem with Carbon Black where, after an update to version 3.7.0.1503 on Windows laptops, the GlobalProtect HIP check suddenly reported CB as realtime protection "no".  This was on GP version 5.2.7.  After upgrading to GP 5.2.10, the problem was resolved.

[yan]

cool. i have tested GPA 5.2.9 and 5.2.10 on CB 3.7.0.1411 and all hip (vendor, realtime, defintion, version) all responded. To those with Cisco Anyconnect, we still have failures on realtime hip for AC 4.8-4.10.04071 with CB 3.7.0.1411.

[Lumt3k]

Our Organization has been encountering this well over 2 years...multiple cases opened. Every-time there is a new release of Carbon Black Defense addressing enhancements, bug fixes, etc - we can't adopt due to the Global Protect Agent failing to detect.

What is interesting is even if you go into GP- HIP Object Configuration for Anti Malware and disable\set to none on the Virus Definition Date, Product Version, and Last Scan time, users will still fail due to the 1970 date that many are plagued with.

We have test users with the same Model PC, Same Image, Same Versions, Same Portals and Gateways and they connect fine...others do not. The kicker is sometimes after broken users "reboot 3-4x" their signature changes from 1970 to present date. It extremely sporadic. 

This has occurred on previous versions, however currently on GP 5.2.9 and on 5.2.10 with CB 3.8.0.398 for Windows during our testing.