|
The same is true of networking gear. A network connected by wires is much easier
to secure than a network that is wirelessly beaming information every which way.
That much is obvious. However, the security of wires comes at the price of flexibility.
That's where the tradeoff is and on the whole, wireless is a great alternative.
To secure a wireless network requires a little common sense as well as a little
technical savvy when configuring the settings for the network itself. First, the
actual location of your wireless gear is important.
Try to locate the transmitters (especially the "hubs" or "access
points") in an area where, while accessible to as many systems as possible,
access to an outside wall or window is not available. In fact, the more "centralized"
you can make your network transmissions, the more you'll limit the options a hacker
has at finding an access point that is "safe" for him to use. If he
has to be physically in your office or in the office next door in order to use
it, he's limited as to what he can do with the network. Because wireless networks
are flexible, you can centralize like this and, as circumstances change, move
your units to cover a broader range – always keeping in mind the area covered
outside of your "zone."
Continuing with the theme of access points, do not allow "rogue"
access points on your network. A rogue access point is one that is not officially
a part of the network. For instance, let's say you're in a small office and one
of your co-workers, Jill, brings in her wireless access point because she wants
to be able to use her laptop on the board room – not currently covered by
the network. Instead of requesting through channels that this be set up, she merely
brings her own in, plugs it into the network, and starts using it. This access
point probably hasn't been set to the same security standards as the rest of your
network and is therefore a liability. Making this against the rules up front will
make others aware that it is not allowed so they don't assume that it's "OK."
Access points can usually be set to have individual login ID and passwords
for setup. Changing the defaults is a big step towards raising security. This
can usually be done through the access point's software via your computer. Setting
security standards like 128-bit WEP, Service Set Identifiers (SSIDs), and "authenticating"
users with a firewall are also good ideas. While none of these individually will
stop an intruder who knows how to hack a wireless system, every stumbling block
helps and will slow the intruder down.
Wireless networks - secure or not to secure? Wireless networking is becoming all the rage recently, it certainly makes thinks easier for people like me who administer networks, no more climbing through ceilings or falling through them:)Stick a couple of boxes a wall, fir a wireless card and your done right?
Personally the answer is no, I want my networks secure and dont want anybody
stealing my bandwidth, ok so I don't personally pay for it, but it's my phone
that rings if the network crawls....
Read Replies
|
|
|
Further, by limiting the access rights of certain users (on any network, not
just wireless setups), you limit the possibility of a hacker getting a legitimate
user's pass codes and entering the system. If you further set the network to allow
only a limited number of users (say there are 10 people in the office, set up
only ten user accounts and allow no more) on at any given time, you will stop
"clones" from appearing – the same user being logged in more than
once.
Simple security measures and a watchful eye can keep your wireless network
safe from intrusion and unauthorized use. Even a home- office should have some
measure of security to keep the sanctity of data and access.
About the Author:
Aaron Turpen is the proprietor of Aaronz WebWorkz, which offers many services
to small businesses online including an informative weekly newsletter (advertisement
free!) to subscribers. This and more are avaialble at the website: http://www.AaronzWebWorkz.com
Read this newsletter at: http://www.securitypronews.com/2003/0827.html |
|