Carbon black incomplete definition data

Showing results for 
Show  only  | Search instead for 
Did you mean: 

Carbon black incomplete definition data

L1 Bithead

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?




Accepted Solutions

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

View solution in original post


L4 Transporter

What GP App Version are your users using?

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

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

L2 Linker

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.

L2 Linker

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

L0 Member

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

Orlando S S J

L2 Linker

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 are having the same issue. Version 5.2.9 was just released but still detecting definition date incorrectly as 01/01/1970. 

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

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

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!