Debian Codegraph @

examples/rarpwatch/README

raw
1 /*
2 * Argus-5.0 Client Software. Tools to read, analyze and manage Argus data.
3 * Copyright (c) 2000-2024 QoSient, LLC
4 * All rights reserved.
5 *
6 * THE ACCOMPANYING PROGRAM IS PROPRIETARY SOFTWARE OF QoSIENT, LLC,
7 * AND CANNOT BE USED, DISTRIBUTED, COPIED OR MODIFIED WITHOUT
8 * EXPRESS PERMISSION OF QoSIENT, LLC.
9 *
10 * QOSIENT, LLC DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS
11 * SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
12 * AND FITNESS, IN NO EVENT SHALL QOSIENT, LLC BE LIABLE FOR ANY
13 * SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
14 * WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER
15 * IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION,
16 * ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF
17 * THIS SOFTWARE.
18 *
19 *
20 * rarpwatch - extended arpwatch functionality driven by argus flow data
21 *
22 * Author: Carter Bullard [email protected]
23 */
24
25 /*
26 Rarpwatch is designed to 'watch' arp traffic and to provide awareness of
27 ethernet address resolution. Because arp is used for a lot of basic
28 functions, a lot can be 'learned' from passively listening for arps's
29 on the local network.
30
31 Classic arpwatch behavior consists of tracking solicited / unsolicited
32 as well as directed and undirected arp requests and responses, to provide
33 address resolution integrity, and is primarily used to detect arp poisoning
34 within a network..
35
36 However, so much more can be derived from passively monitoring arp traffic.
37 rarpwatch can be aware of active ethernet addresses in the current LAN,
38 their interest in Layer 3 addresses, the occurence of unsolicited reverse
39 arps to test availability of addresses, all can provide discovery information
40 for the specific LAN that the sensor has visibility to.
41
42 With multi-host, multi-probe correlation, broadcast domains can be tracked,
43 cliques can be determined for network context identification, and LAN
44 defintiion / segmentation can be realized, in addition to simple mpc
45 functions, such as time synchronization.
46
47 The primary thing for rarpwatch.1 is to track ethernet / IP address
48 assignments. When argus resides in an end system, tracking all the arp
49 traffic allows one to track the state of the hosts interface configuration
50 (arp is used to test the availability of the IP address assigned to a
51 given interface), and to understand how local Layer 3 addresses are mapped
52 to active Layer 2 addresses in the LAN. In dynamic DHCP based networks,
53 we can assume that mappings change, and so coupling an awareness of DHCP
54 and ARP traffic can provide an awareness of dynamism in a LAN, especially
55 for mobile end systems.
56
57 In untrusted networks, one should anticipate that arp can be used to spoof
58 systems into forwarding packets to inappropriate nodes, or to present
59 fabricated LAN profiles to an attached end system to modify its security
60 stance.
61
62 One of the design goals of rarpwatch.1, is to be able to identify and
63 track attachment to foriegn LANs, especially for laptops and mobile end
64 systems. Ideally, this would provide LAN identifiation, with wireless
65 SSID and BSSID identifiers if availabile, entity inventory, IP address
66 assignement determination (DHCP mediated static addressing ???) router
67 identification, and possible correlation with local routing tables.
68
69 These goals provide the situational awareness needed to discriminate
70 changes in Layer 2 and Layer 3 associations and to provide classification
71 into familiar/unfamiliar, friendly and unfriendly behavior.
72 */
73
74