McAfee HISCDE-AB-IA Product Guide - Page 105

Wildcards, Use of environment variables, Use of predefined variables, Table 22: Wildcards

Page 105 highlights

Appendix A - Writing Custom Signatures and Exceptions Rule structure Wildcards You can use wildcards for the section values. Note the slightly different use of asterisks with paths and addresses, which normally contain forward or backward slashes. For expert subrules of signatures, the TCL wildcard scheme is used. Table 22: Wildcards Character What it represents ? (question mark) A single character. * (one asterisk) Multiple characters, including / and \ . NOTE: For paths and addresses, use ** (two asterisks) to include / and \; use * (one asterisk) to exclude / and \. | (pipe) Table 23: TCL wildcards Character ? (question mark) * (one asterisk) & (ampersand) ! (exclamation point) Wildcard escape. What it represents A single character. Multiple characters, including / and \. Example: files { Include "C:\*.txt" " } Multiple characters except / and \. Use to match the root-level contents of a folder but not any subfolders. Example: files { Include "C:\test\\&.txt" } Wildcard escape. Example: files { Include "C:\test\\yahoo!.txt" } Use of environment variables Use environment variables, the iEnv command with one parameter (the variable name) in square brackets [ ... ], as a shorthand to specify Windows file and directory path names. Environment variable iEnv SystemRoot iEnv SystemDrive What it represents C:\winnt\, where C is the drive that contains the Windows System folder. Example: files {Include [iEnv SystemRoot]\\system32\\abc.txt } C:\ where C is the drive that contains the Windows System folder. Example: files {Include [iEnv SystemDrive]\\system32\\abc.txt} Use of predefined variables Host Intrusion Prevention provides predefined variables for rule writing. These variables, are preceded by "$," and are listed below. Table 24: Windows IIS Web Server Variable Description IIS_BinDir Directory where inetinfo.exe is located IIS_Computer Machine name that IIS runs on IIS_Envelope Includes all files that IIS is allowed to access McAfee Host Intrusion Prevention 8.0 Product Guide for ePolicy Orchestrator 4.5 105

  • 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

Wildcards
You can use wildcards for the section values. Note the slightly different use of asterisks with
paths and addresses, which normally contain forward or backward slashes. For expert subrules
of signatures, the TCL wildcard scheme is used.
Table 22: Wildcards
What it represents
Character
A single character.
? (question mark)
Multiple characters, including / and \ .
NOTE:
For paths and addresses, use ** (two asterisks)
to include / and \; use * (one asterisk) to exclude / and
\.
* (one asterisk)
Wildcard escape.
| (pipe)
Table 23: TCL wildcards
What it represents
Character
A single character.
? (question mark)
Multiple characters, including / and \. Example:
files {
Include “C:\*.txt” ” }
* (one asterisk)
Multiple characters except / and \. Use to match the
root-level contents of a folder but not any subfolders.
Example:
files { Include “C:\test\\&.txt” }
& (ampersand)
Wildcard escape. Example:
files { Include
“C:\test\\yahoo!.txt” }
! (exclamation point)
Use of environment variables
Use environment variables, the iEnv command with one parameter (the variable name) in square
brackets [ ... ], as a shorthand to specify Windows file and directory path names.
What it represents
Environment variable
C:\winnt\, where C is the drive that contains the Windows
System folder. Example:
files {Include [iEnv
SystemRoot]\\system32\\abc.txt }
iEnv SystemRoot
C:\ where C is the drive that contains the Windows System
folder. Example:
files {Include [iEnv
SystemDrive]\\system32\\abc.txt}
iEnv SystemDrive
Use of predefined variables
Host Intrusion Prevention provides predefined variables for rule writing. These variables, are
preceded by “$,” and are listed below.
Table 24: Windows IIS Web Server
Description
Variable
Directory where inetinfo.exe is located
IIS_BinDir
Machine name that IIS runs on
IIS_Computer
Includes all files that IIS is allowed to access
IIS_Envelope
Appendix A — Writing Custom Signatures and Exceptions
Rule structure
105
McAfee Host Intrusion Prevention 8.0 Product Guide for ePolicy Orchestrator 4.5