Skip to main content

Rule Example (Printing): Restrict large document printing

Updated today

Introduction

You can use the Printing rules to control printer usage. For example, you can restrict which documents can be printed, or warn users about large print jobs to help reduce waste.

Rule Walkthrough

The simple rule below shows you how to block large documents from being printed by restricting the maximum number of pages allowed per print job.

Setting Up the Rule

General Settings

1. Assign a Rule Name. For example, “Restrict print volume”.

2. Select a Parent Policy. For example, “Admin Policy”.

3. Select “Activity” for Rule Type.

4. Select “Printing under Select the type of activities.

Helpful Resources:

Employees

6. Turn it off the Inherit targets from Parent Policy option to manually select the rule's targets. Then, select employees, departments and/or computers for the rules target from the Assign to field. In this case, we selected a computer.

5. Alternatively, you can keep the Inherit targets from Parent Policy option turned on to use the policy’s default targets.

7. Optionally, you can exclude targets in the Exclude from rule field.

Helpful Resources:

Printing

8. A default condition block, "Condition 1," should already be added to the rule. If it's missing, click the New Condition button, then add the On-screen text criterion. Configure the condition as follows:

Condition 1

9. In the On-screen text field, enter:

[0-9]{4}\s*-?\s*[0-9]{4}\s*-?\s*[0-9]{4}\s*-?\s*[0-9]{4}

Then, select the Matches regex condition.

Helpful Resources:

Actions

10. Select the Notify action.

11. Select users you want to notify when the rule is violated.

The time when the OCR rule will trigger depends on how quickly your instance can process the screen recording data (session mining).

You can find your instance's Session mining delay status on the Configurations > Settings > OCR screen.

Help Reference:

Rationale for the Rule

This rule uses Teramind's patented OCR engine to scan the entire screen for sensitive data, which is crucial for capturing information in images, RDP sessions, or un-parsable apps where detecting content might be difficult using other methods.

Its effectiveness relies on using a Matches regex condition which defines the exact pattern of sensitive data to detect 16-digit credit card numbers in several formats, such as: "1234567890123456", "1234-5678-9012-3456", " or "1234 5678 9012 3456".

The Notify action ensures the administrator receives an email notification when the pattern appears on a user's screen.

Did this answer your question?