<?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/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	>
<channel>
	<title>Comments on: The Auditor&#8217;s Prerogative</title>
	<atom:link href="http://www.securitycatalyst.com/the-auditors-prerogative/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.securitycatalyst.com/the-auditors-prerogative/</link>
	<description>Michael Santarcangelo delivers Awareness that Works™</description>
	<lastBuildDate>Wed, 01 Sep 2010 14:21:57 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Jeff Kirsch</title>
		<link>http://www.securitycatalyst.com/the-auditors-prerogative/comment-page-1/#comment-2651</link>
		<dc:creator>Jeff Kirsch</dc:creator>
		<pubDate>Sat, 22 Aug 2009 04:11:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.securitycatalyst.com/?p=2135#comment-2651</guid>
		<description>I am glad to see some discussion around this topic. To answer the question of if this was a satire, the simple answer is yes, I indicated this in the closing paragraph. As I attempted to layout in the Retrospective portion of this article, I do not believe people lie to me nor do I utilize &quot;defensive auditing&quot; techniques. I completely agree with you, Micheal Starks, that credibility is a cornerstone to being an effective auditor. To maintain that credibility we need to act in a professional manner, but we also need to explain our intentions and value to those we audit. I think Micheal Janke makes a good point about both sides learning from the other. The transfer of knowledge between both sides improves the quality of future audits and gives the auditee a better understanding of the overall control environment. 

Chris, I believe you have misunderstood my position. I do not feel auditor&#039;s perform their testing simply to find what is wrong, instead I feel an auditor tries to meet the objectives of their engagement. In the process of conducting procedures to  ensure controls are in place and operating effectively an auditor may find the controls do not meet the control objectives. After performing their due diligence in determining if a control failure effects the overall effectiveness of a system, they must report their findings.

After throwing out all that technical analysis I would say this, both parties to an audit should openly discuss what the objectives are and keep communications open throughout. Hopefully this helps build value for all parties involved.</description>
		<content:encoded><![CDATA[<p>I am glad to see some discussion around this topic. To answer the question of if this was a satire, the simple answer is yes, I indicated this in the closing paragraph. As I attempted to layout in the Retrospective portion of this article, I do not believe people lie to me nor do I utilize &#8220;defensive auditing&#8221; techniques. I completely agree with you, Micheal Starks, that credibility is a cornerstone to being an effective auditor. To maintain that credibility we need to act in a professional manner, but we also need to explain our intentions and value to those we audit. I think Micheal Janke makes a good point about both sides learning from the other. The transfer of knowledge between both sides improves the quality of future audits and gives the auditee a better understanding of the overall control environment. </p>
<p>Chris, I believe you have misunderstood my position. I do not feel auditor&#8217;s perform their testing simply to find what is wrong, instead I feel an auditor tries to meet the objectives of their engagement. In the process of conducting procedures to  ensure controls are in place and operating effectively an auditor may find the controls do not meet the control objectives. After performing their due diligence in determining if a control failure effects the overall effectiveness of a system, they must report their findings.</p>
<p>After throwing out all that technical analysis I would say this, both parties to an audit should openly discuss what the objectives are and keep communications open throughout. Hopefully this helps build value for all parties involved.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Griffin</title>
		<link>http://www.securitycatalyst.com/the-auditors-prerogative/comment-page-1/#comment-2636</link>
		<dc:creator>Chris Griffin</dc:creator>
		<pubDate>Wed, 19 Aug 2009 14:31:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.securitycatalyst.com/?p=2135#comment-2636</guid>
		<description>I agree with you that auditors do look for where people screwed up and not help improve controls. 
But I dont think that is how it should be. We have worked ourselves into this compliance box
where real security doesnt matter. 

With the attitude of just looking for screw up&#039;s, then your not really helping them, or the security world.
We need to be thinking about how to make things better. By looking for flaws without concern for helping, that is only breeding more and more compliance based thinking. And it is hindering true security based thinking. 

Most of us can realize just because its in a regulation, does not mean its good for security. It&#039;s usually
just good for the vendors that fill that void by making the regulation solutions based.

Just wanted to throw my 2 cents in.</description>
		<content:encoded><![CDATA[<p>I agree with you that auditors do look for where people screwed up and not help improve controls.<br />
But I dont think that is how it should be. We have worked ourselves into this compliance box<br />
where real security doesnt matter. </p>
<p>With the attitude of just looking for screw up&#8217;s, then your not really helping them, or the security world.<br />
We need to be thinking about how to make things better. By looking for flaws without concern for helping, that is only breeding more and more compliance based thinking. And it is hindering true security based thinking. </p>
<p>Most of us can realize just because its in a regulation, does not mean its good for security. It&#8217;s usually<br />
just good for the vendors that fill that void by making the regulation solutions based.</p>
<p>Just wanted to throw my 2 cents in.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Starks</title>
		<link>http://www.securitycatalyst.com/the-auditors-prerogative/comment-page-1/#comment-2630</link>
		<dc:creator>Michael Starks</dc:creator>
		<pubDate>Mon, 17 Aug 2009 15:07:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.securitycatalyst.com/?p=2135#comment-2630</guid>
		<description>I&#039;m not sure how much to read into this, but I think you may have lost some perspective. Yes, people will certainly be less-than-honest and not as forthcoming as you would like. But as an auditor, it is your job to focus on the evidence and verifiable facts. Are you serious when you say:

&quot;So I’ve come to the conclusion that the best thing to do when asked questions is to lie right back.&quot;

I really hope that was satirical. The profession needs to maintain credibility with auditees if the process is to be beneficial for both parties.

I am left with the feeling that perhaps I didn&#039;t get the underlying message of the post, because I can&#039;t imagine this would really be the way you conduct yourself.</description>
		<content:encoded><![CDATA[<p>I&#8217;m not sure how much to read into this, but I think you may have lost some perspective. Yes, people will certainly be less-than-honest and not as forthcoming as you would like. But as an auditor, it is your job to focus on the evidence and verifiable facts. Are you serious when you say:</p>
<p>&#8220;So I’ve come to the conclusion that the best thing to do when asked questions is to lie right back.&#8221;</p>
<p>I really hope that was satirical. The profession needs to maintain credibility with auditees if the process is to be beneficial for both parties.</p>
<p>I am left with the feeling that perhaps I didn&#8217;t get the underlying message of the post, because I can&#8217;t imagine this would really be the way you conduct yourself.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Network Security Blog &#187; Thursday night PCI articles</title>
		<link>http://www.securitycatalyst.com/the-auditors-prerogative/comment-page-1/#comment-2624</link>
		<dc:creator>Network Security Blog &#187; Thursday night PCI articles</dc:creator>
		<pubDate>Fri, 14 Aug 2009 04:45:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.securitycatalyst.com/?p=2135#comment-2624</guid>
		<description>[...] The Auditor&#8217;s Prerogative &#8211; No network is so squeeky clean a decent assessor can&#8217;t find at least one mistake.&#160; But that doesn&#8217;t mean the assesor is the enemy. [...]</description>
		<content:encoded><![CDATA[<p>[...] The Auditor&#8217;s Prerogative &#8211; No network is so squeeky clean a decent assessor can&#8217;t find at least one mistake.&nbsp; But that doesn&#8217;t mean the assesor is the enemy. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Janke</title>
		<link>http://www.securitycatalyst.com/the-auditors-prerogative/comment-page-1/#comment-2623</link>
		<dc:creator>Michael Janke</dc:creator>
		<pubDate>Fri, 14 Aug 2009 01:00:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.securitycatalyst.com/?p=2135#comment-2623</guid>
		<description>I&#039;ve been audited by some pretty competent auditors - the kind that can SQL inject an app and rootkit a server, so I&#039;ve been part of some pretty intense audits. I&#039;ve always treated the audit as a learning experience (for me) and an opportunity to nudge upper management in a positive direction. 

If I&#039;ve got a weak area, I&#039;ll admit it. If I&#039;ve got stuff that works pretty good, I&#039;ll let them know. But I figure it doesn&#039;t pay to BS them. If they are good, they&#039;ll know, and if they are incompetent, I will not learn anything from the audit. Learning from *good* auditors is a good thing. 

The stakes are high though. In my case, the findings are public and if they are bad, they&#039;ll make the local news. 

--Mike</description>
		<content:encoded><![CDATA[<p>I&#8217;ve been audited by some pretty competent auditors &#8211; the kind that can SQL inject an app and rootkit a server, so I&#8217;ve been part of some pretty intense audits. I&#8217;ve always treated the audit as a learning experience (for me) and an opportunity to nudge upper management in a positive direction. </p>
<p>If I&#8217;ve got a weak area, I&#8217;ll admit it. If I&#8217;ve got stuff that works pretty good, I&#8217;ll let them know. But I figure it doesn&#8217;t pay to BS them. If they are good, they&#8217;ll know, and if they are incompetent, I will not learn anything from the audit. Learning from *good* auditors is a good thing. </p>
<p>The stakes are high though. In my case, the findings are public and if they are bad, they&#8217;ll make the local news. </p>
<p>&#8211;Mike</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Interesting Information Security Bits for 08/13/2009 &#124; Infosec Ramblings</title>
		<link>http://www.securitycatalyst.com/the-auditors-prerogative/comment-page-1/#comment-2620</link>
		<dc:creator>Interesting Information Security Bits for 08/13/2009 &#124; Infosec Ramblings</dc:creator>
		<pubDate>Thu, 13 Aug 2009 20:59:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.securitycatalyst.com/?p=2135#comment-2620</guid>
		<description>[...] tells it like it is! Actually, he does, but read the whole article to know what I mean. The Auditor&#8217;s Prerogative : The Security Catalyst Tags: ( audit [...]</description>
		<content:encoded><![CDATA[<p>[...] tells it like it is! Actually, he does, but read the whole article to know what I mean. The Auditor&#8217;s Prerogative : The Security Catalyst Tags: ( audit [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Security Briefing &#8211; August 13th : Liquidmatrix Security Digest</title>
		<link>http://www.securitycatalyst.com/the-auditors-prerogative/comment-page-1/#comment-2619</link>
		<dc:creator>Security Briefing &#8211; August 13th : Liquidmatrix Security Digest</dc:creator>
		<pubDate>Thu, 13 Aug 2009 19:54:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.securitycatalyst.com/?p=2135#comment-2619</guid>
		<description>[...] The Auditors Prerogative &#8211; Security Catalyst [...]</description>
		<content:encoded><![CDATA[<p>[...] The Auditors Prerogative &#8211; Security Catalyst [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
