|
|
|
|
|
|
Digg |
|
|
|
Any user on a LAN can sniff and manipulate local traffic. ARP spoofing and poisoning techniques give an attacker an easy way in.
Curiousity, revenge, industrial espionage are all reasons why insiders attack systems on their own network. Statistics show that 70 to 80 percent of all attacks originate on the internal network [1]. Admins have a hard time preventing these internal attacks because protecting the internal network is a lot more difficult than protecting against external attack. One of the most formidable forms of internal attack is known as ARP spoofing. ARP spoofing puts an attacker in a position to sniff and manipulate local traffic. So-called man-in-the-middle attacks are easy to perform, and thanks to sophisticated software, even attackers with little knowledge of networking stand a good chance of succeeding. How ARP Works The ARP protocol was published in November 1982 by David C. Plummer as RFC 826 [2]. As IT security was not an important factor back in 1982, the aim was simply to provide functionality. ARP maps IP addresses to MAC addresses. If client C needs to send a packet to server S, it needs to know the MAC address of S if both machines are on the same subnet. Even if S resides in a different network, C still needs a MAC address – in this case, the address of the next router that will forward the packet. The router takes care of everything else.
|
|
|
| Related Articles | |
|---|---|
| INTRUSION STORIES | Understanding, detecting, and preventing network attacks |
| PICTURES | Tools for visualizing IDS output |
| HONEY NET | |
| FYODOR’S DIET | The Sysadmin’s Daily Grind: Nmap 4 |
| ARP WATCH | The Sysadmin’s Daily Grind: Arpalert |
| SECRETS AND DISKS | Disk-level cryptography in Linux |
| Wherever you go... |
|---|
...Linux Magazine goes with you!Check out the advantages of a Digital Subscription:
|
Comments