The Code42 platform provides powerful tools for performing eDiscovery. This article explains the conceptual foundations of eDiscovery, how the Code42 platform can be leveraged to support it, and then guides you through concrete examples that you can adapt to your needs.
We recommend that you have the following knowledge and skills (or be willing to learn):
Our Zapproved partnership enables you to use Zapproved to manage your legal hold process. Learn more about how to integrate Code42 and Zapproved for eDiscovery.
For help working with the Code42 API, contact your Customer Success Manager (CSM) for enterprise support at email@example.com.
Data-related tasks supported by this article
There are overlaps between eDiscovery, data governance, analytics, and data visualization. Since these tasks have similarities and support each other, it is important to understand the following definitions:
- eDiscovery refers to the process of discovery in legal cases when the information is in electronic format.
- Data governance refers to the ways in which an organization attempts to minimize its compliance risk as well as to make sure that data is properly managed, kept secure, utilized effectively, etc.
- Analytics is the search for and presentation of useful patterns and information in data. Business intelligence, planning, metrics, and many other business activities are supported by analytics.
- Data visualization is one of the ways to present the findings and data gathered by analytics. It uses graphs, charts, and other visual aids to communicate the significance of patterns in data.
eDiscovery consists of a number of steps and functions. The following diagram depicts the general workflow:
You may engage in some but not all of the steps, elect to carry out the steps in a different order, or cycle back to earlier steps.
Here is a list of the steps with associated sub-goals, for easy review:
- Beginning the legal hold process
- Locating and verifying potential sources.
- Preservation: ensuring protection against inappropriate alteration or destruction.
- Collection: gathering for further use in the eDiscovery process.
- Processing: searching and converting into forms more suitable for review and analysis.
- Review: evaluating for relevance and privilege.
- Analysis: evaluating for content and context, including key patterns.
- Production: delivering data in appropriate forms.
- Presentation: displaying results / reports.
eDiscovery functions and features
The following table explains how the Code42 platform's features can be used to accomplish tasks for each of the steps in the eDiscovery process.
|Step||Functional requirement||Code42 for Enterprise feature or resource|
|Identification||Verify or find users||
|Place users on legal hold||
Add custodians to a matter in the Legal Hold web app
|Preservation / Collection||Change deleted file retention period|
|Change archive retention period (also known as cold storage)||
|Change user roles||
|Change file inclusions/exclusions|
|Deauthorize computer (require user to sign in again)||
|Process / Review / Analyze||Search for filename or folders of interest across archives||Search using pattern matching|
|Search for MD5 across archives||Search using pattern matching|
|Analyze restore activity||
The following Code42 API resources:
|Analyze version history||
The following Code42 API resources:
|Presentation||Generate MD5 report||
|Generate files and versions report||
|View user restore history||
Remove custodians, archives, or devices
The following table explains how the Code42 platform's features can be used to remove custodians, archives, or devices from your Code42 environment.
|Code42 feature or resource||Code42 for Enterprise feature or resource|
Release from legal hold
Set system property using the Code42 API:
Additional API information
- Code42 API Documentation Viewer
- The online API Documentation Viewer provides you with the latest documentation.
- All resources are described in detail, including methods, arguments, parameters, and examples.
- Sample Code on the Code42 GitHub site
- These code examples can provide useful examples that you can adapt to your needs.
- Contact your Customer Success Manager (CSM) for enterprise support at firstname.lastname@example.org to engage our Professional Services team for help with adapting code examples or for the creation of customized scripts.
- Code42 API overview
The following examples are meant to provide insight into how the Code42 platform can be integrated with eDiscovery functions. As examples, they are not guaranteed to be suitable for any eDiscovery process without modification, review, and approval by your organization's compliance officer.
Restore history report with the administration console
As part of the eDiscovery process, you may need to determine who has restored files from a particular organization and when the restores occurred. To do this, perform the following steps:
Search the logs
As part of the eDiscovery process or other forensics needs, you may need to search the logs stored on your endpoint devices running the Code42 app.
Code42 app logs
You can access Code42 app logs in the following ways:
- Have the user send you the Code42 app logs.
- Access the device remotely and acquire the logs from the specified directory.
- From the administration console:
Code42 app log example
The endpoint file system is the only place to find a persistent copy of the path names of the files restored by a Code42 app-initiated restore. The information is stored in the file restore_files.log.*, which can be retrieved using the console as described above, or by accessing the endpoint device file system. Here is an example of the information available about the path names of restored files:
I 03/05/14 06:01AM 622091232443159553 Starting restore from CrashPlan PROe Server: 1 file (80KB) I 03/05/14 06:01AM 622091232443159553 Restoring files to /Users/joe.johnson/Desktop I 03/05/14 06:01AM 622091232443159553 /Users/joe.johnson/Desktop/test.pdf I 03/05/14 06:01AM 622091232443159553 Restore from CrashPlan PROe Server completed: 1 file restored @ 26.6Kbps
Advanced log file analytics with third party tools
Log files also can provide a source of data for third-party data analysis and visualization tools such as Splunk. We provide instructions on integrating your Code42 platform with Splunk.
List of devices from the Reporting web app
You may need to produce a list of all active (or deactivated) devices as part of the eDiscovery process.
To create and download a list of all active devices in your Code42 environment:
- Sign in to the administration console.
- Select Reporting > Device Status.
- Under Device Status, choose either Active or Deactivated.
- Click Run Report.
The code examples below are meant to provide examples of the use of the Code42 API in ways that can support eDiscovery. Code42 does not provide any guarantee on the suitability of any script or code example for any particular application. Contact sales about engaging our Professional Services team for assistance with custom scripts.
Script 1: Automate push restores
It may be necessary to perform push restores of select files or user data, in order to secure and preserve the data for eDiscovery.
Please read our article on automating push restores, which includes a sample script, detailed examples, and sample output with explanations.
Script 2: Data leak prevention and detection with the Code42 API
This script monitors and protects the archives of selected users in your Code42 environment against unauthorized or suspicious restore activity.
Other Code42 API examples
Please browse the Code42 API examples on our GitHub site for more examples of ways to use the Code42 API in your eDiscovery projects.