McAfee HISCDE-AB-IA Product Guide - Page 113

Windows class Illegal Use, Windows class Isapi (HTTP)

Page 113 highlights

Appendix A - Writing Custom Signatures and Exceptions Windows custom signatures Executable { Include "*"} user_name { Include "*" } vulnerability_name {Include "Vulnerable ActiveX Control Loading ?"} detailed_event_info { Include "0002E533-0000-0000-C000-000000000046"\"0002E511-0000-0000-C000-000000000046"} directives files:illegal_api_use:bad_parameter illegal_api_use:invalid_call attributes -not_auditable } Windows class Illegal Use The following table lists the possible sections and values for the Windows class Illegal Use: Section Class Id level time user_name Executable name directives Values Illegal_Use See Common sections. Notes One of three values: LsarLookupNames, LsarLookupSids, or ADMCOMConnect illegal:api Windows class Isapi (HTTP) The following table lists the possible sections and values for the Windows class Isapi with IIS: Section Class Id level time user_name Executable url query Values Isapi See Common sections. Notes One of the required parameters. Matched against the URL part of an incoming request. See Notes 1-4. One of the required parameters. Matched against the query part of an incoming request. See Notes 1-4. McAfee Host Intrusion Prevention 8.0 Product Guide for ePolicy Orchestrator 4.5 113

  • 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

Executable { Include “*”}
user_name { Include “*” }
vulnerability_name {Include "Vulnerable ActiveX Control Loading ?"}
detailed_event_info { Include
"0002E533-0000-0000-C000-000000000046"\"0002E511-0000-0000-C000-000000000046"}
directives files:illegal_api_use:bad_parameter illegal_api_use:invalid_call
attributes -not_auditable
}
Windows class Illegal Use
The following table lists the possible sections and values for the Windows class Illegal Use:
Notes
Values
Section
Illegal_Use
Class
See
Common sections
.
Id
level
time
user_name
Executable
One of three values:
LsarLookupNames,
name
LsarLookupSids, or
ADMCOMConnect
illegal:api
directives
Windows class Isapi (HTTP)
The following table lists the possible sections and values for the Windows class Isapi with IIS:
Notes
Values
Section
Isapi
Class
See
Common sections
.
Id
level
time
user_name
Executable
One of the required parameters. Matched against
the URL part of an incoming request. See Notes
1-4.
url
One of the required parameters. Matched against
the query part of an incoming request. See Notes
1-4.
query
Appendix A — Writing Custom Signatures and Exceptions
Windows custom signatures
113
McAfee Host Intrusion Prevention 8.0 Product Guide for ePolicy Orchestrator 4.5