Issue
Recently, Broadcom sent out communications regarding Carbon Black Cloud user authentication migrating to Broadcom's Authentication Hub. All customers who have a Carbon Black Cloud instance will need to take action regarding their logins.
Environment
Carbon Black Cloud
Resolution
How does this affect Red Canary's access to my console?
Red Canary will follow the instructions for the migration for Federated users to allow our employees to continue authentication via SSO as we currently do.
How does this affect me as a customer?
- For instances where your users log in with accounts that are local to your Carbon Black Cloud console (Non-federated users), every user in your organization will receive an activation email from Broadcom GTO asking you to create a new password. You will be prompted to set up MFA as well, which is now required.
- For instances where your users log in using 2FA/SAML (Federated users), a Super Admin in the console will need to complete the migration wizard.
The steps for each of these scenarios are linked below for your review, as well as the knowledgebase article that contains some FAQs. You will need to log in to Broadcom's Community in order to view the instructions. You can register for a community account here.
Broadcom has stated that this will be rolled out in phases. All migration wizards will appear by February 7. Please follow the instructions as indicated in the above documentation. If you experience an issue, please open a support ticket with us and provide as much detail as possible, including any error messages.
Communication from Broadcom:
Carbon Black Cloud user authentication will migrate to Broadcom’s Authentication Hub (AuthHub). AuthHub is a cloud-based authentication service that protects networks and applications by verifying user and device identities. Using AuthHub will ensure security and streamline access to Carbon Black. On or after January 21st you'll be able to execute the re-configuration and a migration wizard will appear in your console UI. You have 3 months to complete this migration: January 21, 2025 through April 28, 2025.
The instructions for this migration vary depending on how CBC users authenticate:
- Non-federated (users who enters corporate credentials directly into CBC login page)
- Federated (Super Admins who uses 2FA/SAML integration)
Additional resources: