Filtering events is accomplished via the auditing 'objectivespolicies' capability. Any number of objectives audit policies may be specified, and are displayed within the Log Filter Configuration window [previously referred to as Objectives Audit Policy Configuration]. Each of the objectives audit policies provides a high level of control over which events are selected and reported. Events are selected using specific log filters. A default log filter is defined to ensure events are captured, that will then be passed directly to the configured network destination.
...
The following parameters of the objective audit policy may be set:
- Select the Match Type. Any matching entries defined in the General Search Term may be included or excluded depending on the option selected. All entries are included by default.
- General Search Term. Used to perform a case insensitive search against each log entry collected (including wildcards such as '*' and '?').
- Regular Expression: The search string may be treated as a Perl Compatible Regular Expression if this checkbox is selected. This allows a more powerful and refined text matching and targeted objectives audit policies allowing sophisticated forensic analysis and reporting, particularly when small details get lost in noisy log environments. Some common useful regular expressions include:
...
#?([a-f0-9]{6}|[a-f0-9]{3})
- Select the Alert Level. A criticality level may be assigned to enable the Snare user to designate audit events to their most pressing business security objectivesaudit policies, and to quickly identify the level of importance via the criticality options in the drop down list. The Latest Events page will highlight the event in the selected Snare criticality color assigned to your objectiveaudit policy. User can choose the criticality level depending on the destination the event is being sent. There are options to assign criticality for each destination based on the format Snare, Syslog, CEF or LEEF. Each of these criticalites is then assigned to the event. While sending to the destination, specific criticality is assigned to the final event string depending on the destination type ie Snare, Syslog, CEF or LEEF.
- Snare - Critical, Priority, Warning, Information, Clear
- Syslog - Emergency, Alert, Critical, Error, Warning, Notice, Info, Debug
- CEF - 0 - 10, 0 is least severe and 10 is most severe.
- LEEF - 1 - 10, 1 is least severe and 10 is most severe.
To save and set the changes to the above settings, and to ensure the registry has received the new configuration perform the following:
...