<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Immutability in Exchange</title><link>http://blogs.technet.com/b/perryclarke/archive/2012/02/03/immutability-in-exchange.aspx</link><description>In this video we spend some time talking about an aspect of our archiving and compliance story for Exchange on-premises and the service. Specifically, if you do decide to take advantage of the simplicity and lower costs of co-locating your &amp;lsquo;archive&amp;rsquo;</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: Immutability in Exchange</title><link>http://blogs.technet.com/b/perryclarke/archive/2012/02/03/immutability-in-exchange.aspx#3515680</link><pubDate>Wed, 22 Aug 2012 17:11:03 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3515680</guid><dc:creator>Ankur Kothari MSFT</dc:creator><description>&lt;p&gt;@Carl &lt;/p&gt;
&lt;p&gt;PST Capture is limited to 1000 users today only for Exchange Online, not for on-premises. We will take the feedback for Online though - thank you.&lt;/p&gt;
&lt;p&gt;Ankur&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3515680" width="1" height="1"&gt;</description></item><item><title>re: Immutability in Exchange</title><link>http://blogs.technet.com/b/perryclarke/archive/2012/02/03/immutability-in-exchange.aspx#3515604</link><pubDate>Wed, 22 Aug 2012 07:54:44 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3515604</guid><dc:creator>Carl</dc:creator><description>&lt;p&gt;Hi Perry, PST capture is not overly helpful given its got a 1000 limit cap! Does pose some challenges to large orgs. Any thoughts on this?&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3515604" width="1" height="1"&gt;</description></item><item><title>re: Immutability in Exchange</title><link>http://blogs.technet.com/b/perryclarke/archive/2012/02/03/immutability-in-exchange.aspx#3494184</link><pubDate>Tue, 24 Apr 2012 21:10:57 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3494184</guid><dc:creator>Ankur Kothari MSFT</dc:creator><description>&lt;p&gt;The statement at the end of the paragraph you quoted is the part I would like to hold onto. Exchange does not create a fingerprint to notify you that the data was there. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;Using a fingerprint/finger analogy:&lt;/p&gt;
&lt;p&gt;If the item is &amp;quot;deleted&amp;quot; by a user, the finger (not fingerprint) is retained without modifying the integrity of the message.&lt;/p&gt;
&lt;p&gt;If the item is changed, the original finger is retained, and a second finger is created with the new modified data. &amp;nbsp;(What we call copy-on-write).&lt;/p&gt;
&lt;p&gt;At the same time, we also provide the finger print for all access (auditing). &amp;nbsp;&lt;/p&gt;
&lt;p&gt;there is another portion where it states that &amp;quot;do not prevent the a record from being changed or deleted&amp;quot; - Exchange nevers alter the item. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;Ankur&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3494184" width="1" height="1"&gt;</description></item><item><title>re: Immutability in Exchange</title><link>http://blogs.technet.com/b/perryclarke/archive/2012/02/03/immutability-in-exchange.aspx#3494121</link><pubDate>Tue, 24 Apr 2012 17:43:07 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3494121</guid><dc:creator>Paul</dc:creator><description>&lt;p&gt;Hello Ankur and Perry,&lt;/p&gt;
&lt;p&gt;Just checking in again to see if you agree that Microsoft does or does not comply with SEC 17a-4 as listed in the SEC interpretation above?&lt;/p&gt;
&lt;p&gt;Thanks,&lt;/p&gt;
&lt;p&gt;Paul&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3494121" width="1" height="1"&gt;</description></item><item><title>re: Immutability in Exchange</title><link>http://blogs.technet.com/b/perryclarke/archive/2012/02/03/immutability-in-exchange.aspx#3492030</link><pubDate>Fri, 13 Apr 2012 14:32:54 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3492030</guid><dc:creator>Paul</dc:creator><description>&lt;p&gt;Thank you Ankur! &amp;nbsp;I appreciate the follow up. &amp;nbsp;Sorry to continue pressing the point but there is the potential for significant architecture simplification if Microsoft guarantees compliance to the SEC rulings. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;The SEC has an article titled the &amp;quot;Interpretation of Electronic Storage of Broker-Dealer Records&amp;quot; at the following link.&lt;/p&gt;
&lt;p&gt;&lt;a rel="nofollow" target="_new" href="http://www.sec.gov/rules/interp/34-47806.htm"&gt;www.sec.gov/.../34-47806.htm&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Your comments are in line with what broker-dealers and vendors have asked for but the Commission&amp;#39;s interpretation towards the middle of the 3rd page makes me uneasy:&lt;/p&gt;
&lt;p&gt;&amp;quot;The Commission&amp;#39;s interpretation does not include storage systems that only mitigate the risk a record will be overwritten or erased. Such systems - which may use software applications to protect electronic records, such as authentication and approval policies, passwords or other extrinsic security controls - do not maintain the records in a manner that is non-rewriteable and non-erasable. The external measures used by these other systems do not prevent a record from being changed or deleted. For example, they might limit access to records through the use of passwords. Additionally, they might create a &amp;quot;finger print&amp;quot; of the record based on its content. If the record is changed, the fingerprint will indicate that it was altered (but the original record would not be preserved). The ability to overwrite or erase records stored on these systems makes them non-compliant with Rule 17a-4(f).&amp;quot;&lt;/p&gt;
&lt;p&gt;I go back and forth on what this means and how it applies to Exchange 2010.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3492030" width="1" height="1"&gt;</description></item><item><title>re: Immutability in Exchange</title><link>http://blogs.technet.com/b/perryclarke/archive/2012/02/03/immutability-in-exchange.aspx#3491894</link><pubDate>Thu, 12 Apr 2012 23:01:42 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3491894</guid><dc:creator>Ankur Kothari MSFT</dc:creator><description>&lt;p&gt;err - the above was for Paul, not Perry.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3491894" width="1" height="1"&gt;</description></item><item><title>re: Immutability in Exchange</title><link>http://blogs.technet.com/b/perryclarke/archive/2012/02/03/immutability-in-exchange.aspx#3491893</link><pubDate>Thu, 12 Apr 2012 23:01:18 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3491893</guid><dc:creator>Ankur Kothari MSFT</dc:creator><description>&lt;p&gt;Perry,&lt;/p&gt;
&lt;p&gt;Section iii states the following: &amp;quot;Broker-dealers and vendors of electronic record storage systems have asked whether broker-dealers may use, consistent with Rule 17a-4(f), systems they describe as storing records in a manner that prevents the records from being overwritten, erased or otherwise altered without relying solely on the system&amp;#39;s hardware features. Specifically, these systems use integrated hardware and&lt;/p&gt;
&lt;p&gt;software codes that are intrinsic to the system to prevent the overwriting, erasure or alteration of the records. Thus, while the hardware storage medium used by these systems (e.g., magnetic disk) is inherently rewriteable, the integrated codes intrinsic to the system prevent anyone from overwriting the records.&amp;quot;&lt;/p&gt;
&lt;p&gt;By using legal hold or rolling hold, you are using such software based codes. &amp;nbsp;&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3491893" width="1" height="1"&gt;</description></item><item><title>re: Immutability in Exchange</title><link>http://blogs.technet.com/b/perryclarke/archive/2012/02/03/immutability-in-exchange.aspx#3491769</link><pubDate>Thu, 12 Apr 2012 13:59:13 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3491769</guid><dc:creator>Paul</dc:creator><description>&lt;p&gt;To be clear. &amp;nbsp;Are you saying that Microsoft Exchange 2010 meets industry regulations, specifically SEC 17a-4(f)(2)(ii)(A) that states that the electronic storage media must preserve records exclusively in a non-re-writeable, non-erasable format?&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3491769" width="1" height="1"&gt;</description></item><item><title>re: Immutability in Exchange</title><link>http://blogs.technet.com/b/perryclarke/archive/2012/02/03/immutability-in-exchange.aspx#3483052</link><pubDate>Fri, 24 Feb 2012 18:39:23 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3483052</guid><dc:creator>Ask Perry</dc:creator><description>&lt;p&gt;Thanks for your interest in the topic @Charles&lt;/p&gt;
&lt;p&gt;@Michael -- Yes, we have the same features available in Exchange Online.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3483052" width="1" height="1"&gt;</description></item><item><title>re: Immutability in Exchange</title><link>http://blogs.technet.com/b/perryclarke/archive/2012/02/03/immutability-in-exchange.aspx#3482701</link><pubDate>Thu, 23 Feb 2012 07:05:36 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3482701</guid><dc:creator>Michael</dc:creator><description>&lt;p&gt;Can I achieve the same using Exchange Online?&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3482701" width="1" height="1"&gt;</description></item></channel></rss>