Social Networks Pose E-Discovery Risks

Growing corporate use of Twitter, Facebook, and cloud-based applications are creating new e-discovery demands, but c-level awareness of risks remains scarce.

Two-thirds of businesses worry about the e-discovery risks posed by social networks, but 25% say they're not prepared, and 33% think they're only partially prepared, to meet related e-discovery requests. Furthermore, only 9% of companies think they're well prepared to deal with e-discovery requests for information stored in cloud-based applications.

Those findings come from a study released Wednesday, based on a survey of 337 U.S. IT, legal, risk, and compliance professionals conducted by the Economist Intelligence Unit for Deloitte Forensic Center.


More Storage Insights

Webcasts

More >>

White Papers

More >>

Reports

More >>

The survey also found that when it comes to understanding e-discovery, while 55% of organizations have senior executives with some level of commitment to e-discovery, there's a complete lack of c-level awareness at 16% of organizations, while at one-quarter of organizations, respondents said it's unclear whether c-level executives had any knowledge of the challenges or risks associated with meeting e-discovery requirements.

Failure to respond to e-discovery requests in an accurate, complete, and timely manner, however, can result in a court imposing sanctions on an organization, as numerous businesses -- including Morgan Stanley and PriceWaterhouseCoopers -- have learned firsthand.

Now, however, e-discovery is growing more challenging as the volume of information that enterprises store increases, and as employees increasingly use social networks and cloud-based applications. Already, multiple court cases have featured e-discovery requests for information stored in social networks.

A further e-discovery challenge, according to Deloitte's study, is poor collaboration between the legal and IT teams, which experts say must work together to accurately provide courts with the information they request. Indeed, the survey found that one-third of respondents don't know how their IT and legal teams communicate. When they do work together, only 13% of organizations say they work together "very well," and at one-third of organizations, IT professionals say that legal teams have a poor grasp of the organization's e-discovery technology limits.

Furthermore, about one-third of companies lack a "discovery response team" -- or similar group -- comprised of representatives from human resources, IT, legal, and other departments relevant to fulfilling e-discovery requests.

Legally, the climate appears to be turning against businesses that don't have their e-discovery act together. Earlier this year, in what many lawyers are calling a landmark e-discovery ruling, U.S. district judge Shira Scheindlin laid out "a framework for determining when, and to what degree, sanctions are appropriate against a party that fails to take the proper steps in preserving ESI [electronically stored information]," according to Amy Longo, a partner at law firm O'Melveny & Myers, writing on her firm's blog.

In the related case -- Pension Committee of the Univ. of Montreal Pension Plan, et al., v. Banc of America Securities, LLC, et al. -- the judge slammed some plaintiffs for failing to cease deleting e-mails after an e-discovery request was made, failing to preserve backup tapes that were the sole source of required information, and for relying exclusively on employees searching their own e-mails to meet e-discovery requests, said Longo. In addition, the judge imposed sanctions against some plaintiffs for utilizing witnesses who weren't familiar with their organization's e-discovery practices, and as a result ended up submitting false or misleading information to the court.

Now that server virtualization is widespread, can we leverage it to make true business continuity a reality--or at least make recovering from disaster faster and less expensive? Download our report here (registration required).

Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
Subscribe to RSS

Resource Links