Cb Defense: REST API not handling Multi-Byte text properly

Products

• Carbon Black Cloud Endpoint Standard (formerly Cb Defense)

Issue/Introduction

• Data containing multi-byte characters not displayed properly when pulled via REST API
  • integrationServices/v3/alerts
  • integrationServices/v3/auditlogs
  • integrationServices/v3/device
  • integrationServices/v3/event
  • integrationServices/v3/notification
  • integrationServices/v3/policy
  • integrationServices/v3/process

Environment

• Cb Defense PSC Console: All Versions
• Cb Defense API Connector

Cause

The Cb Defense REST API currently uses ISO-8859-1 (Latin-1) encoding

Resolution

There is no resolution to this matter as the REST API is functioning as currently designed.

Additional Information

Correctly interpreting multi-byte characters would require the use of different encoding (like UTF-8) which does support multi-byte characters.
There is work underway to improve overall internationalization to support a wider spectrum of languages.
Feel free to vote for https://community.carbonblack.com/ideas/3165 to see changes made to the encoding used for the REST API in future versions of Cb Defense.
Common languages using multi-byte character sets:

• Armenian
• Arabic
• Barents Cyrillic
• Celtic
• CentEuro
• ChineseSimp / EUC-CN
• ChineseTrad / Big5
• Croatian
• Cyrillic
• Devanagari
• Farsi (Persian)
• Gaelic
• Georgian
• Greek
• Gujarati
• Gurmukhi
• Hebrew
• Iceland
• Inuit
• Japanese / ShiftJIS
• Korean / EUC-KR
• Latin (Kermit)
• Maltese/Esperanto
• Ogham / I.S. 434
• Roman
• Romanian
• Sámi
• Thai / TIS-620
• Turkish
• Turkic Latin
• Turkic Cyrillic
• Ukrainian