|
|
| (22 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 ACTIONED.
| |
|
| |
| ''Note:'' Intrusion Prevention installs but is off by default.
| |
|
| |
| ''Note:'' Intrusion Prevention requires at least 2 gigabytes of RAM.
| |
|
| |
|
| |
| == Settings ==
| |
|
| |
| === Status ===
| |
|
| |
| The Status tab simply shows you information about Intrusion Prevention's definitions - there is nothing to configure.
| |
|
| |
| MEMORY METRICS
| |
|
| |
| SIGNATURE ENABLED OVERVIEW
| |
|
| |
| {{ServiceAppScreenshot|intrusion-prevention|status}}
| |
|
| |
|
| |
| === Rules ===
| |
|
| |
| Simply uncheck '''Block''' (and '''Log''' if you wish) and the the traffic will no longer be blocked.
| |
|
| |
| *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.
| |
|
| |
| === Signatures ===
| |
|
| |
| Intrusion Prevention provides a list of [[#Learning More About Signature ID 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 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 Snort signatures.
| |
|
| |
| *SID: The signature's identifier.
| |
| *Classtype: Snort classtype (grouping) of the signature.
| |
| *Category: Snort 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.
| |
|
| |
| {{AppScreenshot|intrusion-prevention|rules}}
| |
|
| |
|
| |
| === 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.
| |
|
| |
| 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 ==
| |
|
| |
| 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}}
| |
|
| |
|
| |
| == 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}}
| |
