Are legacy sensors still going to function after the Carbon Black Cloud Certificate Authority changes?

Products

• Carbon Black Cloud Endpoint Standard
• Carbon Black Cloud Audit and Remediation
• Carbon Black Cloud Audit and Remediation (formerly Cb Live Ops)
• Carbon Black Cloud Container
• Carbon Black Cloud Endpoint Standard (formerly Cb Defense)
• Carbon Black Cloud Enterprise EDR
• Carbon Black Cloud Enterprise EDR (formerly Cb Threathunter)
• Carbon Black Cloud Managed Detection (formerly Cb Threatsight)
• Carbon Black Cloud Managed Detection and Response
• Carbon Black Cloud Managed Threat Hunting
• Carbon Black Cloud Prevention
• Carbon Black Cloud Workload

Issue/Introduction

Will customers be expected to update the Carbon Black agent on the legacy OS versions as well or can they continue using the current version without any issues when the Carbon Black Cloud Certificate Authority changes?

Environment

• Carbon Black Cloud Console: Current Version
• Carbon Black Cloud Windows Sensor: 3.5.x and Lower
• Carbon Black Cloud Linux Sensor: 2.11.x and Lower
• Carbon Black Cloud macOS Sensor: 3.7.2 and Lower
• Microsoft Windows OS: Legacy Versions
• Linux OS: Legacy Versions
• macOS: Legacy Versions

Cause

Effective 1 June 2025, Windows 3.6+, macOS 3.7.3+, and Linux 2.12+ sensor versions are required to communicate with the Carbon Black Cloud because the certificate authority is going to be changed.

Resolution

Legacy OS versions running unsupported sensors will terminate communication with the Carbon Black Cloud console after June 1st 2025 because they will no longer have a valid certificate for communication.

Additional Information

• Upcoming Change to Carbon Black Cloud Certificate Authority