DATE CHANGE: Update to the Carbon Black Defense Local Scanning Engine
NOTE: Due to additional Quality Assurance measures Carbon Black will be delaying the release of the updated local scanner package by one day to April 26th. The post has been updated below.
On April 26th Carbon Black will be providing an update to the local scanner deployed to Microsoft Windows Operating Systems that will reduce the size of the signature database by 25% percent! This update will result in a reduction of the memory footprint and improved overall performance of the Cb Defense sensor.
In order to achieve the reduction Carbon Black will push a one time update to all sensors that is 155 MB in size. This update will take place on Tuesday April 25th and after the initial delivery all subsequent updates will return to the kilobyte range.
Due to the increased size of this update customers with large deployments or reduced network bandwidth may experience temporary network congestion when pulling this update from the cloud. As a result Carbon Black will make available a special installer that can be internally deployed through a systems management tool such as Microsoft’s SCCM.
Temporarily disable updates using policy settings to the local scanner prior to the April 25th delivery date to avoid having the sensors pull the update from the cloud. Then deploy update using the provided standalone installer in a controlled manner then re-enable signature updates via policy settings. Please see the following knowledge base document for more information. https://community.carbonblack.com/docs/DOC-5786
Increase the window of time between updates to spread the update over a larger period of time. This can be configured from the Local Scan Settings tab within a policy. Options include 2, 4, 8, 12 and 24 hours.