Ping32 employs a new-generation transparent encryption kernel that operates with high stability and security. The entire encryption process is seamless and invisible to end users. Multiple encryption modes are provided to meet diverse data protection needs—ensuring the security of core enterprise information without compromising employee productivity.

Overview

Ping32 Document Encryption supports multiple encryption modes and uses high-strength encryption algorithms to provide real-time and comprehensive protection for various types of corporate documents, design drawings, and R&D source code.
This effectively prevents the leakage of confidential enterprise data.

Encryption Modes

The document encryption module supports two primary encryption modes — Transparent Encryption and Semi-Transparent Encryption — which can be selected according to organizational security requirements.

1. Transparent Encryption

In this mode, files are automatically encrypted when created and automatically decrypted when accessed by authorized users.
The entire process is completely transparent, requiring no user intervention and causing no disruption to normal workflow or usage habits.

• Sensitive content is automatically encrypted at the file level.

• Encrypted files remain protected even if copied, transferred, or accessed through unauthorized means.

• Attackers cannot read or extract content from encrypted files, ensuring end-to-end data confidentiality.

This mode is ideal for environments requiring continuous and invisible data protection.

2. Semi-Transparent Encryption

In semi-transparent mode, files created by a local user remain unencrypted, but encrypted documents from other authorized users can still be opened and viewed securely.

• Only encrypted documents are subject to encryption control.

• Modified encrypted files remain encrypted after editing.

• Locally created non-encrypted documents are unaffected.

• Data can be classified into multiple security levels to avoid excessive restrictions that might hinder workflow.

3. Custom Mode

Administrators can define custom encryption behavior by assigning either transparent or semi-transparent encryption to specific authorized applications.
This approach provides flexible, fine-grained control over encryption behavior across different software environments.

Policy Configuration

Once document encryption is enabled, you can configure encryption policies that dictate how data is encrypted and managed across endpoints.

Follow the steps below to create and deploy an encryption policy:

Step 1: Ensure Authorized Software is Imported

Before creating a policy, verify that all required applications have been imported into the Ping32 console.
You can import software by clicking the Import button and selecting the corresponding authorized applications.

Step 2: Create a New Encryption Policy

In the Ping32 console:

1. Navigate to Encryption Policy Management.

2. Click New Policy.

3. Choose an appropriate encryption mode (Transparent or Semi-Transparent) based on organizational needs.

Step 3: Select Authorized Applications

Within the encryption policy configuration window, a list of authorized software will be displayed.
Select the applications that should apply the document encryption rules.

Step 4: Deploy the Policy

After completing the configuration, click Apply.
The newly created encryption policy will be distributed to all selected endpoints, activating the document encryption functionality according to your defined settings.

Summary

Ping32’s flexible encryption framework allows enterprises to balance data security and business efficiency.
Through configurable encryption modes and policy-based management, sensitive data remains protected across all stages of its lifecycle—without disrupting daily operations.