 




<?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>Regulatory Compliance, Governance and Security &#187; description of controls</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/compliance-governance/tag/description-of-controls/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/compliance-governance</link>
	<description></description>
	<lastBuildDate>Thu, 10 Mar 2011 15:04:50 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>SSAE 16 &#124; Description of the &#8220;System&#8221; &#124; What you Need to Know</title>
		<link>http://itknowledgeexchange.techtarget.com/compliance-governance/ssae-16-description-of-the-system-what-you-need-to-know/</link>
		<comments>http://itknowledgeexchange.techtarget.com/compliance-governance/ssae-16-description-of-the-system-what-you-need-to-know/#comments</comments>
		<pubDate>Wed, 17 Nov 2010 17:22:01 +0000</pubDate>
		<dc:creator>Charles Denyer</dc:creator>
				<category><![CDATA[charles denyer]]></category>
		<category><![CDATA[description of controls]]></category>
		<category><![CDATA[description of system]]></category>
		<category><![CDATA[ndb]]></category>
		<category><![CDATA[SAS 70]]></category>
		<category><![CDATA[SSAE 16]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/compliance-governance/?p=278</guid>
		<description><![CDATA[Enter SSAE 16 and it&#8217;s new requirement for service organizations to provide a description of its &#8220;system&#8221;. As for out with the old and in with the new, Statement on Auditing Standards No. 70, simply known as SAS 70 to all of us, required &#8220;only&#8221; a description of &#8220;controls&#8221;. I stress &#8220;only&#8221; because it has [...]]]></description>
				<content:encoded><![CDATA[<p>Enter <strong><a href="http://ssae16.org">SSAE 16</a></strong> and it&#8217;s new requirement for service organizations to provide a description of its <strong><a href="http://ssae16.org/index.php?option=com_content&amp;view=article&amp;id=14&amp;Itemid=14">&#8220;system&#8221;</a></strong>.  As for out with the old and in with the new, Statement on Auditing Standards No. 70, simply known as SAS 70 to all of us,  required &#8220;only&#8221; a description of &#8220;controls&#8221;.  I stress &#8220;only&#8221; because it has gradually being acknowledged by most professional auditors that the new SSAE 16 requirement of a description of one&#8217;s &#8220;system&#8221; is looked upon as more detailed, comprehensive, and far-reaching than that of the SAS 70 audit&#8217;s description of &#8220;controls&#8221;. </p>
<p>In fact, literature released by the AICPA in 2010 regarding the new SSAE 16 standard clearly illustrates and <strong><a href="http://ssae16.org/index.php?option=com_content&amp;view=article&amp;id=14&amp;Itemid=14">gives examples</a></strong> of what is considered subject matter for a description of a service organization&#8217;s &#8220;system&#8221;.  </p>
<p>Service organizations are going to have to re-visit their previous SAS 70 description of &#8220;controls&#8221; narrative, and possibly make significant changes to meet the true intent, rigor and spirit of the new SSAE 16 reporting requirements.  </p>
<p>My advice? Work with your auditor for ensuring your description of the &#8220;system&#8221; meets the requirements set by SSAE 16. </p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/compliance-governance/ssae-16-description-of-the-system-what-you-need-to-know/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
