<?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>Pablowe &#187; Security</title>
	<atom:link href="http://www.pablowe.net/category/security/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pablowe.net</link>
	<description>%&#62; random tech;</description>
	<lastBuildDate>Fri, 30 Sep 2011 16:54:28 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>HandlerSocket&#8217;s Secret Authentication Mechanism</title>
		<link>http://www.pablowe.net/2011/03/handlersockets-secret-authentication-mechanism/</link>
		<comments>http://www.pablowe.net/2011/03/handlersockets-secret-authentication-mechanism/#comments</comments>
		<pubDate>Thu, 31 Mar 2011 17:13:01 +0000</pubDate>
		<dc:creator>rlowe</dc:creator>
				<category><![CDATA[HandlerSocket]]></category>
		<category><![CDATA[Random Tech]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[HandlerSocket Authentication]]></category>

		<guid isPermaLink="false">http://www.pablowe.net/?p=708</guid>
		<description><![CDATA[Matt Ward made a comment on another blog post of mine informing me that HandlerSocket does, in fact, support authentication (committed 20 November 2010 in 43545662ddc23faa90ab). He mentions that it&#8217;s only plaintext (you&#8217;ve got to start somewhere, I suppose) and that it is undocumented, which explains why nobody knew about it. The purpose of this [...]]]></description>
		<wfw:commentRss>http://www.pablowe.net/2011/03/handlersockets-secret-authentication-mechanism/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>PCI DSS &amp; MySQL &#8211; Requirement 6</title>
		<link>http://www.pablowe.net/2010/04/pci-dss-mysql-requirement-6/</link>
		<comments>http://www.pablowe.net/2010/04/pci-dss-mysql-requirement-6/#comments</comments>
		<pubDate>Wed, 07 Apr 2010 22:35:22 +0000</pubDate>
		<dc:creator>rlowe</dc:creator>
				<category><![CDATA[MySQL]]></category>
		<category><![CDATA[MySQL Administration]]></category>
		<category><![CDATA[PCI DSS]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[MySQL Security]]></category>

		<guid isPermaLink="false">http://www.pablowe.net/?p=527</guid>
		<description><![CDATA[Requirement 6 of PCI DSS v1.2 states that in order to be compliant, an organization must: &#8220;Develop and maintain secure systems and applications&#8221; &#8220;Unscrupulous individuals use security vulnerabilities to gain privileged access to systems. Many of these vulnerabilities are fixed by vendor- provided security patches, which must be installed by the entities that manage the [...]]]></description>
		<wfw:commentRss>http://www.pablowe.net/2010/04/pci-dss-mysql-requirement-6/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>PCI DSS &amp; MySQL &#8211; Requirement 4</title>
		<link>http://www.pablowe.net/2010/04/pci-dss-mysql-requirement-4/</link>
		<comments>http://www.pablowe.net/2010/04/pci-dss-mysql-requirement-4/#comments</comments>
		<pubDate>Wed, 07 Apr 2010 19:14:45 +0000</pubDate>
		<dc:creator>rlowe</dc:creator>
				<category><![CDATA[MySQL]]></category>
		<category><![CDATA[MySQL Administration]]></category>
		<category><![CDATA[PCI DSS]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[MySQL Security]]></category>

		<guid isPermaLink="false">http://www.pablowe.net/?p=513</guid>
		<description><![CDATA[Requirement 4 of PCI DSS v1.2 states that we must: &#8220;Encrypt transmission of cardholder data across open, public networks&#8221; Specifically, &#8220;Sensitive information must be encrypted during transmission over networks that are easily accessed by malicious individuals. Misconfigured wireless networks and vulnerabilities in legacy encryption and authentication protocols can be continued targets of malicious individuals who [...]]]></description>
		<wfw:commentRss>http://www.pablowe.net/2010/04/pci-dss-mysql-requirement-4/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>PCI DSS &amp; MySQL: Requirement 3</title>
		<link>http://www.pablowe.net/2010/04/pci-dss-mysql-requirement-3/</link>
		<comments>http://www.pablowe.net/2010/04/pci-dss-mysql-requirement-3/#comments</comments>
		<pubDate>Wed, 07 Apr 2010 14:27:51 +0000</pubDate>
		<dc:creator>rlowe</dc:creator>
				<category><![CDATA[MySQL]]></category>
		<category><![CDATA[PCI DSS]]></category>
		<category><![CDATA[Security]]></category>

		<guid isPermaLink="false">http://www.pablowe.net/?p=447</guid>
		<description><![CDATA[Requirement 3 of the PCI DSS v1.2 is: &#8220;Protect Stored Cardholder Data&#8221; As vague as that sounds, the PCI DSS enumerates exactly what that covers: Data Element Storage Permitted Protection Required PCI DSS Req 3.4 Primary Account Number Yes Yes Yes Cardholder Name* Yes Yes No Service Code* Yes Yes No Expiration Date* Yes Yes [...]]]></description>
		<wfw:commentRss>http://www.pablowe.net/2010/04/pci-dss-mysql-requirement-3/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>PCI DSS &amp; MySQL &#8211; Requirement 2</title>
		<link>http://www.pablowe.net/2010/04/pci-dss-mysql-requirement-2/</link>
		<comments>http://www.pablowe.net/2010/04/pci-dss-mysql-requirement-2/#comments</comments>
		<pubDate>Tue, 06 Apr 2010 14:54:58 +0000</pubDate>
		<dc:creator>rlowe</dc:creator>
				<category><![CDATA[MySQL]]></category>
		<category><![CDATA[PCI DSS]]></category>
		<category><![CDATA[Security]]></category>

		<guid isPermaLink="false">http://www.pablowe.net/?p=414</guid>
		<description><![CDATA[Requirement 2 of the PCI DSS v1.2 is: &#8220;Do not use vendor-supplied defaults for system passwords and other security parameters&#8221; Understanding that we&#8217;re limiting the discussion solely to MySQL (OS, Network Devices, and other software will no doubt apply to overall compliance), we can do this easily. The vendor-supplied default MySQL 5.1.43 (they&#8217;re similar across [...]]]></description>
		<wfw:commentRss>http://www.pablowe.net/2010/04/pci-dss-mysql-requirement-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>HTTP Over SSL Best Practices</title>
		<link>http://www.pablowe.net/2009/08/http-over-ssl-best-practices/</link>
		<comments>http://www.pablowe.net/2009/08/http-over-ssl-best-practices/#comments</comments>
		<pubDate>Sat, 15 Aug 2009 23:51:07 +0000</pubDate>
		<dc:creator>rlowe</dc:creator>
				<category><![CDATA[Random Tech]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[HTTPS]]></category>
		<category><![CDATA[SSL]]></category>

		<guid isPermaLink="false">http://www.pablowe.net/?p=307</guid>
		<description><![CDATA[Encrypting connections to your web server using HTTPS is a trade-off between performance and security. Therefore, there&#8217;s no &#8220;right answer&#8221; for exactly what traffic to encrypt; it&#8217;s a business decision. There are, however, best practices that can guide you in the decision making process. In fact, there is a &#8220;golden rule&#8221; for making this decision: [...]]]></description>
		<wfw:commentRss>http://www.pablowe.net/2009/08/http-over-ssl-best-practices/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

