McAfee EPOCDE-AA-BA Product Guide - Page 220

Importing .MIB files, Working with registered executables and external commands

Page 220 highlights

18 220 Responding to events in your network Configuring Automatic Responses Task 1 Click Menu | Configuration | Registered Servers. 2 From the list of registered servers, select the desired SNMP server, then click Actions | Delete. 3 When prompted, click Yes. The SNMP server is removed from the Registered Servers list. Importing .MIB files Use this task when setting up rules to send notification messages to an SNMP server via an SNMP trap. You must import three .mib files from \Program Files\McAfee\ePolicy Orchestrator\MIB. The files must be imported in the following order: 1 NAI-MIB.mib 2 TVD-MIB.mib 3 EPO-MIB.mib These files allow your network management program to decode the data in the SNMP traps into meaningful text. The EPO-MIB.mib file depends on the other two files to define the following traps: • epoThreatEvent - This trap is sent when an Automatic Response for an McAfee ePO Threat Event is triggered. It contains variables that match properties of the Threat event. • epoStatusEvent - This trap is sent when an Automatic Response for an McAfee ePO Status Event is triggered. It contains variables that match the properties of a (Server) Status event. • epoClientStatusEvent - This trap is sent when an Automatic Response for an McAfee ePO Client Status Event is triggered. It contains variables that match the properties of the Client Status event. • rsdAddDetectedSystemEvent - This trap is sent when an Automatic Response for a Rogue System Detected event is triggered. It contains variables that match the properties of the Rogue System Detected event. • epoTestEvent - This is a test trap that is sent when you click Send Test Trap in the New SNMP Server or Edit SNMP Server pages. For instructions on importing and implementing .mib files, see the product documentation for your network management program. Working with registered executables and external commands Use these tasks when working with registered executables and external commands. You can configure automatic response rules to run an external command when the rule is initiated. Tasks • Adding registered executables on page 221 Use this task to add registered executables to your available resources. You can run external command action by providing the registered executables and their arguments. • Editing registered executables on page 221 Use this task to edit an existing registered executable entry. • Deleting registered executables on page 221 Use this task to delete a registered executable entry. • Duplicating registered executables on page 221 Use this task to duplicate a registered executables to your available resources. McAfee® ePolicy Orchestrator® 4.6.0 Software Product Guide

  • 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
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328

Task
1
Click
Menu
|
Configuration
|
Registered Servers
.
2
From the list of registered servers, select the desired SNMP server, then click
Actions
|
Delete
.
3
When prompted, click
Yes
.
The SNMP server is removed from the Registered Servers list.
Importing .MIB files
Use this task when setting up rules to send notification messages to an SNMP server via an SNMP trap.
You must import three .mib files from
\Program Files\McAfee\ePolicy Orchestrator\MIB
. The files
must be imported in the following order:
1
NAI-MIB.mib
2
TVD-MIB.mib
3
EPO-MIB.mib
These files allow your network management program to decode the data in the SNMP traps into
meaningful text. The EPO-MIB.mib file depends on the other two files to define the following traps:
epoThreatEvent
— This trap is sent when an Automatic Response for an McAfee ePO Threat Event
is triggered. It contains variables that match properties of the Threat event.
epoStatusEvent
— This trap is sent when an Automatic Response for an McAfee ePO Status Event
is triggered. It contains variables that match the properties of a (Server) Status event.
epoClientStatusEvent
— This trap is sent when an Automatic Response for an McAfee ePO Client
Status Event is triggered. It contains variables that match the properties of the Client Status event.
rsdAddDetectedSystemEvent
— This trap is sent when an Automatic Response for a Rogue
System Detected event is triggered. It contains variables that match the properties of the Rogue
System Detected event.
epoTestEvent
— This is a test trap that is sent when you click
Send Test Trap
in the New SNMP
Server or Edit SNMP Server pages.
For instructions on importing and implementing .mib files, see the product documentation for your
network management program.
Working with registered executables and external commands
Use these tasks when working with registered executables and external commands. You can configure
automatic response rules to run an external command when the rule is initiated.
Tasks
Adding registered executables
on page 221
Use this task to add registered executables to your available resources. You can run
external command action by providing the registered executables and their arguments.
Editing registered executables
on page 221
Use this task to edit an existing registered executable entry.
Deleting registered executables
on page 221
Use this task to delete a registered executable entry.
Duplicating registered executables
on page 221
Use this task to duplicate a registered executables to your available resources.
18
Responding to events in your network
Configuring Automatic Responses
220
McAfee
®
ePolicy Orchestrator
®
4.6.0 Software Product Guide