<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Installation on</title><link>https://docs.protegrity.com/10.1/docs/installation/</link><description>Recent content in Installation on</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 01 Apr 2026 06:02:13 +0000</lastBuildDate><atom:link href="https://docs.protegrity.com/10.1/docs/installation/index.xml" rel="self" type="application/rss+xml"/><item><title>Overview of installation</title><link>https://docs.protegrity.com/10.1/docs/installation/ig_overview_of_installation/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/10.1/docs/installation/ig_overview_of_installation/</guid><description>&lt;h2 id="audience">Audience&lt;/h2>
&lt;p>The installation steps is intended for the following stakeholders:&lt;/p>
&lt;ul>
&lt;li>Security professionals like security officers who are responsible for protecting business systems in organizations. They plan and ensure execution of security arrangement for their organization.&lt;/li>
&lt;li>System administrators and other technical personnel who are responsible for implementing data security solutions in their organization.&lt;/li>
&lt;li>System Architects who are responsible for providing expert guidance in designing, development and implementation of enterprise data security solution architecture for their business requirements.&lt;/li>
&lt;/ul>
&lt;h2 id="protegrity-data-security-platform">Protegrity Data Security Platform&lt;/h2>
&lt;p>The Protegrity Data Security Platform is a comprehensive source of enterprise data protection solutions. Its design is based on a hub and spoke deployment architecture.&lt;/p></description></item><item><title>System Requirements</title><link>https://docs.protegrity.com/10.1/docs/installation/ig_system_reqs/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/10.1/docs/installation/ig_system_reqs/</guid><description>&lt;p>The following table lists the supported components and their compatibility settings.&lt;/p>
&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>Component&lt;/th>
 &lt;th>Compatibility&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td>Application Protocols&lt;/td>
 &lt;td>HTTP 1.0, HTTP 1.1, SSL/TLS&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>WebServices&lt;/td>
 &lt;td>SOAP 1.1 and WSDL 1.1&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>Web Browsers&lt;/td>
 &lt;td>Minimum supported Web Browser versions are as follows: &lt;br> - Google Chrome version 129.0.6668.58/59 (64-bit) &lt;br> - Mozilla Firefox version 130.0.1 (64-bit) or higher &lt;br> - Microsoft Edge version 128.0.2739.90 (64-bit)&lt;/td>
 &lt;/tr>
 &lt;/tbody>
&lt;/table>
&lt;p>The following table lists the minimum hardware configurations.&lt;/p>
&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>Hardware Components&lt;/th>
 &lt;th>Configuration&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td>CPU&lt;/td>
 &lt;td>Multicore Processor, with minimum 8 CPUs&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>RAM&lt;/td>
 &lt;td>32 GB&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>Hard Disk&lt;/td>
 &lt;td>320 GB&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>CPU Architecture&lt;/td>
 &lt;td>x86&lt;/td>
 &lt;/tr>
 &lt;/tbody>
&lt;/table>
&lt;p>&lt;strong>Certificate Requirements&lt;/strong>&lt;/p></description></item><item><title>Partitioning of Disk on ESA</title><link>https://docs.protegrity.com/10.1/docs/installation/micro_disk_partition_intro/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/10.1/docs/installation/micro_disk_partition_intro/</guid><description>&lt;p>BIOS is amongst the oldest systems used as a boot loader to perform the initialization of the hardware. UEFI is a comparatively newer system that defines a software interface between the operating system and the platform firmware. The UEFI is more advanced than the BIOS and most of the systems are built with support for UEFI and BIOS.&lt;/p>
&lt;p>Disk Partitioning is a method of dividing the hard drive into logical partitions. When a new hard drive is installed on a system, the disk is segregated into partitions. These partitions are utilized to store data, which the operating system reads in a logical format. The information about these partitions is stored in the partition table.&lt;/p></description></item><item><title>Configuring the ESA</title><link>https://docs.protegrity.com/10.1/docs/installation/ig_configuring_esa/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/10.1/docs/installation/ig_configuring_esa/</guid><description>&lt;h2 id="configuring-authentication-settings">Configuring authentication settings&lt;/h2>
&lt;p>User authentication is the process of identifying someone who wants to gain access to a resource. A server contains protected resources that are only accessible to authorized users. When you want to access any resource on the server, the server uses different authentication mechanism to confirm your identity.&lt;/p>
&lt;p>You can configure the authentication using for the following methods.&lt;/p>
&lt;ul>
&lt;li>&lt;a href="https://docs.protegrity.com/10.1/docs/aog/command_line_interface_cli_manager/working_with_administration/accessing_rest_api_resources/aog_working_with_basic_auth/">Basic Authentication&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://docs.protegrity.com/10.1/docs/aog/command_line_interface_cli_manager/working_with_administration/accessing_rest_api_resources/aog_working_with_client_cert_auth/">Client Certificates&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://docs.protegrity.com/10.1/docs/aog/command_line_interface_cli_manager/working_with_administration/accessing_rest_api_resources/aog_working_with_jwt/">JSON Web Token (JWT)&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://docs.protegrity.com/10.1/docs/aog/command_line_interface_cli_manager/working_with_administration/managing_ldap/aog_proxy_authentication/">Proxy Authentication&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://docs.protegrity.com/10.1/docs/aog/accessing_appliances_using_single_sign_on/">Single Sign-On (SSO)&lt;/a>&lt;/li>
&lt;/ul>
&lt;h2 id="configuring-accounts-and-passwords">Configuring accounts and passwords&lt;/h2>
&lt;p>You can change your current password from the CLI Manager. The CLI Manager includes options to change passwords and permissions for multiple users.&lt;/p></description></item><item><title>Verifying the ESA installation from the Web UI</title><link>https://docs.protegrity.com/10.1/docs/installation/ig_working_with_esa_using_web_ui/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/10.1/docs/installation/ig_working_with_esa_using_web_ui/</guid><description>&lt;p>To verify the ESA installation from the Web UI:&lt;/p>
&lt;ol>
&lt;li>
&lt;p>Login to the ESA Web UI.&lt;/p>
&lt;p>The ESA dashboard appears.&lt;/p>
&lt;p>&lt;img src="https://docs.protegrity.com/10.1/docs/images/aog_web_ui.png" alt="ESA Dashboard">&lt;/p>
&lt;/li>
&lt;li>
&lt;p>Navigate to &lt;strong>System&lt;/strong> &amp;gt; &lt;strong>Information&lt;/strong>.&lt;/p>
&lt;p>The screen displaying the information of your system appears.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>Under the &lt;strong>Installed Patches&lt;/strong> area, the &lt;strong>ESA_10.1.0&lt;/strong> entry appears.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>Navigate to &lt;strong>System&lt;/strong> &amp;gt; &lt;strong>Services&lt;/strong> and ensure that all the required services are running.&lt;/p>
&lt;/li>
&lt;/ol></description></item><item><title>Initializing the Policy Information Management (PIM) Module</title><link>https://docs.protegrity.com/10.1/docs/installation/ig_working_with_esa_using_pm/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/10.1/docs/installation/ig_working_with_esa_using_pm/</guid><description>&lt;p>To initialize the PIM module:&lt;/p>
&lt;ol>
&lt;li>
&lt;p>In a web browser, enter the ESA IP address in the window task bar.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>Enter the &lt;strong>Username&lt;/strong> and &lt;strong>Password&lt;/strong>.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>Click &lt;strong>Sign in&lt;/strong>.&lt;/p>
&lt;p>The ESA dashboard appears.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>Navigate to &lt;strong>Policy Management&lt;/strong> &amp;gt; &lt;strong>Dashboard&lt;/strong>.&lt;/p>
&lt;p>The following screen to initialize PIM appears.&lt;/p>
&lt;p>&lt;img src="https://docs.protegrity.com/10.1/docs/images/ig_initialize_pim.png" alt="" title="PIM Initialization Screen">&lt;/p>
&lt;/li>
&lt;li>
&lt;p>Click &lt;strong>Initialize PIM&lt;/strong>.&lt;/p>
&lt;p>A confirmation message appears.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>Click &lt;strong>OK&lt;/strong>.&lt;/p>
&lt;p>The Policy management screen appears.&lt;/p>
&lt;/li>
&lt;/ol></description></item><item><title>Configuring the ESA in a Trusted Appliances Cluster (TAC)</title><link>https://docs.protegrity.com/10.1/docs/installation/ig_config_esa/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/10.1/docs/installation/ig_config_esa/</guid><description>&lt;p>The following figure illustrates the TAC setup.&lt;/p>
&lt;p>&lt;img src="https://docs.protegrity.com/10.1/docs/images/upg_3esa_9000.png" alt="" title="TAC on ESA 9.2.0.0">&lt;/p>
&lt;ol>
&lt;li>
&lt;p>TAC is established between the primary ESA A and the secondary ESAs, ESA B and ESA C.&lt;/p>
&lt;p>For more information about TAC, refer &lt;a href="https://docs.protegrity.com/10.1/docs/aog/trusted_appliances_cluster/">here&lt;/a>.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>Data replication for policies, forensics, or DSG configuration takes place between all the ESAs.&lt;/p>
&lt;p>For more information about replication tasks, refer &lt;a href="https://docs.protegrity.com/10.1/docs/aog/web_user_interface_management/aog_system_webui/aog_backup_restore/">here&lt;/a>.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>The Audit Store cluster is enabled for the ESAs.&lt;/p>
&lt;p>For more information about enabling Audit Store Cluster, refer &lt;a href="https://docs.protegrity.com/10.1/docs/installation/upg_creating_audit_store_cluster/">here&lt;/a>.&lt;/p></description></item><item><title>Creating an Audit Store Cluster</title><link>https://docs.protegrity.com/10.1/docs/installation/upg_creating_audit_store_cluster/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/10.1/docs/installation/upg_creating_audit_store_cluster/</guid><description>&lt;p>The Audit Store cluster is a collection of nodes that process and store data. The Audit Store is installed on the ESA nodes. The logs generated by the Appliance, such as, ESA or DSG, and Protector machines are stored in this Audit Store. The logs are useful for obtaining information about the nodes and the cluster on the whole. The logs can also be monitored for any data loss, system compromise, or any other issues with the nodes in the Audit Store cluster.&lt;/p></description></item></channel></rss>