Carbon Black 2.3.0 QRadar App Returns HTTP 410 Error

Products

• Carbon Black Cloud Endpoint Standard
• Carbon Black Cloud Enterprise EDR (formerly Cb Threathunter)
• Carbon Black Cloud Endpoint Standard (formerly Cb Defense)

Issue/Introduction

• After upgrading to the 2.3.0 QRadar App and applying a new API key
• Using the Test fails with Invalid Configuration 410 or 502 error

Environment

• QRadar Carbon Black App: 2.3.0
• Carbon Black Console: All Supported Versions

Cause

Known issue with the 2.3.0 QRadar App regarding the test connection API an older API call that no longer works

Resolution

• This can be ignored until a new version of the App is released which replaces the failing test connection API call
• This should not affect the QRadar Apps functionality
• The save button in the App will prompt with an error but it can be ignored
• 502 errors may also occur which can also be ignored
• The QRadar Documentation can still be used to setup the app and Alert and Audit log data can be collected

Additional Information

• API Calls which were deprecated
• Additional QRadar App Documentation