- 1 About Intrusion Prevention
- 2 Settings
- 3 Updates
- 4 Reports
- 5 Related Topics
- 6 Intrusion Prevention FAQs
- 6.1 Is Intrusion Prevention based on an open source project?
- 6.2 Why is there no reference information for a specific signature?
- 6.3 Why aren't most of Intrusion Prevention's signatures blocked by default?
- 6.4 Can Intrusion Prevention rules be configured differently within different policies?
- 6.5 What is the difference between rule block actions?
- 6.6 How can I exclude network processing for signatures?
- 6.7 How do I extend the HOME_NET variable?
About Intrusion Prevention
Intrusion Prevention is an Intrusion Detection system that detects malicious activity on your network. To detect malicious activity, Intrusion Prevention uses signature detection, a method that draws upon a database of known attack patterns. If Intrusion Prevention detects malicious activity, the session for that activity can be logged or blocked.
Note: Intrusion Prevention installs but is off by default.
Note: Intrusion Prevention requires at least 2 gigabytes of RAM.
Signatures & Actions
A signature matches behavior patterns such as plain text in a connection or the number of times a particular host attempts to open TCP connections to another host. When the conditions for a signature are met, the incident is either logged to the event log without distruption to the session or blocked which both logs the incident but breaks the connection causing that session to "stop".
The default signature database is automatically populated and updated on a regular basis, usually every 2-3 days. You can add custom signatures if you wish but it is not neccessary.
While it is tempting to block all signatures, there is a high potential for false positives which could cause legitmate traffic to stop working. It is therefore recommmnted that signatures are logged, the event log reviewed, and if the incident is deemed problematic, change the signature action to block.
It may be similarly temping to log all signatures. While logging won't stop traffic it will consume system processing resources (CPU and memory) and potentially fill your event log with false positives.
A signature can also be disabled. This means is it not loaded into the engine at all.
Signature actions are set by rules. In the context of signatures, actions are recommmended only.
Rules match characteristics of signatures and if matched, set signature action as follows:
- Enable Log
- Enable Block if Recommended is Log
- Emable Block
- Signature Identifier
- Group Identifier
- Source Address
- Source Port
- Destination Address
- Destination Port
- Any part of signature
- Custom signature
- Recommended Action
- System Memory
Variables define common attributes like the home network and ports. Under most circumstances these should be left alone.
For HOME_NET and EXTERNAL_NET, the default values ensures these are automatically calculated.
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.
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.
Simply uncheck Block (and Log if you wish) and the the traffic will no longer be blocked.
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.
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.
Signatures are automatically updated every night. Any rule modifications the administrator has made will remain. New signatures are added with recommended actions.
The Reports tab provides a view of all reports and events for all traffic handled by Intrusion Prevention.
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:
|Intrusion Prevention Summary||A summary of intrusion detection and prevention actions.|
|Intrusion Detection (all)||The amount of detected and blocked intrusions over time.|
|Intrusion Detection (logged)||The amount of detected intrusions over time.|
|Intrusion Detection (blocked)||The amount of blocked intrusions over time.|
|Top Rules (all)||The number of intrusions detevted by rule.|
|Top Rules (logged)||The number of intrusions logged by rule.|
|Top Rules (blocked)||The number of intrusions blocked by rule.|
|Top Signatures (all)||The number of intrusions detected by signature.|
|Top Signatures (logged)||The number of intrusions logged by signature.|
|Top Signatures (blocked)||The number of intrusions blocked by signature.|
|Top Classtypes (all)||The number of intrusions detected by classtype.|
|Top Classtypes (logged)||The number of intrusions logged by classtype.|
|Top Classtypes (blocked)||The number of intrusions blocked by classtype.|
|Top Categories (all)||The number of intrusions detected by category.|
|Top Categories (logged)||The number of intrusions logged by category.|
|Top Categories (blocked)||The number of intrusions blocked by category.|
|Top Source IP Addresses (all)||The number of intrusions detected by source IP address.|
|Top Source IP Addresses (logged)||The number of intrusions logged by source IP address.|
|Top Source IP Addresses (blocked)||The number of intrusions blocked by source IP address.|
|Top Source Ports (all)||The number of intrusions detected by source port.|
|Top Source Ports (logged)||The number of intrusions logged by source port.|
|Top Source Ports (blocked)||The number of intrusions blocked by source port.|
|Top Destination IP Addresses (all)||The number of intrusions detected by destination IP address.|
|Top Destination IP Addresses (logged)||The number of intrusions logged by destination IP address.|
|Top Destination IP Addresses (blocked)||The number of intrusions blocked by destination IP address.|
|Top Destination Ports (all)||The number of intrusions detected by destination port.|
|Top Destination Ports (logged)||The number of intrusions logged by destination port.|
|Top Destination Ports (blocked)||The number of intrusions blocked by destination port.|
|Top Protocols (all)||The number of intrusions detected by protocol.|
|Top Protocols (logged)||The number of intrusions logged by protocol.|
|Top Protocols (blocked)||The number of intrusions blocked by protocol.|
|All Events||All sessions scanned by Intrusion Prevention.|
|Logged Events||All sessions matching Intrusion Prevention signatures and logged.|
|Blocked Events||All sessions matching Intrusion Prevention signatures and blocked.|
The tables queried to render these reports:
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 Untangle 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.