Difference between revisions of "Intrusion Prevention3"

From UntangleWiki
Jump to: navigation, search
(Blanked the page)
(12 intermediate revisions by the same user not shown)
Line 1: Line 1:
<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]] &nbsp; &nbsp; '''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]]
== 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 ''signatures'', a method that draws upon a database of known attack patterns.
If a network [http://en.wikipedia.org/wiki/Session_%28computer_science%29 session] matches a signature, its enabled ''action'' directs Intrusion Prevention to
''Log'' (records the incident but '''does not stop''' the activity) or ''Block'' (records the incident and '''does stop''' the 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.
''Note:'' Intrusion Prevention installs but is off by default.
=== 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.
* 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 [[#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 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.
=== 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 ==
{{:Intrusion Prevention Reports}}
== All Events ==
== Related Topics ==
[http://en.wikipedia.org/wiki/Intrusion_prevention_system Intrusion Prevention Systems]
[https://suricata.readthedocs.io/en/suricata-3.2.1/rules/index.html Suricata - Writing Suricata Signatures]
== Intrusion Prevention FAQs ==
{{:Intrusion Prevention FAQs}}

Latest revision as of 20:57, 13 November 2018