Discussion Locked

An entire network on DHCP reservations....plausible?

0 helpful
1 reply
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Ok here is my idea: I have a network that is very focused on security, with a small amount of workstations (50). We have no wireless network nor will we ever. We are also fairly concerned with the idea of people simply plugging into a switch or cat5 cable and getting on the network. Would it be beneficial to us to move to a system where we leave DHCP on, but disable the scope, and simply use all DHCP reservations, so that someone wont pull an IP if he plugs in? Obviously he could set his IP statically, but I dont know how he would be able to find the IP format we use. Assuming someone did not previously have that IP info, and could not log on to any workstations to find it, is this a viable option? Am I just crazy? Let me know what you think about this, and about securing a network in this manner in general.

1 reply

by davy.geurts

... what threat you want to secure your network for.
- is it for packet sniffing
- just for visitors not plugging in their laptops
- .....

depends all on the goal you want to achieve.

From my experience (and I?m surely no expert) I would start by setting goals and work from there, not from a concept and then asking ?is it enough?

examples:
If you want to prevent ?Packet sniffing?  forget that, that will never work. At least not at the it level, you could setup procedures that no laptops or something like that are allowed onsite without supervision.
Their might be triggers for unknown devices to send an alert if they are plugged in (surely) but I have no experience with that (maybe another reader)

If you want to prevent users just plugging in devices into empty sockets.
This is quit easy: don?t patch any unused sockets?

If you want to prevent users from plugging into switches:
You could work with VLANs and create a VLAN for guests (only allowing internet access or so) Or just disabling the port all together on the switch.

If its just a matter of being sure that users wont access documents etc.
This is best done on a higher level, on the application level with usernames and domain security?.

I could go on for hours like this, but according to me it all comes down to what you want to achieve. (or what are you afraid of)

Regards,

Davy

This discussion is closed to new replies.