New Features
Behavior Rules: Applications
Agent support for the Applications Activity-based rules are now available.
You can create a Applications rule by clicking the the ADD RULE FOR THIS POLICY button on the Behavior > Policies screen:
Here are a few things to note:
The rule currently supports only the Application Name condition.
Only the Block and Warn rule actions are supported at the moment.
Rule violation events will be captured on the BI Reports > Behavior Alerts, Monitoring > Webpages and Applications and other relevant reports.
Please see the Rules Guide >Activity Rules: What Activities Can You Detect? > Applications section to learn more.
Behavior Rules: Printing
Agent support for the Printing Activity-based rules are now available.
You can create a Printing rule by clicking the the ADD RULE FOR THIS POLICY button on the Behavior > Policies screen:
Here are a few things to note:
The rule currently supports all the conditions: Number of Pages, Document Name, and Printer Name.
Only the Block and Warn rule actions are supported at the moment.
Rule violation events will be captured on the BI Reports > Behavior Alerts, Monitoring > Printing and other relevant reports.
Please see the Rules Guide >Activity Rules: What Activities Can You Detect? > Printing section to learn more.
Behavior Rules: Keystrokes
Agent support for the Keystrokes Activity-based rules are now available.
You can create a Keystrokes rule by clicking the the ADD RULE FOR THIS POLICY button on the Behavior > Policies screen:
Here are a few things to note:
The rule currently supports the Text Typed, Word Typed, and the Application Name conditions.
Only the Block and Warn rule actions are supported at the moment.
Rule violation events will be captured on the BI Reports > Behavior Alerts, Monitoring > Keystrokes and other relevant reports.
Please see the Rules Guide >Activity Rules: What Activities Can You Detect? > Keystrokes section to learn more.
Monitoring Settings: Printing
The following Printed Doc monitoring settings are now supported by the Agent:
If the MAXIMUM CAPTURE DOCUMENT SIZE (PAGES) is set, the Agent will not capture any documents that exceed the number of pages specified in the field. In the above example, any document which has more than 50 pages will not be captured.
The EXCLUDED PRINTER NAME (REGEXP) lets you exclude any printers that matches the specified regular expression. In the above example, any printer that starts with the name 'epson' will not be monitored.
Note:
You can toggle the document capture by using the CAPTURE ACTUAL DOCUMENT option. If you enable it, you can then view the documents being printed and download copies of them from the BI Reports > Printing screen:
Please see the User Guide >Monitoring Settings > Editing Printed Doc / Printer Settings section to learn more about these settings.
Agent: Configure Auto-Update
You can now enable/disable auto-update of the Agent from its configuration file (usually located at this location: /usr/local/teramind/agent/etc/agent.conf).
To prevent auto-update of the Agent, add this line in the agent.conf file:
disable-autoupdate=1
To enable the auto-update, use this line instead:
disable-autoupdate=0
Improvements
Cached Behavior Policies and Rules
The Agent now stores a copy of the Behavior Policies and Rules locally to speed up their processing and better offline enforcement.
Bug Fixes
Revealed Agent on M1 Mac Crashes After Pressing the Start/Stop Button
On an M1 Mac, macOS Monterey, Revealed Agent version 230 would crash with the following error message when the user clicked the Start and then the Stop button repeatedly:
The bug is fixed now.
Printed Documents Not Captured
Due to a bug, printed documents weren't being captured even when the CAPTURE ACTUAL DOCUMENT setting on the Monitoring Settings > Printed Doc was turned on:
The bug is fixed now.
HTML Alert Messages Displayed Incorrectly
If you used the CUSTOM USER ALERT HTML option on the Settings > Alerts screen to create a HTML alert template and then used the USE HTML TEMPLATE option with a rule's Warn/Block action, the alert would be shown incorrectly to the user:
The bug is fixed now so that the HTML alert messages are rendered with the correct tags and elements.