McAfee EPOCDE-AA-BA Product Guide - Page 269

Rogue Sensor Blacklist, Rogue System Detection policy settings, Considerations for policy settings

Page 269 highlights

Detecting Rogue Systems What are rogue systems 21 Rogue Sensor Blacklist The Rogue Sensor Blacklist is the list of managed systems where you do not want sensors installed. These can include systems that would be adversely affected if a sensor were installed on them, or systems you have otherwise determined should not host sensors. For example, mission critical servers where peak performance of core services is essential, such as database servers or servers in the DMZ (demilitarized zone). Also, systems that might spend significant time outside your network, such as laptops. The Rogue Sensor Blacklist is different than the Exceptions list, in that systems on the Exceptions list are those that either can't have an agent on them, or that you don't want categorized as Rogue, such as printers or routers. Rogue System Detection policy settings Rogue System Detection policy settings allow you to configure and manage the instances of the Rogue System Sensor installed throughout your network. Settings can be applied to individual systems, groups of systems, and IP ranges. You can configure policy settings for all sensors deployed by the server. This is similar to managing policies for any deployed product, such as VirusScan Enterprise. The Rogue System Detection policy pages are installed on the McAfee ePO server at installation. Configure the sensor policy settings in the Rogue System Detection policy pages the same way you would for any managed security product. Policy settings that you assign to higher levels of the System Tree are inherited by lower-level groups or individual systems. For more information about policies and how they work, see Managing your Network with Policies and Client Tasks. McAfee recommends that you configure policy settings before you deploy sensors to your network. Doing so ensures that the sensors work according to your intended use. For example, DHCP monitoring is disabled by default. As a result, if you deploy sensors to DHCP servers without enabling DHCP monitoring during your initial configuration, those sensors report limited information to the McAfee ePO server. If you deploy sensors before you configure your policies, you can update them to change sensor functionality. Considerations for policy settings Policy settings configure the features and performance of the Rogue System Sensor. These settings are separated into four groups: • Communication settings • Detection settings • General settings • Interface settings Communication settings Communication settings determine: • Communication time for inactive sensors. • Reporting time for active sensors. • Sensor's detected system cache lifetime. The communication time for inactive sensors determines how often passive sensors check in with the server. McAfee® ePolicy Orchestrator® 4.6.0 Software Product Guide 269

  • 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

Rogue Sensor Blacklist
The Rogue Sensor Blacklist is the list of managed systems where you do not want sensors installed.
These can include systems that would be adversely affected if a sensor were installed on them, or
systems you have otherwise determined should not host sensors. For example, mission critical servers
where peak performance of core services is essential, such as database servers or servers in the DMZ
(demilitarized zone). Also, systems that might spend significant time outside your network, such as
laptops.
The Rogue Sensor Blacklist is different than the Exceptions list, in that systems on the Exceptions list
are those that either can’t have an agent on them, or that you don’t want categorized as Rogue, such
as printers or routers.
Rogue System Detection policy settings
Rogue System Detection policy settings allow you to configure and manage the instances of the Rogue
System Sensor installed throughout your network. Settings can be applied to individual systems,
groups of systems, and IP ranges.
You can configure policy settings for all sensors deployed by the server. This is similar to managing
policies for any deployed product, such as VirusScan Enterprise. The Rogue System Detection policy
pages are installed on the McAfee ePO server at installation.
Configure the sensor policy settings in the Rogue System Detection policy pages the same way you
would for any managed security product. Policy settings that you assign to higher levels of the System
Tree are inherited by lower-level groups or individual systems. For more information about policies and
how they work, see
Managing your Network with Policies and Client Tasks
.
McAfee recommends that you configure policy settings before you deploy
sensors to your network. Doing so ensures that the sensors work
according to your intended use. For example, DHCP monitoring is
disabled by default. As a result, if you deploy sensors to DHCP servers
without enabling DHCP monitoring during your initial configuration, those
sensors report limited information to the McAfee ePO server. If you
deploy sensors before you configure your policies, you can update them
to change sensor functionality.
Considerations for policy settings
Policy settings configure the features and performance of the Rogue System Sensor. These settings
are separated into four groups:
Communication settings
Detection settings
General settings
Interface settings
Communication settings
Communication settings determine:
Communication time for inactive sensors.
Reporting time for active sensors.
Sensor’s detected system cache lifetime.
The communication time for inactive sensors determines how often passive sensors check in with the
server.
Detecting Rogue Systems
What are rogue systems
21
McAfee
®
ePolicy Orchestrator
®
4.6.0 Software Product Guide
269