<?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>Security Pie &#187; Regulations</title>
	<atom:link href="http://securitypie.com/category/regulations/feed/" rel="self" type="application/rss+xml" />
	<link>http://securitypie.com</link>
	<description>The ramblings of three security curmudgeons</description>
	<lastBuildDate>Thu, 26 Aug 2010 21:32:46 +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>Amex &#8211; Where is PCI?</title>
		<link>http://securitypie.com/amex-where-is-pci/</link>
		<comments>http://securitypie.com/amex-where-is-pci/#comments</comments>
		<pubDate>Wed, 08 Jul 2009 23:51:00 +0000</pubDate>
		<dc:creator>assafl</dc:creator>
				<category><![CDATA[Data protection]]></category>
		<category><![CDATA[Regulations]]></category>
		<category><![CDATA[privacy]]></category>
		<category><![CDATA[AMEX]]></category>
		<category><![CDATA[PCI]]></category>

		<guid isPermaLink="false">http://securitypie.com/?p=555</guid>
		<description><![CDATA[Ok &#8211; so this stuff bugs me. Whenever a company sets up standards for others to live by but fails to live up to the same standards themselves I get annoyed. Amex is the &#8220;bully&#8221; in point. See http://www.kpho.com/money/19936013/detail.html for a story in which two guys who worked at Amex were able to abscond with [...]]]></description>
			<content:encoded><![CDATA[<p>Ok &#8211; so this stuff bugs me. Whenever a company sets up standards for others to live by but fails to live up to the same standards themselves I get annoyed. Amex is the &#8220;bully&#8221; in point.</p>
<p>See <a href="http://www.kpho.com/money/19936013/detail.html">http://www.kpho.com/money/19936013/detail.html</a> for a story in which two guys who worked at Amex were able to abscond with &#8220;thousands&#8221; of credit card number and &#8220;millions&#8221; of customer dollars.</p>
<p>I have two Amex cards. So I went to the Amex website to figure out if my card was somehow exposed. NADA. Not a single word anywhere on the site (perhaps I missed it?).</p>
<p>What is the use of PCI if one of the three card peddlers (Visa and Mastercard being the other two) reflect an attitude of indifference towards protecting MY data.</p>
<p>Wake up Amex CEO: Kenneth I. Chenault. I entrust you with my data. It is time for you to protect it! Mighty nice of you to harrass others with odd PCI requirements. Perhaps it is time you pass a PCI audit yourself.</p>
<p>/al</p>
]]></content:encoded>
			<wfw:commentRss>http://securitypie.com/amex-where-is-pci/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Federal Regulations Mandates Protection Of Private Sector Data</title>
		<link>http://securitypie.com/federal-regulations-mandates-protection-of-private-sector-data/</link>
		<comments>http://securitypie.com/federal-regulations-mandates-protection-of-private-sector-data/#comments</comments>
		<pubDate>Thu, 18 Sep 2008 05:38:10 +0000</pubDate>
		<dc:creator>sharon</dc:creator>
				<category><![CDATA[Politics]]></category>
		<category><![CDATA[Regulations]]></category>
		<category><![CDATA[Security Business]]></category>
		<category><![CDATA[Data protection]]></category>
		<category><![CDATA[Federal]]></category>
		<category><![CDATA[FISMA]]></category>

		<guid isPermaLink="false">http://securitypie.com/?p=87</guid>
		<description><![CDATA[Here&#8217;s some very interesting reading material. I must admit that I was not aware of all the Federal policies to govern and protect IT systems and data in private sector companies. Below you can read the summary of the United States Government Accountability Office GAO-08-1075R. More important, this document lists some of the penalties and [...]]]></description>
			<content:encoded><![CDATA[<p>Here&#8217;s some very interesting reading material. I must admit that I was not aware of all the Federal policies to govern and protect IT systems and data in <strong>private </strong>sector companies. Below you can read the summary of the United States Government Accountability Office <a href="http://www.gao.gov/new.items/d081075r.pdf" target="_blank">GAO-08-1075R.</a></p>
<p>More important, this document lists some of the penalties and enforcement options that the Feds can use.</p>
<div id="attachment_88" class="wp-caption aligncenter" style="width: 310px"><a href="http://securitypie.com/wp-content/uploads/2008/09/figure-1-of-gao-08-1075r.png"><img class="size-medium wp-image-88" title="figure-1-of-gao-08-1075r" src="http://securitypie.com/wp-content/uploads/2008/09/figure-1-of-gao-08-1075r-300x185.png" alt="Summary of Federal Requirements for Securing Privately Owned IT Systems and Data" width="300" height="185" /></a><p class="wp-caption-text">Summary of Federal Requirements for Securing Privately Owned IT Systems and Data</p></div>
<p>Federal policy identifies 18 infrastructure sectors&#8211;such as banking and finance, energy, public health and healthcare, and telecommunications&#8211;that are critical to the nation&#8217;s security, economy, public health, and safety. Because these sectors rely extensively on computerized information systems and electronic data, it is crucial that the security of these systems and data is maintained. Further, because most of these infrastructures are owned by the private sector, it is imperative that public and private entities work together to protect these assets. The federal government uses both voluntary partnerships with private industry and requirements in federal laws, regulations, and mandatory standards to assist in the security of privately owned information technology (IT) systems and data within critical infrastructure sectors. As agreed, our objectives were to (1) identify, for each critical infrastructure sector, the federal laws, regulations, and mandatory standards that pertain to securing that sector&#8217;s privately owned IT systems and data and (2) identify enforcement mechanisms for each of the above laws, regulations, and mandatory standards.<br />
<span id="more-87"></span><br />
There are at least 34 federal laws, regulations, and mandatory standards that pertain to securing privately owned IT systems and data in our nation&#8217;s critical infrastructure sectors. Of the 34, 1 is a law, 25 are regulations, and 8 are mandatory standards. These requirements pertain to 10 of the 18 critical infrastructure sectors, including the agriculture and food; energy; nuclear reactors, materials, and waste; and transportation systems sectors. Each of the 34 federal legal requirements has at least one enforcement mechanism. These mechanisms include court injunctions, civil monetary penalties, criminal penalties, and administrative actions, such as license revocation and suspension. Typically, these mechanisms are what agencies use to enforce requirements in general, and are not necessarily specific to the requirements for securing privately owned IT systems and data.</p>
]]></content:encoded>
			<wfw:commentRss>http://securitypie.com/federal-regulations-mandates-protection-of-private-sector-data/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
