Configure your network infrastructure and endpoints to ensure proper communication between sensors and the backend.

The current implementation of the Carbon Black Cloud service uses dynamically managed load balancers to provide the best possible levels of scalability, reliability, and performance. The Carbon Black Cloud services hostname resolves several possible IP addresses that can change dynamically.

There is no static IP, range of IP addresses, or subnet to allow or exclude in firewall or proxy settings.

Network proxies and firewalls can interfere with communication between the Carbon Black Cloud sensor and the Carbon Black Cloud backend if they are improperly configured.

Note: Some third-party products might attempt to validate the Carbon Black Cloud server certificate, and then terminate the connection due to a name mismatch between the certificate issued to the Carbon Black Cloud Login URL and the service to which the sensor is connected. In this situation, the third-party product must be configured to not validate the domain certificate.