Who is this article for?
Incydr Professional, Enterprise, Horizon, and Gov F2, yes.
Incydr Basic, Advanced, and Gov F1, yes.
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 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 use this functionality, Incydr users must be assigned specific roles. For more information, see Permissions for Incydr.
- Case data is secured in the Code42 cloud in accordance with the security data collection details in the Code42 architecture article. For Incydr Basic, Advanced, and Gov F1, file contents are stored separately from preservation (backup) data.
To access cases:
- Sign in to the Code42 console.
- Select Cases.
- Click any column heading to sort the list by that column.
- Click any entry in the table to view detailed case information.
|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 Insider Risk Analyst or Insider Risk Admin 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.
Indicates when the case was, or will be, archived:
The automatic archival date varies based on your product plan and ranges from 90 to 365 days after the case's Created date.
Cases created before October 18, 2022
Automatic case archival was introduced on October 18, 2022. To allow you enough time to export older cases, cases created before October 18, 2022 use this date for the purposes of calculating the automatic archival date.
For example, if the Automatic cases archival value for your product plan is 180 days, cases created before October 18, 2022 will be automatically archived 180 days after October 18, 2022 (on April 16, 2023).
Click to filter the case list by:
|i||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.
Click to export the case. Choose one or more components:
If you select Files, or select more than one component, the case is exported as a .zip file.
Click to archive this case.
Click to permanently delete this case. Deleting a case:
|f||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 attributes synced from your provisioning provider, risk context, and a link to the user's profile.
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.
|j||User attributes||Displays user attributes synced from your provisioning provider, including Department, Title, Location, and Manager. If your Code42 environment does not use provisioning, these attributes do not appear and cannot be added manually.|
If the user is on the Departing watchlist, displays the date entered for the employee's departure. If no date was entered, no value is listed.
|l||Notes||Displays notes from the User Profile.|
|m||Edit subject||Edit which user is associated with this case.|
Provides a place for you to enter notes about the case.
|o||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.
File event limit
Each case is limited to 10,000 file events.
Indicates the risk severity for the file event, based on observed risk indicators. Higher scores denote higher severity.
To learn more about how risk scores are calculated, see Risk settings reference.
|r||Risk indicators||List of risks that determine the overall severity and score for this event. To learn more about risk indicators and how risk scores are calculated, see Risk settings reference.|
|s||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).|
|t||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.
|v||Remove file event||Click to remove the event from the case.|
|w||View file event details||
Click to view all metadata for the event, including a link to download the file contents. (If the file contents are available for download, the link appears in the File > Filename section.)
For in-depth descriptions of all metadata fields, see the File event metadata reference.