Environment
- CB Response Server: 6.x and Higher
- CB Response Sensor: All Supported Versions
Symptoms
- Error within in the Sensor.log file:
CheckinResponse contained an empty/invalid ProtectionConfig
Cause
This is a legacy message that has no impact on the endpoint or server cluster. It is caused when the Cb Response server sends an empty list of newly banned hashes to the endpoint sensor during checkin.
Resolution
- No workarounds at this time
- This issue will be resolved in an upcoming sensor release (CB-22526, CB-21689)
