Welcome to the Aanval Wiki. Snort, Suricata and Syslog Intrusion Detection, Situational Awareness and Risk Management.
Visit http://www.aanval.com/ for more information.
Rules flag specific activity for which they're designed and generate events that are shown in Aanval's Live Monitor. The more rules a console has selected, two outcomes will occur. First, the system's operation can slow, as it's scanning for a myriad of activity and producing such events (this is most common when nearly or every rule is selected). Second, Aanval will be bombarded with events, many to most of which don't enhance the scope or situational awareness of the network, as they aren't true threats or at least harmful to the given environment. Though Aanval is designed to handle high loads of traffic and billions of events, disk space can be quickly filled with needless event data, leaving less space for real threats, and necessitating additional work to manage disk space, either by compressing or deleting logs.
Identifying Nuisance Events
Nuisance events are those that simply fill disk space, cloud Aanval's Live Monitor, and don't add to one's situational awareness.
To identify nuisance events and create a dovetailed signature recipe:
Aanval is used from home networks to large-scale enterprise networks, and rules are available for the entire spectrum; thus, it would be misleading to list rules that every Aanval deployment should activate. However, Aanval does come loaded with the correlational features to display those nuisance events, allowing users of every deployment to easily create their own signature recipe, dovetailed for their specific environment.
- Visit Charts & Graphs (from the icons on the top-left of the screen).
- Click Frequent Events.
Displayed will be the events most frequently topping the charts, found on the Live Monitor, and filling disk space. With each selection, the signature ID will first be displayed on the left. Users can visit the following sites to learn more about that particular signature ID and whether that rule has any precedence in their environment:
For Snort rules, visit http://snort.org/search, and enter the signature ID in the search field.
The signature name and number of events generated will also be displayed, in addition to visual representations of event traffic by way of bar graphs and pie charts. Users can also perform an Advanced Search (by clicking the Search button displayed next to the signature ID) to display every instance of that particular event, the dates, times, and sources and destinations involved.
Once an event has been determined a nuisance, proceed to suppress the event. Event suppression (completely stopping event(s) from being generated or displayed) within Aanval can be accomplished by one of two methods: Signature Management or Action Management, as described below.
To suppress events by way of signature management:
- Visit Console Configuration (in the lower right-hand corner, the gear icon) > Snort Module > Signature Management.
- From the Policy drop-down box on the left of the screen, select the policy to be modified, and the rules currently selected on that policy will display. If no policy exists, visit Console Configuration > Snort Module > Policy Management, click Create Policy from the right of the screen, enter a name for the policy, and then click Update. Once complete, navigate back to Signature Management. If only one policy exists, it will be displayed in the drop-down box by default.
- On the right of the screen, select the category of the rule to be suppressed. The category is found in the message displayed for any event. Example: "WEB-CLIENT Microsoft Windows ASF parsing memory corruption attempt" is the message displayed for this particular event, "WEB-CLIENT" is the category under which the rule would be found. If both VRT (Snort) and Emerging Threats rules are being used, users may need to search two or more categories to find the specific rule, keeping in mind the first or second word of the event message displayed directs to the proper category. If the rule's name or category cannot be determined, or if more information on a rule is desired, visit http://snort.org/search/ and enter the rule's signature ID.
- Once the category is selected, navigate to the specific rule and unselect it. (To quickly find the rule, especially in a category with thousands of rules, press Ctrl/Command+F and enter the signature ID.)
- Next to the policy drop-down box, click Update.
- The updated policy now needs to be pushed to or synced with the sensor(s), and especially so that Snort recognizes the update and changes and operates accordingly, Snort needs to be restarted. This can be done via Aanval when the Sensor Management Tools (SMTs) are installed and running. Reference Signature Management to properly execute commands for syncing Aanval with Snort/Suricata sensors.
Users can use the Action Management menu, found under My Options (the paper-with-the-gear icon at the top of the console), to create a new action that deletes events based on a signature or category ID, thus suppressing unnecessary events.
To suppress events by way of the Action Management menu:
- Either select Create Action from the bottom of the menu or select an existing action.
- Once the new or existing action is selected, click "edit".
- Click Enabled.
- Enter a name and description for the action.
- Click Update.
- Click the drop-down box under Criteria to Match and choose the identifying mark. In this case, select Signature ID. Once selected, click Add. Some users may wish to add additional criteria, for example if the signature ID or event is specific to one or a couple machines. If this is the case, ensure the Match All option just above is selected.
- Click Update.
- Click the drop-down box under Actions to be Performed and choose Delete Event.
- Click Update.
Reference Action Management for additional information and commands.