Who is this article for?
CrashPlan for Enterprise, no.
Code42 for Enterprise, no.
CrashPlan for Small Business, no.
This article applies to Code42 cloud environments.
Cases helps you manage and respond to security investigations with tools that collect, organize, and retain user file activity. This reference guide describes the information available in the Response > Cases section of the Code42 console.
Specifically, Cases enables you to:
- Assemble evidence related to an investigation
- Add file events from Forensic Search
- Add notes to provide additional context
- Summarize and share findings with others in your organization
To access cases:
- Sign in to the Code42 console.
- Select Response > Cases.
- Click any column heading to sort the list by that column.
- Click any entry in the table to view case details.
|a||Create case||Click to create a new case.|
|b||Case name||The name of the case.|
Indicates the status of the case.
The Code42 username/email address of the security analyst or administrator assigned to investigate this case. Only users with the Customer Cloud Admin or Security Center User roles can be assigned to a case.
Assignee is optional. Cases without an assignee display Unassigned.
|e||Created||Date and time the case was created. Dates appear in Coordinated Universal Time (UTC).|
Date and time the case was last modified. Dates appear in Coordinated Universal Time (UTC).
For cases with the status Closed, the Last modified date indicates when the case was closed.
Click to filter the case list by:
|h||View case details||Click to view case details (see below), including case subject, findings, and all file events and associated metadata.|
|a||Case name||The name of the case.|
Indicates the status of the case.
|c||Close case||Click to close this case. Once you close a case, it cannot be re-opened or modified.|
Provides information about the person being investigated in this case, including:
Provides general information about the case:
Click the edit icon to update the Case name or Description.
Click to view the User Profile, which highlights file activity for this user over the past 90 days that may indicate a file exfiltration risk.
|g||Edit subject||Edit which user is associated with this case.|
Provides a place for you to enter notes about the case.
|i||Edit findings||Click to edit the findings. This field supports basic html formatting, including titles, bold, italics, and numbered and bulleted lists.|
Lists all file events included in this case.
To add file activity to a case, from Forensic Search, click the Add to case icon for a file event.
|k||Date observed||Date and time Code42 detected the file event. The file metadata for the event is based on this detection time. The time is based on the device’s system clock and reported in Coordinated Universal Time (UTC).|
|l||Exposure type||The type of exposure risk.|
|m||Filename||The name of the file, including the file extension.|
The file location on the user's device.
Endpoint file events only. Cloud and email events do not include a file path.
|o||Remove file event||Click to remove the event from the case.|
|p||View file event details||
Click to view all metadata for the event, including a link to download the file. (If the file is available for download, the link appears in the File > Filename section.)
For in-depth descriptions of all metadata fields, see the Forensic Search event details.