Intrusion Prevention3: Difference between revisions
No edit summary |
No edit summary |
||
| Line 42: | Line 42: | ||
=== Overview === | === Overview === | ||
Signatures match malicious network traffic patterns and perform actions such as logging without affecting the session or blocking the session. | ''Signatures'' match malicious network traffic patterns and perform actions such as logging without affecting the session or blocking the session. | ||
A signature may also be disabled. | A signature may also be disabled. | ||
Matching patterns and performing an action is how IPS works. | Matching patterns and performing an action is how IPS works. | ||
| Line 59: | Line 59: | ||
All enabled and matched signature sessions are logged to the Intrusion Prevention All Events log. It's highly recommended that you review this log on a daily basis. | All enabled and matched signature sessions are logged to the Intrusion Prevention All Events log. It's highly recommended that you review this log on a daily basis. | ||
=== | === Considerations === | ||
Intrusion Prevention requires at least 2 gigabytes of RAM. | Intrusion Prevention requires at least 2 gigabytes of RAM. | ||
Revision as of 14:15, 13 November 2018
 Intrusion Prevention
|
|
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.
Overview
Signatures match malicious network traffic patterns and perform actions such as logging without affecting the session or blocking the session. A signature may also be disabled. Matching patterns and performing an action is how IPS works.
A signature's Recommended Action is recommended by the provider. Its action can be set to Log, Block, or Disabled. If Disabled, the signature is not loaded into memory. Providers rare never set a signautre's Recommendation Action to block as pattern matching is not always perfect and can cause a false positive. Blocking a false positive prevents legitimate traffic on your network so enabling the Block action should be done with caution.
Rules are used to set a group of one or more signature's actions, allowing you to effectively manage the large number of recommended signatures, current around 26,0000 signatures. Rules can match signature conditions such as a signature's classtype or category groupings. On a match, a rule will cause a signature to be enabled (Log, Block), disabled, or follow Recommended actions. Any signature not matched by a rule is Disabled.
Recommended signatures are automatically updated several times a week. Whether new or updated signatures are enabled is determined by your rule settings.
All enabled and matched signature sessions are logged to the Intrusion Prevention All Events log. It's highly recommended that you review this log on a daily basis.
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.
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.
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.
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.
Updates
Signatures are automatically updated every night. Any rule modifications the administrator has made will remain. New signatures are added with recommended actions.
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:
All Events
Related Topics
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.
