<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>M and L Adventures &#187; Security</title>
	<atom:link href="http://www.mandladventures.com/category/tech-stuff/security/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mandladventures.com</link>
	<description>Leading you on the technical adventure</description>
	<lastBuildDate>Thu, 28 Jul 2011 21:45:14 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>DD-WRT Vulnerability</title>
		<link>http://www.mandladventures.com/2009/07/27/dd-wrt-vulnerability/</link>
		<comments>http://www.mandladventures.com/2009/07/27/dd-wrt-vulnerability/#comments</comments>
		<pubDate>Tue, 28 Jul 2009 01:44:20 +0000</pubDate>
		<dc:creator>Lauren</dc:creator>
				<category><![CDATA[DD-WRT]]></category>
		<category><![CDATA[Security]]></category>

		<guid isPermaLink="false">http://www.mandladventures.com/?p=419</guid>
		<description><![CDATA[For all of my readers who are DD-WRT users you may want to stop using v24 SP1, SANS Internet Storm Center (ISC) has a brief post about a DD-WRT vulnerability that will allow an attacker to run programs with root privileges on a vulnerable router. In other words, this is a really bad vulnerability. Root [...]
Related post
<strong>Related Posts:</storng><ul>s:<ol>
<li><a href='http://www.mandladventures.com/2008/01/26/linksys-wrt54gl-cross-site-request-forgery-csrf-vulnerability/' rel='bookmark' title='Linksys WRT54GL Cross Site Request Forgery (CSRF) Vulnerability'>Linksys WRT54GL Cross Site Request Forgery (CSRF) Vulnerability</a></li>
</ul>]]></description>
			<content:encoded><![CDATA[<p>For all of my readers who are DD-WRT users you may want to stop using v24 SP1, SANS Internet Storm Center (ISC) has a brief post about a DD-WRT vulnerability that will allow an attacker to run programs with root privileges on a vulnerable router. In other words, this is a really bad vulnerability. Root privileges in Linux is the equivalent to admin privileges in Windows. With root access, a hacker could do anything with your router. Since your router controls what you do on the Internet, that could be really, really bad. The SANS post has a link to the dd-wrt forum which provides additional details regarding the problem as well as some options on how to mitigate it and/or patch the DD-WRT firmware. I highly recommend checking it out right now. Now that I&#8217;ve stressed it enough, here&#8217;s the link to the SANS ISC page:  <a href="http://isc.sans.org/diary.html?storyid=6853&#038;rss">http://isc.sans.org/diary.html?storyid=6853&#038;rss</a>.</p>
<p>Related post<p><strong>Related Posts:</storng></p><ul>s:<ol>
<li><a href='http://www.mandladventures.com/2008/01/26/linksys-wrt54gl-cross-site-request-forgery-csrf-vulnerability/' rel='bookmark' title='Linksys WRT54GL Cross Site Request Forgery (CSRF) Vulnerability'>Linksys WRT54GL Cross Site Request Forgery (CSRF) Vulnerability</a></li>
</ul>]]></content:encoded>
			<wfw:commentRss>http://www.mandladventures.com/2009/07/27/dd-wrt-vulnerability/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>More Secure OpenID</title>
		<link>http://www.mandladventures.com/2008/01/03/more-secure-openid/</link>
		<comments>http://www.mandladventures.com/2008/01/03/more-secure-openid/#comments</comments>
		<pubDate>Thu, 03 Jan 2008 22:21:51 +0000</pubDate>
		<dc:creator>Lauren</dc:creator>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[Tech Advice]]></category>

		<guid isPermaLink="false">http://www.mandladventures.com/2008/01/03/more-secure-openid/</guid>
		<description><![CDATA[OpenID is a very cool authentication idea. It allows you to have single sign-on (i.e., login once using one user name and password for multiple websites/applications) for sites that support OpenID. The ability to only login to one site and then only provide your OpenID URL to other sites you would like to authenticate to [...]
No related posts.]]></description>
			<content:encoded><![CDATA[<p>OpenID is a very cool authentication idea. It allows you to have single sign-on (i.e., login once using one user name and password for multiple websites/applications) for sites that support OpenID. The ability to only login to one site and then only provide your OpenID URL to other sites you would like to authenticate to (prove that you are who you say you are) is very nice. For one, it alleviates the problem of having to remember multiple user names and passwords (I hope you use different passwords for different sites&#8230;at the very least different passwords for financial sites). For two, it saves time. Unfortunately, every site I use does not yet support OpenID so I still end up having to deal with multiple user names and passwords.</p>
<p>Like all things with computer security, OpenID is not without its fair share of problems. One of the biggest problems is a result of OpenID&#8217;s main benefit, single sign-on. Single sign-on is great as long as no one is able to compromise your user name and password. However, if someone manages to compromise your user name and password then they&#8217;ve compromised every site for which that single sign-on is used. Therefore, it is imperative that your OpenID account has a very strong (read long, random, mixed case, numbers, and special characters) password. </p>
<p>It is also important that you don&#8217;t fall victim to a phishing attack that tricks you into thinking your logging in to your OpenID account when you’re not. Otherwise, it doesn&#8217;t matter how strong your password is if you simply give it away to a fake site. In order to ensure the OpenID provider site you’re logging into is legitimate you should examine the SSL certificate to make sure it belongs to your OpenID provider and has been signed by a trustworthy certificate authority (e.g., Verisign, Thawte, etc.).</p>
<p>Another concern with OpenID that I won&#8217;t cover in this article because its out of scope is privacy. The jest of the issue is that your OpenID provider can basically track every site you use your OpenID account with. A few other concerns with OpenID exist. I recommend that you checkout <a href="http://www.grc.com/sn/SN-111.htm">Security Now episode 111</a> if your interested in learning more about OpenID concerns.</p>
<p>Wouldn&#8217;t it be great if there was a way to easily and effectively reduce some of the risk with OpenID? Two-factor authentication provides the solution. For those of you who are not familiar with what two-factor authentication is, I&#8217;ll give a brief explanation. Two-factor authentication is when you provide more than one form of evidence that you are who you say you are. Generally, people just provide a password which is something you know. However, two other common factors of authentication exist—something you are (biometrics) and something you have (security token/fob, smart card, etc.). </p>
<p>Two-factor authentication is a great solution because it ensures someone can&#8217;t easily steal your account by guessing, cracking, or stealing your OpenID password. The second factor means that would need to possess your security token as well. Security tokens work by providing a random string of typically six digits periodically (most tokens do so every thirty seconds). The current six digits being displayed by the token (which only you have) must be appended to the password (which hopefully only you know). Additionally, a two-factor authentication mitigates the risk of falling victim to a phishing site because the password the phisher stole is only good for thirty seconds.</p>
<p>Luckily for all of us <a href="https://pip.verisignlabs.com/login.do">Verisign</a> is a free OpenID provider which offers support for two-factor authentication. They call their service <a href="https://pip.verisignlabs.com/login.do">Personal Identity Provider</a> (PIP). To take advantage of their service you need to have a supported security token (i.e., a little key-chain device which provides a random number every thirty seconds). Luckily, you can <a href="https://www.paypal.com/securitykey">buy</a> one of these devices through <a href="https://www.paypal.com/securitykey">PayPal</a> for only $5. As an added benefit, this security token works not only with PIP but also with <a href="https://www.paypal.com/securitykey">PayPal</a> and <a href="http://pages.ebay.com/securitycenter/security_key.html">eBay</a>.</p>
<p>A Firefox extension, <a href="https://pip.verisignlabs.com/seatbelt.do">SeatBelt</a>, automatically fills in your OpenID URL in websites with the appropriate form field. The extension also provides some useful security and OpenID management capabilities. </p>
<p>In conclusion, OpenID is a great solution for trivial sites like blogs and forums as long as you are aware of the dangerous that exist and take the necessary precautions. I still wouldn&#8217;t recommend OpenID for financial and medical sites but for pretty much everything else it is great. I know I can&#8217;t wait till more of the sites I use start to take advantage of it.</p>
<p>In case your wondering, I&#8217;m not getting paid anything to write this post nor do I make any money if you sign up for an account or buy a security key. I just think Verisign is offering a really good, secure OpenID solution that not many people know about. I just wanted my readers to know that this is an available solution. Plus, if enough people start using OpenID more sites are likely to offer it is an login option. Before I forget, you can find a list of OpenID enabled sites at the <a href="http://openiddirectory.com/">OpenID directory</a>.</p>
<p>No related posts.</p>]]></content:encoded>
			<wfw:commentRss>http://www.mandladventures.com/2008/01/03/more-secure-openid/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>AJAX Security Considerations&#8230;</title>
		<link>http://www.mandladventures.com/2007/08/10/ajax-security-considerations/</link>
		<comments>http://www.mandladventures.com/2007/08/10/ajax-security-considerations/#comments</comments>
		<pubDate>Fri, 10 Aug 2007 12:19:50 +0000</pubDate>
		<dc:creator>Matt</dc:creator>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[Web Development]]></category>

		<guid isPermaLink="false">http://www.mandladventures.com/?p=244</guid>
		<description><![CDATA[As many of my blog readers know AJAX is a very popular web development technology right now. AJAX offers web developers the ability to provide desktop application like functionality in web applications. Without AJAX many of the tools I use every day such as GMail, Google Reader, and Google Maps just wouldn&#8217;t be near as [...]
Related post
<strong>Related Posts:</storng><ul>s:<ol>
<li><a href='http://www.mandladventures.com/2007/04/21/securing-your-wireless-network/' rel='bookmark' title='Wireless Network Security Tips'>Wireless Network Security Tips</a></li>
</ul>]]></description>
			<content:encoded><![CDATA[<p>As many of my blog readers know <a href="http://en.wikipedia.org/wiki/Ajax_(programming)">AJAX</a> is a very popular web development technology right now. AJAX offers web developers the ability to provide desktop application like functionality in web applications. Without AJAX many of the tools I use every day such as <a href="https://mail.google.com">GMail</a>, <a href="http://www.google.com/reader/">Google Reader</a>, and <a href="http://maps.google.com/">Google Maps</a> just wouldn&#8217;t be near as fun or easy to use. Don&#8217;t worry, I do occasionally use non-Google sites that make heavy use of AJAX, I just can&#8217;t think of them right now.</p>
<p>However, as recently reported by security researches from <a href="http://www.spidynamics.com/">SPI Dynamics</a> at the <a href="http://www.blackhat.com/html/bh-usa-07/bh-usa-07-speakers.html#Sullivan">Blackhat USA 2007 security conference</a>, the benefits of AJAX don&#8217;t come without significant security risks.</p>
<p>One of the main problems with AJAX is that a lot of traditional server side code is now executed on the client side. This provides would be hackers with a ton of insight on how your application functions. Once equipped with these details it is much easier for hackers to trick web applications into doing things they&#8217;re not designed to do.</p>
<p>The presenters at Blackhat showed the audience how a mock AJAX travel site could be tricked into selling tickets cheaper and also tricked into blocking ticket sales for the same airplane. I think these two examples show exactly how important it is for web developers to secure AJAX.</p>
<p>My recommendation on this subject is to not stop developing with AJAX but to take the time and effort to learn about the security problems associated with this web development technique and the ways to avoid the common pitfalls&#8211;doing so will make the web a safer place for each of us.</p>
<p>Just so you know where to start more about AJAX security, <a href="http://www.darknet.org.uk/2006/04/ajax-is-your-application-secure-enough/">Darknet</a> offers some good insight on securing AJAX by explaining some of the common ways to attack AJAX applications.</p>
<p>[via <a href="http://arstechnica.com/news.ars/post/20070802-security-experts-warn-developers-about-the-risks-of-premature-ajax-ulation.html">Ars Technica</a>]</p>
<p>Related post<p><strong>Related Posts:</storng></p><ul>s:<ol>
<li><a href='http://www.mandladventures.com/2007/04/21/securing-your-wireless-network/' rel='bookmark' title='Wireless Network Security Tips'>Wireless Network Security Tips</a></li>
</ul>]]></content:encoded>
			<wfw:commentRss>http://www.mandladventures.com/2007/08/10/ajax-security-considerations/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Wireless Network Security Tips</title>
		<link>http://www.mandladventures.com/2007/04/21/securing-your-wireless-network/</link>
		<comments>http://www.mandladventures.com/2007/04/21/securing-your-wireless-network/#comments</comments>
		<pubDate>Sat, 21 Apr 2007 16:54:52 +0000</pubDate>
		<dc:creator>Matt</dc:creator>
				<category><![CDATA[DD-WRT]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[Tech Advice]]></category>

		<guid isPermaLink="false">http://www.mandladventures.com/?p=205</guid>
		<description><![CDATA[This post describes some best practices for securely configuring your home wireless network. A few high-level PC security tips are thrown in for good measure. I&#8217;ve been on a bit of a security kick lately&#8230;more than usual anyway. I&#8217;ve always been a bit of a security fanatic but lately I&#8217;ve been learning a whole lot [...]
Related post
<strong>Related Posts:</storng><ul>s:<ol>
<li><a href='http://www.mandladventures.com/2007/08/10/ajax-security-considerations/' rel='bookmark' title='AJAX Security Considerations&#8230;'>AJAX Security Considerations&#8230;</a></li>
<li><a href='http://www.mandladventures.com/2006/09/21/d-link-dwl-g710-wireless-range-extender-review/' rel='bookmark' title='D-Link DWL-G710 Wireless Range Extender Review'>D-Link DWL-G710 Wireless Range Extender Review</a></li>
</ul>]]></description>
			<content:encoded><![CDATA[<p><span  class="alignleft"><iframe src="http://rcm.amazon.com/e/cm?lt1=_blank&#038;bc1=FFFFFF&#038;IS2=1&#038;npa=1&#038;bg1=FFFFFF&#038;fc1=000000&#038;lc1=0D78B6&#038;t=wrt54g-20&#038;o=1&#038;p=8&#038;l=as4&#038;m=amazon&#038;f=ifr&#038;ref=ss_til&#038;asins=0071666613" style="width:120px;height:240px;" scrolling="no" marginwidth="0" marginheight="0" frameborder="0"></iframe></span></p>
<p>This post describes some best practices for securely configuring your home wireless network. A few high-level PC security tips are thrown in for good measure. I&#8217;ve been on a bit of a security kick lately&#8230;more than usual anyway. I&#8217;ve always been a bit of a security fanatic but lately I&#8217;ve been learning a whole lot more. Working as an IT auditor by day and just naturally being attracted to technology, security is of great interest to me. I&#8217;m also becoming a huge fan of the open source <a href="http://dd-wrt.com/wiki/index.php/What_is_DD-WRT%3F">DD-WRT firmware</a> as I start to use more and more of its features on my home network.</p>
<p>A lot of security topics exists that I&#8217;d love to write about sometime, but securing your wireless network is one that should be useful to most of my blog readers. Plus, this is a natural progression from my recent post about <a href="http://www.mandladventures.com/2007/04/12/how-to-flash-the-wrt54gl-with-dd-wrt-firmware/">How to Flash the WRT54GL with DD-WRT Firmware</a>. This post will not cover the intricate details of the hows and whys of wireless security nor will provide a ton of details on how to circumvent (i.e., crack) common security settings. Maybe I&#8217;ll cover those topics at a later date. For now, I just want to tell you about what security settings you should use on your home or small business wireless network to ensure no one is able to sniff (see what your doing on your wireless connection) or use your wireless connection without your permission.<span id="more-205"></span></p>
<p><strong>Table of Contents</strong></p>
<ul>
<li><a href="#Encryption">Select Your Encryption Method</a></li>
<li><a href="#Password">Select Your Password</a></li>
<li><a href="#SSID">Disable SSID Broadcast</a></li>
<li><a href="#MAC">MAC Filtering</a></li>
<li><a href="#UPnP">Turn Off UPnP</a></li>
<li><a href="#Default">Change Default Router Log-In Settings</a></li>
<li><a href="#Firewall">Setup Your Firewall</a></li>
<li><a href="#Patch">Patch Windows Client</a></li>
<li><a href="#Client">Configure Client Devices</a></li>
<li><a href="#Resources">External Resources</a></li>
</ul>
<p><a id="Encryption"></a><strong>Select Your Encryption Method</strong><br />
The first thing you must decide on is what encryption to use. The decision is pretty simple; pick the strongest form of wireless encryption that your network will support (excluding the Radius methods for reasons noted below). Remember, even if your wireless router supports the strongest encryption but some of the wireless cards joining the network does not then you will have problems connecting from those machines if you don&#8217;t pick a level of encryption supported by all of your devices. Most people with remotely up-to-date hardware will not have trouble supporting all of the encryption levels mentioned below.</p>
<p>Below I&#8217;ve listed the DD-WRT&#8217;s wireless encryption security mode options (these will be available in most other wireless routers) from strongest to weakest:</p>
<ol>
<li>WPA2 Radius Only</li>
<li>WPA2 Radius Mixed</li>
<li>WPA Radius</li>
<li>WPA2 Pre-Shared Key Only</li>
<li>WPA2 Pre-Shared Key Mixed</li>
<li>WPA Pre-Shared Key</li>
<li>Radius</li>
<li>WEP</li>
<li>Disabled</li>
</ol>
<p>All of the <abbr title="Remote Authentication Dial In User Service">RADIUS</abbr> methods are too complex for most home users because they require a separate <a href="http://en.wikipedia.org/wiki/RADIUS">Radius server</a> for for authentication. <abbr title="Remote Authentication Dial In User Service">RADIUS</abbr> is designed for a Corporate type environment.</p>
<p>The DD-WRT firmware provides a second option for WPA Algorithms (for WPA security modes) or Encryption (for WEP security modes).</p>
<p>The <a href="http://en.wikipedia.org/wiki/Wi-Fi_Protected_Access">WPA</a> preferred order is:</p>
<ol>
<li><a href="http://en.wikipedia.org/wiki/Advanced_Encryption_Standard">AES</a></li>
<li>AES + TKIP</li>
<li><a href="http://en.wikipedia.org/wiki/TKIP">TKIP</a></li>
</ol>
<p><small><em>The DD-WRT help file suggests using WPA2 Mixed/TKIP+AES for maximum interoperability. So if you&#8217;re having trouble getting WPA2 AES to work on your network, try this configuration. Also note that WPA2 TKIP is not supported. Don&#8217;t worry, any form of WPA is very secure.</em></small></p>
<p>For <a href="http://en.wikipedia.org/wiki/Wired_Equivalent_Privacy">WEP</a>, the preferred order is:</p>
<ol>
<li>128-bits 26 hex digits</li>
<li>64-bits 10 hex digits</li>
</ol>
<p>Below is a screenshot of the encryption settings I recommend:</p>
<p><img src='http://www.mandladventures.com/wp-content/uploads/2007/04/encryption.png' alt='Encryption Settings' /></p>
<p><small><em>Note:  Both forms of WEP are easy to hack due to poor implementation of the RC4 Stream Cipher; don&#8217;t worry what this means right now, just know its really insecure. Also, note some people call 128 bit 105 bit WEP and 64 bit WEP 40 bit because they subtract the 24 initialization vector (IV).</em></small></p>
<p><a id="Password"></a><strong>Select Your Password</strong><br />
Password selection is of vital importance as well because if someone can easily <a href="http://en.wikipedia.org/wiki/Brute_force_attack">brute force</a> your password (quickly determine your password by trying all possible values) then the strongest form of encryption is worthless. Some people claim WPA has been broken, but in reality all that has really happened is someone sniffed a lot of packets and then carried out a <a href="http://en.wikipedia.org/wiki/Dictionary_attack">dictionary</a> or brute force attack and correctly guessed the password. A WEP password doesn&#8217;t really matter as a WPA password because a hacker with a little time and some free tools can quickly determine your WEP password due to the improper implementation of the encryption algorithm.</p>
<p>So, how can you make it practically impossible to brute force your password? The answer is simple&#8230;use a long, random password. The longer the password the more time brute forcing takes to work (as in thousands of years for a strong password). Basically, brute forcing tries all possible combinations of letters and number (or a predetermined sub-set of them) until the combination works so the longer the password the more guesses required. Randomness protects against dictionary attacks. A dictionary attack is just like it sounds. A very large list of common passwords is tried; therefore, you don&#8217;t want to use any words that may be in a dictionary.</p>
<p>Because you are not required to enter your wireless password more than once on each client you want to connect to your wireless network, you can easily select a very long and complex password and not worry about having to memorizing it. <abbr title="Gibson Research Corporation">GRC</abbr> has an excellent random <a href="https://www.grc.com/passwords.htm">password generator</a> perfect for wireless security. Use the 63 random printable ASCII character for ultimate security. Why 63 characters? Its the maximum length accepted by WPA.</p>
<p><img src='http://www.mandladventures.com/wp-content/uploads/2007/04/passwords.Png' alt='Passwords' /></p>
<p>Although I trust <a href="https://www.grc.com/passwords.htm">GRC&#8217;s Ultra High Security Password Generator</a>, I still hit the refresh button a few times to collect a small selection of passwords. Then, I cut and pasted tidbits of each password to ensure its security&#8211;I know you think I&#8217;m crazy.</p>
<p>Of course, you must store this password in a protected place to keep others from finding it. I recommend putting it on a portable storage device such as a CD or USB drive. If you want to be ultra secure, and geeky, store the password in an encrypted form with a tool such as <a href="http://www.truecrypt.org/">TrueCrypt</a>.</p>
<p>WEP requires you to use an exact password length so you won&#8217;t be able to use the full 63 character long password generated by <a href="https://www.grc.com/passwords.htm">GRC&#8217;s Ultra High Security Password Generator</a>. 26 hexadecimal characters equates to 13 alpha-numeric characters and 10 hexadecimal characters equals 5 alpha-numeric characters. If you must use WEP, you can just select the appropriate subset (26 characters for 128bit WEP and 10 characters from the 64bit WEP) from the 64 random hexadecimal characters section of the password generator.</p>
<p><a id="SSID"></a><strong>Disable SSID Broadcast</strong><br />
Hiding Your Service Set IDentifier (SSID) doesn&#8217;t provide much security because anyone using a tool such as <a href="http://en.wikipedia.org/wiki/Kismet_%28program%29">Kismet</a> can still find your <a href="http://en.wikipedia.org/wiki/SSID">SSID</a>, but at least your wireless network ID will be hidden from the average Joe. If you do hide your <abbr title="Service Set IDentifier">SSID</abbr>, your network will not show up when you scan for wireless networks in Windows or OS X so you must manually type in the SSID name you selected on each client when you first time connect to your network.</p>
<p><img src='http://www.mandladventures.com/wp-content/uploads/2007/04/ssid.png' alt='SSID' /></p>
<p><strong><a id="MAC">MAC Filtering</a></strong><br />
<abbr title="Media Access Control">MAC</abbr> Filtering is a way to limit what network cards can connect to your network. Every networking device has a unique <a href="http://en.wikipedia.org/wiki/MAC_address">MAC address</a> assigned to it during the manufacturing process. To set up MAC filtering, you will need to determine the MAC address of every device you want to connect to your network and enter this information into the router.</p>
<p><img src='http://www.mandladventures.com/wp-content/uploads/2007/04/mac_filter.png' alt='Mac Filtering' /></p>
<p>As you can tell, I have MAC Filtering disabled. Why? Its takes quite a bit of time to setup and it doesn&#8217;t provide much security. The idea behind MAC filtering is good, but its flawed because a user is able to <em><a href="http://en.wikisource.org/wiki/Changing_MAC_addresses">change</a></em> their MAC address to anything they want. So, a someone wanting to access your network would use a good wireless sniffer (i.e., Kismet) to determine what MAC addresses are connected to your network. They would then change their MAC address to one of those allowed addresses. Because MAC addresses are supposed to be unique, your access point will get confused if two clients with the same MAC address is connected to it. So, a smart hacker will kickoff the original machine whose MAC address they stole using a common <a href="http://en.wikipedia.org/wiki/Denial-of-service_attack">Denial-of-service</a> (DOS) attack or simply wait for that machine to disconnect.</p>
<p>You must decide whether or not MAC Filtering is worth the trouble because it does provide some protection.</p>
<p><a id="UPnP"></a><strong>Turn Off UPnP</strong><br />
Another worthwhile security measure is turning of <a href="http://en.wikipedia.org/wiki/Universal_plug_and_play">Universal Plug and Play</a> (UPnP) on both your PC and your router. <abbr title="Universal Plug and Play">UPnP</abbr> is bad because it lets software automatically open ports on your router without your knowledge. To make it even worse, you can&#8217;t tell which ports have been opened. The idea behind <abbr title="Universal Plug and Play">UPnP</abbr> was to make it easy for network software/devices to work without a user having to manually configure <a href="http://en.wikipedia.org/wiki/Port_forwarding">Port Forwarding</a>.</p>
<p>The problem is that malware could also use this auto-configuration feature to open ports behind your back in order to communicate with the outside world. Additionally, <abbr title="Universal Plug and Play">UPnP</abbr> has several major vulnerabilities in the past such as buffer overruns that could lead to remote code execution. Although the known vulnerabilities have been patched, turning off <abbr title="Universal Plug and Play">UPnP</abbr> would prevent any future exploits.</p>
<p>The easiest way I know of to turn off <abbr title="Universal Plug and Play">UPnP</abbr> on your PC is to use the <a href="http://www.grc.com/unpnp/unpnp.htm">UnPlug n&#8217; Pray</a> utility.</p>
<p><img src='http://www.mandladventures.com/wp-content/uploads/2007/04/unplugpray.png' alt='UnPlug and Pray' /></p>
<p>Go to the Applications and Gaming tab and the UPnP sub-tab to disable <abbr title="Universal Plug and Play">UPnP</abbr>.</p>
<p><img src='http://www.mandladventures.com/wp-content/uploads/2007/04/upnp.png' alt='UPnP' /></p>
<p><small><em>Note: I believe most routers not running the DD-WRT firmware have a similar option to disable <abbr title="Universal Plug and Play">UPnP</abbr>. If not, disabling it on your PC should be enough as long as Windows, as it has bad habits of doing, doesn&#8217;t decide to turn the feature back on.</em></small></p>
<p>It is important to reset your router to factory defaults to undo any ports opened by <abbr title="Universal Plug and Play">UPnP</abbr> when it was enabled. Please note that resetting your router to factory defaults will also reset any of your custom options, so think twice before doing this.    Be sure to reset your router before completing the rest of the security steps or else you&#8217;ll probably have to re-do them. See the following two pages on the DD-WRT wiki for information on how to perform a reset: <a href="http://www.dd-wrt.com/wiki/index.php/Factory_Defaults">Factory Defaults</a> &#038; <a href="http://www.dd-wrt.com/wiki/index.php/Reset_And_Reboot">Reset and Reboot</a>.</p>
<p>I am uncertain, but simply rebooting (not resetting) your router may also undo the ports opened by <abbr title="Universal Plug and Play">UPnP</abbr>. One way to ensure all your important ports have been closed is to check out the <a href="https://www.grc.com/x/ne.dll?bh0bkyd2">Shields Up</a> web service. If you want to do a full port scan check out <a href="http://en.wikipedia.org/wiki/Nmap">NMAP</a>.</p>
<p><a id="Default"></a><strong>Change Default Router Log-In Settings</strong><br />
Changing the User Name and Password used to configure your router is very important (this is the info you type in when going to 192.168.1.1 o whatever your router&#8217;s internal IP address is). The default router user names and passwords are widely known&#8230;you can easily find a massive list of them. Symantec published an article on a very interesting concept they coined &#8220;<a href="http://www.symantec.com/enterprise/security_response/weblog/2007/02/driveby_pharming_how_clicking_1.html">Drive-By Pharming: How Clicking on a Link Can Cost You Dearly</a>.&#8221; The basic concept is <a href="http://en.wikipedia.org/wiki/Cross-site_request_forgery">Cross Site Request Forgery</a> can be used to log in to your wireless router if you haven&#8217;t changed the default log-in settings. Once access has been gained to your router, your <a href="http://en.wikipedia.org/wiki/Domain_Name_System">DNS</a> Server setting can be changed to a malicious <abbr title="Domain name system">DNS</abbr> server. This is a major problem because <abbr title="Domain name system">DNS</abbr> associates domain names (web site addresses) with server&#8217;s IP addresses. A malicious <abbr title="Domain name system">DNS</abbr> server could associate your-bank.com with spoofed site that looks just like your bank&#8217;s site and collect your user name and password when you try to log in. However, the simple change of your router&#8217;s user name and password protects against this attack.</p>
<p>Go to the Administration tab and the Management sub-tab to change the default settings. While your there, go ahead and disable all Remote Access as well.</p>
<p><img src='http://www.mandladventures.com/wp-content/uploads/2007/04/router_management.png' alt='Router Management' /></p>
<p><a id="Firewall"></a><strong>Setup Your Firewall</strong><br />
Firewalls are set rules for what can come in and out of your network. One of the main benefits of all routers is Network Address Translation (NAT). Basically, it only allows connections into your network if one of your computers made the initial request. Sometimes you will need to use <a href="http://en.wikipedia.org/wiki/Port_forwarding">Port Forwarding</a> to allow connections through certain ports for services running behind your router that you won&#8217;t make the initial request&#8230;for instance you&#8217;re running a web server on your network that needs to accept connections on port 80. If you recall, <abbr title="Universal Plug and Play">UPnP</abbr> automatically configures port forwarding which could open up ports you don&#8217;t want open.</p>
<p><a href="http://en.wikipedia.org/wiki/Stateful_firewall">Stateful packet inspection</a> (SPI) provides an extra layer of security to NAT routers. I recommend enabling <abbr title="Stateful packet inspection">SPI<abbr>, blocking anonymous Internet request, filtering multicast, and filtering <a href="http://en.wikipedia.org/wiki/Ident">IDENT</a>. You can set all of these by going to the Security tab and the Firewall sub-tab.</p>
<p><img src='http://www.mandladventures.com/wp-content/uploads/2007/04/firewall.png' alt='Firewall' /></p>
<p><a id="Patch"></a><strong>Patch Windows Client</strong><br />
One thing I do recommend is downloading the following patches from Microsoft: <a href="http://support.microsoft.com/kb/893357">The Wi-Fi Protected Access 2 (WPA2)/Wireless Provisioning Services Information Element (WPS IE)</a> and <a href="http://support.microsoft.com/?kbid=917021">Wireless Client Update for Windows XP with Service Pack 2</a>.</p>
<p>The first update &#8220;enhances the Windows XP wireless client software with support for the new Wi-Fi Alliance certification for wireless security. The update also makes it easier to connect to secure public spaces that are equipped with wireless Internet access.&#8221;</p>
<p>The second update &#8220;enhances support for Wi-Fi Protected Access 2 (WPA2) options in Wireless Group Policy. This update helps prevent a Windows wireless client from advertising the wireless networks in its preferred networks list.&#8221; Please note that this patch was never included in any automatic updates from Microsoft. Unless you specifically went to Microsoft to download this patch, your system will not have it (as far as I know anyway). Don&#8217;t ask me why Microsoft didn&#8217;t include this in their standard update cycle.</p>
<p><a id="Client"></a><strong>Configure Client Devices</strong><br />
You should configure Windows to only connect to Access Points because Ad-Hoc (computer-to-computer) networks are dangerous. To do this go to Start > Control Panel > Network and Internet Connections >Network Connections then right-click on Wireless Network Connection device and select properties. On the Wireless Network Connections properties screen select the Wireless Networks tab and then the Advanced button. Make sure to select Access point (infrastructure) networks only and uncheck Automatically connect to non-preferred networks.</p>
<p><img src='http://www.mandladventures.com/wp-content/uploads/2007/04/access_point_only.png' alt='Access Points Only' /></p>
<p>You will also need to add your network to the preferred networks list by going back to the Wireless Networks tab and selecting Add. Then type in the appropriate information for you wireless setup.</p>
<p><img src='http://www.mandladventures.com/wp-content/uploads/2007/04/association.png' alt='Wireless Configuration' /></p>
<p><a id="Resources"></a><strong>External Resources</strong><br />
To learn more about Wi-Fi security, I recommend listening to the following episodes of Security Now:</p>
<ul>
<li><a href="http://www.grc.com/securitynow.htm#10">Episode 10:  Open Wireless Access Points</a></li>
<li><a href="http://www.grc.com/securitynow.htm#11">Episode 11:  Bad WiFi Security (WEP and MAC address filtering)</a></li>
<li><a href="http://www.grc.com/securitynow.htm#13">Episode 13:  Unbreakable WiFi Security</a></li>
<li><a href="http://www.grc.com/securitynow.htm#14">Episode 14:  Virtual Private Networks (VPN): Theory</a></li>
<li><a href="http://www.grc.com/securitynow.htm#15">Episode 15:  VPN Secure Tunneling Solutions</a></li>
</ul>
<p><small><em>Note: Each Security Now podcast also have text transcripts.</em></small></p>
<p>I also recommend checking out the following articles:</p>
<ul>
<li><a href="http://en.wikipedia.org/wiki/Wireless_security">Wireless Security</a></li>
<li><a href="http://en.wikipedia.org/wiki/Wireless_LAN_Security">Wireless LAN Security</a></li>
<li><a href="http://www.cs.wright.edu/~pmateti/InternetSecurity/Lectures/WirelessHacks/Mateti-WirelessHacks.htm">Hacking Techniques in Wireless Networks</a></li>
</ul>
<p>I realize this is a long, fairly technical post so feel free to ask any questions, correct any mistakes, offer suggestions, or anything else using the commenting feature below. If nothing else, just let me know if you found this post useful. Thanks!</p>
<p><small><em>Note: Although I touched on a few ways to get around wireless security, I do not advocate doing so. I mentioned some of the techniques because the best way to secure against attacks is to know what attacks are out there.</em></small></p>
<p>Related post<p><strong>Related Posts:</storng></p><ul>s:<ol>
<li><a href='http://www.mandladventures.com/2007/08/10/ajax-security-considerations/' rel='bookmark' title='AJAX Security Considerations&#8230;'>AJAX Security Considerations&#8230;</a></li>
<li><a href='http://www.mandladventures.com/2006/09/21/d-link-dwl-g710-wireless-range-extender-review/' rel='bookmark' title='D-Link DWL-G710 Wireless Range Extender Review'>D-Link DWL-G710 Wireless Range Extender Review</a></li>
</ul>]]></content:encoded>
			<wfw:commentRss>http://www.mandladventures.com/2007/04/21/securing-your-wireless-network/feed/</wfw:commentRss>
		<slash:comments>42</slash:comments>
		</item>
	</channel>
</rss>

