<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Configuration on</title><link>https://docs.protegrity.com/10.2/docs/configuration/</link><description>Recent content in Configuration on</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 14 Apr 2026 08:15:03 +0000</lastBuildDate><atom:link href="https://docs.protegrity.com/10.2/docs/configuration/index.xml" rel="self" type="application/rss+xml"/><item><title>Sending logs to an external security information and event management (SIEM)</title><link>https://docs.protegrity.com/10.2/docs/configuration/esa_siem_setup/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/10.2/docs/configuration/esa_siem_setup/</guid><description>&lt;blockquote>
&lt;p>This is an optional step.&lt;/p>&lt;/blockquote>
&lt;p>The following options are available for forwarding logs from the Protector:&lt;/p>
&lt;ul>
&lt;li>The default setup, that is, ESA.&lt;/li>
&lt;li>Sending logs to the ESA and a SIEM.&lt;/li>
&lt;/ul>
&lt;p>In addition to the ESA or the ESA and a SIEM, logs can be sent to the Amazon CloudWatch. For more information about configuring Amazon CloudWatch, refer to &lt;a href="https://docs.protegrity.com/10.2/docs/aog/installing_appliances_on_cloud_platforms/installing_protegrity_appliances_on_aws/working_with_cloud_based_applications/working-_with-_cloudwatch_console/">Working with CloudWatch Console&lt;/a>.&lt;/p>
&lt;p>In the &lt;em>default setup&lt;/em>, the logs are sent from the protectors directly to the Audit Store on the ESA using the Log Forwarder on the protector.&lt;/p></description></item><item><title>Configuring a Trusted Appliance Cluster (TAC) without Consul Integration</title><link>https://docs.protegrity.com/10.2/docs/configuration/ig_uninstalling_consul/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/10.2/docs/configuration/ig_uninstalling_consul/</guid><description>&lt;p>For more information about creating a TAC, refer to the section &lt;a href="https://docs.protegrity.com/10.2/docs/aog/trusted_appliances_cluster/">Trusted Appliances Cluster (TAC)&lt;/a>.&lt;/p>
&lt;p>&lt;strong>Note:&lt;/strong> If the node contains scheduled tasks associated with it, then you cannot uninstall the cluster services on it. Ensure that you delete all the scheduled tasks before uninstalling the cluster services.&lt;/p>
&lt;p>&lt;strong>Note:&lt;/strong> If you are uninstalling the &lt;strong>Consul Integration&lt;/strong> services, then the &lt;strong>Consul&lt;/strong> related ports and certificates are not required.&lt;/p>
&lt;p>To uninstall cluster services, perform the following steps.&lt;/p></description></item><item><title>Configuring the IP Address for the Docker Interface</title><link>https://docs.protegrity.com/10.2/docs/configuration/ig_apendix_f_networking/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/10.2/docs/configuration/ig_apendix_f_networking/</guid><description>&lt;p>From ESA v9.0.0.0, the default IP addresses assigned to the docker interfaces are between &lt;strong>172.17.0.0/16&lt;/strong> and &lt;strong>172.18.0.0/16&lt;/strong>. If your have a VPN or your organization&amp;rsquo;s network configured with the IP addresses are between &lt;strong>172.17.0.0/16&lt;/strong> and &lt;strong>172.18.0.0/16&lt;/strong>, then this might cause conflict with your organization&amp;rsquo;s private or internal network resulting in loss of network connectivity.&lt;/p>
&lt;p>&lt;strong>Note:&lt;/strong> Ensure that the IP addresses assigned to the docker interface must not conflict with the organization&amp;rsquo;s private or internal network.&lt;/p></description></item><item><title>Identifying the protector version</title><link>https://docs.protegrity.com/10.2/docs/configuration/log_protver/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/10.2/docs/configuration/log_protver/</guid><description>&lt;p>Perform the following steps to identify the PEP server version of the protector:&lt;/p>
&lt;ol>
&lt;li>
&lt;p>Log in to the ESA.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>Navigate to &lt;strong>Policy Management &amp;gt; Nodes&lt;/strong>.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>View the &lt;strong>Version&lt;/strong> field for all the protectors.&lt;/p>
&lt;/li>
&lt;/ol></description></item></channel></rss>