This Page

has been moved to new address

Navigating eDiscovery in the Cloud Shouldn't Be That Difficult

Sorry for inconvenience...

Redirection provided by Blogger to WordPress Migration Service
----------------------------------------------------- Blogger Template Style Name: Snapshot: Madder Designer: Dave Shea URL: mezzoblue.com / brightcreative.com Date: 27 Feb 2004 ------------------------------------------------------ */ /* -- basic html elements -- */ body {padding: 0; margin: 0; font: 75% Helvetica, Arial, sans-serif; color: #474B4E; background: #fff; text-align: center;} a {color: #DD6599; font-weight: bold; text-decoration: none;} a:visited {color: #D6A0B6;} a:hover {text-decoration: underline; color: #FD0570;} h1 {margin: 0; color: #7B8186; font-size: 1.5em; text-transform: lowercase;} h1 a {color: #7B8186;} h2, #comments h4 {font-size: 1em; margin: 2em 0 0 0; color: #7B8186; background: transparent url(http://www.blogblog.com/snapshot/bg-header1.gif) bottom right no-repeat; padding-bottom: 2px;} @media all { h3 { font-size: 1em; margin: 2em 0 0 0; background: transparent url(http://www.blogblog.com/snapshot/bg-header1.gif) bottom right no-repeat; padding-bottom: 2px; } } @media handheld { h3 { background:none; } } h4, h5 {font-size: 0.9em; text-transform: lowercase; letter-spacing: 2px;} h5 {color: #7B8186;} h6 {font-size: 0.8em; text-transform: uppercase; letter-spacing: 2px;} p {margin: 0 0 1em 0;} img, form {border: 0; margin: 0;} /* -- layout -- */ @media all { #content { width: 700px; margin: 0 auto; text-align: left; background: #fff url(http://www.blogblog.com/snapshot/bg-body.gif) 0 0 repeat-y;} } #header { background: #D8DADC url(http://www.blogblog.com/snapshot/bg-headerdiv.gif) 0 0 repeat-y; } #header div { background: transparent url(http://www.blogblog.com/snapshot/header-01.gif) bottom left no-repeat; } #main { line-height: 1.4; float: left; padding: 10px 12px; border-top: solid 1px #fff; width: 428px; /* Tantek hack - http://www.tantek.com/CSS/Examples/boxmodelhack.html */ voice-family: "\"}\""; voice-family: inherit; width: 404px; } } @media handheld { #content { width: 90%; } #header { background: #D8DADC; } #header div { background: none; } #main { float: none; width: 100%; } } /* IE5 hack */ #main {} @media all { #sidebar { margin-left: 428px; border-top: solid 1px #fff; padding: 4px 0 0 7px; background: #fff url(http://www.blogblog.com/snapshot/bg-sidebar.gif) 1px 0 no-repeat; } #footer { clear: both; background: #E9EAEB url(http://www.blogblog.com/snapshot/bg-footer.gif) bottom left no-repeat; border-top: solid 1px #fff; } } @media handheld { #sidebar { margin: 0 0 0 0; background: #fff; } #footer { background: #E9EAEB; } } /* -- header style -- */ #header h1 {padding: 12px 0 92px 4px; width: 557px; line-height: 1;} /* -- content area style -- */ #main {line-height: 1.4;} h3.post-title {font-size: 1.2em; margin-bottom: 0;} h3.post-title a {color: #C4663B;} .post {clear: both; margin-bottom: 4em;} .post-footer em {color: #B4BABE; font-style: normal; float: left;} .post-footer .comment-link {float: right;} #main img {border: solid 1px #E3E4E4; padding: 2px; background: #fff;} .deleted-comment {font-style:italic;color:gray;} /* -- sidebar style -- */ @media all { #sidebar #description { border: solid 1px #F3B89D; padding: 10px 17px; color: #C4663B; background: #FFD1BC url(http://www.blogblog.com/snapshot/bg-profile.gif); font-size: 1.2em; font-weight: bold; line-height: 0.9; margin: 0 0 0 -6px; } } @media handheld { #sidebar #description { background: #FFD1BC; } } #sidebar h2 {font-size: 1.3em; margin: 1.3em 0 0.5em 0;} #sidebar dl {margin: 0 0 10px 0;} #sidebar ul {list-style: none; margin: 0; padding: 0;} #sidebar li {padding-bottom: 5px; line-height: 0.9;} #profile-container {color: #7B8186;} #profile-container img {border: solid 1px #7C78B5; padding: 4px 4px 8px 4px; margin: 0 10px 1em 0; float: left;} .archive-list {margin-bottom: 2em;} #powered-by {margin: 10px auto 20px auto;} /* -- sidebar style -- */ #footer p {margin: 0; padding: 12px 8px; font-size: 0.9em;} #footer hr {display: none;} /* Feeds ----------------------------------------------- */ #blogfeeds { } #postfeeds { }

Tuesday, November 29, 2011

Navigating eDiscovery in the Cloud Shouldn't Be That Difficult

In a follow up to my Blog post titled, "eDiscovery in the Cloud: The Sky Is Not Falling", this Blog post is dedicated to the premise that successfully navigating eDiscovery in the cloud is not as complicated as many are indicating it should be or as complicated as many are making it.

Successfully navigating the brave new world of eDiscovery in the cloud is really just a matter of education and a willingness to move beyond the status quo.  There is no doubt that if you don't pay attention, you and your team will perish on the rocks. However, don't pass on taking the eDiscovery in the cloud journey because it is too dangerous or give up before you at least make an attempt to learn how to save your ship.

First of all, in case anyone missed the memo, the cloud train has left the station.  As an example, independent research firm Forrester Research predicted in a research report published earlier this year titled, “Sizing the Cloud” that the global cloud computing market would reach $241 billion in 2020 compared to $40.7 in 2010.  So, more than likely, whether you want your data in the cloud or not, it is moving quicker than you think.  And, as an end-user, unless you have some kind of cloud storage phobia, it really shouldn't matter that much.  The real debate doesn't start until you couch the question(s) about cloud computing in terms of what happens when your have to perform the delicate and often times messy operation of eDiscovery in the cloud.  If you are a glutton for punishment and like to dwell on all of the negative things that could possible happen in the life then I encourage you to read "The Promise of the Cloud Meets the Obligations of E-Discovery", published on the Law.com website on October 12, 2011 by Brendan M. Schulman and Samantha V. Ettari.  This article does a great job of indicating that the sky is falling and that we are all doomed.  However, as I indicated in the my response to this piece, "cloud computing has already made it and most of us are just fine, eDiscovery in the cloud and all!!"  But, the devil is always in the details and therefore what does this mean in practical terms?

Further, please note that if you are currently doing a bad job of eDiscovery in general, you had better read the Schulman and Ettari article as the sky is going to fall if you attempt to perform eDiscovery in the cloud under your current practices. Once you have completed reading that article and if you still want a road map for successful implementation of eDiscovery in the cloud, come back and finish reading this blog post.

What is eDiscovery in the Cloud?To properly perform eDiscovery in the cloud,  you first have to understand what it is and, probably more importantly, what it is not.  The current crop of litigation technology vendors have done a great job of confusing the market in regards to eDiscovery in the cloud.  However, I believe that over the next 12-18 months, the market will become much more educated and some amount of consensus will begin to form regarding a more realistic and concise definition of eDiscovery in the cloud.

eDiscovery in the cloud is NOT uploading all of your potentially responsive ESI to a litigation service provider's data center and then accessing that ESI via the Internet to perform searches and document review.  That may be Early Case Assessment (ECA) or document review delivered under a Software-as-a-Service (SaaS) model.  But, it is not eDiscovery in the cloud.

Likewise, eDiscovery in the cloud is NOT manually collecting big chunks (that's a technical term) of potentially responsive ESI from your cloud provider and the performing eDiscovery with that ESI the same way you process ESI from your corporate network or from unconnected desktops and laptops (BTW - I am in the process of investigating the nightmare of collecting ESI from your cloud provider and plan to author a Blog post of my findings before the end of the year.  So, if anyone has any input, send it to me and I will consider including it in my post).

eDiscovery in the cloud ultimately means having a virtual eDiscovery process that actually runs in the cloud right alongside of your cloud storage and allows you to perform, Early Case Assessment (ECA) including First Pass Review, possibly preservation and legal hold management, definitely forensically sound collection and the generation of an industry standard load file and/or full on document review and production.  In addition, eDiscovery in the cloud also means that you can operate these processes remotely through an Internet based user interface and don't have to have operational bodies physically inside the cloud data center(s) to perform any of the normal magic that is currently required by many of the legacy hosted eDiscovery platforms. 

Further, eDiscovery in the cloud should also include what I am going to call (for lack of a better term at this point) federated eDiscovery to enable an organization to "perform eDiscovery" on data no matter where it resides.  Currently, users that are supported by competent IT organizations, don't have to worry about where ESI is physically located.  Therefore, eDiscovery professionals shouldn't have to worry either.  This would include ESI behind the corporate firewall, housed with different cloud service providers or housed with the same cloud service providers in different data centers potentially in different countries (don't get me started on the debate regarding the legal issues with moving ESI in and out of countries as that is the topic of a future Blog post). Please note that I am not oblivious to the challenges of moving large amounts of data around.  However, we all might be surprised to learn that class 5 rapids have been successfully navigated in other industries.

Is this Definition Realistic
This definition of eDiscovery in the cloud may sound like something that only Scotty, the engineer from the Star Trek Enterprise, could cobble together with technology from the next century and a good amount of duct tape.  However, the technology exists today and is ready to be utilized with little or no duct tape required.  Therefore, the only real speed bumps on this journey will be convincing the cloud service providers to install the appropriate eDiscovery technology as a standard part of their technology stack, enlisting a new generation of eDiscovery consultants to support the development of best practices for eDiscovery in the cloud and finally to show the market that eDiscovery is no longer a reason to NOT move your data to cloud.  I realize that these are not insignificant roadblocks.  However, providing eDiscovery as a standard part of it's technology stack is a homerun for cloud service providers and the associated services represents a blue water/green field market opportunity for eDiscovery consultants and possibly service provides. Therefore, resistance should be minimal and buy-in should be quick.

What's Next?
In the coming weeks I will be releasing my initial list of eDiscovery technology vendors that can support my vision of eDiscovery in the cloud along with an initial overview of the best practices.  If anyone has any input that you believe should be included in these upcoming Blog posts, send them to me and I will consider including them.

In the mean time, if you are concerned with moving your data to the cloud and are hesitant because you are concerned about eDiscovery or if you are currently faced with the daunting task of extracting your ESI from a cloud service provider, contact me as I can help you successfully navigate your way through this paradigm shift.

Labels: , , , , , , ,

1 Comments:

At November 29, 2011 at 9:35 PM , Blogger -Coder said...

Nice post. Most people I talk to in this industry think e-discovery in the cloud will never happen. I think it's the way of the future and nearly all e-discovery will be done this way eventually. In fact, I'm working hard to make this a reality!

 

Post a Comment

Subscribe to Post Comments [Atom]

Links to this post:

Create a Link

<< Home