<?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>Hyper Dog Denver SEO Blog &#124; Colorado Web Site Development &#187; Security</title>
	<atom:link href="http://www.hyperdogmedia.com/blog/category/security/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.hyperdogmedia.com/blog</link>
	<description>Denver, Colorado SEO &#124; Web Development Tips</description>
	<lastBuildDate>Mon, 23 Aug 2010 17:29:43 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>5 web development techniques to prevent Google from crawling your HTML forms</title>
		<link>http://www.hyperdogmedia.com/blog/2008/04/18/5-web-development-techniques-to-prevent-google-from-crawling-your-html-forms/</link>
		<comments>http://www.hyperdogmedia.com/blog/2008/04/18/5-web-development-techniques-to-prevent-google-from-crawling-your-html-forms/#comments</comments>
		<pubDate>Fri, 18 Apr 2008 21:36:39 +0000</pubDate>
		<dc:creator>Jim</dc:creator>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[Web Design]]></category>
		<category><![CDATA[Web Development]]></category>
		<category><![CDATA[colorado web development]]></category>
		<category><![CDATA[googlebot]]></category>

		<guid isPermaLink="false">http://www.hyperdogmedia.com/blog/2008/04/18/5-web-development-techniques-to-prevent-google-from-crawling-your-html-forms/</guid>
		<description><![CDATA[Google has recently decided to let it&#8217;s Googlebot crawl through forms in an effort to index the &#8220;Deep Web&#8221;. There are numerous stories about wayward crawlers deleting and changing content through submitting forms, and it&#8217;s about to get worse. Googlebot is about to start submitting forms in an effort to get to your website&#8217;s deeper [...]]]></description>
			<content:encoded><![CDATA[<p>Google has recently decided to let it&#8217;s Googlebot <a title="Google will start crawling forms" href="http://googlewebmastercentral.blogspot.com/2008/04/crawling-through-html-forms.html" rel="nofollow">crawl through forms</a> in an effort to index the &#8220;Deep Web&#8221;. There are numerous stories about wayward crawlers deleting and changing content through submitting forms, and it&#8217;s about to get worse. Googlebot is about to start submitting forms in an effort to get to your website&#8217;s deeper data.  So what&#8217;s a web developer to do?</p>
<p>1. Use GET and POST requests correctly<br />
Use GET requests in forms to look up information, use POST requests to make changes. Google will only be crawling forms via GET requests, so following this &#8220;Best Practice&#8221; for forms is vital.</p>
<p>2. Make sure your POST forms do not respond to GET requests<br />
It sounds so simple, but many sites are being exploited for XSS (Cross Site Scripting) vulnerabilities because they respond (and return HTML) to both GET and POST requests. Be sure to check your form input carefully on the backend, and for heaven&#8217;s sake &#8211; do not use globals!</p>
<p>3. Use robots.txt to keep robots OUT<br />
robots.txt file keeps Googlebot out of where it doesn&#8217;t belong. Luckily, Googlebot will continue it&#8217;s excellent support of robots.txt directives when it goes crawling through forms. Be sure not to accidentally restrict your website too much, however. Keep the directives simple, excluding by directory if possible. And test, test, test in Google&#8217;s Webmaster Tools!</p>
<p>4. Use robots metatag directives<br />
Using the robots metatag directives for more refined control. We recommend &#8220;nofollow&#8221; and &#8220;noindex&#8221; directives for both the form submission page and search results pages you want Google to stay out of, even though Google says disallowing the form submission page is enough. Consider using tags and category pages that are Google friendly instead.</p>
<p>5. Use a CAPTCHA where possible<br />
Googlebot isn&#8217;t going to fill out a CAPTCHA, so it&#8217;s an easy way to make sure some bot isn&#8217;t filling out your form.</p>
<p>Googlebot is, of course, the nicest bot you can hope to have visit your website. This provides a chance to secure forms and take necessary precautions before other  &#8211; not so polite &#8211; bots visit your forms.
<p>Tags: <a href="http://technorati.com/tag/denver+web+design" rel="tag">denver web design</a>, <a href="http://technorati.com/tag/seo" rel="tag">seo</a>, <a href="http://technorati.com/tag/website+development" rel="tag">website development</a>, <a href="http://technorati.com/tag/denver+web+development" rel="tag">denver web development</a>, <a href="http://technorati.com/tag/search+engine+optimization" rel="tag">search engine optimization</a>, <a href="http://technorati.com/tag/website+design" rel="tag">website design</a></p>
<p align="left"><a class="tt" href="http://twitter.com/home/?status=5+web+development+techniques+to+prevent+Google+from+crawling+your+HTML+forms+http://amgfk.th8.us" title="Post to Twitter"><img class="nothumb" src="http://www.hyperdogmedia.com/blog/wp-content/plugins/tweet-this/icons/tt-twitter.png" alt="Post to Twitter" /></a> <a class="tt" href="http://twitter.com/home/?status=5+web+development+techniques+to+prevent+Google+from+crawling+your+HTML+forms+http://amgfk.th8.us" title="Post to Twitter">Tweet This Post</a></p>]]></content:encoded>
			<wfw:commentRss>http://www.hyperdogmedia.com/blog/2008/04/18/5-web-development-techniques-to-prevent-google-from-crawling-your-html-forms/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Keeping track of multiple passwords</title>
		<link>http://www.hyperdogmedia.com/blog/2006/09/13/keeping-track-of-multiple-passwords/</link>
		<comments>http://www.hyperdogmedia.com/blog/2006/09/13/keeping-track-of-multiple-passwords/#comments</comments>
		<pubDate>Wed, 13 Sep 2006 21:28:26 +0000</pubDate>
		<dc:creator>Jim</dc:creator>
				<category><![CDATA[Misc]]></category>
		<category><![CDATA[Security]]></category>

		<guid isPermaLink="false">http://hyperdogmedia.com/blog/2006/09/13/keeping-track-of-multiple-passwords/</guid>
		<description><![CDATA[RSA Security&#8217;s newest password management survey found that one of the greatest threats to corporate security is the weak password. Employees that change their too often, or have to juggle too many passwords for login to various services, are likely to choose weak passwords or even write them on a scrap of paper near their [...]]]></description>
			<content:encoded><![CDATA[<p>RSA Security&#8217;s newest <strong>password management survey</strong> found that one of the greatest threats to corporate security is the weak password. Employees that change their too often, or have to juggle too many passwords for login to various services, are likely to choose weak passwords or even write them on a scrap of paper near their station. I am a little suspicious a survey that highlights RSA security as the solution to this problem, but it is valuable to stop and ask yourself &#8220;Do I have too many passwords to keep track of?&#8221;.<br />
Sure, too many passwords lead to &#8220;irresponsible password behavior&#8221;. A single login and password for every service is usually a bad idea, too. Once an intruder has access, they could wreak tremendous havoc.</p>
<p>A sensible alternative is to choose Four passwords that you can actually remember. Make each password incrementally more random, if possible. Choose the weakest password, and use it to sign up for services that only need a password for the most rudimentary of tasks. Use the &#8220;second level&#8221; password for sites that may have some personal information &#8211; your name, address, etc. Save the &#8220;third level&#8221; password for sites that have your credit card on file. The final password is to be used only in online banking and/or paypal.</p>
<p>Gee, so simple. But who can keep track of Four passwords, anyway?! Good luck out there &#8211; no one ever said good security was easy!</p>
<p>(<a title="RSA password management survey" href="http://www.paymentsnews.com/2006/09/volume_of_busin.html">More information on the password survey</a>)</p>
<p align="left"><a class="tt" href="http://twitter.com/home/?status=Keeping+track+of+multiple+passwords+http://ewg96.th8.us" title="Post to Twitter"><img class="nothumb" src="http://www.hyperdogmedia.com/blog/wp-content/plugins/tweet-this/icons/tt-twitter.png" alt="Post to Twitter" /></a> <a class="tt" href="http://twitter.com/home/?status=Keeping+track+of+multiple+passwords+http://ewg96.th8.us" title="Post to Twitter">Tweet This Post</a></p>]]></content:encoded>
			<wfw:commentRss>http://www.hyperdogmedia.com/blog/2006/09/13/keeping-track-of-multiple-passwords/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Electronic Voting Machines: More troubles</title>
		<link>http://www.hyperdogmedia.com/blog/2006/09/13/electronic-voting-machines-more-troubles/</link>
		<comments>http://www.hyperdogmedia.com/blog/2006/09/13/electronic-voting-machines-more-troubles/#comments</comments>
		<pubDate>Wed, 13 Sep 2006 06:02:22 +0000</pubDate>
		<dc:creator>Jim</dc:creator>
				<category><![CDATA[Misc]]></category>
		<category><![CDATA[Privacy]]></category>
		<category><![CDATA[Security]]></category>

		<guid isPermaLink="false">http://hyperdogmedia.com/blog/2006/09/13/electronic-voting-machines-more-troubles/</guid>
		<description><![CDATA[In Maryland, the electronic voting machines were inoperable when polling places opened. It was human error, though: Plastic wallet sized cards needed ro operate the machines were forgotten and a scramble ensued. By the end of the day, election workers had voters casting on scraps of paper, sealed inside envelopes purchased at the local pharmacy. [...]]]></description>
			<content:encoded><![CDATA[<p>In Maryland, the electronic voting machines were inoperable when polling places opened. It was human error, though: Plastic wallet sized cards needed ro operate the machines were forgotten and <a title="Maryland electronic polling problems" href="http://www.washingtonpost.com/wp-dyn/content/article/2006/09/12/AR2006091200535.html">a scramble ensued</a>. By the end of the day, election workers had voters casting on scraps of paper, sealed inside envelopes purchased at the local pharmacy. Despite the cases of security issues(<a title="Diebold machine hacked by a monkey" href="http://www.foxnews.com/story/0,2933,133214,00.html">once hacked by a monkey?!</a>), electronic voting is here to stay. Unfortunately, it seems the machines are being phased in too quickly &#8211; without the necessary fallbacks to paper balloting systems when needed. Track the latest issues during the primaries at <a target="_blank" title="Diebold electronic voting issues" href="http://www.blackboxvoting.org/">www.blackboxvoting.org</a>.</p>
<p align="left"><a class="tt" href="http://twitter.com/home/?status=Electronic+Voting+Machines%3A+More+troubles+http://nirsn.th8.us" title="Post to Twitter"><img class="nothumb" src="http://www.hyperdogmedia.com/blog/wp-content/plugins/tweet-this/icons/tt-twitter.png" alt="Post to Twitter" /></a> <a class="tt" href="http://twitter.com/home/?status=Electronic+Voting+Machines%3A+More+troubles+http://nirsn.th8.us" title="Post to Twitter">Tweet This Post</a></p>]]></content:encoded>
			<wfw:commentRss>http://www.hyperdogmedia.com/blog/2006/09/13/electronic-voting-machines-more-troubles/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
