|
|
| (23 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| [[Category:Applications]]
| |
| <span style="display:none" class="helpSource intrusion_prevention">Intrusion_Prevention</span>
| |
| <span style="display:none" class="helpSource intrusion_prevention_status">Intrusion_Prevention#Status</span>
| |
| <span style="display:none" class="helpSource intrusion_prevention_rules">Intrusion_Prevention#Rules</span>
| |
| <span style="display:none" class="helpSource intrusion_prevention_variables">Intrusion_Prevention#Variables</span>
| |
| <span style="display:none" class="helpSource intrusion_prevention_event_log">Intrusion_Prevention#Event_Log</span>
| |
|
| |
|
| {| width='100%'
| |
| |-
| |
| | align="center" | [[Image:IntrusionPrevention.png|128px]] '''Intrusion Prevention'''
| |
| | align="center" |
| |
| {|
| |
| |-
| |
| | Other Links:
| |
| |-
| |
| |[http://www.untangle.com/store/intrusion-prevention.html Intrusion Prevention Description Page]
| |
| |-
| |
| |[http://demo.untangle.com/admin/index.do#service/intrusion-prevention Intrusion Prevention Demo]
| |
| |-
| |
| |[http://forums.untangle.com/intrusion-prevention/ Intrusion Prevention Forums]
| |
| |-
| |
| |[[Intrusion Prevention Reports]]
| |
| |-
| |
| |[[Intrusion Prevention FAQs]]
| |
| |}
| |
| |}
| |
| <br/>
| |
| ----
| |
|
| |
|
| |
| == About Intrusion Prevention ==
| |
|
| |
| Intrusion Prevention is an [http://en.wikipedia.org/wiki/Intrusion_detection_systems 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 [http://en.wikipedia.org/wiki/Session_%28computer_science%29 session] for that activity is terminated.
| |
|
| |
| ''Note:'' Intrusion Prevention installs but is off by default. When you enable Intrusion Prevention for the first time, you will be presented with a setup wizard. It is highly recommended to complete the wizard and use the recommended configuration. Using a custom configuration and enabling too many signatures may negatively impact your network.
| |
|
| |
| ''Note:'' Intrusion Prevention requires at least 2 gigabytes of RAM.
| |
|
| |
| == Setup Wizard ==
| |
|
| |
| Intrusion Prevention includes a setup wizard to help optimize the The wizard is designed to help you correctly configure the appropriate amount of rules for your network by selecting rule identifiers: classtypes and categories. The more that you select, the more rules will be enabled.
| |
|
| |
| Again, too many enabled rules may negatively impact your network, so it is highly suggested to use the recommended settings.
| |
|
| |
| ==== Step 1 - Classtypes ====
| |
|
| |
| Classtypes are a generalized grouping for rules, such as attempts to gain user access or web application attacks. The recommended settings will enable all classtypes with a medium or higher threat level. It is highly suggested to use the recommended setting.
| |
|
| |
| To enable low level classtypes or disable the recommended classtypes you can choose the '''Custom''' radio option. You will see a list of all classtypes and have the ability to enable or disable to meet your needs.
| |
|
| |
| ==== Step 2 - Categories ====
| |
|
| |
| Categories are a different rule grouping that can span multiple classtypes, such as VOIP access or operating systems. The recommended setting is to enable the preprocessor_portscan which is always included. It is highly suggested to use the recommended setting.
| |
|
| |
| To other categories choose the '''Select by name''' radio option. You will see a list of all categories and have the ability to enable or disable additional categories.
| |
|
| |
|
| |
| After Step 2 the Intrusion Prevention setup wizard is complete. Based on your selections and the amount of memory in your system, the appropriate Intrusion Prevention rules will automatically be enabled.
| |
|
| |
| Note: You can always re-run the setup wizard at any time using the '''Run Intrusion Detection/Prevention Setup Wizard''' button on the Status tab. This is useful to reset back to the recommended settings if you find problems with network performance.
| |
|
| |
|
| |
| == Settings ==
| |
|
| |
| === Status ===
| |
|
| |
| The Status tab simply shows you information about Intrusion Prevention's definitions - there is nothing to configure.
| |
|
| |
| Click the '''Run Intrusion Detection/Prevention Setup Wizard''' to re-run the setup wizard.
| |
|
| |
| {{ServiceAppScreenshot|intrusion-prevention|status}}
| |
|
| |
|
| |
| === Rules ===
| |
|
| |
| Intrusion Prevention provides a list of [[#Learning More About Signature ID Rules|rules (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 default settings configured in the setup wizard. You should only need to disable a rule if that rule blocks traffic from a unique software application that you must use. Simply uncheck '''Block''' (and '''Log''' if you wish) and the the traffic will no longer be blocked.
| |
|
| |
| The rules are automatically updated using the latest Snort signatures.
| |
|
| |
| *SID: The signature ID of the rule.
| |
| *Classtype: Snort classtype (grouping) of the rule.
| |
| *Category: Snort category (grouping) for the rule.
| |
| *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: Edit the rule. This is not recommended and should only be attempted by advanced users with a strong understanding of Snort rules. Invalid or poorly written rules will negatively impact network performance.
| |
| *Delete: Delete the rule from the system.
| |
|
| |
| Using the Add button, you can also add your own signatures to the system. This should only be attempted by advanced users with a strong knowledge of Snort signature creation. Adding invalid or poorly written rules will negatively impact network performance.
| |
|
| |
| {{AppScreenshot|intrusion-prevention|rules}}
| |
|
| |
|
| |
| === Variables ===
| |
|
| |
| This tab provides administrators access to Snort variables. These variables are used in rules to specify criteria for the source and destination of a packet.
| |
|
| |
| Snorts 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 Snort signature creation.
| |
|
| |
| {{AppScreenshot|intrusion-prevention|variables}}
| |
|
| |
|
| |
| == Updates ==
| |
|
| |
| Rules are automatically updated every night. Any rule modifications the administrator has made will remain even if the rule's behavior is updated. New rules are added with the recommended Log action. Deleted rules are not removed unless they are not enabled (neither Log or Block).
| |
|
| |
| == Reports ==
| |
|
| |
| {{:Intrusion Prevention Reports}}
| |
|
| |
|
| |
| == Related Topics ==
| |
|
| |
| [http://en.wikipedia.org/wiki/Intrusion_prevention_system Intrusion Prevention Systems]
| |
|
| |
| [http://manual.snort.org/node36.html Snort - Writing Good Snort Rules]
| |
|
| |
| [http://manual.snort.org/node27.html Snort - Writing Snort Rules]
| |
|
| |
| == Intrusion Prevention FAQs ==
| |
|
| |
| {{:Intrusion Prevention FAQs}}
| |
