<?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>EmailTide &#187; Compliance</title>
	<atom:link href="http://www.emailtide.com/category/compliance/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.emailtide.com</link>
	<description>Observations and insights on the challenges and risks of managing corporate email and IM.</description>
	<lastBuildDate>Tue, 04 Oct 2011 16:54:28 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Announcing Permessa Control! v6</title>
		<link>http://www.emailtide.com/2010/01/20/announcing-permessa-control-v6/</link>
		<comments>http://www.emailtide.com/2010/01/20/announcing-permessa-control-v6/#comments</comments>
		<pubDate>Wed, 20 Jan 2010 17:30:18 +0000</pubDate>
		<dc:creator>sm</dc:creator>
				<category><![CDATA[Compliance]]></category>
		<category><![CDATA[Email]]></category>
		<category><![CDATA[IBM Lotus]]></category>
		<category><![CDATA[Instant Messaging]]></category>
		<category><![CDATA[Lotusphere]]></category>
		<category><![CDATA[Permessa]]></category>
		<category><![CDATA[Permessa Control!]]></category>

		<guid isPermaLink="false">http://www.emailtide.com/?p=736</guid>
		<description><![CDATA[Kudos to our team here at Permessa. Everyone worked extra hard and many long hours over the last few weeks to get the newest release of Permessa Control! out the door just in time for Lotusphere. Permessa Control! v6 is the Most Comprehensive Monitoring, Reporting and Compliance Solution for IBM Lotus Domino and Lotus Sametime [...]]]></description>
			<content:encoded><![CDATA[<p>Kudos to our team here at Permessa. Everyone worked extra hard and many long hours over the last few weeks to get the newest release of Permessa Control! out the door just in time for Lotusphere.</p>
<p>Permessa Control! v6 is the Most Comprehensive Monitoring, Reporting and Compliance Solution for IBM Lotus Domino and Lotus Sametime available today.</p>
<blockquote><p><em>LOTUSPHERE, ORLANDO, FL. (<a title="Permessa Control! the Most  Comprehensive Monitoring, Reporting and Compliance Solution for IBM  Lotus Domino and Lotus Sametime" href="http://www.prweb.com/" target="_blank">PR WEB</a>) January 18, 2010 &#8211;  New  versions of the award-winning Permessa Control! products were announced  today by Permessa Corporation at Lotusphere in Orlando, Florida.  These  products enable enterprises to both lower costs and improve compliance  with their mission-critical messaging systems.  Permessa Email Control!  won the 2009 Lotus Award for Best Tool or Utility and was a finalist for  the prestigious 2009 IBM Beacon Award.  Permessa IM Control! was a  finalist for the 2009 Lotus Award for Best Collaboration product.</em></p></blockquote>
<p>See the full announcement <a title="Permessa Control! v6 is the Most Comprehensive Monitoring, Reporting and Compliance Solution for IBM Lotus Domino and Lotus Sametime" href="http://www.permessa.com/news/PR01182010" target="_blank">here</a>.</p>
<p><a class="a2a_dd a2a_target addtoany_share_save" href="http://www.addtoany.com/share_save#url=http%3A%2F%2Fwww.emailtide.com%2F2010%2F01%2F20%2Fannouncing-permessa-control-v6%2F&amp;title=Announcing%20Permessa%20Control%21%20v6" id="wpa2a_2">Share/Save</a></p>]]></content:encoded>
			<wfw:commentRss>http://www.emailtide.com/2010/01/20/announcing-permessa-control-v6/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Do-Not-Reply</title>
		<link>http://www.emailtide.com/2008/03/27/do-not-reply/</link>
		<comments>http://www.emailtide.com/2008/03/27/do-not-reply/#comments</comments>
		<pubDate>Thu, 27 Mar 2008 16:07:59 +0000</pubDate>
		<dc:creator>sm</dc:creator>
				<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[Compliance]]></category>
		<category><![CDATA[Email]]></category>
		<category><![CDATA[Risk Management]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[donotreply.com]]></category>
		<category><![CDATA[email risk]]></category>
		<category><![CDATA[mass-mailers]]></category>

		<guid isPermaLink="false">http://www.emailtide.com/2008/03/27/do-not-reply/</guid>
		<description><![CDATA[We all receive emails from automated services such as payment reminders, news alerts or other opt-in communications. The emails are computer-generated and the sender typically includes a notice asking the recipient not to reply to the message, since the sending account is not being monitored. Apparently, some companies go one step further and put an [...]]]></description>
			<content:encoded><![CDATA[<p>We all receive emails from automated services such as payment reminders, news alerts or other opt-in communications. The emails are computer-generated and the sender typically includes a notice asking the recipient not to reply to the message, since the sending account is not being monitored. Apparently, some companies go one step further and put an invalid return address in the message envelope.</p>
<p><span id="more-121"></span>No question, this is a bad practice.  All emails, auto-generated or not, should have a valid return address, not simply as a matter of customer courtesy, but also for other reasons.  As it turns out, many of these messages cannot be delivered to the intended recipient. People’s email addresses change, they forget to update their email notification preferences, and of course many anti-spam filters mislabel these messages as spam and block the delivery.</p>
<p>And here is where it gets interesting.<br />
Some of the geniuses in charge of these mail servers apparently use as the “fake” return address: some_address-at-donotreply-dot-com. <a href="http://www.donotreply.com/">DoNotReply.com</a> of course is a valid internet domain, registered thankfully to somebody with a sense of humor. Chet Faliszek maintains a blog that exposes the worst offenders.</p>
<p>What really got my attention is who’s made the list:</p>
<ul>
<li><a href="http://www.donotreply.com/index.php/2008/02/16/scary-week-ends-the-department-of-homeland-security/">The Department of Homeland Security</a></li>
<li><a href="http://www.donotreply.com/index.php/2008/02/14/merrill-lynch-bullish-on-privacy-and-security/">Merrill Lynch</a></li>
<li><a href="http://www.donotreply.com/index.php/2007/08/26/messagelabs-managing-their-clients-straight-to-me/">MessageLabs</a></li>
<li><a href="http://www.donotreply.com/index.php/2007/07/27/capitol-one-whats-in-your-bounced-email/">Capital One</a></li>
<li><a href="http://www.donotreply.com/index.php/2007/04/30/dear-verizon-wireless/">Verizon Wireless</a></li>
<li><a href="http://www.donotreply.com/index.php/2007/01/03/microsoft-funds-piracy/">Microsoft</a></li>
</ul>
<p>Besides the embarrassment, there is also great potential for legal liability for these companies, as some messages contained privileged information.</p>
<p>If you are in charge of messaging operations at your company, I would suggest reviewing the procedures for configuring auto-mailers. Here is what I recommend:</p>
<ul>
<li>Provide a valid return address to accept undeliverable messages.</li>
<li>Implement a process that checks this bounce mailbox and purges undeliverable email addresses from the auto-mailer after a certain count.</li>
<li>Include a real email address for customer support in the do-not-reply disclaimer in the body of the message to allow recipients to respond.</li>
<li>Include an unsubscribe link in the message.</li>
</ul>
<p>Technorati Tags: <a href="http://technorati.com/tag/donotreply.com" rel="tag">donotreply.com</a>, <a href="http://technorati.com/tag/email+risk" rel="tag"> email risk</a>, <a href="http://technorati.com/tag/mass-mailers" rel="tag"> mass-mailers</a></p>
<p><a class="a2a_dd a2a_target addtoany_share_save" href="http://www.addtoany.com/share_save#url=http%3A%2F%2Fwww.emailtide.com%2F2008%2F03%2F27%2Fdo-not-reply%2F&amp;title=Do-Not-Reply" id="wpa2a_4">Share/Save</a></p>]]></content:encoded>
			<wfw:commentRss>http://www.emailtide.com/2008/03/27/do-not-reply/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Red Sox won</title>
		<link>http://www.emailtide.com/2007/10/29/red-sox-won/</link>
		<comments>http://www.emailtide.com/2007/10/29/red-sox-won/#comments</comments>
		<pubDate>Mon, 29 Oct 2007 18:07:11 +0000</pubDate>
		<dc:creator>sm</dc:creator>
				<category><![CDATA[Compliance]]></category>
		<category><![CDATA[Email]]></category>
		<category><![CDATA[email liability]]></category>
		<category><![CDATA[hidden email cost]]></category>
		<category><![CDATA[personal email]]></category>

		<guid isPermaLink="false">http://www.emailtide.com/2007/10/29/red-sox-won/</guid>
		<description><![CDATA[That is probably an email subject that many of us have seen in our inbox this morning, announcing the conclusion of an exciting series for the team and all Red Sox fans. The chatter in the email ether will probably spike again today as fans now coordinate their own celebrations or make plans to attend [...]]]></description>
			<content:encoded><![CDATA[<p>That is probably an email subject that many of us have seen in our inbox this morning, announcing the conclusion of an exciting series for the team and all Red Sox fans. The chatter in the email ether will probably spike again today as fans now coordinate their own celebrations or make plans to attend the official team party in Boston later this week. The last few months have been amazing for Boston sports fans with the Patriots being on a tear as well, and now the Celtics are anticipating their best season in years.</p>
<p>What does this mean to your business? It is usually easy to tell in the morning who stayed up late to watch the end of last night&#8217;s game, and the media has covered the <a href="http://www.capecodonline.com/apps/pbcs.dll/article?AID=/20071026/NEWS/710260328">impact on worker productivity</a>.</p>
<p><span id="more-103"></span>Every company observes their seasonal and event-induced spikes in messaging traffic, which also affects productivity. What is not apparent is the hidden cost of that traffic.</p>
<p>Many firms are now archiving all emails due to current regulatory requirements, and the the cost of that non-business email is adding to the bill. Do you know how much personal email is circulating in your company’s network, and is your archiving solution smart enough to filter out those emails?</p>
<p>Perhaps this is something to think about when reevaluating your archiving solutions and corresponding budget.</p>
<p>Go Pats!</p>
<p>Technorati Tags: <a href="http://technorati.com/tag/personal+email" rel="tag">personal email</a>, <a href="http://technorati.com/tag/hidden+email+cost" rel="tag"> hidden email cost</a></p>
<p><a class="a2a_dd a2a_target addtoany_share_save" href="http://www.addtoany.com/share_save#url=http%3A%2F%2Fwww.emailtide.com%2F2007%2F10%2F29%2Fred-sox-won%2F&amp;title=Red%20Sox%20won" id="wpa2a_6">Share/Save</a></p>]]></content:encoded>
			<wfw:commentRss>http://www.emailtide.com/2007/10/29/red-sox-won/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Don’t shoot the messenger</title>
		<link>http://www.emailtide.com/2007/06/15/don%e2%80%99t-shoot-the-messenger/</link>
		<comments>http://www.emailtide.com/2007/06/15/don%e2%80%99t-shoot-the-messenger/#comments</comments>
		<pubDate>Fri, 15 Jun 2007 21:40:29 +0000</pubDate>
		<dc:creator>sm</dc:creator>
				<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[Compliance]]></category>
		<category><![CDATA[Email]]></category>
		<category><![CDATA[Instant Messaging]]></category>
		<category><![CDATA[Risk Management]]></category>

		<guid isPermaLink="false">http://www.emailtide.com/2007/06/15/don%e2%80%99t-shoot-the-messenger/</guid>
		<description><![CDATA[As if corporate IT departments don’t have enough to worry about, their staff is often on the receiving end of employee abuse. Most companies have clearly stated rules of proper business conduct documented in form of an employee manual or other written HR policy. The rules covering electronic communication typically spell out the terms of [...]]]></description>
			<content:encoded><![CDATA[<p>As if corporate IT departments don’t have enough to worry about, their staff is often on the receiving end of employee abuse. Most companies have clearly stated rules of proper business conduct documented in form of an employee manual or other written HR policy.</p>
<p>The rules covering electronic communication typically spell out the terms of use, appropriate and permissible content and usage limits or restrictions. These rules are driven by HR and business policy and more often follow specific regulatory and compliance requirements that must be monitored and enforced.</p>
<p><span id="more-59"></span>What is somewhat surprising is that the monitoring and enforcement function, in many cases, is the responsibility of corporate IT, often without being given the proper authority to act on violations. Michael Osterman of <a href="http://www.ostermanresearch.com/">Osterman Research</a> recently wrote about <a href="http://www.ostermanresearch.com/blog/2007/05/inappropriate-responses-to-policy.html">this issue in his blog</a>, quoting this particular incident:</p>
<blockquote><p><em>“One of the panelists in a session on content filtering and encryption told us about her experience when responding to someone who had violated a company policy on inappropriate content being sent through email. This panelist, a senior IT manager, reminded the individual about the corporate policy, to which the offender replied, &#8220;Bite Me!&#8221;. The individual who offered this less-than-appropriate response is no longer employed at that company.”</em></p></blockquote>
<p>Anybody who has ever worked in IT can probably relate and may recall similar encounters. The issues of contention surrounding email are plentiful:</p>
<ul>
<li>Exceeding of message size and mailbox storage quotas,</li>
<li>Emailing of inappropriate content,</li>
<li>Email overuse for personal purposes,</li>
<li>Illegal message forwarding, and</li>
<li>Other disruptive user activities.</li>
</ul>
<p>Companies are well advised to remove IT from the thankless role of the policy messenger. It leads to employee burnout and can create a hostile work environment.</p>
<p>Instead, regulatory and HR violations should be routed automatically to the appropriate business manager with the proper authority to enact on the rules.</p>
<p>The same applies to core IT policies such as quotas. Rather than having IT chase individual offenders, firms should implement technology solutions that can <a href="http://www.permessa.com/products_email_enforcer.php" title="Email CONTROL! Enforcer">automatically enforce IT policy </a>while offering alternatives that enable employees to get their work done.</p>
<p>Technorati Tags: <a href="http://technorati.com/tag/email+policy" rel="tag">email policy</a>, <a href="http://technorati.com/tag/best+practices" rel="tag"> best practices</a>, <a href="http://technorati.com/tag/osterman+research" rel="tag"> osterman research</a>, <a href="http://technorati.com/tag/inappropriate+conduct" rel="tag"> inappropriate conduct</a></p>
<p><a class="a2a_dd a2a_target addtoany_share_save" href="http://www.addtoany.com/share_save#url=http%3A%2F%2Fwww.emailtide.com%2F2007%2F06%2F15%2Fdon%25e2%2580%2599t-shoot-the-messenger%2F&amp;title=Don%E2%80%99t%20shoot%20the%20messenger" id="wpa2a_8">Share/Save</a></p>]]></content:encoded>
			<wfw:commentRss>http://www.emailtide.com/2007/06/15/don%e2%80%99t-shoot-the-messenger/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>New email guidelines for Wall Street</title>
		<link>http://www.emailtide.com/2007/06/14/new-email-guidelines-for-wall-street/</link>
		<comments>http://www.emailtide.com/2007/06/14/new-email-guidelines-for-wall-street/#comments</comments>
		<pubDate>Thu, 14 Jun 2007 15:14:18 +0000</pubDate>
		<dc:creator>sm</dc:creator>
				<category><![CDATA[Compliance]]></category>
		<category><![CDATA[Email]]></category>
		<category><![CDATA[Instant Messaging]]></category>
		<category><![CDATA[Risk Management]]></category>

		<guid isPermaLink="false">http://www.emailtide.com/2007/06/14/new-email-guidelines-for-wall-street/</guid>
		<description><![CDATA[According to an article published in the NY Times today (reprinted here), new regulatory guidelines for internal and external electronic communications for Wall Street are expected to be released later this week. The guidelines are meant to bring more clarity to how new and evolving forms of text based electronic communication, such as email, IM [...]]]></description>
			<content:encoded><![CDATA[<p>According to an article published in the <a href="http://www.emailtide.com/wp-admin/Stefan%20Mehlhorn%20-%20Fw:%20NYT:%20Wall%20Street%20firms%20to%20get%20guidelines%20on%20emails">NY Times</a> today (<a href="http://www.iht.com/articles/2007/06/14/business/email.php">reprinted here</a>), new regulatory guidelines for internal and external electronic communications for Wall Street are expected to be released later this week. The guidelines are meant to bring more clarity to how new and evolving forms of text based electronic communication, such as email, IM and SMS text messaging should be governed and enforced to meet existing industry regulations.</p>
<p><span id="more-58"></span></p>
<blockquote><p><em>“Though Wall Street has learned the consequences of paying too little attention to messages zipping through its corporate pipelines, other ways of communicating have cropped up faster than regulators have been able to address them.”</em></p></blockquote>
<p>Although the specific guidelines are not yet published, the general principle is to implement solutions to monitor all text based electronic communications.</p>
<p>This also means prohibiting the use of personal email and instant messaging in order to prevent  bypassing the enterprises monitoring solutions. Some firms already block access to personal email web sites and suggest limiting the use of personal cellphones.</p>
<p>Technorati Tags: <a href="http://technorati.com/tag/email+monitoring" rel="tag">email monitoring</a>, <a href="http://technorati.com/tag/wall+street" rel="tag"> wall street</a>, <a href="http://technorati.com/tag/compliance" rel="tag"> compliance</a>, <a href="http://technorati.com/tag/risk+management" rel="tag"> risk management</a>, <a href="http://technorati.com/tag/electronic+communication" rel="tag"> electronic communication</a>, <a href="http://technorati.com/tag/NYSE" rel="tag"> NYSE</a>, <a href="http://technorati.com/tag/NASD" rel="tag"> NASD</a></p>
<p><a class="a2a_dd a2a_target addtoany_share_save" href="http://www.addtoany.com/share_save#url=http%3A%2F%2Fwww.emailtide.com%2F2007%2F06%2F14%2Fnew-email-guidelines-for-wall-street%2F&amp;title=New%20email%20guidelines%20for%20Wall%20Street" id="wpa2a_10">Share/Save</a></p>]]></content:encoded>
			<wfw:commentRss>http://www.emailtide.com/2007/06/14/new-email-guidelines-for-wall-street/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Personal information leaked in emails</title>
		<link>http://www.emailtide.com/2007/05/23/personal-information-leaked-in-emails/</link>
		<comments>http://www.emailtide.com/2007/05/23/personal-information-leaked-in-emails/#comments</comments>
		<pubDate>Thu, 24 May 2007 03:43:55 +0000</pubDate>
		<dc:creator>sm</dc:creator>
				<category><![CDATA[Compliance]]></category>
		<category><![CDATA[Email]]></category>
		<category><![CDATA[Risk Management]]></category>

		<guid isPermaLink="false">http://www.emailtide.com/2007/05/23/personal-information-leaked-in-emails/</guid>
		<description><![CDATA[It happened again, an employee at a New Hampshire based temp agency accidentally emailed hundreds of social security numbers to Internet recipients. The Boston Channel 5 aired a story about the incident this morning. The exact details are a little sketchy, but it seems that a list of job candidate profiles containing social security numbers [...]]]></description>
			<content:encoded><![CDATA[<p>It happened again, an employee at a New Hampshire based temp agency accidentally emailed hundreds of social security numbers to Internet recipients. <a href="http://www.thebostonchannel.com/">The Boston Channel 5</a> aired a story about the <a href="http://www.thebostonchannel.com/asseenon5/13371650/detail.html?taf=bos">incident</a> this morning.</p>
<p><span id="more-44"></span>The exact details are a little sketchy, but it seems that a list of job candidate profiles containing social security numbers and personal email addresses was mistakenly sent as a broadcast message originally intended to inform about job opportunities.</p>
<blockquote><p><em>&#8220;She hit a button and it sent out a broadcast e-mail, so it certainly was not intentional on her part, …&#8221; </em></p></blockquote>
<p>I always feel bad for the employee that makes this type of mistake, since the ramifications can be significant &#8211; but to err is human.</p>
<p><a href="http://www.aarp.org/research/frauds-scams/fraud/fs122_id_theft.html">Identity theft</a> through impersonation via social security numbers is common place and companies must pro-actively protect the personal information of their employees and customers.</p>
<p>This raises a number of questions:</p>
<p>Why would anybody be permitted to extract lists of names, email addresses and social security numbers from a company database in the first place? Sensitive information should always be obfuscated and only be accessible on a need-to-know basis per individual record. In essence, that kind of data should never be stored in a portable document format.</p>
<p>Secondly, why does it always take the occurence of a serious incident before businesses take action? Companies should actively protect themselves and their employees from such mistakes. There are <a href="http://www.dysanalytics.com/prod_email_control_enforcer.php">technology solutions</a> available today that can help in preventing accidental and deliberate data leakage via email. The costs associated with <u>one</u> single error can easily outweigh the cost of a preventative solution.</p>
<p>Technorati Tags: <a href="http://technorati.com/tag/email+data+leakage" rel="tag">email data leakage</a>, <a href="http://technorati.com/tag/social+security+number+leak" rel="tag"> social security number leak</a>, <a href="http://technorati.com/tag/ssn" rel="tag"> ssn</a>, <a href="http://technorati.com/tag/information+risk+management" rel="tag"> information risk management</a>, <a href="http://technorati.com/tag/identity+theft" rel="tag"> identity theft</a></p>
<p><a class="a2a_dd a2a_target addtoany_share_save" href="http://www.addtoany.com/share_save#url=http%3A%2F%2Fwww.emailtide.com%2F2007%2F05%2F23%2Fpersonal-information-leaked-in-emails%2F&amp;title=Personal%20information%20leaked%20in%20emails" id="wpa2a_12">Share/Save</a></p>]]></content:encoded>
			<wfw:commentRss>http://www.emailtide.com/2007/05/23/personal-information-leaked-in-emails/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>The next wav of email</title>
		<link>http://www.emailtide.com/2007/05/22/the-next-wav-of-email/</link>
		<comments>http://www.emailtide.com/2007/05/22/the-next-wav-of-email/#comments</comments>
		<pubDate>Tue, 22 May 2007 19:19:30 +0000</pubDate>
		<dc:creator>sm</dc:creator>
				<category><![CDATA[Compliance]]></category>
		<category><![CDATA[Email]]></category>
		<category><![CDATA[Network Traffic]]></category>
		<category><![CDATA[Unified Communication]]></category>

		<guid isPermaLink="false">http://www.emailtide.com/2007/05/22/the-next-wav-of-email/</guid>
		<description><![CDATA[Email administrators at most companies are struggling to keep up with the ever-increasing storage demands of email. A frequently raised question is: What is the main force driving the consistent increase in email traffic? A review of the data quickly confirms some of the usual suspects: Spam Document sharing Mailing list subscriptions Personal emails, and [...]]]></description>
			<content:encoded><![CDATA[<p>Email administrators at most companies are struggling to keep up with the ever-increasing storage demands of email. A frequently raised question is: What is the main force driving the consistent increase in email traffic?</p>
<p><span id="more-17"></span>A review of the data quickly confirms some of the usual suspects:</p>
<ul>
<li>Spam</li>
<li>Document sharing</li>
<li>Mailing list subscriptions</li>
<li>Personal emails, and</li>
<li>General overuse of email</li>
</ul>
<p>There is however a notable addition to this mix: Voice mail messages sent as “.wav” attachments via email.</p>
<p><a href="http://en.wikipedia.org/wiki/Unified_messaging">Unified Messaging</a> now also referred to as <a href="http://searchvoip.techtarget.com/sDefinition/0,290660,sid66_gci1239583,00.html">Unified Communication</a> is slowly but surely making its way into the enterprise. Maurene Caplan Grey had a good take on the difference between unified messaging and unified communication posted in a <a href="http://blogs.zdnet.com/ecommunity/?p=107">recent blog entry</a>:</p>
<blockquote><p><em>&#8220;What&#8217;s the difference between unified messaging and unified communications? From a purist perspective, UC means near real-time communications (instead of store-and-forward), which integrate with line-of-business processes and workflow. However, with the mushrooming of UC hype, the difference between UM and UC will be semantics. UC sounds sexier than UM, yet UM dressed in the UC emperor&#8217;s clothes is still UM.&#8221; </em></p></blockquote>
<p>While initial implementations were expensive and plagued by integration issues, modern on-premise and hosted VOIP telephony solutions all offer some sort of voice mail to email forwarding capability.</p>
<p>However, that is just the beginning. Both <a href="http://www-142.ibm.com/software/sw-lotus/products/product4.nsf/wdocs/unifiedcommunications">IBM</a> and <a href="http://www.microsoft.com/presspass/press/2006/jun06/06-25UCGRoadmapPR.mspx">Microsoft</a> have committed to the development of unified communication solutions, in essence integrating their existing email, IM and collaboration products with telephony. I think it is fair to assume that email will remain the medium of choice for storing and transporting voice mail messages.</p>
<p>The primary concern when deploying VOIP is typically focused on network issues, specifically QoS to guarantee voice quality. Companies planning the deployment of these solutions must carefully evaluate the impact on the entire infrastructure before embarking on a full-scale rollout. The secondary impact on email traffic and storage can be significant. A 30-60 second voice mail generates on average an email of 100kB in size. Legacy PBX voice mail doesn’t allow to store an unlimited number of messages for an infinite time. Email integration changes that.</p>
<p>Lastly, let&#8217;s not forget the compliance implications. Many companies are now archiving their emails, in some cases for up to seven years. The voice messages stored as emails will add to the archiving volume and makes you wonder what kind of cost it would add to potential e-discovery projects.</p>
<p>Bottom line: Unified Communication is coming. Make sure you consider all of the cost factors when planning a deployment.</p>
<p>Technorati Tags: <a href="http://technorati.com/tag/unified+communication" rel="tag">unified communication</a>, <a href="http://technorati.com/tag/unified+messaging" rel="tag"> unified messaging</a>, <a href="http://technorati.com/tag/VOIP" rel="tag"> VOIP</a>, <a href="http://technorati.com/tag/voice+mail" rel="tag"> voice mail</a>, <a href="http://technorati.com/tag/email+archiving" rel="tag"> email archiving</a>, <a href="http://technorati.com/tag/email+storage" rel="tag"> email storage</a></p>
<p><a class="a2a_dd a2a_target addtoany_share_save" href="http://www.addtoany.com/share_save#url=http%3A%2F%2Fwww.emailtide.com%2F2007%2F05%2F22%2Fthe-next-wav-of-email%2F&amp;title=The%20next%20wav%20of%20email" id="wpa2a_14">Share/Save</a></p>]]></content:encoded>
			<wfw:commentRss>http://www.emailtide.com/2007/05/22/the-next-wav-of-email/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Fake email spoofs Apple</title>
		<link>http://www.emailtide.com/2007/05/16/fake-email-spoofs-apple/</link>
		<comments>http://www.emailtide.com/2007/05/16/fake-email-spoofs-apple/#comments</comments>
		<pubDate>Wed, 16 May 2007 22:36:33 +0000</pubDate>
		<dc:creator>sm</dc:creator>
				<category><![CDATA[Compliance]]></category>
		<category><![CDATA[Email]]></category>
		<category><![CDATA[Risk Management]]></category>

		<guid isPermaLink="false">http://www.emailtide.com/2007/05/16/fake-email-spoofs-apple/</guid>
		<description><![CDATA[Here is another example of why companies must take better care in protecting their communication infrastructure (see also my post on KP). An internal memo to all Apple employees sent earlier today announced shipping delays for both the much-anticipated iPhone and the Leopard OS. The bad news spread quickly to the Internet appearing on Engadget’s [...]]]></description>
			<content:encoded><![CDATA[<p>Here is <a href="http://svextra.com/blogs/gmsv/2007/05/fake_e-mail_takes_apple_stock_for_a_dip.html">another example</a> of why companies must take better care in protecting their communication infrastructure <em>(<a href="http://www.emailtide.com/2007/04/27/kaiser-permanente-jolted-by-mass-email/">see also my post on KP</a>)</em>. An internal memo to all <a href="http://www.apple.com">Apple</a> employees sent earlier today announced shipping delays for both the much-anticipated iPhone and the Leopard OS. The bad news spread quickly to the Internet appearing on <a href="http://www.engadget.com/2007/05/16/iphone-delayed-until-october-leopard-delayed-again-until-januar/">Engadget’s web site</a> promptly sending Apple’s stock for a dip.</p>
<p><span id="more-43"></span>A few hours later Apple employees received another email:</p>
<blockquote><p><em>&#8220;You may have received what appeared to be a Bullet*News from Apple. This communication is fake and did not come from Apple. Apple is on track to ship iPhone in late June and Mac OS X Leopard in October.&#8221;</em></p></blockquote>
<p>The correction spread just as quickly as the fake story and the stock has recovered since. There is wild speculation of what really happened here:</p>
<blockquote><p><em>&#8220;This couldn&#8217;t all be about checking for where Apple&#8217;s leaks are, could it? Or perhaps a criminal ploy to get a Apple stock at a discount?&#8221;</em></p></blockquote>
<p>It is highly unlikely that Apple orchestrated this in an attempt to trace insider leaks. Instead, I am sure the IT department at Apple is scrambling to find out who high jacked their email system.</p>
<p>Either way, Apple could be open to liability claims due to the impact on the stock market, if the company is found to have acted in bad faith or grossly negligent.</p>
<p>Companies must realize that their messaging infrastructure is a powerful communication tool capable of reaching thousands and in some cases hundreds of thousands of employees. As such, corporate email and IM must be better protected from misuse. Most companies already lock down the send-to-all capabilities (I’m sure Apple does that as well), but the recently publicized cases at Apple and KP show that this is not enough. <a href="http://www.dysanalytics.com/prod_email_control_enforcer.php">Stricter email policy enforcement</a> can prevent these unsanctioned emails from ever being sent.</p>
<p>Technorati Tags: <a href="http://technorati.com/tag/Apple+fake+email" rel="tag">Apple fake email</a>, <a href="http://technorati.com/tag/email+policy+enforcement" rel="tag"> email policy enforcement</a>, <a href="http://technorati.com/tag/email+risk" rel="tag"> email risk</a>, <a href="http://technorati.com/tag/email+policy+management" rel="tag"> email policy management</a>, <a href="http://technorati.com/tag/Apple" rel="tag"> Apple</a></p>
<p><a class="a2a_dd a2a_target addtoany_share_save" href="http://www.addtoany.com/share_save#url=http%3A%2F%2Fwww.emailtide.com%2F2007%2F05%2F16%2Ffake-email-spoofs-apple%2F&amp;title=Fake%20email%20spoofs%20Apple" id="wpa2a_16">Share/Save</a></p>]]></content:encoded>
			<wfw:commentRss>http://www.emailtide.com/2007/05/16/fake-email-spoofs-apple/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>HP email leak</title>
		<link>http://www.emailtide.com/2007/05/09/hp-email-leak/</link>
		<comments>http://www.emailtide.com/2007/05/09/hp-email-leak/#comments</comments>
		<pubDate>Wed, 09 May 2007 19:42:57 +0000</pubDate>
		<dc:creator>sm</dc:creator>
				<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[Compliance]]></category>
		<category><![CDATA[Email]]></category>
		<category><![CDATA[Risk Management]]></category>

		<guid isPermaLink="false">http://www.emailtide.com/2007/05/09/hp-email-leak/</guid>
		<description><![CDATA[HP was forced to disclose its second quarter forecast before the scheduled official announcement date due to one of those unfortunate email address slip-ups. An email containing the latest financial results was accidentally sent to an unintended external recipient. I am sure that many of us can sympathize with the employee’s mistake. The common use [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.siliconvalley.com/latestheadlines/ci_5845456">HP was forced to disclose</a> its second quarter forecast before the scheduled official announcement date due to one of those unfortunate email address slip-ups. An email containing the latest financial results was accidentally sent to an unintended external recipient.</p>
<p>I am sure that many of us can sympathize with the employee’s mistake. The common use of multiple address books containing internal and external addresses often mixed with personal contacts in combination with the oh-so-handy recipient type-ahead feature of contemporary email clients make it very easy to send a message to the wrong address.</p>
<p><span id="more-41"></span>Thankfully, in this particular case other than embarrassment no real harm was done, since the leaked information contained all but good news for HP. Just imagine if the message contained proprietary engineering specs, customer or employee data, strategic marketing plans, … The list goes on, you fill in the blanks.</p>
<p>This raises the issue of good email practices and enforced policies that would help to avoid such situations.</p>
<p>Here are a few examples of how to prevent this:</p>
<ul>
<li>Do not send confidential information via email, use a secure document sharing system instead.</li>
<li>If email is used, make sure to protect the message and/or attachments through encryption and possibly <a href="http://en.wikipedia.org/wiki/Digital_rights_management" title="Digital Rights Management">Digital Rights Management (DRM).</a></li>
<li>Implement an outbound content inspection and traffic monitoring solution that enables  flexible use policies and workflow.</li>
</ul>
<p>Technorati Tags: <a href="http://technorati.com/tag/HP+email+leak" rel="tag"> HP email leak</a>, <a href="http://technorati.com/tag/email+policy" rel="tag"> email policy</a>, <a href="http://technorati.com/tag/outbound+content+inspection" rel="tag"> outbound content inspection</a></p>
<p><a class="a2a_dd a2a_target addtoany_share_save" href="http://www.addtoany.com/share_save#url=http%3A%2F%2Fwww.emailtide.com%2F2007%2F05%2F09%2Fhp-email-leak%2F&amp;title=HP%20email%20leak" id="wpa2a_18">Share/Save</a></p>]]></content:encoded>
			<wfw:commentRss>http://www.emailtide.com/2007/05/09/hp-email-leak/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Email archiving part of corporate risk management</title>
		<link>http://www.emailtide.com/2007/05/01/email-archiving-part-of-corporate-risk-management/</link>
		<comments>http://www.emailtide.com/2007/05/01/email-archiving-part-of-corporate-risk-management/#comments</comments>
		<pubDate>Wed, 02 May 2007 01:58:17 +0000</pubDate>
		<dc:creator>sm</dc:creator>
				<category><![CDATA[Compliance]]></category>
		<category><![CDATA[Email]]></category>
		<category><![CDATA[Risk Management]]></category>

		<guid isPermaLink="false">http://www.emailtide.com/2007/05/01/email-archiving-part-of-corporate-risk-management/</guid>
		<description><![CDATA[In light of recent high-profile cases involving email as evidence (Intel vs. AMD, Oracle vs. SAP and the White House email scandal), many companies not currently bound by regulatory rules are recognizing the need for a comprehensive archiving strategy in order to mitigate overall legal risks (see also: Outside email use puts companies at risk [...]]]></description>
			<content:encoded><![CDATA[<p>In light of recent high-profile cases involving email as evidence (<a href="http://www.eweek.com/article2/0,1895,1832180,00.asp">Intel vs. AMD</a>, <a href="http://blogs.zdnet.com/BTL/?p=4708">Oracle vs. SAP</a> and the <a href="http://www.washingtonpost.com/wp-dyn/content/article/2007/04/12/AR2007041202408.html">White House email scandal</a>), many companies <u>not currently</u> bound by regulatory rules are recognizing the need for a comprehensive archiving strategy in order to mitigate overall legal risks</p>
<p>(see also: <a href="http://www.emailtide.com/2007/04/04/outside-email-use-puts-companies-at-risk/">Outside email use puts companies at risk</a> and <a href="http://www.emailtide.com/2007/04/25/losing-emails-is-difficult-but-finding-them-may-prove-expensive/">Losing emails is difficult, but finding them may prove expensive</a>).</p>
<p><span id="more-36"></span>eWeek just published <a href="http://www.eweek.com/article2/0,1895,2123982,00.asp?kc=EWNAVEMNL050107EOAD">an article about email archiving</a> that seems to support this trend.</p>
<p>The article notes:</p>
<blockquote><p><em>“Only about 14 percent of all corporate e-mail accounts are currently being backed up and archived for future access, but that number is going to shoot up to nearly 70 percent by the year 2011, according to a new storage industry study.”</em></p></blockquote>
<p>The article further predicts a significant rise in per user mail volume over the next few years based on data from a recent <a href="http://www.radicati.com/">Radicati</a> report.</p>
<p>While this is good news if you are in the storage industry, corporate IT departments will face increasing pressure to control the impending cost escalation by exploring strategies to slow email growth as well as the implementation of tight email retention policies.</p>
<p>The tide may finally turn: For years, IT staffers at many companies have been told to back-off on implementing mailbox quota restrictions and retention policies especially when it comes to executive mailboxes that are often gigabytes in size. This picture will most likely change rather quickly as archiving costs mount and corporate lawyers fear hidden liabilities.</p>
<p>Technorati Tags: <a href="http://technorati.com/tag/email+archiving" rel="tag">email archiving</a>, <a href="http://technorati.com/tag/email+evidence" rel="tag"> email evidence</a>, <a href="http://technorati.com/tag/corporate+risk+management" rel="tag"> corporate risk management</a></p>
<p><a class="a2a_dd a2a_target addtoany_share_save" href="http://www.addtoany.com/share_save#url=http%3A%2F%2Fwww.emailtide.com%2F2007%2F05%2F01%2Femail-archiving-part-of-corporate-risk-management%2F&amp;title=Email%20archiving%20part%20of%20corporate%20risk%20management" id="wpa2a_20">Share/Save</a></p>]]></content:encoded>
			<wfw:commentRss>http://www.emailtide.com/2007/05/01/email-archiving-part-of-corporate-risk-management/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

