McAfee EPOCDE-AA-BA Product Guide - Page 61

Configuring Rogue System Detection server settings - meeting locations

Page 61 highlights

Configuring advanced server settings Configuring Rogue System Detection server settings 7 • Verify the DN field is correct on the user configuration page. • Verify the browser is providing the correct certificate. • Check the audit log for authentication messages. Configuring Rogue System Detection server settings Rogue System Detection server settings determine how information about subnets and detected systems is displayed in the Detected Systems page within your ePolicy Orchestrator console. Configuring server settings for Rogue System Detection These server settings allow you to customize Rogue System Detection to meet the specific needs of your organization. These settings control important behavior, including: • Whether a detected system is compliant (based on last agent communication). • The categories for system exceptions (systems that don't need an agent). • How detected system interfaces are matched. • The list of OUIs used to identify vendor specific NICs used by systems connecting to your network. • How your Rogue System Sensors are configured. Use these tasks to configure server settings for Rogue System Detection. Tasks • Editing Detected System Compliance on page 61 Use this task to edit the Detected System Compliance settings. These settings are user-configured and have two important functions: • Editing Detected System Exception Categories on page 62 • Editing Detected Systems Matching on page 62 Use this task to edit the matching settings for Rogue System Detection. Matching settings are user-configured and have these important functions: • Editing Detected System OUIs on page 63 Use this task to edit the settings that specify the method and location used to update Detected System OUIs (Organizationally Unique Identifiers). Rogue System Detection uses OUIs to provide details about the systems on your network. • Editing Rogue System Sensor settings on page 63 Use this task to edit the sensor settings for Rogue System Detection. Sensor settings are user-configured and specify: Editing Detected System Compliance Use this task to edit the Detected System Compliance settings. These settings are user-configured and have two important functions: • They specify the time-frame that determines the state of detected systems (Managed, Rogue, Exception, Inactive). • They control the visual feedback of the Rogue System Detection status monitors on the Detected Systems page. For option definitions, click ? in the interface. McAfee® ePolicy Orchestrator® 4.6.0 Software Product Guide 61

  • 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

Verify the DN field is correct on the user configuration page.
Verify the browser is providing the correct certificate.
Check the audit log for authentication messages.
Configuring Rogue System Detection server settings
Rogue System Detection server settings determine how information about subnets and detected
systems is displayed in the Detected Systems page within your ePolicy Orchestrator console.
Configuring server settings for Rogue System Detection
These server settings allow you to customize Rogue System Detection to meet the specific needs of
your organization.
These settings control important behavior, including:
Whether a detected system is compliant (based on last agent communication).
The categories for system exceptions (systems that don't need an agent).
How detected system interfaces are matched.
The list of OUIs used to identify vendor specific NICs used by systems connecting to your network.
How your Rogue System Sensors are configured.
Use these tasks to configure server settings for Rogue System Detection.
Tasks
Editing Detected System Compliance
on page 61
Use this task to edit the Detected System Compliance settings. These settings are
user-configured and have two important functions:
Editing Detected System Exception Categories
on page 62
Editing Detected Systems Matching
on page 62
Use this task to edit the matching settings for Rogue System Detection. Matching settings
are user-configured and have these important functions:
Editing Detected System OUIs
on page 63
Use this task to edit the settings that specify the method and location used to update
Detected System OUIs (Organizationally Unique Identifiers). Rogue System Detection uses
OUIs to provide details about the systems on your network.
Editing Rogue System Sensor settings
on page 63
Use this task to edit the sensor settings for Rogue System Detection. Sensor settings are
user-configured and specify:
Editing Detected System Compliance
Use this task to edit the Detected System Compliance settings. These settings are user-configured and
have two important functions:
They specify the time-frame that determines the state of detected systems (Managed, Rogue,
Exception, Inactive).
They control the visual feedback of the Rogue System Detection status monitors on the Detected
Systems page.
For option definitions, click
?
in the interface.
Configuring advanced server settings
Configuring Rogue System Detection server settings
7
McAfee
®
ePolicy Orchestrator
®
4.6.0 Software Product Guide
61