Access official resources from Carbon Black experts
This document describes the steps required to transition already deployed Sensors to the Carbon Black Cloud Appliance. The opposite direction is also supported, transitioning from the Carbon Black Cloud Appliance to your on Premise Server.
Transitioning already deployed sensors
Provide the contents of the /etc/cb/certs directory before provisioning the server. Compress the directory using the tar utility and send the resulting .tar.gz file to us. To do this:
tar zcvf ~/hostname.certs.tar.gz /etc/cb/certs
/usr/share/cb/cbpost ~/hostname.certs.tar.gz
Once your cloud server has gone live, you will need to change the Server URL in the Sensor Group Settings of your on-premise server from within the Carbon Black UI:
Administration > Sensors > Edit Settings > update Server URL
At the next sensor check-in, the Sensor’s will receive the new URL update and begin communicating to your new Carbon Black Cloud Server instead
Transitioning from Cloud to on Premises Server
Carbon Black will provide you with the contents of the /etc/cb/certs directory from the Carbon Black Cloud Server for you to import onto your on-premise Carbon Black Server.
Note: It’s critical to always create backups of the /etc/cb/certs directory prior to making changes.
Why do we need the Certificate Directory?
Carbon Black’s SSL dual authentication mechanism utilizes:
Browser / Rest API clients to Cb server:
Sensor to Cb Server:
We support transitioning sensors, not transitioning data.
Carbon Black Cloud service does not support transitioning data due to the size. A Carbon Black server can have a large amount of data stored (in some cases, terabytes). To transfer that data would be a taxing process. The lifetime of the data is typically ~30 days by default; resulting in the time of the transfer outliving the data on larger servers.