Who is this article for?
Incydr Professional, Enterprise, Gov F2, and Horizon, yes.
Incydr Basic, Advanced, and Gov F1, yes.
CrashPlan Cloud, no.
Retired product plans, no.
CrashPlan for Small Business, no.
Code42 Alerts let you know when important data may be leaving your company. Use the Manage Rules table to view or update the different alert rules you have in your Code42 environment that trigger these notifications.
This article is a reference guide with detailed descriptions of the rules in the Manage Rules table. You can also use Alerts to view and dismiss the alert notifications generated by these rules. For information about alert notifications, see Review Alerts reference. For information on creating and configuring alert rules, see Create and manage alert rules.
To use this functionality, Incydr users must be assigned specific roles. For more information, see Permissions for Incydr.
You must connect Code42 to at least one corporate business, cloud storage, or email service to see this download, file sharing, or attachment activity.
Use the Manage Rules screen to view, create, edit, duplicate, and delete existing alert rules that trigger alert notifications.
To add or edit alert rules:
- Sign in to the Code42 console.
- Select Alerts > Manage Rules.
Click to open the risk settings where you can set the score of each risk indicator. Scores are used to calculate the severity of each file event. For more information, see the Risk settings reference.
|b||Create rule||Creates a new rule that you can use to alert you when important data may be leaving your company.|
Creates a new rule from a pre-configured template that has recommended settings. Click one of the rule names to start creating a rule from that template, or click View all recommendations to view all of the recommended rules. You can change and customize the settings to match your specific needs.
|d||Rule name||Name entered for the rule when it was created.|
|e||Created||Date the rule was created.|
|f||Column sort||Hover over any column header to see the sort option. Click the up arrow to sort results by this column in ascending order. Click the down arrow to sort in descending order.|
|g||Last modified||Date the rule was last changed.|
Click to enable or disable rules.
|i||Actions||Click to make a copy of an existing rule or to delete a rule.|
|j||View||Click to view an alert rule's settings. For more information on editing rule settings, see Create and manage alert rules.|
|k||Rows per page||Select the number of rules to display on each page.|
|l||Pagination||Click the right and left arrows to scroll through pages of rules.|
Recommended rule templates
Code42 includes a number of pre-configured, recommended rule templates. You can quickly create rules from these templates, modifying the default settings to match your needs and environment.
To start creating a rule from a template:
- If the template you want appears in the Recommended rules list, click its name.
- Otherwise, click View all recommendations to view all recommended rule templates and then click the rule name.
When the Step 1 of 3 panel opens for that template, use it to customize the rule for your unique needs and environment. Each recommended rule template uses alert rule settings to identify the specific file activity to alert on.
Alert rule settings
To create an alert rule, you select rule settings that match the activity you want to be alerted about. You can mix and match settings as needed to target specific activity your organization has identified as carrying the most risk.
For more information about a setting, follow these links:
- Risk severity
- Filename or extension
- File categories
- File extension mismatch
- File volume
- Individual users
After adding settings to a rule, complete the rule by naming it, giving it a description, and identifying the users you want to notify when Code42 detects activity matching the rule's criteria.
For any alert rule listed in the Manage Rules table, click View to view details about that rule. You can then change the rule name, description, and add or edit the rule's settings.
Rule details vary. Specific rules may display different details than those shown in the example below.
|a||Rule name and description||
The name and description entered when the rule was created. Rule names must be unique.
Click to open the Actions menu where you can:
The settings that were added to the rule when it was created. The options selected for each setting are also listed. Click the "more" link when it appears to view all of the options selected for that setting
"No users defined" error message
An error message appears when the rule has the Individual users setting but no users have been added to that setting.
You can either either add users to the Individual users setting or remove the setting entirely. If you remove the setting, you can instead add the Watchlists setting to the rule to monitor the activity of higher-risk users on a watchlist.
|d||Add settings||Click to add a new setting to the rule and select its options.|
|e||Edit||Click to update the options selected for that setting, or to update the email addresses to which notification emails are sent when an alert is generated.|
|f||Show default settings||
By default, Code42 automatically monitors for all file activity, and uses the options you select in rule settings as filters to alert only on matching activity to reduce noise. To view the default rule settings that Code42 automatically uses for the rule, click Show default criteria.
The email addresses of the users who are automatically notified when activity that matches the rule is detected. Click Edit to update these addresses as needed.
If you do not enter any email addresses, Code42 does not send any emails but still collects information about the file activity that triggers the alert. You can view these notifications in the Review Alerts table.
Code42 automatically filters file events to alert you only about activity that occurs outside the domains, URL paths, or Slack workspaces you trust. While Code42 still records all file activity (and you can view it in Forensic Search), you are not notified by alert rules for trusted events.