Endpoint Monitoring settings reference
Who is this article for?
Incydr, no.
CrashPlan for Enterprise, no.
Code42 for Enterprise, yes.
CrashPlan for Small Business, no.
Overview
This article contains a reference guide for settings used to enable endpoint monitoring for your entire Code42 environment. To access endpoint monitoring, navigate to Settings > Endpoint Monitoring.
Endpoint Monitoring
| Item | Description | |
|---|---|---|
| a | Removable media |
Enables or disables scanning of file metadata on all removable media, such as USB drives or SD cards. |
| b |
Cloud Sync Applications (version 8.2 and later)
Cloud service (versions 6.0.x - 7.0.5) |
Enables or disables detection of syncing files using these cloud storage apps:
|
| c |
Browser and other Application Activity (version 8.2 and later)
Application Activity (version 7.0 and later)
Browser activity
File upload |
Enables or disables detection of files accessed by web browsers and other applications (for example, uploading attachments to web-based email or downloading files via FTP). This may also include other instances of apps accessing a file, such as opening a local file to view it in a web browser without actually uploading it. Devices using Code42 app versions older than 7.0.0 only monitored activity in web browsers, and only on Windows devices. Version 7.0.0 expands upload and download detection to include Macs as well as other applications, such as Slack, FileZilla, FTP, and cURL. |
| d |
File restore (versions 7.x and earlier) |
Enables or disables detection of file-restore activity, such as restores of files belonging to other users. |
| e |
Pattern matching (versions 7.x and earlier) |
Enables or disables detection of dangerous, malicious, or sensitive file metadata and file contents based on specified patterns using the YARA rule framework. Pattern matching requires creating a YARA rule file and manually deploying it to each user device. Unlike the other types of endpoint monitoring, pattern matching only searches files included in the user's backup file selection. Pattern matching can scan for MD5 hash and filename matches on any file, but does not extract file contents of binary or compressed files. Practically speaking, this means pattern matching only searches the contents of plain text files, unless you create a rule targeting a specific binary string. |