Carbon Black Cloud on AWS GovCloud (US) Documentation

End of Life Announcement

The End of Life/ End of General Support date for Carbon Black on AWS GovCloud is Monday, October 7, 2024.

Please export and take action to securely deprovision your data BEFORE your licenses expire. Data will not be available beyond the EOL date of October 7, 2024, so quick action is strongly advised.

See:

Exporting Carbon Black data
Safely Deprovisioning your Carbon Black Account


Quick Links:
Console Documentation Release Notes User Guide Identity and Access Onboarding Getting Support Workloads Workloads Guide Product Operating Environment Requirements* Endpoint Standard OER Audit and Remediation OER Enterprise EDR OER Prevention OER Workloads OER	Sensor Installation Sensor Installation Guide Latest Sensor Release Notes Windows Sensor 4.0.0.1292 Linux Sensor 2.15.1 macOS Sensor 3.8.0.58 Sensor Operating Environment Requirements* Windows Sensor OER (Desktop) Windows Sensor OER (Server) Linux Sensor OER macOS Sensor OER Sensor Lifecycle Support Policy	Additional Resources Carbon Black Developer Network Documentation for Related Products Carbon Black Cloud Documentation
Attention: * The content for product OERs, Sensor OERs, and sensor release notes is maintained on the documentation site: Carbon Black Cloud Documentation These links open on a separate tab.

Carbon Black Cloud™ on AWS GovCloud (US) is an integrated cloud offering jointly developed by Amazon Web Services (AWS) and VMware.

Carbon Black Cloud is a cloud native endpoint, workload, and container protection platform that combines the intelligent system hardening and behavioral prevention needed to keep emerging threats at bay, using a single lightweight agent and an easy-to-use console.

Exporting Carbon Black data

Console data can be exported in .csv format. This includes audit logs which need to be retained for a longer period to meet compliance requirements established by your company, as well as device inventories and other data types. If you have set up integrations through data forwarders to your own data storage solution/SIEM, you will be in control of the retention of this data.

Tip: For more information on exporting data, consult the respective export topics in the VMware Docs. Note: This site will be transitioning to techdocs.broadcom.com in the near future.

Safely Deprovisioning your Carbon Black Account

To safely deprovision your Carbon Black account, you should follow the below steps in the order provided:

Remove all the Carbon Black Cloud sensors from devices:
- Devices can be uninstalled and removed in bulk from the Carbon Black Cloud console.
- Ensure no sensors are displayed in the Carbon Black Cloud console.
Reset the sensor install codes to prevent new automated installations.
Remove all alert configurations, sensor groups, policies, etc.
Remove all API keys.
Remove all users from the CSP console except the user who is performing the operation.
Remove any SSO configuration.

Failure to perform these actions could result in orphaned software running on your systems.