The incident snapshot doesn't seem to show enough data around the matches to verify the complete context of the original match.
DLP - supported versions
Textual data surrounding incident match highlighting is limited in order to keep performance impacts to a minimum. While all the incident data is stored in the database, displaying it requires processing power on the manager.
In this file within the Enforce server directory, SymantecDLP\Protect\config\Manager.properties
The following entries (lines 104-117 in DLP v16.1) relate to the defaults:
### Configuration for highlighting of violations on incident snapshots
# The maximum number of highlights that are shown in a chunk.
# If there are more than this number of highlights, then they are broken into separate chunks.
# The value must be less than or equal to 20.
com.vontu.manager.incidents.matches.maxHighlightsPerViolation = 20
# The maximum number of non-violating characters to show between highlighted violations in a chunk.
# The value must be less than or equal to 1000.
com.vontu.manager.incidents.matches.maxCharactersBetweenHighlights = 1000
# The maximum number of non-violating characters to show before the first highlight in a chunk
# or after the last highlight in a chunk.
# The value must be less than or equal to 20.
com.vontu.manager.incidents.matches.maxCharactersSurroundingHighlights = 20
Changing the highlighted setting will increase the amount of textual data that appears in incident snapshots:
com.vontu.manager.incidents.matches.maxCharactersSurroundingHighlights = 100
Please note that any changes to this file require a restart of the SymantecDLPManager service - which will force you to log back in to Enforce as that will kill any active sessions.
Please also note that this change affects how all incidents are displayed. Changing it substantially may vastly affect performance of the UI when viewing reports.