Five on Forensics Page 1 - Craig Ball
Five on Forensics Page 1 - Craig Ball
Five on Forensics Page 1 - Craig Ball
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
<str<strong>on</strong>g>Five</str<strong>on</strong>g> <strong>on</strong> <strong>Forensics</strong><br />
© 2002-2008 <strong>Craig</strong> <strong>Ball</strong> All Rights Reserved<br />
Twenty Tips for Counsel Seeking Discovery<br />
1. Get your preservati<strong>on</strong> letter out early and be both specific and general. Assume that<br />
the recipients d<strong>on</strong>’t know their own systems and d<strong>on</strong>’t understand computer forensics.<br />
Educate them in the letter so they can’t use ignorance as an excuse.<br />
2. Do your homework: use the Net and ask around to learn about the nature and extent<br />
of your opp<strong>on</strong>ent’s systems and practices. You’re probably not the first pers<strong>on</strong> to ever<br />
pursue discovery against the oppositi<strong>on</strong>. Others might know where the sweet spots<br />
can be found.<br />
3. Get your e-discovery out fast, with the petiti<strong>on</strong> if you’re the plaintiff. Data is going to<br />
disappear. You’re in a poor positi<strong>on</strong> to complain about it if you didn’t ask while it was<br />
still around.<br />
4. Force broad retenti<strong>on</strong>, but pursue narrow discovery<br />
5. What they must preserve and what they must produce are very different obligati<strong>on</strong>s.<br />
Keeping the first broad protects your client’s interests and exposes the oppositi<strong>on</strong>’s<br />
negligence and perfidy. Keeping requests for producti<strong>on</strong> narrow and carefully crafted<br />
makes it hard for your opp<strong>on</strong>ent to buy delays through objecti<strong>on</strong>. Laser-like requests<br />
mean that your opp<strong>on</strong>ents must search with a spo<strong>on</strong> instead of a backhoe. Tactically,<br />
ten single, surgical requests spread over 20 days are more effective than 20 requests<br />
in <strong>on</strong>e.<br />
6. Be aware that your opp<strong>on</strong>ent may not understand the systems as well as you do, but<br />
may not want any<strong>on</strong>e—especially his client--to know it. Help your opp<strong>on</strong>ent “get it,” so<br />
he can pose the right questi<strong>on</strong>s to his client.<br />
7. Questi<strong>on</strong> the IT people. Avoid the managers and focus <strong>on</strong> the grunts. The latter are<br />
have spent less time in the woodshed and they know the real retenti<strong>on</strong> practices.<br />
8. Seek a copy of any document retenti<strong>on</strong> policies and a complete inventory and<br />
topology of system resources. You need to know where the data is stored and <strong>on</strong><br />
what equipment.<br />
9. Invoke the court’s injunctive power early to force preservati<strong>on</strong>. The agreement that<br />
can be secured to forestall a court order may be better than you’ll get from the judge.<br />
10. If you can’t get make any headway, seek appointment of a neutral or special master.<br />
11. Ask all opp<strong>on</strong>ent employee witnesses what they were told to do in the way of e-<br />
document retenti<strong>on</strong> and what they actually did.<br />
12. Know how and when to check for authenticity of data produced. Digital data is easily<br />
forged.<br />
13. Be sure to get metadata whenever it may be relevant.<br />
14. D<strong>on</strong>’t accept image data (TIFF or PDF) when you need native data.<br />
15. Have the principal cases and rules <strong>on</strong> e-discovery and cost shifting at hand. Tailor<br />
your requests to the language of the cases and the rules.<br />
16. Set objecti<strong>on</strong>s for hearing immediately. Require asserti<strong>on</strong>s of burden and cost to be<br />
supported by evidence.<br />
17. Analyze what you get promptly after you get it and pin down that it is represented to be<br />
“everything” resp<strong>on</strong>sive to the request. Follow up with additi<strong>on</strong>al requests based up<strong>on</strong><br />
your analysis.<br />
18. D<strong>on</strong>’t let yourself be railroaded into cost sharing but, if it happens, be sure you’re<br />
protected from waste and excess by the other side, and leverage your role as<br />
underwriter to gain greater access.<br />
<strong>Page</strong> 74