Application Protector Java Container

The following sections outline the business problems faced by customers in protecting their data in a native cloud environment. It then lists the Protegrity solution to this business problem using Application Protector Java APIs in a Kubernetes cluster.

Business Problem

As more use cases are moving to the Cloud, a solution is required that can protect data in a native cloud environment:

• Protegrity customers are moving to the cloud. This includes data and workloads in support of transactional application and analytical systems.
• Native Cloud capabilities can be used to solve this problem and deliver the agility and scalability required to keep up with the customers’ business.
• Kubernetes can be configured with Protegrity data security components that can leverage the autoscaling capabilities of Kubernetes to scale.

Protegrity Solution

The Protegrity Application Protector Java Container provides a robust and scalable APIs designed to simplify integration of Protegrity functions across your systems. Whether you are building custom applications, streamlining workflows, or enabling third-party access, our API offers secure, reliable, and well-documented interface.

The Protegrity Application Protector Java Container has the following characteristics:

• Cloud standard form factor:
  • The delivery form factor for cloud deployments is an SDK and a supporting Dockerfile. Customers can use this Dockerfile to build the Application Protector Java Container, which is based on the Application Protector form factor that Protegrity has been delivering for several years.
  • The Application Protector Java Container is a standard Docker Container that is familiar and expected in cloud deployments.
  • The Application Protector Java Container form factor makes the container a lightweight deployment of Application Protector Java.
• Support for Dynamic and Static deployment:
  • Dynamic deployment: The dynamic term refers to runtime updates to policy changes that are applied to the cluster. Dynamic updates are managed by the Resilient Package Proxy (RPProxy or RPP). The RPP is connected to the ESA and applies the policy changes to the Application Protector Java Containers.
  • Static deployment: This deployment is suitable where a fixed policy configuration is required for the Application Protector Java Container. A secure policy package is created using the ESA API. The policy package is secured using Cloud-based Key Management Solution (KMS). The same policy package is applied to all the Application Protector Java Containers in the cluster.

For more information about the Application Java Protector, refer to the section Application Protector Java