<?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: Auditors And ERPs &#8211; Can We Rest &#8220;Assured&#8221; ?</title>
	<atom:link href="http://retheauditors.com/2008/07/08/auditors-and-erps-can-we-rest-assured/feed/" rel="self" type="application/rss+xml" />
	<link>http://retheauditors.com/2008/07/08/auditors-and-erps-can-we-rest-assured/</link>
	<description>The Business of the Big 4 Audit Firms</description>
	<lastBuildDate>Tue, 22 May 2012 15:02:22 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: re: The Auditors &#187; Blog Archive &#187; Auditing Standard 5: How Now, Brown Cow?</title>
		<link>http://retheauditors.com/2008/07/08/auditors-and-erps-can-we-rest-assured/comment-page-1/#comment-70674</link>
		<dc:creator>re: The Auditors &#187; Blog Archive &#187; Auditing Standard 5: How Now, Brown Cow?</dc:creator>
		<pubDate>Tue, 29 Dec 2009 16:50:57 +0000</pubDate>
		<guid isPermaLink="false">http://76.12.174.187/?p=754#comment-70674</guid>
		<description>[...] challenges for the IT audit and risk teams within the audit [...]</description>
		<content:encoded><![CDATA[<p>[...] challenges for the IT audit and risk teams within the audit [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: keystonesandrivets</title>
		<link>http://retheauditors.com/2008/07/08/auditors-and-erps-can-we-rest-assured/comment-page-1/#comment-793</link>
		<dc:creator>keystonesandrivets</dc:creator>
		<pubDate>Thu, 28 Aug 2008 15:04:00 +0000</pubDate>
		<guid isPermaLink="false">http://76.12.174.187/?p=754#comment-793</guid>
		<description>Hi Francine,&lt;br/&gt;&lt;br/&gt;You and Dennis Howlett put together a great series of posts on this topic.&lt;br/&gt;&lt;br/&gt;In your ‘Links to this Post’ section there is a link my post “Auditing IT systems” where I discuss them and add my take:&lt;br/&gt;&lt;br/&gt;“To be able to accurately assess risk of IT system failure, three things need to be clearly understood and easily communicable:&lt;br/&gt;&lt;br/&gt;1.      Which IT assets or resources support a particular business process or service - allowing the question, “Which parts of the business will be directly affected should this IT System, or part thereof, fail?” to be answered.&lt;br/&gt;&lt;br/&gt;2.      The value of those business processes to the company operation - allowing the question “What would be the financial impact should an IT system, or component thereof, fail?” to be answered.&lt;br/&gt;&lt;br/&gt;3.      How data flows between the IT Systems that enable the business services to operate - which, critically, allows an assessment to be made of “Which parts of the business will be indirectly affected should this IT asset fail?” ”&lt;br/&gt;&lt;br/&gt;What do you think? Your feedback is very welcome.&lt;br/&gt;&lt;br/&gt;Regards,&lt;br/&gt;Paul Wallis</description>
		<content:encoded><![CDATA[<p>Hi Francine,</p>
<p>You and Dennis Howlett put together a great series of posts on this topic.</p>
<p>In your ‘Links to this Post’ section there is a link my post “Auditing IT systems” where I discuss them and add my take:</p>
<p>“To be able to accurately assess risk of IT system failure, three things need to be clearly understood and easily communicable:</p>
<p>1.      Which IT assets or resources support a particular business process or service &#8211; allowing the question, “Which parts of the business will be directly affected should this IT System, or part thereof, fail?” to be answered.</p>
<p>2.      The value of those business processes to the company operation &#8211; allowing the question “What would be the financial impact should an IT system, or component thereof, fail?” to be answered.</p>
<p>3.      How data flows between the IT Systems that enable the business services to operate &#8211; which, critically, allows an assessment to be made of “Which parts of the business will be indirectly affected should this IT asset fail?” ”</p>
<p>What do you think? Your feedback is very welcome.</p>
<p>Regards,<br />Paul Wallis</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Francine McKenna</title>
		<link>http://retheauditors.com/2008/07/08/auditors-and-erps-can-we-rest-assured/comment-page-1/#comment-708</link>
		<dc:creator>Francine McKenna</dc:creator>
		<pubDate>Wed, 09 Jul 2008 19:27:00 +0000</pubDate>
		<guid isPermaLink="false">http://76.12.174.187/?p=754#comment-708</guid>
		<description>@IJustWorkHere  Thanks much.  SAS 70 was just one area  around ERP risks, specifically related to growth of SaaS/cloud computing, that I wanted to mention, based on some recent conversations.  You raise several more really good ones.</description>
		<content:encoded><![CDATA[<p>@IJustWorkHere  Thanks much.  SAS 70 was just one area  around ERP risks, specifically related to growth of SaaS/cloud computing, that I wanted to mention, based on some recent conversations.  You raise several more really good ones.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://retheauditors.com/2008/07/08/auditors-and-erps-can-we-rest-assured/comment-page-1/#comment-707</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Wed, 09 Jul 2008 18:46:00 +0000</pubDate>
		<guid isPermaLink="false">http://76.12.174.187/?p=754#comment-707</guid>
		<description>The failure to map CLC&#039;s and not having a centralized list of all required SAS 70 reports are both common. As an external auditor I am not overly concerned about them though because we can perform our own mapping and identify all required SAS 70&#039;s with proper scoping and understanding of the clients systems. &lt;br/&gt;&lt;br/&gt;To me, the real risks are:&lt;br/&gt;1) Defining roles and responsibilities via access rights (SOD)&lt;br/&gt;2) Improperly configured software allowing application controls to be bypassed&lt;br/&gt;3) Push back from the client and the audit teams, forcing the IT Auditor to only do a cursory review of the ERP&lt;br/&gt;4) Failure to identify certain application controls as key&lt;br/&gt;5) Competency of client ERP admins.&lt;br/&gt;6) Competency of IT Auditors&lt;br/&gt;&lt;br/&gt;-IJustWorkHere</description>
		<content:encoded><![CDATA[<p>The failure to map CLC&#8217;s and not having a centralized list of all required SAS 70 reports are both common. As an external auditor I am not overly concerned about them though because we can perform our own mapping and identify all required SAS 70&#8217;s with proper scoping and understanding of the clients systems. </p>
<p>To me, the real risks are:<br />1) Defining roles and responsibilities via access rights (SOD)<br />2) Improperly configured software allowing application controls to be bypassed<br />3) Push back from the client and the audit teams, forcing the IT Auditor to only do a cursory review of the ERP<br />4) Failure to identify certain application controls as key<br />5) Competency of client ERP admins.<br />6) Competency of IT Auditors</p>
<p>-IJustWorkHere</p>
]]></content:encoded>
	</item>
</channel>
</rss>

