| VMware Carbon Black Cloud Workload 1.2.2 | 26 OCT 2023 | Build 20722338 Check for additions and updates to these release notes. |
Overview
VMware Carbon Black Cloud Workload is a data center security product that protects your workloads running in a virtualized environment. It provides an ability to ensure workloads have built-in protection making security intrinsic to the virtualized environment. It includes core capabilities such as agent-less delivery, inventory, lifecycle management, vulnerability assessment, and remediation. It also includes endpoint protection capabilities such as next-gen antivirus, real-time threat hunting and endpoint detect and response. For more information, see:
Update - 26 October 2023
This update of the VMWare Carbon Black Workload introduces the Sensor Gateway appliance 1.2. You can now easily deploy the Sensor Gateway as an OVA and take advantage of all the functionalities provided with previous versions. For details, see Installing and Using Carbon Black Sensor Gateway.
Important:
Carbon Black recommends using the appliance for your current and future Sensor Gateway implementations. Sensor Gateway for Linux and the related HA capabilities are going to be deprecated soon.
Update - 24 August 2023
This update introduces the following functionality related to Carbon Black Sensor Gateway.
Manage Sensor Gateway Connection
The Carbon Black Cloud console now allows you to manage the connection between the sensors installed on your workloads and Carbon Black Cloud. You can select the connectivity path as either a direct connection or through the Sensor Gateway. For more information, see Manage Connectivity to Carbon Black Cloud.
Update Sensor Gateway Certificate
Carbon Black Cloud now allows you to update the SSL certificate of a Sensor Gateway before it expires or if it has been compromised. By keeping your Sensor Gateway certificate updated, you can avoid getting the Carbon Black sensors permanently disconnected from the Carbon Black Cloud. For more information, see Update Sensor Gateway Certificate.
You can also create a subscription for certificate expiration notifications. For more information, see Subscribe for Sensor Gateway Notifications.
Update - 9 May 2023
This update introduces the following changes that you can retrieve from the VMware Carbon Black Cloud Workload 1.2.2 Appliance Open Source:
-
Carbon Black launcher 1.3 for Linux VM now supports custom configuration, which is already available on Windows.
-
Resolved issues.
The Carbon Black launcher 1.3 allows you to specify the default sensor configuration from the Carbon Black Cloud console during the installation process. To take advantage of this functionality, make sure your Carbon Black Linux sensor is with version 2.13 or later. For sensors with version 2.12 or earlier, the sensor installation ignores the custom configuration you have specified. For more information, see Carbon Black Launcher for Linux VMs.
What's New
The VMware Carbon Black Cloud Workload product now includes a Sensor Gateway for ensuring your workloads are not directly exposed to the Internet for security, regulatory, and compliance reasons. All the communication, originating from the Carbon Black sensors and going to and from Carbon Black Cloud, is directed through the Sensor Gateway. Thus, removing the burden of owning, managing, and budgeting for additional proxy servers.
After installing and having your Carbon Black Sensor Gateway 1.0 up and running, to configure the Carbon Black sensor to communicate with the Carbon Black Cloud through the Sensor Gateway, you must perform a fresh sensor install. For more information, see Install and Configure Carbon Black Sensor Gateway.
Each Sensor Gateway supports up to ten thousand sensors and additional Sensor Gateways can be spun up to handle the increased overhead. When a Sensor Gateway is disconnected or overburdened, you receive notifications in the product as well as via email. You can turn off subsequent notifications in the Carbon Black Cloud console UI. For more information, see Sensor Gateway Notifications.
Previous Release
The VMware Carbon Black Cloud Workload appliance 1.2.2 security patch release addresses the CVE-2022-42889.
Resolved Issues
-
New - The Carbon Black launcher now installs sensors on machines with non-English locale
-
New - Sensor installation no longer fails when custom configuration URL is missing
If the custom configuration URL is missing, the sensor installation now completes successfully due to the Carbon Black launcher falling back to using the
CompanyCodefromGuestInfo. -
New - The Carbon Black launcher now sets the expected status code 3016 in case of a bad sensor URL
Known Issues
-
New - Sensor installation completes, even though there are wrong parameters in the custom configurtion
When you specify a custom sensor configuration in the process of installing your Carbon Black Linux sensor, the installation completes successfully even if there are wrong parameters in the
config.inifile. -
Upgrading NSX from 4.0.0.1 to 4.0.1 incorrectly preserves the previous version of NSX in the Carbon Black Cloud Workload appliance
When you upgrade NSX to 4.0.1 and register it successfully with the Carbon Black Cloud Workload appliance, you can view the previous 4.0.0.1 version of NSX in the Appliance > Registration > NSX details page. However, you can view the correct 4.0.1 version of NSX in the About VMware NSX pop-up, part of the NSX console UI.
Workaround: None.
-
Carbon Black Cloud console displays unreachable appliance as eligible
On the Carbon Black Cloud console, from the Inventory > Workloads > Not Enabled tab, you can filter VMs based on the Eligibility status. Some eligible VMs are listed with a note 'Not eligible. Unreachable appliance' if the on-premise appliance is unable to communicate with the Carbon Black Cloud. Even though the appliance is unreachable, the Carbon Black Cloud console displays the unreachable appliance under the Eligible filter.
Workaround: None
-
Upgrading Carbon Black Cloud Workload appliance fails when there is discrepancy between the appliance version in Carbon Black Cloud and the actual appliance version
Workaround: Carbon Black Cloud and the Carbon Black Cloud Workload appliance must be always in sync on the appliance version. For example, to upgrade successfully the appliance from versio 1.0.2 to version 1.1.2, make sure the version of the appliance is 1.0.2 in the cloud as well.
-
Upgrading Carbon Black Cloud Workload appliance fails if it is not registered with the vCenter Server
Workaround: Register the appliance with the vCenter Server prior upgrading it to version 1.2. For details, see Register Appliance with vCenter Server.
