New Features
Support for New File Transfers Monitoring Options
We have enabled Mac support for a number of File Transfers monitoring options.
Under Monitoring Settings > Monitoring Profile:
1. You can now turn File Transfers monitoring on/off by using the YES/NO toggle switch.
Under Monitoring Settings > Monitoring Profile > File Transfers > BASIC SETTINGS tab:
2. FILE TYPES TO TRACK: You can select which file types to track. For example, TXT, DOC(S), etc.
3. FILE EXTENSIONS LIST TO TRACK: If the files you want to track aren't available under the FILE TYPES TO TRACK option, you can manually enter their extensions in this field. For example, pkg, log, etc.
If you use options 2 and/or 3, only files matching the types/extensions will be tracked by the Agent.
4. DO NOT MONITOR THESE LOCATIONS: You can exclude certain location(s), e.g., a folder from monitoring. For example, ~/Downloads, ~/Desktop, etc.
Under Monitoring Settings > Monitoring Profile > File Transfers > ADDITIONAL SETTINGS tab:
5. TRACK THE FOLLOWING OPERATIONS: You can track only certain file operations such as Copy, Rename, etc.
6. Monitoring Schedule: You can specify the date and time of the monitoring schedule.
Note that these settings will not affect the Behavior Rules.
Improvements
Improved File Monitoring Extension
Previously, in rare cases, if the Agent terminated unexpectedly, it could cause system instability and lock you out from regular file operations.
We have made some improvements to how the file monitoring works so that in case of any exceptions or abnormal termination of the Agent, it shouldn't affect the Mac file system.
Bug Fixes
Webpages Rule Alerts wouldn't Show Browser Names
Due to a bug, if you created a Webpages rule like the one below, the alert description of the rule wouldn't include the browser's name. Instead, it would show "n/a" in BI Reports > Behavior Alerts, Behavior > Alerts, or the Alerts tab in the Employee's page reports:
The bug is fixed now so that the alert description will now show the browser's name such as "chrome.exe", "safari.exe", etc.
High CPU Usage when File Monitoring was Enabled
Due to a bug, sometimes you might have noticed high CPU usage for the Teramind file monitoring process (com.teramind.systemextension.endpointsecurity):
The bug is fixed now.