McAfee HISCDE-AB-IA Product Guide - Page 130

Solaris/Linux class UNIX_apache (HTTP), url namely, abc.

Page 130 highlights

Appendix A - Writing Custom Signatures and Exceptions Non-Windows custom signatures Solaris/Linux class UNIX_apache (HTTP) The following table lists the possible sections and values for the UNIX-based class apache: Section Class Id level time user_name Executable url query method zone directives Values UNIX_apache See Common sections. Notes Optional. Matched against the url part of an inomcing request. See Notes 1-4. Optional. Matched against the query part of an incoming request. See Notes 1-4. "GET", "POST", "INDEX" and all Optional. See Note 4. other allowed http methods Name of the zone to which the Solaris 10 or later. See Note 5. signature applies apache:requrl For URL requests. apache:reqquery For query requests. apache:rawdata For raw data requests. 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 { Class UNIX_apache Id 4001 level 1 url { Include "*abc*" } time { Include "*" } application { Include "*"} user_name { Include "*" } directives apache:request } This rule is triggered because {url}=/search/abc.exe, which matches the value of the section "url" (namely, abc). 130 McAfee Host Intrusion Prevention 8.0 Product Guide for ePolicy Orchestrator 4.5

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154

Solaris/Linux class UNIX_apache (HTTP)
The following table lists the possible sections and values for the UNIX-based class apache:
Notes
Values
Section
UNIX_apache
Class
See
Common sections
.
Id
level
time
user_name
Executable
Optional. Matched against the url part of an
inomcing request. See Notes 1-4.
url
Optional. Matched against the query part of an
incoming request. See Notes 1-4.
query
Optional. See Note 4.
“GET”, “POST”, “INDEX” and all
other allowed http methods
method
Solaris 10 or later. See Note 5.
Name of the zone to which the
signature applies
zone
For URL requests.
apache:requrl
directives
For query requests.
apache:reqquery
For raw data requests.
apache:rawdata
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 {
Class UNIX_apache
Id 4001
level 1
url { Include “*abc*” }
time { Include “*” }
application { Include “*”}
user_name { Include “*” }
directives apache:request
}
This rule is triggered because {url}=/search/abc.exe, which matches the value of the section
“url” (namely, abc).
Appendix A — Writing Custom Signatures and Exceptions
Non-Windows custom signatures
McAfee Host Intrusion Prevention 8.0 Product Guide for ePolicy Orchestrator 4.5
130