EDRM mandates collection of specific metadata attributes for the data to be legally admissible. To adhere to the EDRM process, inSync client 5.5 collects the metadata attributes only with a valid Governance license. Whenever a user is put on legal hold, the EDRM-recommended metadata attributes along with the data can be exposed to any eDiscovery tool, for verifying the authenticity of the electronic data.
Following are the advantages:
- Assess authenticity of data
The EDRM metadata attributes help organizations to determine origin, context, authenticity, and distribution of the electronic data across the organization and endpoints. This lets you ensure that the data retained during legal hold is valid, is not tampered, and follows the EDRM process in cases of internal investigations, compliance, and legal admissibility purposes.
- Filter data
The attributes help to configure the connectors and identify the dataset within the eDiscovery tool. Users can filter through the WebDAV-exposed data by using the additional metadata attributes, and find the content of interest.
- You are required to upgrade your existing inSync client to version 5.5 for this functionality to be available with your inSync deployment.
- The metadata attributes would be collected only if the Governance license is valid, and up to 30 days from the expiry of the license.
- The EDRM-recommended metadata attributes will be collected from Windows and Mac devices only.
- The metadata attributes will be collected for regular files only, that is, files which are not special files or directories.
Metadata attributes that are collected
To adhere with the eDiscovery reference model, following metadata attributes are collected from inSync client and exposed via WebDAV:
File or folder name
The name of the file or folder. The file name will be exposed as part of file path via WebDAV.
The absolute path at the Microsoft DOS. It will be exposed from WebDAV.
|File extension||The suffix that is attached to the file name, which indicates the format of the file.|
|File modified||The time when the file was last modified, which will be backed up from the file system.|
|File owner|| |
The user who is logged on to the computer, and will be collected from the file system. For example, Domain\User or Group\User.
Permission of a file, which provides information about the file's view or edit access rights to specific users or group of users.
|Logical size|| |
The exact size that is consumed by the file on the computer's hard disk, and is displayed in bytes.
|Creation time|| |
The time when the file was created, which will be backed up from the file system.
|Last accessed time|| |
The time when the file was last accessed, which will be backed up from the file system.
SHA1 hash codes
The Secure Hashing Algorithm-1 (SHA-1) hash code is a specific and unique construction that is used to calculate the message authentication code. SHA-1 is a proof that the file is not tampered.
How the metadata attributes can be used by HTTP connectors within eDiscovery tools
inSync client collects the EDRM-recommended metadata attributes of data that is backed up from devices of users who are on legal hold. inSync then provides WebDAV access to the preserved data and associated metadata. eDiscovery HTTP connector can be used to collect the preserved data and metadata attributes, parse through the data, and help data custodians to analyze and act on them.
For more information about creating a legal hold policy and accessing the WebDAV using AccessData, see Create legal hold using inSync. For more information about how AccessData can be integrated with Druva inSync to mine data under inSync’s legal hold, see Using Druva inSync with AccessData.
For more information about creating a legal hold policy and accessing the WebDAV using Recommind, see Create legal hold using inSync. For more information about how Recommind can be integrated with Druva inSync to mine data under inSync’s legal hold, see Using Druva inSync with Recommind.