<?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: Are Compliance and Security Related?</title>
	<atom:link href="http://spiresecurity.com/?feed=rss2&#038;p=102" rel="self" type="application/rss+xml" />
	<link>http://spiresecurity.com/?p=102</link>
	<description>Risk and Cybersecurity Analysis</description>
	<lastBuildDate>Wed, 21 Aug 2013 23:28:51 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Anton Chuvakin</title>
		<link>http://spiresecurity.com/?p=102&#038;cpage=1#comment-94</link>
		<dc:creator>Anton Chuvakin</dc:creator>
		<pubDate>Wed, 04 Feb 2009 18:41:40 +0000</pubDate>
		<guid isPermaLink="false">http://spiresecurity.com/blog/?p=102#comment-94</guid>
		<description><![CDATA[&quot;There must be someone out there who believe that compliance and security ARE related.&quot;

Of course they are! Compliance (its infosec-related part) was created to push people who ignored security to do a bit of security

See the link below e.g.

&lt;a href=&quot;http://chuvakin.blogspot.com/2007/11/risk-vs-risk.html&quot; rel=&quot;nofollow&quot;&gt;http://chuvakin.blogspot.com/2007/11/risk-vs-risk.html&lt;/a&gt;
]]></description>
		<content:encoded><![CDATA[<p>&#8220;There must be someone out there who believe that compliance and security ARE related.&#8221;</p>
<p>Of course they are! Compliance (its infosec-related part) was created to push people who ignored security to do a bit of security</p>
<p>See the link below e.g.</p>
<p><a href="http://chuvakin.blogspot.com/2007/11/risk-vs-risk.html" rel="nofollow">http://chuvakin.blogspot.com/2007/11/risk-vs-risk.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: www.google.com/accounts/o8/id?id=AItOawl7U21TVobUkIe4n8TDkiZ1qGmVeaO642s</title>
		<link>http://spiresecurity.com/?p=102&#038;cpage=1#comment-93</link>
		<dc:creator>www.google.com/accounts/o8/id?id=AItOawl7U21TVobUkIe4n8TDkiZ1qGmVeaO642s</dc:creator>
		<pubDate>Sat, 31 Jan 2009 01:11:21 +0000</pubDate>
		<guid isPermaLink="false">http://spiresecurity.com/blog/?p=102#comment-93</guid>
		<description><![CDATA[Where do you think the rules you&#039;re being asked to comply with come from?  They&#039;re created by security professionals, just like all good security rules.  They&#039;re intended to set a generic baseline of good practice that everyone is expected to follow.  There&#039;s no harm in having stronger controls than the compliance requirements -- in fact it&#039;s usually a very good idea.  It&#039;s security &quot;un-professionals&quot; who have such runaway egos that they think unless the control was specified by themselves, it&#039;s automatically no good.
]]></description>
		<content:encoded><![CDATA[<p>Where do you think the rules you&#8217;re being asked to comply with come from?  They&#8217;re created by security professionals, just like all good security rules.  They&#8217;re intended to set a generic baseline of good practice that everyone is expected to follow.  There&#8217;s no harm in having stronger controls than the compliance requirements &#8212; in fact it&#8217;s usually a very good idea.  It&#8217;s security &#8220;un-professionals&#8221; who have such runaway egos that they think unless the control was specified by themselves, it&#8217;s automatically no good.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Augusto Paes de Barros</title>
		<link>http://spiresecurity.com/?p=102&#038;cpage=1#comment-92</link>
		<dc:creator>Augusto Paes de Barros</dc:creator>
		<pubDate>Fri, 30 Jan 2009 20:38:00 +0000</pubDate>
		<guid isPermaLink="false">http://spiresecurity.com/blog/?p=102#comment-92</guid>
		<description><![CDATA[Trying to be a little more effective than the prevoous comment,

Compliance related to external regulations and to your standards (that reflect your desired security state) equals security.

Compliance to external regulations only is certainly smaller than security, as your security needs may not be addressed by them.
]]></description>
		<content:encoded><![CDATA[<p>Trying to be a little more effective than the prevoous comment,</p>
<p>Compliance related to external regulations and to your standards (that reflect your desired security state) equals security.</p>
<p>Compliance to external regulations only is certainly smaller than security, as your security needs may not be addressed by them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Augusto Paes de Barros</title>
		<link>http://spiresecurity.com/?p=102&#038;cpage=1#comment-91</link>
		<dc:creator>Augusto Paes de Barros</dc:creator>
		<pubDate>Fri, 30 Jan 2009 20:34:26 +0000</pubDate>
		<guid isPermaLink="false">http://spiresecurity.com/blog/?p=102#comment-91</guid>
		<description><![CDATA[Good question. Compliance is more targeted to ensure that you are following risk standards determined by third parties, usually regulatory bodies. That&#039;s mostly to avoid an organization risk apetite increasing the risk to others (like one merchant affecting cardholders and other merchants). It&#039;s a way to define a baseline of controls.

What usually makes compliance different from security is that you usually need to be compliant to standards that are target to reduce risk to others, not to you. When you include internal policies as compliance matter, it starts to walk hand in hand with security, as your policies are your proposed posture on security. If you are in compliance with your policies you should be at your desired level of security. Ensuring that your policies really reflect the most effective security for your business can also be seen as compliance with risk management based standards, like ISO27001.
]]></description>
		<content:encoded><![CDATA[<p>Good question. Compliance is more targeted to ensure that you are following risk standards determined by third parties, usually regulatory bodies. That&#8217;s mostly to avoid an organization risk apetite increasing the risk to others (like one merchant affecting cardholders and other merchants). It&#8217;s a way to define a baseline of controls.</p>
<p>What usually makes compliance different from security is that you usually need to be compliant to standards that are target to reduce risk to others, not to you. When you include internal policies as compliance matter, it starts to walk hand in hand with security, as your policies are your proposed posture on security. If you are in compliance with your policies you should be at your desired level of security. Ensuring that your policies really reflect the most effective security for your business can also be seen as compliance with risk management based standards, like ISO27001.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: shrdlu</title>
		<link>http://spiresecurity.com/?p=102&#038;cpage=1#comment-90</link>
		<dc:creator>shrdlu</dc:creator>
		<pubDate>Fri, 30 Jan 2009 20:00:22 +0000</pubDate>
		<guid isPermaLink="false">http://spiresecurity.com/blog/?p=102#comment-90</guid>
		<description><![CDATA[Compliance is for those who are too lame to do their own security.

How&#039;s that? ;-)

]]></description>
		<content:encoded><![CDATA[<p>Compliance is for those who are too lame to do their own security.</p>
<p>How&#8217;s that? <img src='http://spiresecurity.com/blog/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>
