Carbon Black Cloud: How to remediate ManifestDownloadFailure alarms (macOS)

[#1]

Environment

• Carbon Black Cloud Console: All Versions
  • Endpoint Standard
  • Enterprise EDR
  • Audit & Remediation
  • Workload
• Carbon Black Cloud Sensor: 3.5.3.x and Higher
• Apple macOS: All Supported Versions

Objective

Provide steps for correcting issues for macOS Sensors with downloading of content manifest data from content.carbonblack.io after receiving a related Alert

Resolution

1. Check access to content.carbonblack.io from endpoint
2. Verify that any configured proxy or firewall allows outbound (endpoint to cloud) communication

   URL	Port	Direction	SSL Inspection
   content.carbonblack.io	TCP/443	Outbound	Disabled

3. Check status of Manifest downloads and ContentDownloadFailure alarms
4. If ManifestDownloadFailure alarms continue in SensorAlarms.log, please open a case with Carbon Black Technical Support and provide

   Hostname
   Verification of access from step 1
   Configuration information of firewall/proxy exclusion from step 2 (along with date/time implemented)
   Firewall/proxy logs with any errors in communicating with content.carbonblack.io
   Output of step 3 above

Additional Notes

There is no need to perform these steps unless directed to do so by a CB Analytics Alert in the Carbon Black Cloud Console or by a member of VMware Carbon Black Technical Support.

Related Content

Carbon Black Cloud: Is access to content.carbonblack.io required?
Carbon Black Cloud: How to determine if content.carbonblack.io is blocked?
Carbon Black Cloud: What Ports must be opened on the Firewall and Proxy Servers?
Carbon Black Cloud: What’s the static IP address or hostname used by the back-end?
Carbon Black Cloud: Increased Event/Alert Volume After August 31st, 2021
Carbon Black Cloud: How to Check for ManifestDownloadFailure Alarms (macOS)