McAfee EPOCDE-AA-BA Product Guide - Page 272

How the Rogue System Sensor works, Passive listening to layer-2 traffic

Page 272 highlights

21 Detecting Rogue Systems How the Rogue System Sensor works How the Rogue System Sensor works The Rogue System Sensor is the distributed portion of the Rogue System Detection architecture. Sensors detect systems, routers, printers, and other devices connected to your network. They gather information about the devices they detect, and forward the information to the McAfee ePO server. The sensor is a Win32 native executable application that runs on any NT-based Windows operating system, including: • Windows XP • Windows Server 2003 • Windows 2008 • Windows Vista • Windows 7 It can be installed on systems throughout your network. A sensor reports on all systems in the broadcast segment where it is installed. A sensor installed on a DHCP server reports on all systems or subnets using DHCP. To maintain coverage In networks or broadcast segments that don't use DHCP servers, you must install at least one sensor in each broadcast segment, usually the same as a subnet. DHCP deployment can be used with segment-specific deployment of the Rogue System Sensor for the most comprehensive coverage. Passive listening to layer-2 traffic To detect systems on the network, the sensor uses WinPCap, a packet capture library. It captures layer-2 broadcast packets sent by systems that are connected to the same network broadcast segment. It also listens passively to all layer-2 traffic for Address Resolution Protocol (ARP), Reverse Address Resolution Protocol (RARP), IP traffic, and DHCP responses. To obtain additional information, the sensor also performs NetBIOS calls and OS fingerprinting on systems that were already detected. It does this by listening to the broadcast traffic of all devices in its broadcast segment, and by using NetBIOS calls, actively probing the network to gather additional information about the devices connected to it, such as the operating system of a detected system. The sensor does not determine whether the system is a rogue system. It detects systems connected to the network and reports these detections back to the McAfee ePO server, which determines whether the system is rogue based on user-configured settings. Intelligent filtering of network traffic The sensor filters network traffic "intelligently" - it ignores unnecessary messages and captures only what it needs, which is Ethernet and IP broadcast traffic. By filtering out unicast traffic, which might contain non-local IP addresses, the sensor focuses only on devices that are part of the local network. To optimize performance and minimize network traffic, the sensor limits its communication to the server by relaying only new system detections, and by ignoring any re-detected systems for a user-configured time. For example, the sensor detects itself among the list of detected systems. If the sensor sent a message every time it detected a packet from itself, the result would be a network overloaded with sensor detection messages. 272 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

How the Rogue System Sensor works
The Rogue System Sensor is the distributed portion of the Rogue System Detection architecture.
Sensors detect systems, routers, printers, and other devices connected to your network. They gather
information about the devices they detect, and forward the information to the McAfee ePO server.
The sensor is a Win32 native executable application that runs on any NT-based Windows operating
system, including:
Windows XP
Windows Server 2003
Windows 2008
Windows Vista
Windows 7
It can be installed on systems throughout your network. A sensor reports on all systems in the
broadcast segment where it is installed. A sensor installed on a DHCP server reports on all systems or
subnets using DHCP. To maintain coverage In networks or broadcast segments that don’t use DHCP
servers, you must install at least one sensor in each broadcast segment, usually the same as a
subnet. DHCP deployment can be used with segment-specific deployment of the Rogue System Sensor
for the most comprehensive coverage.
Passive listening to layer-2 traffic
To detect systems on the network, the sensor uses WinPCap, a packet capture library. It captures
layer-2 broadcast packets sent by systems that are connected to the same network broadcast
segment. It also listens passively to all layer-2 traffic for Address Resolution Protocol (ARP), Reverse
Address Resolution Protocol (RARP), IP traffic, and DHCP responses.
To obtain additional information, the sensor also performs NetBIOS calls and OS fingerprinting on
systems that were already detected. It does this by listening to the broadcast traffic of all devices in
its broadcast segment, and by using NetBIOS calls, actively probing the network to gather additional
information about the devices connected to it, such as the operating system of a detected system.
The sensor does not determine whether the system is a rogue system. It
detects systems connected to the network and reports these detections
back to the McAfee ePO server, which determines whether the system is
rogue based on user-configured settings.
Intelligent filtering of network traffic
The sensor filters network traffic "intelligently" — it ignores unnecessary messages and captures only
what it needs, which is Ethernet and IP broadcast traffic. By filtering out unicast traffic, which might
contain non-local IP addresses, the sensor focuses only on devices that are part of the local network.
To optimize performance and minimize network traffic, the sensor limits its communication to the
server by relaying only new system detections, and by ignoring any re-detected systems for a
user-configured time. For example, the sensor detects itself among the list of detected systems. If the
sensor sent a message every time it detected a packet from itself, the result would be a network
overloaded with sensor detection messages.
21
Detecting Rogue Systems
How the Rogue System Sensor works
272
McAfee
®
ePolicy Orchestrator
®
4.6.0 Software Product Guide