Ethical Hacking Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package. | Computer Forensics Training at InfoSec Institute Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors. |

| Subject: | Re: Network "Change Management" |
|---|---|
| Date: | Thu, 16 Sep 2004 12:24:44 -0700 |
Dave,
Does anyone know of a Linux utility that can watch the MAC address tables in Cisco switches and alert admins as to when a new device has been plugged in?
I don't work with Cisco switches too much, however you may be able to configure it to send an snmp alert to your Linux box when a new device is plugged in. You'd then use snmp-util (or whatever it's called these days) to handle the message on the Linux side. Alternatively you can set up arpwatch on your Linux box and periodically ping your whole range of IPs. Arpwatch will alert you when it sees new or changed MAC addresses for those IPs.
Basically, we have your standard client network with DHCP. Internet access is restricted to authenticated users, and so are the file shares. However, we've had a few instances where people just plug in their personal laptops which makes me very worried...
Okay, then a couple other things you might want to consider: 1. If it is a managed switch, you should be able to configure it to only allow MACs on a given list, hence preventing new boxes from even getting a layer 2 connection. 2. Set up the dhcp server to only allocate IPs to certain MAC addresses. 3. You should be able to get dhcpd to report to you when it allocates to a previously unseen MAC address (probably by throwing together some scripts to parse the log messages and comparing the MACs in them to a list). Of course, all of the above are assuming that someone isn't spoofing their MAC address to one that you allow on your network. Typically someone has to be deliberately malicious to do that though, so the above strategies (especially blocking based on MAC) are good for stopping people from connecting up their personal laptop and infecting the network with the worm du jure. The best prevention against MAC spoofing is to trust your users. Hope this helps, Terry
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Network "Change Management", Adrian Senn |
|---|---|
| Next by Date: | RE: Network "Change Management", Jorge Reyes |
| Previous by Thread: | Re: Network "Change Management", Adrian Senn |
| Next by Thread: | Re: Network "Change Management", Fred Leeflang |
| Indexes: | [Date] [Thread] [Top] [All Lists] |