Activity monitors provide a key advantage to security programs by identifying modifications to specific files or paths. These may be critical system files, paths containing valuable intellectual property, or files that must be tracked for regulatory or compliance purposes.

You can use activity monitors to observe file modifications and leverage detection engines that can pull double duty by identifying file modifications of interest.

This feature is not currently supported with Linux EDR.

Create a file modification activity monitor

You can create an activity monitor that identifies the creation, modification, or deletion of specific files on your endpoints. These monitors are dependent on the fidelity of file telemetry collected by your EDR/EPP sensor (not all sensors record file activity for all files).

1. From the navigation menu, click the Analytics dropdown, and then click File Activity Monitors.
2. Click New file activity monitor.
3. Configure your monitor by completing the form.
   Note: You can specify either whole directories or individual files for each activity monitor.
4. Click Save.

View endpoint activity matches

You can view endpoint activities that match your activity monitor. This includes information about the endpoint, user, and process associated with the activity. 

1. From the navigation menu, click the Analytics dropdown, and then click File Activity Monitors.
2. Click matches found in the Results column.
3. Review the list of matches.

Delete an activity monitor

You can delete activity monitors that are no longer valuable for your team.

1. From your Red Canary dashboard, click the Analytics dropdown, and then click File Activity Monitors.
2. Click the name of the monitor you would like to delete. 
3. Click Delete.

Trigger automation playbooks by activity monitors

You can trigger an automation playbook when an activity monitor matches endpoint activity. This enables both simple and complex automation using email, SMS, and any other supported automation actions.

1. Click Automation.
2. Click the Configure new trigger dropdown, and then select When a File Integrity Match occurs.
3. Customize the trigger and connect the associated playbooks as desired.