Home » McAfee Manuals » Computer Software » McAfee HISCDE-AB-IA » Manual Viewer

McAfee HISCDE-AB-IA Product Guide - Page 114

Note 1, matched against {url} and the query is matched against {query}. For example

View all McAfee HISCDE-AB-IA manuals

Add to My Manuals
Save this manual to your list of manuals

Page 114 highlights

Appendix A - Writing Custom Signatures and Exceptions Windows custom signatures Section method directives Values Notes GET, POST, INDEX or any other One of the required parameters. See Note 4. allowed HTTP method isapi:request For all three types of incoming http requests. isapi:requrl For url requests. isapi:reqquery For query requests. isapi:rawdata For raw data requests. isapi:response For request response. Note 1 An incoming http request can be represented as: http://www.myserver.com/ {url}?{query}. In this document, we refer to {url} as the "URL" part of the http request and {query} as the "query" part of the http request. Using this naming convention, we can say that the section "URL" is matched against {url} and the section "query" is matched against {query}. For example the following rule is triggered if the http request http:// www.myserver.com/search/abc.exe?subject=wildlife&environment=ocean is received by IIS: Rule { tag "Sample6" Class Isapi Id 4001 level 1 url { Include "*abc*" } Executable { Include "*"} user_name { Include "*" } directives isapi:request } This rule is triggered because {url}=/search/abc.exe, which matches the value of the section "url" (i.e. abc). Note 2 Before matching is done, sections "url" and "query" are decoded and normalized so that requests cannot be filled with encoding or escape sequences. Note 3 A maximum length restriction can be defined for the sections "url" and "query". By adding ";number-of-chars" to the value of these sections, the rule can match only if the {url} or {query} have more characters than "number-of-chars". For example, "abc*;500" matches strings containing 'abc' that are 500 characters or more; "*abc;xyz*;" matches any string containing 'abc;xyz' regardless of length. Note 4 A rule needs to contain at least one of the optional sections url, query, method. 114 McAfee Host Intrusion Prevention 8.0 Product Guide for ePolicy Orchestrator 4.5

Section	Page
Contents	3
Introducing Host Intrusion Prevention	7
Host IPS protection	7
Host IPS policies	8
Host IPS policy management	9
Host IPS policy tracking and tuning	10
Managing Your Protection	12
Information management	12
Host IPS dashboards	12
Host IPS queries	13
Predefined and custom queries to analyze your protection	13
Policy management	16
Where to find policies	16
Configuring polices	17
Creating a new policy	18
Changing policy assignment	18
Default protection and tuning	18
Clients and planning your deployment	19
Client data and what it tells you	19
Adaptive mode	20
FAQ — Adaptive mode	21
Host IPS policy migration	22
System management	23
Host IPS permission sets	23
Assigning permission sets	24
Host IPS server tasks	25
Host IPS event responses	26
Tips on using automatic responses	26
Host IPS protection updates	27
Checking in update packages	27
Checking in packages manually	28
Updating clients with content	28
Updating content from the client	28
Configuring IPS Policies	29
Overview of IPS policies	29
Methods for delivery of IPS protection	30
Signatures	31
Behavioral rules	32
Reactions	32
Exceptions	32
Application protection rules	33
Events	33
Enable IPS protection	33
Configuring the IPS Options policy	34
Set the reaction for IPS signatures	35
Configuring the IPS Protection policy	36
Define IPS protection	36
Configuring the IPS Rules policy	37
Assigning multiple instances of the policy	37
FAQ — Multiple-instance policies	38
How IPS signatures work	39
Configuring IPS signatures	40
Creating custom signatures	41
Creating custom signatures with a wizard	42
FAQ — Use of wildcards in IPS Rules	42
How IPS application protection rules work	43
Configuring IPS application protection rules	45
Creating application protection rules	45
How IPS exceptions work	46
Configuring IPS exceptions	46
Creating exception rules	47
Monitor IPS events	47
Managing IPS events	48
Creating an exception from an event	49
Creating a trusted application from an event	50
Monitor IPS client rules	50
Managing IPS client rules	50
Configuring Firewall Policies	52
Overview of Firewall policies	52
How firewall rules work	53
Firewall protocols	53
How firewall rule groups work	55
Firewall rule group connection isolation	56
How the Host IPS catalog works	58
Firewall stateful packet filtering and inspection	59
Firewall state table	60
How stateful filtering works	60
How stateful packet inspection works	61
Stateful protocol tracking	62
How learn and adaptive modes affect the firewall	63
Firewall client rules	64
Enable firewall protection	64
Configuring the Firewall Options policy	65
FAQ — McAfee TrustedSource and the firewall	66
Define firewall protection	67
Configuring the Firewall Rules policy	68
Creating and editing firewall rules	69
Creating and editing firewall rule groups	69
Creating connection isolation groups	70
Blocking DNS traffic	70
Using the Host IPS catalog	70
Managing firewall client rules	71
FAQ — Use of wildcards in Firewall Rules	72
Configuring General Policies	73
Overview of General policies	73
Define client functionality	74
Configuring a Client UI policy	74
Setting Client UI general options	75
Setting Client UI advanced options and passwords	75
Creating passwords on a per system basis	76
Setting Client UI troubleshooting options	76
Define trusted networks	77
Configuring a Trusted Networks policy	78
Define trusted applications	78
Configuring a Trusted Applications policy	79
Creating and editing Trusted Application rules	79
Assigning multiple instances of the policy	80
Working with Host Intrusion Prevention Clients	81
Overview of the Windows client	81
System tray icon menu	81
Client console for Windows clients	83
Unlocking the Windows client interface	83
Setting client UI options	83
Troubleshooting the Windows client	84
Setting options for IPS logging	85
Settings options for Firewall logging	85
Disabling Host IPS engines	85
Windows client alerts	86
Responding to Intrusion alerts	86
Responding to Firewall alerts	87
Responding to Spoof Detected alerts	87
About the IPS Policy tab	88
Customizing IPS Policy options	88
Creating and editing IPS Policy exception rules	89
About the Firewall Policy tab	89
Customizing Firewall Policy options	90
Creating and editing Firewall rules	90
About the Blocked Hosts tab	91
Editing the Blocked Hosts list	92
About the Application Protection List tab	92
About the Activity Log tab	93
Customizing Activity Log options	93
Overview of the Solaris client	94
Policy enforcement with the Solaris client	94
Troubleshooting the Solaris client	95
Verifying Solaris installation files	96
Verifying the Solaris client is running	96
Stopping the Solaris client	96
Restarting the Solaris client	96
Overview of the Linux client	97
Policy enforcement with the Linux client	97
Notes about the Linux client	97
Troubleshooting the Linux client	98
Verifying Linux installation files	99
Verifying the Linux client is running	99
Stopping the Linux client	99
Restarting the Linux client	99
Appendix A — Writing Custom Signatures and Exceptions	101
Rule structure	101
Common sections	102
Optional common sections	104
Wildcards and variables	104
Windows custom signatures	107
Windows class Buffer Overflow	107
Windows class Files	108
Windows class Hook	111
Windows class Illegal Host IPS API Use	112
Windows class Illegal Use	113
Windows class Isapi (HTTP)	113
Windows class Program	116
Windows class Registry	117
Windows class Services	120
Windows class SQL	122
Classes and directives per Windows platform	123
Non-Windows custom signatures	127
Solaris/Linux class UNIX_file	127
Solaris/Linux class UNIX_apache (HTTP)	130
Solaris/Linux class UNIX_Misc	131
Solaris class UNIX_bo	132
Solaris class UNIX_map	133
Solaris class UNIX_GUID	133
Classes and directives per UNIX platform	134
Appendix B — Troubleshooting	136
General issues	136
Host IPS logs	141
Clientcontrol.exe utility	144

Match case Limit results 1 per page

Notes

Values

Section

One of the required parameters. See Note 4.

GET, POST, INDEX or any other

allowed HTTP method

method

For all three types of incoming http requests.

isapi:request

directives

For url requests.

isapi:requrl

For query requests.

isapi:reqquery

For raw data requests.

isapi:rawdata

For request response.

isapi:response

Note 1

An incoming http request can be represented as: http://www.myserver.com/ {url}?{query}. In

this document, we refer to {url} as the “URL” part of the http request and {query} as the “query”

part of the http request. Using this naming convention, we can say that the section “URL” is

matched against {url} and the section “query” is matched against {query}. For example the

following rule is triggered if the http request http://

www.myserver.com/search/abc.exe?subject=wildlife&environment=ocean is received by IIS:

Rule {

tag "Sample6"

Class Isapi

Id 4001

level 1

url { Include “*abc*” }

Executable { Include “*”}

user_name { Include “*” }

directives isapi:request

}

This rule is triggered because {url}=/search/abc.exe, which matches the value of the section

“url” (i.e. abc).

Note 2

Before matching is done, sections “url” and “query” are decoded and normalized so that requests

cannot be filled with encoding or escape sequences.

Note 3

A maximum length restriction can be defined for the sections “url” and “query”. By adding

“;number-of-chars” to the value of these sections, the rule can match only if the {url} or {query}

have more characters than “number-of-chars”. For example, "abc*;500" matches strings

containing 'abc' that are 500 characters or more; "*abc;xyz*;" matches any string containing

'abc;xyz' regardless of length.

Note 4

A rule needs to contain at least one of the optional sections url, query, method.

Appendix A — Writing Custom Signatures and Exceptions

Windows custom signatures

McAfee Host Intrusion Prevention 8.0 Product Guide for ePolicy Orchestrator 4.5

114