https://docs.protegrity.com/cloud-protect/4.0.0/docs/gcp/api/appendix/Recent content in Appendices onHugoenhttps://docs.protegrity.com/cloud-protect/4.0.0/docs/gcp/api/appendix/install_with_ppc/Mon, 01 Jan 0001 00:00:00 +0000https://docs.protegrity.com/cloud-protect/4.0.0/docs/gcp/api/appendix/install_with_ppc/<p> <ol id="toc"></ol> <script> // JavaScript to generate the table of contents from H2 headings document.addEventListener("DOMContentLoaded", function () { //get all h2 headings within the 'main' element and generate a toc with links to them //excluding h2 heading 'Feedback' if it exists const toc = document.getElementById("toc"); const headings = document.querySelectorAll("main h2"); headings.forEach(heading => { if (heading.textContent === "Feedback") { return; // Skip the 'Feedback' heading } const li = document.createElement("li"); const a = document.createElement("a"); const id = heading.textContent.toLowerCase().replace(/\s+/g, '-'); heading.id = id; // Set the id for the heading a.href = `#${id}`; a.textContent = heading.textContent; li.appendChild(a); toc.appendChild(li); }); }); </script> 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. <h2 id="key-differences-ppc-vs-esa">Key Differences: PPC vs ESA</h2> <table> <thead> <tr> <th>Feature</th> <th>ESA 10.2</th> <th>PPC (this guide)</th> </tr> </thead> <tbody> <tr> <td>Datastore Key Fingerprint</td> <td>Optional/Recommended</td> <td><strong>Required</strong></td> </tr> <tr> <td>CA Certificate on Agent</td> <td>Optional/Recommended</td> <td><strong>Optional/Recommended</strong></td> </tr> <tr> <td>CA Certificate on Log Forwarder</td> <td>Optional/Recommended</td> <td><strong>Not supported</strong></td> </tr> <tr> <td>Client Certificate Authentication from Log Forwarder</td> <td>Optional/Recommended</td> <td><strong>Not supported</strong></td> </tr> <tr> <td>IP Address</td> <td>ESA IP address</td> <td><strong>PPC address</strong></td> </tr> </tbody> </table> <h2 id="prerequisites">Prerequisites</h2> <ul> <li>Access to PPC and required credentials.</li> <li>Tools: <code>curl</code>, <code>kubectl</code> installed.</li> </ul> <h2 id="policy-agent-setup-with-ppc">Policy Agent Setup with PPC</h2> <div class="alert alert-warning" role="alert"> <h4 class="alert-heading">Important</h4> When connecting to PPC, the Policy Agent <strong>requires</strong> use of a datastore key fingerprint. For connecting to ESA 10.2 with Cloud Protect Policy Agent, the fingerprint is optional but recommended. See <a href="https://docs.protegrity.com/cloud-protect/4.0.0/docs/gcp/api/installation/agent/">Policy Agent Installation</a> for general setup steps. </div> <p>Follow these instructions as a guide for understanding specific inputs for Policy Agent integrating with PPC:</p>https://docs.protegrity.com/cloud-protect/4.0.0/docs/gcp/api/appendix/protection_methods/Mon, 01 Jan 0001 00:00:00 +0000https://docs.protegrity.com/cloud-protect/4.0.0/docs/gcp/api/appendix/protection_methods/<h2 id="protection-methods">Protection Methods</h2> <p>For more information about the protection methods supported by Protegrity, refer to the <a href="https://docs.protegrity.com/protectors/10.1/docs/pmr/">Protection Methods Reference</a>.</p> <table><thead><tr><th> <p>Tokenization Type</p> </th><th> <p>Supported Input Data Types</p> </th><th> <p>Notes</p> </th></tr></thead><tbody><tr><td> <p>Numeric</p> <p>Credit Card</p> <p>Alpha</p> <p>Upper-case Alpha</p> <p>Alpha-Numeric</p> <p>Upper Alpha-Numeric</p> <p>Lower ASCII</p> <p>Printable</p> <p>Decimal</p> <p>Unicode</p> <p>Unicode Base64</p> <p>Unicode Gen2</p> <p>Email</p> </td><td> <p>STRING</p> <p>NULL</p> </td><td> </td></tr><tr><td> <p>Integer</p> </td><td> <p>NUMBER</p> <p>NULL</p> </td><td> </td></tr><tr><td> <p>Date</p> <p>Datetime</p> </td><td> <p>STRING</p> <p>NULL</p> </td><td> <p>For information about supported formats, refer to the <a href="https://docs.protegrity.com/protectors/10.1/docs/pmr/">Protection Methods Reference</a>.</p>https://docs.protegrity.com/cloud-protect/4.0.0/docs/gcp/api/appendix/username_regex_configuration/Mon, 01 Jan 0001 00:00:00 +0000https://docs.protegrity.com/cloud-protect/4.0.0/docs/gcp/api/appendix/username_regex_configuration/<h2 id="configuring-regular-expression-to-extract-policy-username">Configuring Regular Expression to Extract Policy Username</h2> <p>Cloud Protect Cloud Function exposes USERNAME_REGEX configuration to allow extraction of policy username from user in the request.</p> <ul> <li> <p><strong>USERNAME_REGEX Cloud Function Environment configuration</strong></p> <p>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.</p> </li> </ul> <table><thead><tr><th> <p>USERNAME_REGEX</p> </th><th> <p>User in the request</p>https://docs.protegrity.com/cloud-protect/4.0.0/docs/gcp/api/appendix/gcp_agent_ip_address_config/Mon, 01 Jan 0001 00:00:00 +0000https://docs.protegrity.com/cloud-protect/4.0.0/docs/gcp/api/appendix/gcp_agent_ip_address_config/<h2 id="associating-esa-data-store-with-cloud-protect-agent">Associating ESA Data Store With Cloud Protect Agent</h2> <p>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&rsquo;s IP address is identified by ESA.</p>https://docs.protegrity.com/cloud-protect/4.0.0/docs/gcp/api/appendix/cloud_protect_audit_log_recovery_overview_gcp/Mon, 01 Jan 0001 00:00:00 +0000https://docs.protegrity.com/cloud-protect/4.0.0/docs/gcp/api/appendix/cloud_protect_audit_log_recovery_overview_gcp/<p> <ol id="toc"></ol> <script> // JavaScript to generate the table of contents from H2 headings document.addEventListener("DOMContentLoaded", function () { //get all h2 headings within the 'main' element and generate a toc with links to them //excluding h2 heading 'Feedback' if it exists const toc = document.getElementById("toc"); const headings = document.querySelectorAll("main h2"); headings.forEach(heading => { if (heading.textContent === "Feedback") { return; // Skip the 'Feedback' heading } const li = document.createElement("li"); const a = document.createElement("a"); const id = heading.textContent.toLowerCase().replace(/\s+/g, '-'); heading.id = id; // Set the id for the heading a.href = `#${id}`; a.textContent = heading.textContent; li.appendChild(a); toc.appendChild(li); }); }); </script> <p>Protegrity Cloud Protect Log Forwarder installation provides a solution to recover undelivered audit logs. Reasons for undeliverable logs may include:</p>