Endpoint Standard: How to Configure Sensors to use HTTPS for Signature Updates

[#1]

Environment

• Carbon Black Cloud Console: 0.45 and higher
  • Endpoint Standard
• Carbon Black Cloud Sensor: 3.3.x.x and higher
• Microsoft Windows: All supported versions
• Local Scanner installed and enabled by policy to use Carbon Black Cloud servers for updates

Objective

Configure the Local Scanner policy to use HTTPS for Signature updates

Resolution

1. Go to Enforce > Policies
2. Select desired policy
3. Go to Local Scanner tab
4. Click Add button under "Update Servers For Onsite Devices" section
5. Enter HTTPS URL

   https://updates2.cdc.carbonblack.io/update2

6. Tick box for "Preferred Servers" for HTTPS entry or delete HTTP entry
7. Perform same actions for "Update Servers For Offsite Devices" if desired (recommended)
8. Save policy changes
9. Allow the Sensor to update on schedule and monitor results or run update manually via RepCLI 
10. Confirm URL used in C:\Program Files\Confer\scanner\upd.log file

    Param 9 --internet-srvs=https://updates2.cdc.carbonblack.io/update2

Additional Notes

• Sensor versions prior to 3.3.x.x are not be able to update signatures over an HTTPS session
  • Where an organization has Sensors at or below 3.3.x.x the HTTP URL needs to remain

Related Content

Endpoint Standard: Signature Updates Fail With Default Settings
Endpoint Standard: How to Update Virus Definition Files With RepCLI
Cb Defense: How to Download the AV Signature Pack and Configure Updates for Local Scan