Warning: session_start() [function.session-start]: open(/tmp/sess_eef431f6c693edc8ec8350f8b66ce1e5, O_RDWR) failed: No space left on device (28) in /home/ciscoart/public_html/include/includes.php on line 17

Warning: session_start() [function.session-start]: Cannot send session cookie - headers already sent by (output started at /home/ciscoart/public_html/include/includes.php:17) in /home/ciscoart/public_html/include/includes.php on line 17

Warning: session_start() [function.session-start]: Cannot send session cache limiter - headers already sent (output started at /home/ciscoart/public_html/include/includes.php:17) in /home/ciscoart/public_html/include/includes.php on line 17

Warning: Cannot modify header information - headers already sent by (output started at /home/ciscoart/public_html/include/includes.php:17) in /home/ciscoart/public_html/include/header.php on line 17
Conclusion: Finding Security in an Unsecured World
Header
Home | Set as homepage | Add to favorites
  Search the Site     » Advanced Search
Sections
Syndication


Blogroll:

||||| ALL Cisco-Network ARTICLES |||||  
CCIE Journey,
The CCIE Journey,


Conclusion: Finding Security in an Unsecured World

Apr 21,2010 by alperen

image

Conclusion: Finding Security in an
Unsecured World


This chapter has focused on the concept of how a wireless network can
effectively provide the same level of security as that of a wired network.
However, the most important section of this chapter details all the ways
in which the wired equivalent privacy (WEP) can be circumvented
through several methods including:

 IRL in real-life physical damage
 Jamming and interference
 Eavesdropping
 Unauthorized access

By understanding these methods of attack, you can determine the
best manner in which you can prevent a hacker from accessing your system
and compromising the WEP of your wireless network. Using WEP
encryption enables your WLAN to resist the way in which encryption
keys are stolen. Effectively managing these keys maintains the wired
equivalent privacy of your WLAN so that you can use your network with
the confidence of maintaining a level of security analogous to that
offered by a wired LAN. 133

Physical barriers and protection mechanisms are the most important
means of making certain that hackers are unable to gain access to precious
network resources.
What equipment is vulnerable?

 Access points/wireless routers
 Laptop computers
 Wireless PDAs
 Wireless network interface cards
 Network printers
 Network file servers
 Network fax servers

Effectively maintaining physical safeguards prevents hackers from
getting into these systems in person, and therefore makes it harder for
them to log in wirelessly. The idea is to protect wireless users as well as
the actual access points; only then can you be certain to manage all your
network resources effectively.

Finally, maintain a log of every activity on your WLAN. Keeping this
information protects you from hacking activity. Your best defense in
keeping your network secure is to make certain you can identify malicious
activity on your system. If you maintain a vigilant eye on your
resources, you can effectively protect your wireless network against
many possible intrusion attempts.

Following these guidelines will enable you to operate a secure wireless
network without fear of being hacked.

190 times read

Related news

» Conclusion: Maintaining a Secure Infrastructure
by alperen posted on Apr 19,2010
» Conclusion: Keeping Your WLAN Secure
by alperen posted on Mar 30,2010
» 802.11 Encryption: Wired Equivalent Privacy
by alperen posted on Apr 21,2010
» Conclusion
by alperen posted on Apr 08,2010
» Encryption
by alperen posted on Mar 25,2010
Did you enjoy this article?
(total 0 votes)

comment Comments (0 posted) 

More Top News
CCSP-Cisco Certified Security Professional
Most Popular
Most Commented
Featured Author

Warning: Unknown: open(/tmp/sess_eef431f6c693edc8ec8350f8b66ce1e5, O_RDWR) failed: No space left on device (28) in Unknown on line 0

Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/tmp) in Unknown on line 0