<?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"
	>

<channel>
	<title>edgeblog &#187; Compliance</title>
	<atom:link href="http://www.edgeblog.net/category/compliance/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.edgeblog.net</link>
	<description>Notes from the edge</description>
	<pubDate>Wed, 13 Aug 2008 05:18:56 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
	<language>en</language>
			<item>
		<title>OFAC Compliance, the Easy Way</title>
		<link>http://www.edgeblog.net/2006/ofac/</link>
		<comments>http://www.edgeblog.net/2006/ofac/#comments</comments>
		<pubDate>Thu, 14 Dec 2006 13:30:15 +0000</pubDate>
		<dc:creator>bill</dc:creator>
		
		<category><![CDATA[Compliance]]></category>

		<category><![CDATA[Security]]></category>

		<guid isPermaLink="false">http://www.edgeblog.net/2006/ofac/</guid>
		<description><![CDATA[     <link rel="alternate" type="application/atom+xml" title="edgeblog Category: Compliance" href="http://www.edgeblog.net/category/compliance/feed/" />
     <link rel="alternate" type="application/atom+xml" title="edgeblog Category: Security" href="http://www.edgeblog.net/category/security/feed/" />
<p><font face="Arial" size="2"><img id="image67" title="treas_logo.gif" alt="treas_logo.gif" src="http://www.edgeblog.net/wp-content/uploads/2006/12/treas_logo.thumbnail.gif" align="left" />Occasionally, I find a simple solution to a complex problem that works better than expected. <a href="http://www.treas.gov/offices/enforcement/ofac/programs/terror/terror.shtml" target="_blank">Office of Foreign Assets Control (OFAC)</a> compliance can be difficult. OFAC is the treasury department responsible for, among other things, enforcing the PATRIOT ACT and <a href="http://www.treas.gov/offices/enforcement/ofac/programs/terror/terror.pdf" target="_blank">Terrorism Sanction Regulations</a> regarding blocking financial transactions with suspected terrorists. Basically, OFAC requires you to compare your client list regularly to the published terrorist watch lists. If you find a match, you are required to stop doing business, freeze the money, and contact the Feds. </font></p>
<p><font face="Arial" size="2">The hard part of OFAC compliance is matching your clients to the watch list. OFAC publishes a list on a regular basis, but the list is not exactly user friendly. Complicating matters is the fact that the list contains lots of Mohammeds, Usamas, and John Smiths. Most names on the list also have dozens of aliases. Obviously, not everyone named Mohammed doing business with you is a terrorist, so how do you distinguish the good from the bad?<!--more--></font></p>
<p><font face="Arial" size="2">Enter <a href="http://www.bridgerinsight.choicepoint.com/" target="_blank">Bridger Insight</a> from ChoicePoint. For about $6K per year, Bridger provides a simple software solution that lets you track your customers against the OFAC list, the Dept of Homeland Security Terrorist Watch List, the FBI Most Wanted List, and numerous international lists from the UK, the UN and Interpol. Bridger matches your customers based upon name, company name, address, phone number, social security #, driver&#8217;s license #, passport #, and account #s. The power of the Bridger match is that it creates a ranked score. You can filter your results down, based on a degree of sensitivity to reduce false-positives. </font></p>
<p><font face="Arial" size="2">For example, if the list matches your customer named Paddy O&#8217;Leary to a Paddy O&#8217;Leary in Dublin, Ireland, but your customer lives in Dublin, California, the match might score an 85% probability. If you have set your filter to 90% probability, Bridger would filter the match from you. Bridger also allows you to flag false-positives that you have verified as false to an exception list. That way, you won&#8217;t be bothered with the same alert the next time you run your check. </font></p>
<p><font face="Arial" size="2">Perhaps the best part of Bridger is that you can set it up to run in a mostly automated state. Each of the different sources of watch lists updates at different frequencies. Bridger will check on a daily, or even hourly basis, for updates and install them automatically. You can also map Bridger to your customer list data source, and then schedule it to run checks on whatever frequency you want. All that is left to you is to periodically review the results and take action if you think you&#8217;ve found a match.</font></p>
<p><font face="Arial" size="2">OFAC applies to &#8220;All U.S. persons and entities (companies, non-profit groups, government agencies, etc.) wherever located,&#8221; so you can not simply ignore this compliance issue. For smaller companies that don&#8217;t deal much with foreign customers, the risk of non-compliance is fairly small. For larger companies, especially financial firms, OFAC compliance is not optional. If you do not already have a solution in place, Bridger may be the solution for you.</font></p>
<p><font face="Arial" size="2">-Bill</font></p>
]]></description>
		<wfw:commentRss>http://www.edgeblog.net/2006/ofac/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Supreme Court Releases New E-Discovery Rules</title>
		<link>http://www.edgeblog.net/2006/supreme-court-releases-new-e-discovery-rules/</link>
		<comments>http://www.edgeblog.net/2006/supreme-court-releases-new-e-discovery-rules/#comments</comments>
		<pubDate>Sat, 02 Dec 2006 08:35:41 +0000</pubDate>
		<dc:creator>bill</dc:creator>
		
		<category><![CDATA[Compliance]]></category>

		<guid isPermaLink="false">http://www.edgeblog.net/2006/supreme-court-releases-new-e-discovery-rules/</guid>
		<description><![CDATA[<p><img id="image7" title="blog.jpg" alt="blog.jpg" src="http://www.edgeblog.net/wp-content/uploads/2006/10/blog.thumbnail.jpg" align="left" /></p>
<p>In case you missed the news, today new Supreme Court rules went into effect regarding e-discovery. There were several good articles on the wires today: <a href="http://news.yahoo.com/s/cmp/20061202/tc_cmp/195900034" target="_blank">Yahoo</a>; <a href="http://www.washingtonpost.com/wp-dyn/content/article/2006/12/01/AR2006120100567.html" target="_blank">Washington Post</a>; <a href="http://biz.yahoo.com/ibd/061201/general.html?.v=1" target="_blank">Investor&#8217;s Business Daily</a>.</p>
<p>The problem with all these articles is that they don&#8217;t provide links to the actual rules published by the court. Since I have no life, I searched the Supreme Court&#8217;s website for the published rules. The new rules (<a href="http://www.supremecourtus.gov/orders/courtorders/frcv06p.pdf" target="_blank">http://www.supremecourtus.gov/orders/courtorders/frcv06p.pdf</a>) were released by the Supremes last April. Based on my reading, there is both good and bad news in the rules with regards to e-discovery.</p>
<p>(<em>Legal Disclaimer: I am not a lawyer; Do not rely upon my opinions; When in doubt hire a real lawyer and make sure he&#8217;s a good one; I am not responsible if you rely upon my analysis</em>.)<!--more--></p>
<div>The good news is contained in Rules 26(b)(2)(B) &#038; 37(f):</div>
<div id="code">Rule 26 (b)(2)(B) &#8220;A party need not provide discovery of electronically stored information from sources that the party identifies as not reasonably accessible because of undue burden or cost. On motion to compel discovery or for a protective order, the party from whom discovery is sought must show that the information is not reasonably accessible because of undue burden or cost. If that showing is made, the court may nonetheless order discovery from such sources if the requesting party shows good cause…&#8221;                </p>
<p>Rule 37 (f) &#8220;Absent exceptional circumstances, a court may not impose sanctions under these rules on a party for failing to provide electronically stored information lost as a result of the routine, good-faith operation of an electronic information system.&#8221;</p></div>
<p>These rules are good for two reasons:</p>
<p>First, there is now a potential release from e-discovery based upon &#8220;undue burden or cost.&#8221; As an example, if a company can show that it would be prohibitively expensive to search every pc in the company for a document that the other party suspects exists, but has no proof, this rule allows for the potential to have this request waived. Of course, if the requester can &#8220;show good cause,&#8221; the court can still order the discovery, but at least this rule provides a potential cost exclusion where it did not exist before.</p>
<p>Second, sanctions cannot be imposed for &#8220;information lost as a result of the routine, good-faith operation&#8230;&#8221; So if a company stores its archive tapes at a secure off-site storage facility, and that facility burns down, the loss of those tapes will not trigger court sanctions. This is a big change, but the key provision is &#8220;good-faith operation.&#8221; A company that doesn&#8217;t backup its data, or store it in a manner consistent with its data retention obligations is not operating in good-faith and could still be subject to sanctions if the data is not produce-able.</p>
<div>The bad news is contained in Rule 34 (a):</div>
<div id="code">Rule 34 (a) Any party may serve on any other party a request (1) to produce and permit the party making the request, or someone acting on the requestor’s behalf, to inspect, copy, test, or sample any designated documents or electronically stored information — including writings, drawings, graphs, charts, photographs, sound recordings, images, and other data or data compilations stored in any medium from which information can be obtained — translated, if necessary, by the respondent into reasonably usable form, or to inspect, copy, test, or sample any designated tangible things which constitute or contain matters within the scope of Rule 26(b) and which are in the possession, custody or control of the party upon whom the request is served…</div>
<p>Rule 34 (a) expands the types of electronic data to include sound recordings, images, and other &#8220;data compilations.&#8221; This is being interpreted in the press to include things like instant messaging and text messages on cell phones and Blackberrys. If you have a VOIP system that integrates your voice mail system with your e-mail system, such as <a href="http://www.cisco.com/en/US/products/sw/voicesw/ps2237/index.html" target="_blank">Cisco&#8217;s UNITY</a> product, be prepared for your voice mail messages to become discoverable.</p>
<p>Rule 34 (a) also specifies data &#8220;stored in any medium from which information can be obtained.&#8221; This would appear to include cell phones, PDAs, and USB flash drives. Not withstanding the cost exclusion of Rule 26 (b)(2)(B), companies have an expanded duty to track where their data is stored, and how it is maintained.</p>
<p>Last September, I published a <a title="E-Discovery Compliant Archive System" href="http://www.edgeblog.net/2006/e-mail-retention-sarbanes-oxley-white-paper/">white-paper</a> regarding designing an e-mail archive system for compliance. The topics discussed in that article are even more important under the new rules. To meet obligations under these new rules, companies must act in &#8220;good-faith&#8221; to identify their electronic data, establish policies regarding the storage and retention of their data, and then design systems to enforce the retention policies. Also, if you work for a public company, pay close attention to <a href="http://www.sox-online.com/act_section_802.html" target="_blank">Sarbanes-Oxley section 802</a>. SOX 802 crimializes the destruction of business documents.</p>
<p>The new Supreme Court rules apply to all companies involved in Federal litigation. Unfortunately, if you wait until you are involved in litigation, it is too late. You must prepare for these rules before they apply.</p>
<p>-Bill</p>
<p><img height="16" alt="Digg!" src="http://digg.com/img/badges/16x16-digg-guy.gif" width="16" /> <a href="http://www.digg.com/security/New_Court_Rules_Allow_Companies_to_Subpoena_Cell_Phones_PDAs_IMs">Digg This Story!</a></p>
]]></description>
		<wfw:commentRss>http://www.edgeblog.net/2006/supreme-court-releases-new-e-discovery-rules/feed/</wfw:commentRss>
		</item>
		<item>
		<title>E-Mail Retention &#038; Sarbanes-Oxley White Paper</title>
		<link>http://www.edgeblog.net/2006/e-mail-retention-sarbanes-oxley-white-paper/</link>
		<comments>http://www.edgeblog.net/2006/e-mail-retention-sarbanes-oxley-white-paper/#comments</comments>
		<pubDate>Fri, 29 Sep 2006 07:01:11 +0000</pubDate>
		<dc:creator>bill</dc:creator>
		
		<category><![CDATA[Compliance]]></category>

		<category><![CDATA[Popular]]></category>

		<guid isPermaLink="false">http://www.edgebacklabs.net/2006/8/</guid>
		<description><![CDATA[<p><img id="image7" title="blog.jpg" alt="blog.jpg" src="http://www.edgeblog.net/wp-content/uploads/2006/10/blog.thumbnail.jpg" align="left" />I wrote <a onmousedown="selectLink(6);" id="p6" href="http://www.edgebacklabs.net/wp-content/uploads/2006/10/email_retention.pdf">this paper</a> last year on document retention &#038; compliance with regard to e-mail systems. Sarbanes-Oxley <a href="http://www.sox-online.com/act_section_802.html">section 802</a> has created a small nightmare for IT managers, and there is precious little information for what 802 really means. I wrote this paper as a guide for designing a system that would satisfy the worst case scenario. SOX 802 carries big financial penalties as well as jail time for company officers. If you are an IT manager of a public company, this paper will serve as a good starting point. It is written with a vendor neutral approach.</p>
<p>If you are looking for a compliance solution for e-mail, I highly recommend Hewlett-Packard&#8217;s <a href="http://h18006.www1.hp.com/storage/archivalstorage.html">RISS/RIM</a> product suite. Symantec&#8217;s <a href="http://www.symantec.com/Products/enterprise?c=prodinfo&#038;refId=322&#038;cid=1018">Enterprise Vault</a> is also a good product, although in my experience it does not scale well beyond 1 data center. If you find this paper useful, drop me a comment and let me know how you are dealing with e-mail &#038; SOX.<br />
<a href="http://www.edgeblog.net/wp-content/uploads/2006/10/email_retention.pdf" target="_blank">«download here»</a></p>
<p><img height="16" alt="Digg!" src="http://digg.com/img/badges/16x16-digg-guy.gif" width="16" /> <a href="http://www.digg.com/security/E_Mail_Retention_Sarbanes_Oxley_White_Paper">Digg This Story!</a></p>
]]></description>
		<wfw:commentRss>http://www.edgeblog.net/2006/e-mail-retention-sarbanes-oxley-white-paper/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.465 seconds -->
