Forensic Search reference guide

Last updated
Save as PDF
Share
1. Share
2. Tweet

Who is this article for?

Incydr Professional and Enterprise

Incydr Basic and Advanced

CrashPlan Cloud

CrashPlan for Small Business

Incydr Professional and Enterprise, yes.

Incydr Basic and Advanced, yes.

CrashPlan Cloud, no.

Other product plans, yes.

CrashPlan for Small Business, no.

This article applies to Code42 cloud environments.

Forensic Search administrator guide Step 3 of 6

Overview

Forensic Search is a powerful search interface that enables security teams to monitor and investigate suspicious file activity. Forensic Search provides detailed visibility about files:

Stored on user devices, including files not selected for backup
Stored in corporate cloud services, such as Google Drive and Microsoft OneDrive
Synced to personal cloud services, such as Box, Dropbox, iCloud, and OneDrive
Moved to removable media
Sent as email attachments in Microsoft Office 365 and Gmail
Sent to printers (Mac and Linux only)

This enables security personnel to gain a clearer understanding of file activity throughout the organization.

In order to see results in Forensic Search, you must first enable File Metadata Collection.

For cloud services and email services configuration instructions, see Introduction to adding data connections.

Forensic Search

To access Forensic Search:

Sign in to the Code42 console.
You must have a role with permissions that allow access to Forensic Search.
Select Forensic Search > Search.

What is a "file event"?
Forensic Search reports on file events detected by Code42. A file event is defined as any activity observed for a file. For example, creating, modifying, renaming, moving, or deleting a file generates an event for that file. Events are reported for both user and system actions.

Search results

Forensic Search results

Item		Description
a	Load Saved Search	Displays a searchable list of searches created and saved by users in your Code42 environment. Click the name of a search to immediately execute that search and display the results.
b	Date selector	All searches must specify a date range. Select one the following options: Events observed in the last: Select a pre-defined time period ranging from the past 15 minutes to the past 30 days. This is especially useful for saved searches because they can be used at any time in the future and still search the same relative time period. Events observed on or after: Search events on or after a specific date and time. To include all events on the start date, enter a time value of 00:00:00. Events observed on or before: Search events on or before a specific date and time. To include all events on the end date, enter a time value of 23:59:59. Events observed is in range: Search events between specific start and end dates/times. Enter a time range of 00:00:00 to 23:59:59 to include all events on the start and end dates. Times are evaluated as Coordinated Universal Time (UTC).
c	Search filters	Select an item from the menu or type the name of a filter to include in your search: Event Event type Source Risk indicator Process user Trusted activity Username Print Printer name Print job name File Filename File path File size File category File owner MD5 hash SHA256 hash File classification Device Hostname Username (signed in to device) IP address (public) IP address (private) Remote activity Cloud (visible only with licensing for one or more cloud service data sources) Directory ID Actor Shared with users Shared File exposure changed to Exposure (visible only with licensing for the endpoint data source) Exposure type Destination category Destination name Device vendor Device name Device media name Device volume name Device partition ID Device serial number Executable name Active tab URL (browser) Active tab title (browser or other app) Sync destination Sync username Email (visible only with licensing for the email data source) Policy names (Microsoft Office 356 DLP data connection only) Subject Sender From Recipients
d	Search operator	Search operator options vary based on the search filter. Single value Is: Returns events that match the search criteria Is not: Excludes events that match the search criteria Exists: Returns events including any value for the search criteria Does not exist: Returns events with no value for the search criteria Multi-value (OR) Includes any: Returns events that match any item in the list of search criteria. This search is evaluated as though the "OR" operator exists between each value. Includes none: Returns events that do not match the items included in the list of search criteria. For File Size, select is greater than or is less than.
e	Value	Defines the search criteria. Searches are case-insensitive. For multi-value searches (includes any or includes none), enter each value on a separate line. Do not enter a comma-separated list. Use the * wildcard character to search for a partial string. Use the ? wildcard to replace a single character. File size For example: Enter the search string expenses* to return events for any filename beginning with the phrase expenses, such as expenses.xls, expenses.doc, expenses to review.txt, and so on. Enter the search string expenses201?.xls to return events only for filenames matching that exact pattern, such as expenses2016.xls, expenses2017.xls, and so on. Wildcards are supported for all search filters except MD5 hash, SHA256 hash, IP address, and file size. Avoid starting a search term with a wildcard Entering a search string that begins with a wildcard or contains only wildcards is not recommended (for example, `filename is ` or `file path is documents`). These searches may take a long time to complete and can return many millions of results, which are not practical to review or export. File Path searches require a trailing slash (/) or wildcard at the end of the search term. For example: Enter /Users/Clyde/ExampleFolder/ to view only events for files in ExampleFolder. Enter /Users/Clyde/ExampleFolder* to view events for files in ExampleFolder and any subfolders. For File Size, enter a whole number (decimals are not supported) and then select a unit of measurement (bytes, kB, MB, or GB).
f	Remove search criteria	Removes this search criteria.
g	Add search criteria	Adds another item to the search criteria. Search results only return events that match all criteria.
h	Save As	Adds the current search criteria to the list of saved searches. When viewing an existing saved search, you can either Save As a new search or Save changes under the same name.
i	Update Search	Performs a search based on the current search criteria.
j	Modify columns	Displays a list of available columns. Select or deselect items to customize the format of your search results.
k	Export results	Downloads the current search results to a CSV file. Exports are limited to 200,000 results. Only includes the fields applicable to your product plan. The CSV file is UTF-8 encoded. The CSV file also includes a leading byte order mark (BOM) specifying the file is UTF-8 encoded. If you use customized scripts to parse the CSV export, you may need to account for the BOM at the start of the file to ensure column headings are read correctly.
l	Select all	Click to select or deselect all search results on the current page. When multiple results are selected, click Add to case in the upper right to add them all to a case.
m	Column sort indicator	Indicates how the results are currently sorted and displayed. Click any column heading to sort by that column. Click the heading again to switch between ascending and descending order.
n	Event selector	Click to select a file event. When multiple results are selected, click Add to case in the upper right to add them all to a case.
o	Risk indicator	Denotes file activity that may indicate a greater insider risk, such as a file extension that does not match the file contents, or activity performed outside a user's typical active hours.
p	Add to case	Click to add the file event to a Case: Select an existing case from the list of available options. Click Create case to create a new case and add this event to it. To view the case, click the case name in the confirmation message that appears upon adding the event. Alternatively, navigate to Response > Cases. Only available in Incydr product plans.
q	View details	Displays all metadata for the file event. See the sections below for detailed descriptions of each field.
r	Events per page	Select to display 10, 25, 50, or 100 events per page.

File event details

To view file event details within search results:

From the list of search results, click View details to show all metadata for a file event.
Event details slide in from the right.
Within the Event details, scroll to view all metadata for the event. See the sections below for detailed descriptions of each field.

Expanded Forensic Search results

Missing file metadata
Some file events may not capture all metadata. Missing metadata is indicated by a dash (–) in the field. Most commonly, this occurs if the file did not exist on disk long enough for Code42 to capture all the metadata.

Event

The Event section provides summary information about the event, including date observed, event type, and event source.

Forensic Search results - event details

Item	Description
Risk indicators	Indicates file activity that may be a greater risk. File mismatch highlights files with extensions that do not match the file contents (for example, a file with the .jpg extension that contains source code content). This may indicate an attempt to disguise and exfiltrate data. Off hours indicates the file activity occurred outside the user's typical active hours. The off hours determination is unique to each user and is based on the user's past patterns of behavior. For more details, see Introduction to risk indicators.
Date observed	Endpoint file activity Date and time that the Code42 service on the device detected an event for the file. 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). File activity can be detected in two ways: Real-time: Reported by the operating system as changes occur. Scanner: The Code42 app performs a scan once per day to identify any changes that might have been missed by the real-time file watcher. The scan runs once every 24 hours and cannot be configured. Cloud file activity Date and time that Code42 detected activity in the cloud service. This may not be the exact time the activity occurred, but should be within 5 minutes. The time is reported in Coordinated Universal Time (UTC). Email file activity Microsoft Office 365: Date and time Code42 was notified that an email attachment was detected by a data loss prevention (DLP) policy, as defined in your Microsoft Office 365 Security & Compliance Center. Gmail: Date and time Code42 was notified that an email was sent with any attachment. This may not be the exact time the email was sent, but should typically be within 5 minutes. The time is reported in Coordinated Universal Time (UTC).
Event type	The type of file event observed: New file: This is the first event detected for this filename and file path on the device (for endpoint events) or in the cloud service (for cloud events). New file events are reported when: A new file is created (endpoint) or uploaded (cloud). An existing file is moved to a new location. File Metadata Collection is initially enabled for a cloud service. As part of the initial scan, New file events are created for all existing files. Modified Endpoint events: File contents changed for a file Code42 already detected with this filename and file path on the device. Cloud events: The cloud service detected a new file version. This occurs when file contents are modified or the file is renamed, moved, or shared. No longer observed: The filename for a previously detected file no longer exists in this file path on the device (for endpoint events) or in the cloud service (for cloud events). The metadata shown for this event is the metadata from the last New file or Modified event. No longer observed file events are reported when: A file is deleted. A file is moved or renamed. Browser or app read: The file was opened in an app that is commonly used for uploading files, such as a web browser, Slack, AirDrop, FTP client, or curl. Emailed: The file was sent as an email attachment via Microsoft Office 365 and detected by a data loss prevention (DLP) policy, as defined in your Microsoft Office 365 Security & Compliance Center. The file was sent as an email attachment via Gmail. Printed: The file was sent to a printer.
Source	The source of the file event: Endpoint: The file activity occurred on a user device. Google Drive: The file activity occurred in Google Drive. OneDrive: The file activity occurred in OneDrive. Box: The file activity occurred in Box. Office 365 Email: The file was sent as an attachment in Microsoft Office 365 email. Gmail: The file was sent as an attachment in Gmail. This field appears only if you are licensed for more than one data source.
Process user	The username of the process owner, as reported by the device's operating system. Applies only to Printed* and Browser or app read events.*
Trusted activity	Indicates if this is activity you trust, as defined by your Data Preferences. True: The activity occurred on your list of trusted domains. False: The activity occurred outside your list of trusted domains. Applies only to Endpoint and Email events. For Cloud events, use the Exposure Type filter Outside trusted domain.
Username	Indicates the user associated with the event for the following sources: Endpoint: The Code42 username used to sign in to the Code42 app on the device. Code42 usernames must be email addresses. Cloud: The cloud service username of the person who caused the event. In rare cases, the Username may be blank if it is not provided by the cloud service. Email: The address of the person who sent the message. If the Username matches a Code42 user, a View profile link is included. Click to review the User Profile, which highlights file activity for this user over the past 90 days that may indicate a file exfiltration risk.

Print

The Print section shows print event details and a link to download an image of the printed file. The Print section only appears for Printed event types.

Print detection is only supported on Mac and Linux devices and requires Code42 app version 8.0 or later.

Printer file event details

Item	Description
Printer name	The name of the printer.
Print job name	The name of the print job. This is often the name of the printed document. Click Download file to download an image of the printed file.

File

The File section provides a link to download the file, along with details such as the file's name, path, owner, and other metadata.

Forensic Search results - file event details

Item	Description
File type mismatch (not pictured)	If Code42 detects the file contents do not match the file extension, a File Type Mismatch row appears with details about the mismatch (for example, the file extension is .jpg but the file contains source code content). This may indicate an attempt to disguise and exfiltrate data.
Filename	The name of the file, including the file extension. If applicable, links to download the file appear below the filename. Endpoint file activity If the file is included in the user's Code42 backup file selection, or among files backed up by other users in your Code42 environment, links to download the file contents appear. Depending on available versions, one or both links may appear: Most Recent Version: Downloads the most recent version of the file in the backup archive. Exact Match: Downloads the version of the file in the backup archive which matches the MD5 hash of the this specific file event. If the most recent version also matches the MD5 hash for this event, only the Exact Match link appears. You must be signed in as a user with either the Customer Cloud Admin* or Security Center - Restore role to download files.* Cloud file activity Click the filename to open the file in the respective cloud service's file viewer. To view the file: The file must still exist in the cloud service. You must have permission to access the file. Depending on how the file is shared, you may have to sign in to your cloud service's user account before viewing it. For example, for Box, you must be logged in to the "Admin Console" for the link to be valid. Email file activity Click the filename to open the file attached to the email. (Microsoft Office 365 email data connections only)
File path	The file location on the user's device. Endpoint file events only. Cloud and email events do not include a file path.
File category	The type of file, as determined by the file extension and file contents. For example, .gif, .jpg, and .png files are categorized as Image files. For a complete list of file categories and the specific file types in each category, see Forensic Search file categories.
File size	Size of the file. Not available for Google file types (for example, Google Sheets or Google Docs).
File owner	The name of the user who owns the file, as reported by the device's file system (for endpoint events) or the cloud service (for cloud events).
MD5 hash	The MD5 hash of the file contents. If the file cannot be hashed, an error message explains why. Not available for: Google file types (for example, Google Sheets or Google Docs). Files in cloud services that have not been modified since Code42's initial extraction. Files over 3 GB (Code42 app version 8.5 and later).
SHA256 hash	The SHA256 hash of the file contents. If the file cannot be hashed, an error message explains why. Not available for: Google file types (for example, Google Sheets or Google Docs). Files in cloud services that have not been modified since Code42's initial extraction. Files over 3 GB (Code42 app version 8.5 and later)
File created	File creation timestamp as reported by the device's operating system or the data connection. This appears in Coordinated Universal Time (UTC). Mac and Windows NTFS devices only.
File modified	File modification timestamp as reported by the device's operating system or the data connection. For endpoints, this only indicates changes to file contents. Changes to file permissions, file owner, or other metadata are not reflected in this timestamp. For cloud data connections, this timestamp reflects when the file's contents, sharing permissions, name, or storage location changed. This timestamp is not supported for for email data connections. This appears in Coordinated Universal Time (UTC).
File classification (not pictured)	File classification data, as reported by your external data classification vendor. Classification data contains two values: Classification: The classification value applied to the file. For example: Confidential. Vendor: The name of the vendor that classified the file. For example: Microsoft Information Protection (MIP). A single file may have more than one classification. Applies only to endpoint* file events.*

Device

The Device section provides detailed information about the device, including the hostname, IP address, and other metadata.

Device details are only visible only if you are licensed for the endpoint data source. Device details do not apply to cloud events.

	Description
Hostname	The device name reported by the device's operating system. The hostname may be different than the device name in the Code42 console. You must enter the complete hostname. Wildcard searches are not supported.
Fully qualified domain name	Fully qualified domain name (FQDN) for the user's device at the time the event is recorded. If the device is unable to resolve the domain name of the host, it reports the IP address of the host.
Username (signed in to device)	The username signed in to the device when the file activity was observed, as reported by the device’s operating system. For devices with multiple user accounts, this helps you identify the user responsible for the file activity.
IP address (public)	The external IP address of the user's device, as seen by Code42 via the device's outbound connection to the Code42 cloud. If the IP address is not included in your list of in-network IP addresses, it is labeled Remote activity.
IP address (private)	The IP address of the user's device on your internal network. This includes: Network interfaces Virtual network interface controllers (VNICs) Loopback/non-routable addresses (for example, 127.0.01) If there is more than one active network interface, this displays a list.

Cloud

The Cloud section provides detailed information about how and where the file is exposed in the cloud service.

Visible only with licensing for one or more cloud service data sources. Cloud details do not apply to endpoint events.

Item	Description
Directory ID	Unique identifier of the cloud drive or folder that contains the file. Search by this ID to find events for files within the same drive or folder. Google Drive files that exist at the root level of the cloud drive display the value None. Some cloud services allow users to add a file to multiple folders, so Directory ID may display a list of values.
Actor	The cloud service username of the person who caused the event. In some cases, if multiple users interact with the same file within a 5-minute window, only the last user to take an action on the file is displayed.
Shared with users	At the time the event occurred, the list of users who have been granted to access the file. Click View to display a searchable list of usernames. This only includes users the file is explicitly shared with. It does not capture users who only accessed a shared link. This list can include: Individual email addresses Group email addresses First and last name (for OneDrive users without an email address) Google Drive users without email addresses (for example, service or integration accounts with sharing permissions) are not listed.
Shared	Indicates the shared status of the file at the time the event occurred, but does not capture whether or not a link to the file has been shared: True: One or more users were granted explicit access to the file. False: No users were granted explicit access to the file.
File exposure changed to	Identifies an increase in exposure due to a change in sharing permissions for the file: Public via direct link: The file is not listed in public search engines, but is available to anyone who accesses the link. Users do not need to be signed in to a cloud services account to see the file. Public on the web (Google Drive only): The file is available on public search engines and accessible to the entire World Wide Web. Users do not need to be signed in to a cloud services account to see the file. Outside trusted domain: The file is shared with a domain not included in your list of Trusted Domains. Because Code42 prioritizes file-based monitoring, detection of sharing permissions changes to folders in Box and OneDrive may be delayed. For this reason, the File exposure changed to value may be blank when a file inherits a permissions change from its parent folder. This avoids attributing that change to an incorrect actor.

Exposure

The Exposure section provides detailed information about where the file is exposed.

Forensic Search results - exposure event details

Each Exposure Type displays different metadata
No single event contains values for all items in the table below. For example, the image above does not include removable media metadata (such as Device Name), because this exposure event was detected in a web browser, not on removable media.

Removable media metadata
Available values vary based on the device manufacturer. In some cases, one or more values may not be supplied by the manufacturer or provided by the device's operating system.

That's why we provide multiple pieces of information for removable media events. For example, if a drive does not report a serial number, you may be able to reference a combination of Capacity, Device Partition ID, and other unique fields to confirm the drive's identity during an investigation.

Item Description

Exposure type

The type of exposure risk, based on both cloud and device activity.

In cloud services

The exposure status of the file at the time the activity was observed.

Public on the web (Google Drive only): The file is available on public search engines and accessible to the entire World Wide Web. Users do not need to be signed in to a cloud services account to see the file. The method used to share the file appears in the Google Drive UI as "Public on the Web."
Public via direct link: The file is not listed in public search engines, but is available to anyone who accesses the link. Users do not need to be signed in to a cloud services account to see the file. The method used to share the file appears in the cloud service UI as follows:
- Box: "People with the link"
- Google Drive: "Anyone with the link"
- Microsoft OneDrive: "Anyone with the link"
Shared with corporate domain: The file is not publicly accessible, but is available to all users on your corporate domain. For Google Drive, this includes both files that users on your domain can find on their own, and files that require users to know the specific link. The method used to share the file appears in the cloud service UI as follows:
- Box: "People in your company"
- Google Drive: "Anyone at <your company> with the link"
- Microsoft OneDrive: "People in <your company> with the link"
Outside trusted domain: The file is shared with a domain not included in your list of Trusted Domains. Applies only to Cloud file activity. For Endpoint and Email activity, use the Trusted Activity filter.

On the device

Windows and Mac devices only

Activity on removable media: The file activity occurred on an external device, such as an external drive or memory card.
Read by browser or other app: The file was opened in an app that is commonly used for uploading files, such as a web browser, Slack, AirDrop, FTP client, or curl.
Synced to cloud service: The file exists in a folder on the device used for syncing with one of these cloud services:
- Apple iCloud
- Box
- Box Drive
- Dropbox
- Google Backup and Sync
- Google Drive
- Microsoft OneDrive

Destination category

The general category of where the file was sent. Categories include:

Cloud Storage: The file was sent to a cloud service, either via a web browser upload or synced via an installed app.
Device: The file was sent to another device via AirDrop.
Email: The file was uploaded to an email provider via a web browser.
Messaging: The file was shared via a messaging service.
Social Media: The file was shared via social media. This does not necessarily mean it's posted publicly; for example, the file could have been sent in a direct message on LinkedIn, etc.
Source Code Repository: The file was uploaded to location typically used for storing code files.
Uncategorized: The destination could not be matched to one of the above categories.
Unknown: Unable to determine the destination. On Macs, this may indicate Code42 does not have the required permissions to collect the destination details.

If the user accessed more than one tab while uploads were in progress, the destination category may indicate Multiple possibilities. Review the Active tab titles and URLs to identify all possible destinations.

Applies to Read by browser or other app and Synced to cloud service events.

Destination name

The specific location where the file was sent. Example names for each category are listed below, but this is not a complete list:

Destination Category	Example Destination Names
Cloud Storage	Dropbox, OneDrive, Box
Device	Clyde's iPhone, Carmen's MacBook Pro
Email	Gmail, Outlook, Comcast
Messaging	Slack, Teams, WhatsApp
Social Media	Facebook, Twitter, Reddit
Source Code Repository	Bitbucket, Github

If the user accessed more than one tab while uploads were in progress, the destination name may indicate Multiple possibilities. Review the Active tab titles and URLs to identify all possible destinations.

Applies to Read by browser or other app and Synced to cloud service events.

Bus type

The type of removable media connection. For example: USB, eSATA, Thunderbird.