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.




Network Security Focus-Microsoft
[Top] [All Lists]

Re: IP address assignment problem

Subject: Re: IP address assignment problem
Date: Sat, 26 Aug 2006 01:32:43 +0200
Davy Davidson wrote:

I have a little problem and seek for ur thoughts, let's assume I'm in a very open environment where everyone can very easily try to get his/her laptop on the network and IP addresses are assigned by a DHCP server and we are in a domain environment, how do I prevent machines that are not part of our domain to be assigned an IP address?

This is a chicken-egg-problem: Since DHCP is preceding all meaningful communication in most networks, this only can be done by denying DHCP communication beforehand. The Clients will need to prove that they are members of the domain before they are able to get served by a DHCP server. You can achieve this by using 802.1x throughout your network, but this will require appropriate equipment.


Mostly, the problem "I do not want to get them a DHCP address" can be refined as "I do not want them to communicate with any of my domain members" which can be achieved by for example only allowing encrypted communications (i.e. implementing IPSEC) for every domain member. You should be able to trust the domain authentication mechanisms not to let just anybody to get to your domain machines, providing your password policy is feasible, your systems are patched and access controls are set correctly (read: with the least privelege needed).

Denis

---------------------------------------------------------------------------
---------------------------------------------------------------------------

<Prev in Thread] Current Thread [Next in Thread>