Application Protector .Net

Protegrity Application Protector (AP) .Net Overview

The Protegrity Application Protector (AP) .Net provides APIs that integrate with customer applications to protect, unprotect, and reprotect sensitive data. It can be used with any application developed using .NET Standard 2.0.

Note: The DLL file creation is supported only by .NET Core 8.0 and .NET Core 9.0. The .NET application can be run by using any supported versions.

Protection and Security Access Methods

The AP .Net provides the following methods:

• Get product version
• Check Access
• Protect
• Unprotect
• Reprotect

For more information about these protection and security access methods, refer to AP .Net APIs.

Key Features

The key features of this protector include support of the .Net distributions listed here. Other key features include use of only trusted applications for access, audit logs, and initialization audit logs.

Supported .Net Distributions

The AP .Net supports the following versions:

Trusted Applications

The AP .Net can only be accessed by trusted applications.
Any application that protects, unprotects, or reprotects data must first be configured as a trusted application.

For details on configuring a trusted application, refer to Creating a Trusted Application.

Audit Logs

The AP .Net generates an audit record for every protection method call, including the data element and user name.

Single Data Item Audit Example

Three audit log events are generated in the following scenarios:

• 1 protect operation with data element a (count = 1)
• 5 protect operations with data element b (count = 5)
• 1000 unprotect operations with data element a (count = 1000)

Bulk Data Item Audit Example

For bulk operations, each protect, unprotect, and reprotect call generates audit logs.

Example:

• If bulk size = 3 and 2 bulk protect operations of the same data element are performed, then 1 audit log event is generated with a count = 6.

Initialization Audit Logs

• Each time a trusted application is initialized, an audit log is generated showing whether initialization was successful.
• These audits are available in ESA Audit Store Dashboard for easy access by the Security Officer.