McAfee HISCDE-AB-IA Product Guide - Page 112

Windows class Illegal Host IPS API Use

Page 112 highlights

Appendix A - Writing Custom Signatures and Exceptions Windows custom signatures Section Id level time user_name Executable handler module directives Values See Common sections. Notes Path name of the executable that A required parameter. is being hooked by another executable. hook:set_windows_hook To prevent injection of a DLL into an executable when using hook:set_windows_hook, include the executable in the Application Protection List. Windows class Illegal Host IPS API Use The following table lists the possible sections and values for the Windows class Illegal API Use: Section Class Id level time user_name Executable vulnerability_name detailed_event_info directives Values Illegal_API_Use See Common sections. Notes Name of the vulnerability One or more CLSIDs. This is a 128-bit number that represents a unique ID for a software component. Typically displayed as: "{FAC7A6FB-0127-4F06-9892-8D2FC56E3F76}" illegal_api_use:bad_parameter illegal_api_use:invalid_call Use this class to create a custom killbit signature. The killbit is a security feature in web browsers and other applications that use ActiveX. A killbit specifies the object class identifier (CLSID) for ActiveX software controls that are identified as security vulnerability threats. Applications that use ActiveX do not load specified ActiveX software with a corresponding killbit in place. The primary purpose of a killbit is to close security holes. Killbit updates are typically deployed to Microsoft Windows operating systems via Windows security updates. Here is an example of a signature: Rule { tag "Sample4" Class Illegal_API_Use Id 4001 level 4 112 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

Notes
Values
Section
See
Common sections
.
Id
level
time
user_name
Executable
A required parameter.
Path name of the executable that
is being hooked by another
executable.
handler module
To prevent injection of a DLL into an executable
when using hook:set_windows_hook, include the
executable in the Application Protection List.
hook:set_windows_hook
directives
Windows class Illegal Host IPS API Use
The following table lists the possible sections and values for the Windows class Illegal API Use:
Notes
Values
Section
Illegal_API_Use
Class
See
Common sections
.
Id
level
time
user_name
Executable
Name of the vulnerability
vulnerability_name
This is a 128-bit number that represents a unique
ID for a software component. Typically displayed
One or more CLSIDs.
detailed_event_info
as:
"{FAC7A6FB-0127-4F06-9892-8D2FC56E3F76}"
illegal_api_use:bad_parameter
directives
illegal_api_use:invalid_call
Use this class to create a custom killbit signature. The killbit is a security feature in web browsers
and other applications that use ActiveX. A killbit specifies the object class identifier (CLSID) for
ActiveX software controls that are identified as security vulnerability threats. Applications that
use ActiveX do not load specified ActiveX software with a corresponding killbit in place.
The primary purpose of a killbit is to close security holes. Killbit updates are typically deployed
to Microsoft Windows operating systems via Windows security updates.
Here is an example of a signature:
Rule {
tag "Sample4"
Class Illegal_API_Use
Id 4001
level 4
Appendix A — Writing Custom Signatures and Exceptions
Windows custom signatures
McAfee Host Intrusion Prevention 8.0 Product Guide for ePolicy Orchestrator 4.5
112