<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: My reply to Bejtlich on DRM and PCI Requirements</title>
	<atom:link href="http://www.bloginfosec.com/2007/06/13/my-reply-to-bejtlich-on-drm-and-pci-requirements/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bloginfosec.com/2007/06/13/my-reply-to-bejtlich-on-drm-and-pci-requirements/</link>
	<description>An Information Security Magazine in a Blog Format</description>
	<lastBuildDate>Mon, 30 Jan 2012 11:01:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Kenneth F. Belva</title>
		<link>http://www.bloginfosec.com/2007/06/13/my-reply-to-bejtlich-on-drm-and-pci-requirements/comment-page-1/#comment-92</link>
		<dc:creator>Kenneth F. Belva</dc:creator>
		<pubDate>Wed, 13 Jun 2007 22:15:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.bloginfosec.com/2007/06/13/my-reply-to-bejtlich-on-drm-and-pci-requirements/#comment-92</guid>
		<description>Hi B.K. DeLong,

Our paper does not argue against the validity of PCI. Our paper deals with whether or not security mechanisms may be used as enabling mechanisms.

In our paper we argue they can and we cite examples of how security enables processes, hence the apple DRM example.

Richard was arguing against the enablement perspective by saying that PCI compliance does not contribute to the bottom line and it does not have a ROI.

Sincerely,
Ken</description>
		<content:encoded><![CDATA[<p>Hi B.K. DeLong,</p>
<p>Our paper does not argue against the validity of PCI. Our paper deals with whether or not security mechanisms may be used as enabling mechanisms.</p>
<p>In our paper we argue they can and we cite examples of how security enables processes, hence the apple DRM example.</p>
<p>Richard was arguing against the enablement perspective by saying that PCI compliance does not contribute to the bottom line and it does not have a ROI.</p>
<p>Sincerely,<br />
Ken</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Bejtlich</title>
		<link>http://www.bloginfosec.com/2007/06/13/my-reply-to-bejtlich-on-drm-and-pci-requirements/comment-page-1/#comment-91</link>
		<dc:creator>Richard Bejtlich</dc:creator>
		<pubDate>Wed, 13 Jun 2007 18:06:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.bloginfosec.com/2007/06/13/my-reply-to-bejtlich-on-drm-and-pci-requirements/#comment-91</guid>
		<description>Hi Ken,

Thanks for your answer.  I think security is only *appreciated* &quot;when something happens&quot;.  A world without security would be no world at all.</description>
		<content:encoded><![CDATA[<p>Hi Ken,</p>
<p>Thanks for your answer.  I think security is only *appreciated* &#8220;when something happens&#8221;.  A world without security would be no world at all.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: B.K. DeLong</title>
		<link>http://www.bloginfosec.com/2007/06/13/my-reply-to-bejtlich-on-drm-and-pci-requirements/comment-page-1/#comment-90</link>
		<dc:creator>B.K. DeLong</dc:creator>
		<pubDate>Wed, 13 Jun 2007 15:18:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.bloginfosec.com/2007/06/13/my-reply-to-bejtlich-on-drm-and-pci-requirements/#comment-90</guid>
		<description>Interesting - while PCI may not directly boost the bottom line, lack of compliance could hurt it. Very much.

Not only is the PCI Consortium actively fining those not in compliance, (some companies are choosing to take the hit), but they are now removing repeat offenders&#039; ability to process cards for long periods of time.

The problem is because the fines and the rights revocation is a private relationship between a credit card company and a vendor, the PCI Consortium is not publicly disclosing the information about them. Thus a) consumers don&#039;t know who is being deemed insecure and b) vendors don&#039;t realize that the PCI co *is* taking action against those not in compliance.</description>
		<content:encoded><![CDATA[<p>Interesting &#8211; while PCI may not directly boost the bottom line, lack of compliance could hurt it. Very much.</p>
<p>Not only is the PCI Consortium actively fining those not in compliance, (some companies are choosing to take the hit), but they are now removing repeat offenders&#8217; ability to process cards for long periods of time.</p>
<p>The problem is because the fines and the rights revocation is a private relationship between a credit card company and a vendor, the PCI Consortium is not publicly disclosing the information about them. Thus a) consumers don&#8217;t know who is being deemed insecure and b) vendors don&#8217;t realize that the PCI co *is* taking action against those not in compliance.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

