 




<?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>Email Archiving &#38; Compliance Blog &#187; finra record retention rules</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/email-archiving-compliance/tag/finra-record-retention-rules/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/email-archiving-compliance</link>
	<description></description>
	<lastBuildDate>Mon, 25 Feb 2013 20:48:39 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>FINRA Email Archiving Requirements</title>
		<link>http://itknowledgeexchange.techtarget.com/email-archiving-compliance/finra-email-archiving-requirements/</link>
		<comments>http://itknowledgeexchange.techtarget.com/email-archiving-compliance/finra-email-archiving-requirements/#comments</comments>
		<pubDate>Fri, 11 Nov 2011 19:19:46 +0000</pubDate>
		<dc:creator>Naplesguy</dc:creator>
				<category><![CDATA[broker dealer compliance]]></category>
		<category><![CDATA[email archiving requirements]]></category>
		<category><![CDATA[finra record retention rules]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/email-archiving-compliance/?p=21</guid>
		<description><![CDATA[Email archiving is a common requirement for many different types of industries. When it comes to broker dealer compliance, FINRA is the regulator for this particular financial industry. And the email archiving requirements that FINRA has in place are very specific. Let&#8217;s look at some of the FINRA record retention rules in detail: FINRA 3010 [...]]]></description>
				<content:encoded><![CDATA[<p>Email archiving is a common requirement for many different types of industries. When it comes to <a href="http://www.smarsh.com/broker-dealers">broker dealer compliance</a>, FINRA is the regulator for this particular financial industry. And the email archiving requirements that FINRA has in place are very specific. Let&#8217;s look at some of the <a href="http://www.smarsh.com/broker-dealers">FINRA record retention rules</a> in detail:</p>
<p><strong>FINRA 3010 &#8211; Supervision of Sales Activities</strong>. This rule requires firms to maintain a system to supervise correspondence and transactions with their users. Included in this system are written procedures and the review of outgoing and incoming electronic correspondence on a regular basis.</p>
<p><strong>FINRA 3110 &#8211; Books &amp; Records</strong>. This rule requires members of firms to make and preserve accounts, records, memoranda, books and correspondence in conformity with all applicable regulations, statements, and rules under SEC 17a-3. Also, the record keeping medium, retention period and format must company with Rule 17a-4 under the Securities Exchange Act of 1934.</p>
<p><strong>SEC 17a-4 &#8211; Electronic Storage of Broker-Dealer Records</strong>. According to SEC 17a-4, broker-dealers must store required records in a non-rewriteable and non-erasable format. Therefore, the storage system used must be a system that prevents alteration or erasure of records for defined retention periods. WORM optical media (write once, read many) is commonly used in compliance with SEC 17a-4 and related regulation.</p>
<p>As you can see, FINRA record retention rules for email archiving are quite strict. In the end, it&#8217;s best for the member firm and regulator to have these records available.</p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/email-archiving-compliance/finra-email-archiving-requirements/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
