Skip to content
  • There are no suggestions because the search field is empty.

RSA NetWitness Platform Reports with non-ASCII characters in the CSV output do not show correctly

Issue

When viewing a NetWitness generated Report with non-ASCII characters in the CSV output (e.g Hebrew), it does not display correctly in Microsoft Excel. 
 
  • Column 1:
  • Column 2: Detect languageAfrikaansAlbanianArabicArmenianAzerbaijaniBasqueBengaliBelarusianBulgarianCatalanChinese (Simp)Chinese (Trad)CroatianCzechDanishDutchEnglishEsperantoEstonianFilipinoFinnishFrenchGalicianGeorgianGermanGreekGujaratiHaitian CreoleHebrewHindiHungarianIcelandicIndonesianIrishItalianJapaneseKannadaKoreanLaoLatinLatvianLithuanianMacedonianMalayMalteseNorwegianPersianPolishPortugueseRomanianRussianSerbianSlovakSlovenianSpanishSwahiliSwedishTamilTeluguThaiTurkishUkrainianUrduVietnameseWelshYiddish
  • Column 3:
     
  • Column 4: AfrikaansAlbanianArabicArmenianAzerbaijaniBasqueBengaliBelarusianBulgarianCatalanChinese (Simp)Chinese (Trad)CroatianCzechDanishDutchEnglishEsperantoEstonianFilipinoFinnishFrenchGalicianGeorgianGermanGreekGujaratiHaitian CreoleHebrewHindiHungarianIcelandicIndonesianIrishItalianJapaneseKannadaKoreanLaoLatinLatvianLithuanianMacedonianMalayMalteseNorwegianPersianPolishPortugueseRomanianRussianSerbianSlovakSlovenianSpanishSwahiliSwedishTamilTeluguThaiTurkishUkrainianUrduVietnameseWelshYiddish
  • Column 5:
  • Column 6:
     
  • Column 7:
     
  • Column 8:
     
     
  • Column 9:
     
  • Column 10:
  • Column 11:
     

 
Text-to-speech function is limited to 100 characters
 


Tasks

The NetWitness Reporting Engine produces a valid CSV file encoded in UTF-8 (without BOM) if the output data contains non-ASCII characters.

Although the Unicode Standard does not require or even recommend to use the byte order mark (BOM) in UTF-8 there is a common problem where Microsoft Excel opens CSV files as ASCII because it uses BOM to detect that the stream is encoded in UTF-8.

Resolution

As a workaround you can either:
  1. Convert a file to UTF-8 with BOM using any available tool or a script  (e.g. vi)
    $ vi report.csv
    :set bomb
    :set fileencoding=utf-8
    :wq


    $ file report.csv
    report.csv: UTF-8 Unicode (with BOM) text
    or 
  2. Import a CSV file using the following Microsoft Excel steps: 
    1. Open Microsoft Excel.
    2. Import the data using, Data > Get Data > From File > From Text/CSV
    3. Select the file type of "csv" and browse to your file.
    4. In the import wizard, change the File_Origin to "65001: Unicode (UTF-8)" (or choose the correct language character identifier). 
    5. The Delimiter should be a comma. 
    6. Select Load.

Product Details

RSA Product Set: NetWitness Logs & Network
RSA Product/Service Type:  Reporting Engine
RSA Version/Condition: 10.6.x, 11.x
Platform: CentOS
 
 
 

Summary

A NetWitness generated Report with non-ASCII characters in the CSV output (e.g Hebrew) do not show correctly when view with Microsoft Excel.


Approval Reviewer Queue

RSA NetWitness Suite Approval Queue