Junk values in the Incident CSV export from enforce console.

Products

• Data Loss Prevention Enterprise Suite

Issue/Introduction

There may be junk values seen in incident report exported as csv file which is opened in Excel application.

Environment

NA

Cause

If a single field in a CSV report contains more than 32k characters, Excel will push any characters beyond this limit into the next cell, causing data to shift into additional columns. The "Message component Name" And "Message component Size" field usually exceeds 32K characters, leading to incorrect rendering in Excel. This is an issue with Excel's limitation on cell character count and not a problem with the DLP system.

 

Resolution

This is an MS Excel bug and not a DLP issue this can be verified by viewing the raw CSV data in Notepad++, it appears correctly formatted. Fields are separated by commas, and fields with multiple values, such as "Message Component Name" and "Message Component Size," are enclosed in double-quotes. This encapsulation indicates that these multi-value blocks should be treated as a single entry in the CSV file.