For the complete documentation index, see llms.txt. This page is also available as Markdown.

Print Protection

What is Print Protection?

Print Protection is a Data Loss Prevention (DLP) capability in FenixPyre that prevents sensitive data from being leaked through physical or digital printing channels. It detects and blocks printing actions performed on FenixPyre encrypted files.

Print Protection is part of FenixPyre's DLP suite, alongside Clipboard Protection, Screenshot Protection, and Dynamic Watermark Display.


What Problem Does Print Protection Solve?

Printing is a common way for protected information to leave the digital boundary that encryption provides. A user can encrypt a file at rest yet still produce an unprotected paper copy or a PDF export. Print Protection closes this gap by stopping print operations on encrypted content before sensitive data can be reproduced.


How Does It Work?

When enabled, Print Protection detects and blocks the following actions for FenixPyre encrypted files:

  • Standard printing to a physical printer.

  • Print to PDF and similar export-to-file print operations.

  • Virtual printing actions.

Print Protection is enabled together with Clipboard Protection and Screenshot Protection. When an administrator enables the Clipboard Protection Service in the user policy, all three protections are activated together.


Configurations

Print Protection uses the following Windows registry value.

Registry path: HKEY_LOCAL_MACHINE\Software\FenixPyre\Parameters

The setting uses the REG_MULTI_SZ type.

Setting
Description
Example values

FPDlpMonitoredProcesses

Enforces print protection for these processes.

WINWORD.EXE, EXCEL.EXE, POWERPNT.EXE, ACRORD32.EXE, ACROBAT.EXE, ACAD.EXE, REVIT.EXE, CODE.EXE, NOTEPAD.EXE, NOTEPAD++.EXE, WORDPAD.EXE, REVU.EXE, REVU32.EXE, DWGVIEWR.EXE, INVENTOR.EXE


Limitations

DLP enforcement depends on how each application natively handles system APIs. Applications that use custom UI frameworks, proprietary rendering engines, or non-standard print pipelines may bypass standard Win32 API calls and cause inconsistent enforcement.


For more information on how to enable and configure Print Protection, please contact FenixPyre Support.

Last updated

Was this helpful?