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.
Trending Windows Forum posts
Sort by Trending