Skip to main content
E14 Exchange Uber-Geek

Mark E. Smith's Brain Dump

Go Search
Home
Capax Global Blogs
Public Document Library
  

Mark E. Smith's Brain Dump > Categories
CIOs on Trial: A Check List for eDiscovery and Litigation
Today’s CIO encounters many challenges handling security and regulatory mandates that extend far beyond the once-simple duties of maintaining firewalls. CIOs are today’s corporate first responders to spot insider theft or illegal activity, recover lost or deleted data, and to ameliorate poor document retention.
Even before 2008's financial meltdown, courts realized that the amount of electronic data in litigation was growing exponentially. As a result, new Federal guidelines were introduced in 2006 http://www.cioupdate.com/article.php/3646801 to address this growing problem. At the core of any litigation today is the concept of understanding electronic data―where it is located, how it is managed, and how it can be accessed.
In the past, the litigation team consisted of inside and outside counsel, the business unit manager and outside suppliers. The legal responsibility for the management of a company’s data in most businesses falls squarely on the shoulders of the CIO. Thus, if a company is ever entrenched in a legal battle, the CIO needs to be part of the team and must be prepared to take the stand. Because of this person’s unique ability to discuss the internal systems that generate the data in question, a CIO will almost inevitably make any trial attorney’s short list.
In preparing to testify, a CIO must create a plan of action to address the data involved in the litigation. The CIO must be able to speak to the company’s internal IT functions as well as the complexity of the company’s data architecture. A CIO must also be prepared to defend the company’s work practices and policies in anticipation of, not just in response to, litigation. Creating a litigation response team that prepares these responses and policies ahead of time is critical.
The following are sample issues and questions that a CIO may need to address on the stand and, as part of the litigation response team, should be prepared to tackle:
 
  • Present a simple overview as to how data is managed within the corporate structure.
  • Discuss data mapping and chain of custody procedures within the company. The ability to easily explain this data mapping process, how it was done, who did it and how it was audited, is a key element of any trial involving eDiscovery.
  • Clearly communicate the company’s IT planning approach.
  • Explain how data is handled on a day to day basis by the business unit and managed by the IT services organization.
  • Speak to compliance issues and how they are managed from an IT perspective. Be prepared to assess what impact this system may have on the litigation.
  • Discuss how is data managed in overseas subsidiaries? What safeguards are in place to collect data from these locations? Can data be transferred across borders pursuant to US Department of Commerce Safe Harbor or other criteria?
  • How is the records management program handled and what is the CIO’s role in that process? How might this process be impacted by a litigation hold?
  • What role does the CIO play when staff needs to be interviewed by the legal team for a deposition or interrogatory?
  • How is the collection of data managed internally? Who is collecting the data? Is it self-collection or is it managed by an outside partner?
  • What type of audit trail or chain of custody is in place as part of the day-to-day business activities?
  • What types of reporting are available regarding the data?

Here are a few basic guidelines that the CIO must adhere to as part of the litigation team:

  • Ensure the company complies with regulations pertaining to its business operations.
  • Maintain compliance with regulations pertaining to the records the company must keep.
  • Be certain the company’s records are maintained and can be located by a chosen set of criteria (examples may be by department, facility, subject, product, etc.)
  • Ensure there is an appropriate retention program so required records are kept as long as required and are reliably disposed of when no longer necessary.
  • Respond to the discovery obligations of litigation filed against the company within the time deadlines of the courts.
  • Manage the cost of the litigation to minimize effect on the company, both financially and in terms of the disruption of ongoing operations.
  • Comply fully with the requirements of the courts.
  • Ensure the company’s lawyers, whether in-house or outside counsel, are supplied with the information they need and their efforts are effectively supported.

A good reference tool for the CIO is the Electronic Discovery Reference Model (EDRM), which can be found at http://edrm.net/. EDRM is a collaborative effort that involves corporations, law firms and suppliers working together to better delineate the best practices of managing litigation today. As part of the EDRM model, there are specific areas where a CIO can reference these best practices to help prepare and respond to litigation. The model covers each aspect of the litigation process and defines the necessary components to be successful.

CIO’s know that building a firewall after a system is hacked is too little, too late. Now, more than ever, they must extend that lesson to data management. Implementing a comprehensive plan in anticipation of litigation is the company’s best defense against anything, technology or otherwise, that threatens the company.
 
 
Economic impact of Exchange 2010 (by Forrester)

Based on the interviews with the nine existing customers, Forrester constructed a TEI framework for a composite organization and the associated ROI analysis illustrating the financial impact areas. As seen in Table 1, the ROI for our composite company, computed from hard benefits, is 48% with a breakeven point (payback period) of less than six months after deployment.

E2010EConomicImpact

Exchange 2010 Business Value: The study provides a clear list of Exchange 2010 value-proposition points. Here are the key benefits mentioned in the report:

  • Cost avoidance of storage
  • Reduced cost of high availability and disaster recovery
  • Savings in backup systems and staff
  • Fewer help desk or support calls
  • Cost reduction of extending mobility
  • Enhanced message filtering
  • Simplified compliance and legal eDiscovery
  • Voicemail cost avoidance

The white-paper has 3-year projected present value estimations. Consider this document a great starting point to build the business case for Exchange 2010 with your customers.

Get the whitepaper at :  http://download.microsoft.com/download/7/5/0/75068B44-0A70-4BBF-9824-01ECF076F7AE/TheTotalEconomicImpact_pdf_11042009.pdf

Install Windows Server 2008 via USB thumbdrive

This has been posted around in various flavors for Vista. I've adopted it for our lab and production data center environments that are mainly run on blade servers in remote data centers without DVD drives.

Requirements:
1. 8GB USB thumb drives.
2. BIOS that has the ability to select USB drive as a boot drive independent of the HDD. For example, some BIOS detect the USB drive as a HDD and therefore you can only select HDD in the boot priority. This results in the inability to boot the system while the USB drive is installed in the server.
3. Access to the console while the machine is booting e.g. RiLO/DRAC/IP KVM.

Making the Server 2008 USB Boot Media:
If your stick has U3 installed on it, you’ll probably want to remove that. Here are the instructions on how to remove U3: http://www.u3.com/uninstall/ 

Format the thumb drive

  1. from a CMD prompt execute: diskpart
  2. list disk
  3. select disk 1    (assuming disk 1 was your thumb drive in the above list disk command)
  4. clean
  5. create partition primary
  6. select partition 1
  7. active
  8. format fs=fat32
  9. assign
  10. exit

Copy the Win2008 install files

  1. xcopy d:\*.* /s/e/f e:\   (assumes your dvd is drive D: and your thumb drive is drive E:\, adjust accordingly)

Setting up the server:

  1. Now that you have the USB media, insert them into each of your servers.
  2. Edit the boot priority of the bios to be:
    1. USB
    2. HDD
  3. Test the configuration by booting the server. When booting you should see the "Press any key to boot..." screen in Windows. Let that timeout and your normal windows install should startup.
  4. When you need to recover/rebuild the server, simpy boot from the USB drive.
  5. HINT: Also copy the server's drivers, management softare to the USB stick if necessary.
Resizing a Virtual PC/Virtual Server VHD
Sometimes you'll want to resize a VHD... For example, you might have only made the core OS 30GB and need to expand it. You'll need two tools:
 
GPARTED and VhdResizer.
GParted LiveCD (ISO)
 
VhdResizer
 
This video does a good job of explaining.
 
Note: I had a hard time getting GParted's video display to properly display. After it booted in the garbled video mode I had to hi CTRL-ALT-BACKSPACE to kill X win. Then issue a sudo Forcevideo (case sensitive) and specify the VESA video at 800x600.