Intrusion Prevention3

Intrusion_Prevention Intrusion_Prevention#Status Intrusion_Prevention#Rules Intrusion_Prevention#Variables Intrusion_Prevention#Event_Log

Intrusion Prevention

Other Links: Intrusion Prevention Description Page Intrusion Prevention Demo Intrusion Prevention Forums Intrusion Prevention Reports Intrusion Prevention FAQs

---

About Intrusion Prevention

Intrusion Prevention is an Intrusion Detection system that detects malicious activity on your network.

To detect malicious activity, Intrusion Prevention uses signatures, a method that draws upon a database of known attack patterns. If a network session matches a signature, its ``action`` directs Intrusion Prevention to Log or Block will be applied to that activity. Log records matching activity to the Intrusion Prevention event log. Block performs the log action but also stops the network activity.

There is tremendous diversity between networks and it is possible for a signature to correctly identify malicious activity on one network and incorrectly match legitimate traffic on another. Logging all matching signatures can make it difficult to effectively monitor Intrusion Prevention and blocking can disrupt legitimate traffic causing cause your network to appear to be broken. Therefore it is perfectly legitimate for there to be many signatures set as disabled or not active in Intrusion Prevention. In fact, it is advised that you use to the Recommended actions as specified by the signature database providers.

The database contains over 26,000 signatures making it difficult to manage signatures directly. Rules are used to configure groups of signatures on matching various attributes. A condition can match an attribute such as classtype. For all signatures that match, they are configured in Intrusion Prevention according to the rule action. Any signature not matched by a rule is Disabled. A default set of rules based on system memory are enabled by default.

The signature database is automatically updated several times a week. New and updated rules will be configured as determined by rules.

All detected activity for enabled signatures is recorded to the Intrusion Prevention All Events log. You should review this log on a daily basis.

Overview

A signature may also be disabled.

Considerations

Intrusion Prevention requires at least 2 gigabytes of RAM.

The number of signatures enabled combined with amount of traffic on your network affect how much system memory is used by IPS. Intrusion Prevention can be memory intensive. How much is used is a combination of the number of signatures enabled for Log or Block and the amount of traffic that goes through your system.

Not all signatures should be enabled. In the majority of cases, using Recommended actions for approrpiate classtypes is the most appropriate.

Settings

Status

The Status tab shows the following information:

• Memory Usage. The amount of system memory the IPS engine is using compared to your installed system memory.

• Metrics. The number of blocked, logged, and scanned sessions.

• Overview. Signatures and Signature Updates.
  • Signatures. Total number of signatures available and the number set for Log, Block, Disabled.
  • Updates. The last time signatures were updated and the last time a check was performed. Updates do not neccessarily occur on each check.

Rules

Rules control whether signatures are active or not by matching conditions and performing actions upon signatures.

match characteristics of signatures and if matched, set signature action.

Order.

Conditions:

• Signature Identifier
• Group Identifier
• Category
• Classtype
• Message
• Protocol
• Source Address
• Source Port
• Destination Address
• Destination Port
• Any part of signature
• Custom signature
• Recommended Action
• System Memory

• Recommended
• Enable Log
• Enable Block if Recommended is Log
• Emable Block
• Disable

Simply uncheck Block (and Log if you wish) and the the traffic will no longer be blocked.

view on demo

Signatures

Intrusion Prevention provides a list of signatures that you can have Untangle Log or Block when traffic matches them. The rules are grouped by classtype and can be searched using the search field at the bottom of the page.

In most cases, you do not need to change the recommended settings. You should only need to disable a signature if that rule blocks traffic from a unique software application that you must use. CREATE RULES.

The signatures are automatically updated using the latest Suricata signatures.

• SID: The signature's identifier.
• Classtype: Suricata classtype (grouping) of the signature.
• Category: Suricata category (grouping) for the signature.
• Msg: Name of the signature.
• Reference: Links to reference information on the attack the signature will detect (if available).
• Log/Block: Enable these to log or block traffic matching the signature.

• Edit: Modify a a custom signature from the system.
• Copy: Copy a signature. Copied signatures become part of the custom set.
• Delete: Delete a custom signature from the system.

Using the Add button, you can also add your own custom signatures to the system. This should only be attempted by advanced users with a strong knowledge of Suricata signature creation. Adding invalid or poorly written rules will negatively impact network performance.

Signatures match malicious network traffic patterns and perform actions such as logging without affecting the session or blocking the session.

view on demo

Variables

This tab provides administrators access to Suricata variables. These variables are used in rules to specify criteria for the source and destination of a packet.

Suricata's most important variable is $HOME_NET. $HOME_NET defines the network or networks you are trying to protect - it is computer automatically based on your network configuration - it includes all local networks (including aliases).

Using the Add button, custom variables can be added. Adding variables may be used by users adding their own rules.This should only be attempted by advanced users with a strong knowledge of Suricata signature creation.

view on demo

Updates

Signatures are automatically updated every night. Any rule modifications the administrator has made will remain. New signatures are added with recommended actions.

Reports

Intrusion_Prevention_Reports

The Reports tab provides a view of all reports and events for all traffic handled by Intrusion Prevention.

Reports

This applications reports can be accessed via the Reports tab at the top or the Reports tab within the settings. All pre-defined reports will be listed along with any custom reports that have been created.

Reports can be searched and further defined using the time selectors and the Conditions window at the bottom of the page. The data used in the report can be obtained on the Current Data window on the right.

Pre-defined report queries: {{#section:All_Reports|'Intrusion Prevention'}}

The tables queried to render these reports:

• intrusion_prevention_events

Related Topics

Intrusion Prevention Systems

Suricata - Writing Suricata Signatures

Intrusion Prevention FAQs

Is Intrusion Prevention based on an open source project?

Yes, Intrusion Prevention is based on Suricata.

Why is there no reference information for a specific signature?

If there is no information link available for a specific signautre, you can try searching the signature ID at Suricata Rules for more info.

Why aren't most of Intrusion Prevention's signatures blocked by default?

Because many signatures can block legitimate traffic in addition to malicious exploits we don't enable blocking by default.

You're free to change the action of any rule to block signatures as you see fit for your network.

Can Intrusion Prevention rules be configured differently within different policies?

No. Intrusion Prevention applies to all traffic flowing through NG Firewall so different configurations are not possible.

What is the difference between rule block actions?

Enable Block if Recommended is Log will only enable a signature to Block if its Recommended Action is Log.

Enable Block will unconditionally set all matching signatures to Block.

The difference is that a signature's Recommended Action (almost always either Log or Disabled) is carefully considered by the signature provider. A rule set to Enable Block if Recommended is Log will likely set that smaller and "safer" set of signatures to Block whereas Enable Block will likely set a larger set of signatures with more potential to disrupt legitimate traffic on your network.

How can I exclude network processing for signatures?

Create a variable with the network you wish to exclude in standard CIDR format such as 192.168.1.0/24. If you have multiple networks to exclude, create a comma-separated list surrounded by square brackets such as [192.168.25.1.0/24,10.10.0.0/24].

Next, create a rule to match the signatures you wish to exclude. For Action select Whitelist and then specify the variable you created to either Source or Destination networks.

NOTE: Unlike other Rule actions, the Whitelist action doesn't enable logging/blocking for rules. Signatures affected by Whitelist rules will still be processed by the first matching non-Whitelist Rule.

How do I extend the HOME_NET variable?

IPS attempts to determine the appropriate HOME_NET based on your network configuration but if a network doesn't appear to be in the list (mouse over the variable), you can either replace the HOME_NET variable value entirely or append to the existing using by leaving the default value and adding a comma separated list of additional CIDR formatted networks such as default,10.10.10.10/32,192.168.2.0/24.