The Authorized Software Library is a core component that ensures the proper implementation of document encryption, decryption, and full-disk encryption features. Ping32 provides a robust authorization library that allows enterprises to flexibly manage and control encryption requirements across various applications.

Overview

The Authorized Software Library defines which applications are permitted to transparently encrypt or decrypt files. It serves as the foundation for implementing the document encryption feature.
Different industries can specify authorized software based on their unique encryption requirements. By configuring rules for each authorized application, administrators can achieve precise encryption and decryption control.

Adding Authorized Software

Before deploying encryption policies, authorized software must be added and configured with appropriate encryption rules. If the required application is not listed in the existing library, it can be manually added as a custom authorized software entry.

Step 1: Add Custom Authorized Software

1. Click Add Authorized Software.

2. Fill in the following details:

   • Software Name

   • Type

   • Description

3. (Optional) Click the icon next to the software name field to upload a custom icon for the software.

Step 2: Configure Encryption Rules

Define encryption rules for each authorized software. The rule types include:

• Encrypt — Apply encryption when files are accessed.

• Decrypt — Allow decryption when authorized.

• Ignore — Exclude specific files or formats from encryption.

🧩 Rules can be defined using wildcards or regular expressions and are applied in top-down order.
You can adjust rule priority using Move Up or Move Down controls.

Step 3: Configure Network Rules

Network rules define how the authorized application communicates over the network.

• Action Options: Allow or Deny

• Supported Rule Types:

  • Single or multiple IP addresses

  • IP address ranges

  • Single or multiple ports

  • Port ranges

Specify the appropriate rule type and fill in the corresponding network parameters.

Step 4: Advanced Settings

In Advanced Settings, you can enable or disable additional options for enhanced flexibility and security:

• Filter Directory Query Requests

• Allow Transparent Encryption Trigger

• Enable Debug Logging

Step 5: Debugging and Testing

Double-click an existing authorized software entry or process rule to perform debugging operations.
You can add, modify, or delete rules to test encryption behavior before deploying policies.
This helps ensure that all encryption configurations function correctly and effectively.

Importing and Exporting the Library

The Authorized Software Library supports import and export functionality for easy migration and backup.

• Click Import to upload a saved library file.

• Click Export to save the current library to local storage.

This feature improves flexibility and scalability across enterprise environments.

Important Notes

• When creating encryption rules, ensure that all related file formats are included.
  For example, when Microsoft Word generates a .docx file, it first creates a temporary .tmp file before renaming it to .docx.
  Therefore, both *.docx and *.tmp rules must be configured for encryption to take effect.

• If an application consists of multiple executable files, each executable must be added individually; otherwise, the encryption rules may not apply.

• Rules are executed sequentially from top to bottom, so adjust the order carefully based on the file generation logic.