Carbon black incomplete definition data

cancel
Showing results for 
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?

SammiSolmonson_0-1612807551894.png

 

15 REPLIES 15

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

L2 Linker

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

L1 Bithead

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.

L2 Linker

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.

L0 Member

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.

L0 Member

Per Support Notes - 5.2.11 will address this...which is ETA end of March.

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!