entry path=‘/api/v1/settings/global/advanced’ and content=‘{server_ssl_cert_strict”: {“changeable”: true, “value”: true}
psql -p 5002 -d cb -c “select server_ssl_cert_strict from global_query_settings;”
On the EDR Console, under Admin > Settings > Server Certificates, the mode 'Strict certificate validation' was selected and Saved. If EDR is using legacy certificates (or the Certificate Authority is not configured properly) when Strict Mode is enabled, the sensors checking-in enable this mode locally and then fail to properly authenticate.
'Strict certificate validation' has been enabled mistakenly while troubleshooting Server-to-Sensor communications, only to break additional sensor communications.
On each sensor, the CbServerSSLCertStrictCheck variable needs to be set to zero (or False) and then restart the CB service.
On each Windows sensor:
@echo off reg add HKLM\Software\CarbonBlack\config -v CbServerSSLCertStrictCheck -t REG_DWORD -d 0 -f sc stop carbonblack sc query carbonblack sc query carbonblackk sc stop carbonblackk sc start carbonblack
* May require a reboot.
On each Linux sensor:
Add the variable to /var/opt/carbonblack/response/sensorsetting.ini file.
CbServerSSLCertStrictCheck=false
Restart sensor services.
kill -s 1 $(pidof cbdaemon)
On each Mac sensor:
Run:
'defaults write com.carbonblack.sensor-service CbServerSSLCertStrictCheck 0'
Alternatively, if sensorsetting.ini is available:
Stop sensor services: 'launchctl unload /Library/LaunchDaemons/com.carbonclack.daemon.plist' Apply the change: Add/Modify 'CbServerSSLCertStrictCheck = False' in /var/lib/cb/sensorsettings.ini Restart sensor services: 'launchctl load /Library/LaunchDaemons/com.carbonclack.daemon.plist'
Setting Strict Certificate Validation on legacy certificates will cause sensors to go offline.
Sensors do not attempt to communicate with the EDR server after receiving approximately three HTTP 400 errors.