Integrating Cloud Protect with PPC (Protegrity Provisioned Cluster)

Mon, 01 Jan 0001 00:00:00 +0000

This guide describes how to configure the Protegrity Policy Agent and Log Forwarder to connect to a Protegrity Provisioned Cluster (PPC), highlighting the differences from connecting to ESA.

Key Differences: PPC vs ESA

Feature	ESA 10.2	PPC (this guide)
Datastore Key Fingerprint	Optional/Recommended	Required
CA Certificate on Agent	Optional/Recommended	Optional/Recommended
CA Certificate on Log Forwarder	Optional/Recommended	Not supported
Client Certificate Authentication from Log Forwarder	Optional/Recommended	Not supported
IP Address	ESA IP address	PPC address

Prerequisites

Access to PPC and required credentials.
Tools: curl, kubectl installed.

Policy Agent Setup with PPC

Important

When connecting to PPC, the Policy Agent requires the PTY_DATASTORE_KEY fingerprint. For ESA 10.2, the fingerprint is optional but recommended. See Policy Agent Installation for general setup steps.

Follow these instructions as a guide for understanding specific inputs for Policy Agent integrating with PPC:

Configuring Regular Expression to Extract Policy Username

Mon, 01 Jan 0001 00:00:00 +0000

Configuring Regular Expression to Extract Policy Username

Cloud Protect Function exposes USERNAME_REGEX configuration to allow extraction of policy username from user in the request.

USERNAME_REGEX Function Environment configuration

The USERNAME_REGEX environment variable can be set to contain regular expression with one capturing group. This group is used to extract the username. Examples below show different regular expression values and the resulting policy user.

USERNAME_REGEX

User in the request

Sample Snowflake External Functions for Protegrity Integration

Mon, 01 Jan 0001 00:00:00 +0000

Appendix A. Sample Snowflake External Function

Method: Tokenization

Type: ALPHA

Snowflake Data Types

Snowflake Max Size

Protegrity Max Size

VARCHAR

16M (16,777,216 bytes)

4K (4,096 bytes)

CHAR

STRING

TEXT

External Function Sample Definitions:

CREATE SECURE EXTERNAL FUNCTION PTY_PROTECT_ALPHA ( val varchar ) 
 RETURNS varchar 
 NULL 
 IMMUTABLE 
 COMMENT = 'Protects using an ALPHA data element' 
 API_INTEGRATION = REPLACE_WITH_YOUR_API_INTEGRATION_ID 
 HEADERS =( 
 'X-Protegrity-HCoP-Rules'=
 '{"jsonpaths": [{"op_type":"PROTECT","data_element":"TOK_ALPHA"}]}'
 )
 CONTEXT_HEADERS = ( current_user, current_timestamp, current_account ) 
 AS '<API Gateway URL>/api/Protect';

CREATE SECURE EXTERNAL FUNCTION PTY_UNPROTECT_ALPHA ( val varchar ) 
 RETURNS varchar 
 NULL 
 IMMUTABLE 
 COMMENT = 'Unprotects using an ALPHA data element' 
 API_INTEGRATION = REPLACE_WITH_YOUR_API_INTEGRATION_ID
 HEADERS =( 
 'X-Protegrity-HCoP-Rules'=
 '{"jsonpaths":[{"op_type":"UNPROTECT","data_element":"TOK_ALPHA"}]}'
 ) 
 CONTEXT_HEADERS = ( current_user, current_timestamp, current_account ) 
 AS '<API Gateway URL>/api/Protect';

ARM Template Installation - Required Permissions

Mon, 01 Jan 0001 00:00:00 +0000

ARM Template Installation - Required Permissions

Permissions below are required to install Protegrity service using ARM template.

All permissions in the table must be granted with the Resource group scope.

Permissions

Description

Built-In Azure Role

Microsoft.Insights/components/read

Microsoft.OperationalInsights/workspaces/read

Read access to monitoring data and settings

Monitoring Reader

Microsoft.Insights/components/write

Microsoft.OperationalInsights/workspaces/write

Write and manage access to monitoring data and settings

Monitoring Contributor

Microsoft.Web/serverFarms/write

Microsoft.Web/sites/write

Microsoft.Web/sites/host/listkeys/action

Microsoft.Web/serverFarms/join/action

Microsoft.Web/register/action

Write and manage access to web apps

Associating ESA Data Store With Cloud Protect Agent

Mon, 01 Jan 0001 00:00:00 +0000

Associating ESA Data Store With Cloud Protect Agent

ESA controls which policy is deployed to protector using concept of data store. A data store may contain a list of IP addresses identifying servers allowed to pull the policy associated with that specific data store. Data store may also be defined as default data store, which allows any server to pull the policy, provided it does not belong to any other data stores. Node registration occurs when the policy server (in this case the policy agent) makes a policy request to ESA, where the agent’s IP address is identified by ESA.

Appendices on

Integrating Cloud Protect with PPC (Protegrity Provisioned Cluster)

Key Differences: PPC vs ESA

Prerequisites

Policy Agent Setup with PPC

Important

Configuring Regular Expression to Extract Policy Username

Configuring Regular Expression to Extract Policy Username

Sample Snowflake External Functions for Protegrity Integration

Appendix A. Sample Snowflake External Function

ARM Template Installation - Required Permissions

ARM Template Installation - Required Permissions

Associating ESA Data Store With Cloud Protect Agent

Associating ESA Data Store With Cloud Protect Agent