This release is focused on sensitive data parsing for lists of information. If your logs contain a list of servers and each of those servers are found elsewhere in the logs Strippy can now interpret the list and Sanitise each item rather than the list as one immutable piece of sensitive information.
Changelog
Bug Fixes
- Regex searches that include start and end of line characters now actually work.
^and$now work as expected. - Newline characters provided to the configuration parameters SanitisedFileFirstLine and KeyListFirstLine were not parsed correctly. This was a problem because the default included these not-working newline characters. Strippy will now replace {1} in these configuration parameters with newline characters during processing. Defaults have been updated to match.
- Using old config styles with new scripts should not create any issues.
New Features
- Lists of sensitive data can now be processed into individual items by including a delimiter after the alias. Briefly:
Input: 2020-02-10 INFO ConnectedServers abc,def,bgf
Rule: "INFO ConnectedServers (.+?)$"="Server",","
Output: 2020-02-10 INFO ConnectedServers Server1,Server2,Server3
- There are now 3 different types of Rules that can be described to Strippy.
- Delete Rules:
"<regex>"=\delete- Remove the entire line that they match. This is for very difficult to sanitise information or overly-plentiful lines that provide little information (and clog up processing)
- Basic Rules, the 'normal' kind:
"<regex>"="<alias>"- found once and the first regex group is replaced with a numbered alias everywhere.
- List Rules - new in v2.4.0:
"<regex>"="<alias>","<delimiter>"- Lists of Sensitive information - found, split on the delimiter (delimiter can be regex) and then each element is given a different numbered alias and replaced everywhere.
- Delete Rules:
Product Support
- Added additional rules to the dt-managed.conf file.