Audit Log Messages
It can be useful to see which user actions result in which log message types in the /var/log/messages file.
The event categories spreadsheet included in the log parser package in the NetWitness Platform Parser v2.0.zip archive lists the event categories and the event parser lines to help with building reports, alerts, and queries.
NwConsole for Health & Wellness
RSA has added the command option logParse in NwConsole. This command option supports log parsing, a convenient way to check a log parser without setting up the full system to perform log parsing. For more information about the logParse command, at the command line, type help logParse.
Thick Client Error: remote content device entry not found
The remote content device entry was not found error can be generated for a correlation rule applied to a Concentrator. In NetWitness Platform Investigate, if you click the
correlation-rule-name meta value in the Alert meta key, you do not get session information.
Instead of using correlation rules on Decoders and Concentrators, use ESA rules. The ESA rules do record the correlation sessions that match the ESA rule.
View Example Parsers
Since Flex and Lua parsers are encrypted when they are delivered by Live, you cannot easily view their contents.
However, some plain text examples are available here: https://community.emc.com/docs/DOC-41108.
Configure WinRM Event Sources
The following Inside Dell article has a video that walks through the process of setting up Windows RM (Remote Management) collection: https://inside.dell.com/docs/DOC-122732.
Additionally, it contains two scripts that are shortcuts for procedures described in the "Windows Event Source Configuration Guide."