This Page

has been moved to new address

The eDiscovery Paradigm Shift

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 { }

Saturday, January 21, 2012

The Dangers of Do-It-Yourself eDiscovery: A Warning to Lawyers and Business Leaders.

The goal of eDiscovery is to acquire relevant electronically stored information (ESI) and admit relevant and useful ESI into evidence. While ESI may be used for other purposes, such depositions or settlement negotiations, if the ESI is not gathered properly, it will not be admissible into evidence. Such a result would waste both the time and cost expended to obtain the ESI. Lawyers should not gather ESI personally and the person who does the collection should be qualified to do such work. Otherwise, the ESI may not be admissible and significant damage may be done to a party’s case.

The Lawyer as a Witness. Lawyers who gather ESI directly face several dilemmas and dangers. One of the largest concerns is the lawyer becoming a witness in the case. American Bar Association Model Rule of Professional Conduct 3.7 prohibits the lawyer from acting as the lawyer in the case and being a necessary witness. Rule 3.7 states:

(a) A lawyer shall not act as advocate at a trial in which the lawyer is likely to be a necessary witness unless:
(1) the testimony relates to an uncontested issue;
(2) the testimony relates to the nature and value of legal services rendered in the case; or
(3) disqualification of the lawyer would work substantial hardship on the client.

(b) A lawyer may act as advocate in a trial in which another lawyer in the lawyer's firm is likely to be called as a witness unless precluded from doing so by Rule 1.7 or Rule 1.9.

The comment 2 to Rule 3.7 states:
The tribunal has proper objection when the trier of fact may be confused or misled by a lawyer serving as both advocate and witness. The opposing party has proper objection where the combination of roles may prejudice that party's rights in the litigation. A witness is required to testify on the basis of personal knowledge, while an advocate is expected to explain and comment on evidence given by others. It may not be clear whether a statement by an advocate-witness should be taken as proof or as an analysis of the proof.

In the D.C. Bar in Ethics Opinion No. 228 expanded upon the purpose of this rule:

Beyond the confusion that this combination of roles might create, the rule is justified on at least three other bases: (1) it is necessary to prevent the possibility that, in addressing the jury, the lawyer will appear to vouch for his own credibility; (2) it will prevent the difficult situation that occurs when an opposing counsel must cross-examine a lawyer-adversary and seek to impeach his credibility; and (3) the rule also will prevent the implication that the testifying lawyer is distorting the truth for his/her client’s benefit.

Citing Culebras Enterprises Corp. v. Rivera-Rios, 846 F.2d 94, 99 (1st Cir. 1988), citing Bottaro v. Hatton Associates, 680 F.2d 895, 897 (2d Cir. 1982); International Electronics v. Flanzer, 527 F.2d 1288, 1294 (2d Cir. 1975); MacArthur v. Bank of New York, 524 F. Supp. 1205, 1208 (S.D.N.Y. 1981).

Authentication of ESI. Any person who gathers ESI must be able to authenticate and lay a foundation for that ESI. “Authentication” simply means that the person called to admit the ESI must prove that the ESI is what he or she claims it is. That person must be able to lay a foundation for the ESI.

To authenticate the evidence, the person called to testify may need to establish the following, depending upon what is sought to be introduced and the issues raised:

How the ESI was gathered.
Where the ESI was stored.
Who had access to it.
Establish the chain-of-custody
Whether other ESI was also located.
Whether a thorough search was conducted.
Whether the ESI sought to be introduced was altered from its original state.
Other essential details.

Who should be entrusted with the responsibility to gather the ESI? Who should take the witness stand to testify at trial? Certainly, the law firm’s paralegal, secretary and investigator should not conduct the ESI search unless that individual is qualified to establish the above-listed details and will lay the appropriate foundation for introduction of the ESI.

When gathering evidence it is usually not clear whether the evidence will be challenged when the party seeks to introduce it. Thus, the evidence should be gathered in a thoughtful manner that will withstand future challenges.

If ESI is gathered improperly and a party is unable to lay an appropriate foundation to authenticate the ESI, that evidence will not be admitted into evidence. This could be devastating to the case, depending on how critical the ESI was.

Just as experts are hired to provide opinions and establish essential facts, experts should be used to gather ESI. Ideally, the expert will have both technical are needed to search for, gather and introduce ESI.

The person who gathers ESI should also be a good witness. Parties must generally take witnesses as they come. There is very little control over who witnessed particular facts. However, when gathering evidence, parties are given the opportunity to select the witness. So, there should be some assurance that the person who gathers ESI will be a competent witness who can be depended upon. This witness may end up being the critical witness in the case.

Do-It-Yourself eDiscovery Software Tools. Some eDiscovery software tools are marketed directly to lawyers and this is clearly a terrible idea. A lawyer should not gather ESI if he wants to remain the attorney in the case or introduce the ESI into evidence. If the lawyer chooses to gather ESI, he may even be committing malpractice. Do-it-yourself software tools were intended to reduce the cost of eDiscovery and place direct control over the ESI in the hands of lawyers and business leaders. However, they may have unintended consequences.

The lawyer cannot use these tools to gather ESI or she may be disqualified as the lawyer in the case. Only a person qualified to testify at trial should use these tools to gather ESI. Ideally, this person would be an expert.
Thought must be given to who and how ESI should be gathered before it is obtained. A little bit of caution early will be rewarded later.



Labels: , , , , , , , , , ,

Friday, February 29, 2008

Cell Phones,Text Messages and Smoking Guns

It doesn't take reviewing the results of one of the recent national studies on cell phone usage to realize that that most Americans and most adults throughout the industrialized nations of the world now have cell phones. As such, the collecting the ESI on cell phones should be at the top of the checklist for almost any litigation in 2008. However, given the fact that I spend most of my waking hours discussing eDiscovery and ESI collection and computer forensics, I am still surprised that the potential smoking gun data on cells phone is either over looked or under estimated.

In a recent blog posting titled "Don't Forget the Phone Messages"on ediscoveryinfo, Brett Burney points out several recent high profile cases in which the ESI on cell phones were the basis for the case (i.e. the smoking gun).

Does anyone else have any other examples of either cell phones providing the "smoking gun" evidence or cell phones being overlooked to the determent of the case. Further, does any have any interesting computer forensic case studies in regards to retrieving ESI from cell phones.

Labels: , , , , , , , , ,

Friday, January 18, 2008

Proactive Enterprise eDiscovery Should be a Standard Business Practice

With the changes in the Federal Rules of Civil Procedure at the end of 2006 along with the subsequent and associated sanctions and law suites, corporations that face litigation on a fairly regular basis should consider treating proactive ediscovery as a standard operating processes vs. a series of discrete events.

For example, many organizations are now taking steps toward automating the litigation hold process. As part of this process, witnesses (e.g. employees, vendors, etc.) will automatically receive instructions to suspend the destruction of documents that might be potentially pertinent to an anticipated litigation/investigation matter. However, even in the face of the well know federal and state actions and sanctions that have been broughg against those organizations that do not comply, there is strong evidence that preservation orders, when emailed or even handed out, will not be followed.

As such, these organizations are being forced to turn to more automated and integrated ESI detection and collection to accompany the hold order. As a results, we are quickly seeing explosive growth in what has been tagged Evidence Lifecycle Management (ELM).

Although a somewhat disjointed market that still requires a fair amount of consulting, we are starting to see some very good semi-integrated solutions from vendors such as Kazeon (http://www.kazeon.com/), Clearwell (http://www.clearwellsystems.com/) and WorProducts (http://www.workproducts.com/) that include features such proactive identification of employees (i.e. potential custodians), mapping of their data, preservation and hold lifecycle management, automated collection, culling and de-duping, preservation management, Electronic Data Discovery and Computer Forensics, Online Review, Hosting and long term Storage.

As anyone that reads this Blog on a regular basis knows, I am a big proponent of SaaS and onDemand delivery and therefore will be looking for the first vendor or consortium of vendors that develops and releases a true onDemand SaaS ELM solution.

Stay tunned for the results of my investigation.

Labels: , , , , , , , , , ,

Friday, October 26, 2007

Chain of Custody Study

Regardless of the collection method employed, strict chain of custody records must be maintained for all documents, data, and objects collected so that their authenticity can be assured. Without this assurance the data may not be reliable as evidence in litigation. Every collector, whether a third party vendor, an internal corporate representative or outside counsel representative should document procedures for accepting, storing, and retrieving documents, in the event that he or she may be called upon to testify.

Chain of custody records should be maintained for every "touch" of each item by a search operator. Because the volume of audit history that a large-scale collection project generates can be enormous, selecting tools and processes with automated audit history and the scalability to handle all the audit data is extremely important. Technologies such as Windows Event Logs or Syslog have been proven to scale adequately. Numerous native and third-party solutions exist to parse through, analyze, summarize and report on those types of data logs.

I am in the process of developing a whitepaper regarding "Chain of Custody". As such, I am looking for examples, where:

(1) standard and reasonable Chain of Custody Best Practices were followed and the outcome was as expected (i.e. there were not issues);
(2) standard and reasonable Chain of Custody Best Practices were followed and the outcome was as not as expected (i.e. there were issues);
(3) standard and reasonable Chain of Custody Best Practices were not followed and as a result there were issues.

As part of my investigation, I am looking for written Chain of Custody Best Practices and any onDemand software solutions that have been developed, either home grown or commercially available, to support Chain of Custody.

Labels: , , , ,