<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Enterprise Security Administrator (ESA) on</title><link>https://docs.protegrity.com/10.2/docs/aog/</link><description>Recent content in Enterprise Security Administrator (ESA) on</description><generator>Hugo</generator><language>en</language><atom:link href="https://docs.protegrity.com/10.2/docs/aog/index.xml" rel="self" type="application/rss+xml"/><item><title>Protegrity Appliance Overview</title><link>https://docs.protegrity.com/10.2/docs/aog/aog_product_overview/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/10.2/docs/aog/aog_product_overview/</guid><description>&lt;h1 id="protegrity-appliance-overview">Protegrity Appliance Overview&lt;/h1>
&lt;p>The Protegrity Data Security Platform provides policy management and data protection and has the following appliances.&lt;/p>
&lt;ol>
&lt;li>&lt;strong>Enterprise Security Administrator (ESA)&lt;/strong> is the main component of the Data Security Platform. Working in combination with a Protegrity Protector, it can be used to encrypt or tokenize your data. Protectors include the Database Protector, Application Protector, File Protector, or Big Data Protector.&lt;/li>
&lt;li>&lt;strong>The Data Security Gateway (DSG)&lt;/strong> is a network intermediary that can be classified under Cloud Access Security Brokers (CASB) and Cloud Data Protection Gateway (CDPG). CASBs provide security administrators a central check point to ensure secure and compliant use of cloud services across multiple cloud providers. CDPG is a security policy enforcement check point that exists between cloud data consumer and cloud service provider to interject enterprise policies whenever the cloud-based resources are accessed.&lt;/li>
&lt;/ol>
&lt;p>&lt;strong>Data Protectors&lt;/strong> – Protect sensitive data in the enterprise and deploy security policy for enforcement on each installed system. A policy is deployed from ESA to the Data Protectors and Audit Logs of all activity on sensitive data is forwarded to the appliances, such as, the ESA, or external logging systems.&lt;/p></description></item><item><title>Installing ESA</title><link>https://docs.protegrity.com/10.2/docs/aog/aog_app_installation/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/10.2/docs/aog/aog_app_installation/</guid><description>&lt;p>You can install ESA on-premise or on a cloud platform such as AWS, GCP, or Azure. When you upgrade from a previous version, ESA is available as patch. The following are the different ways of installing ESA:&lt;/p>
&lt;h2 id="installing-esa">Installing ESA&lt;/h2>
&lt;ul>
&lt;li>&lt;strong>ISO Installation&lt;/strong>: This installation is performed for an on-premise environment where ESA is installed on a local system using an ESA ISO is provided by Protegrity. The installation of the ISO begins by installing the hardened version of Linux on your system, setting up the network, and configuring date/time. This is then followed by updating the location, setting up OS user accounts, and installing the ESA-related components. For more information about installing ESA using ISO, refer to &lt;a href="https://docs.protegrity.com/10.2/docs/installation/ig_installing_esa/ig_installing_esa_appliance/">Installing ESA using ISO&lt;/a>.&lt;/li>
&lt;li>&lt;strong>Cloud Platforms&lt;/strong>: On Cloud platforms such as, AWS, GCP, or Azure, ESA images for the respective cloud are generated and provided by Protegrity. In these images, ESA is installed with specific components. You must obtain the image from Protegrity and create an instance on the cloud platform. After creating the instance, you run certain steps for finalizing the installation. For more information about installing ESA on cloud platforms, refer to &lt;a href="https://docs.protegrity.com/10.2/docs/installation/ig_installing_esa/ig_cloud_platforms/">Installing ESA on Cloud Platforms&lt;/a>.&lt;/li>
&lt;/ul>
&lt;p>A temporary license is provided by default when you first install the ESA and is valid for 30 days from the date of this installation. To continue using Protegrity features, you have to obtain a validated license before your temporary license expires.&lt;/p></description></item><item><title>Logging Into ESA</title><link>https://docs.protegrity.com/10.2/docs/aog/esag_login_to_esa/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/10.2/docs/aog/esag_login_to_esa/</guid><description>&lt;p>The Enterprise Security Administrator (ESA), contains several components such as, Insight, Audit Store, Analytics, Policy Management, Key Management, Certificate Management, Clustering, Backup/Restore, Networking, User Management, and so on. You must login to ESA to avail the services of these components. Log in to the CLI Manager or Web UI of ESA to secure your data using these components.&lt;/p>
&lt;p>The login aspect of the appliance can be categorized into the following categories:&lt;/p></description></item><item><title>VMware tools in appliances</title><link>https://docs.protegrity.com/10.2/docs/aog/aog_vmware_tools/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/10.2/docs/aog/aog_vmware_tools/</guid><description>&lt;p>The VMware tools are used to access the utilities that enable you to monitor and improve management of the virtual machines that are part of your environment. When you install or upgrade your appliance, the VMware tools are automatically installed.&lt;/p></description></item><item><title>Increasing the Appliance Disk Size</title><link>https://docs.protegrity.com/10.2/docs/aog/increasing_the_appliance_disk_size/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/10.2/docs/aog/increasing_the_appliance_disk_size/</guid><description>&lt;p>If you need to increase the total disk size of the Appliance, then you can add additional hard disks to the Appliance. The Appliance refers to the added hard disks as logical volumes, or partitions, which offer additional disk capacity.&lt;/p>
&lt;p>As required, partitions can be added, removed, or moved from one hard disk to another. It is possible to create smaller partitions on a hard disk and combine multiple hard disks to form a single large partition.&lt;/p></description></item><item><title>Sample External Directory Configurations</title><link>https://docs.protegrity.com/10.2/docs/aog/appendix_sample_external_directory_configurations/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/10.2/docs/aog/appendix_sample_external_directory_configurations/</guid><description>&lt;p>In appliances, the external directory servers such as, Active Directory (AD) or Oracle Directory Server Enterprise Edition (ODSEE) use the OpenLDAP protocol to authenticate users. The following sections describe the parameters that you must configure to connect with an external directory.&lt;/p>
&lt;h2 id="sample-ad-configuration">Sample AD configuration&lt;/h2>
&lt;p>The following example describes the parameters for setting up an AD connection.&lt;/p>
&lt;p>&lt;strong>LDAP Uri:&lt;/strong> &lt;em>ldap://192.257.50.10:389&lt;/em>&lt;/p>
&lt;p>&lt;strong>Base DN:&lt;/strong> &lt;em>dc=sherwood,dc=com&lt;/em>&lt;/p>
&lt;p>&lt;strong>Bind DN:&lt;/strong> &lt;em>&lt;a href="mailto:administrator@sherwood.com">administrator@sherwood.com&lt;/a>&lt;/em>&lt;/p>
&lt;p>&lt;strong>Bind Password:&lt;/strong> &amp;lt;Password for the Bind User&amp;gt;&lt;/p></description></item><item><title>Working with Keys</title><link>https://docs.protegrity.com/10.2/docs/aog/esa_working_with_keys/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/10.2/docs/aog/esa_working_with_keys/</guid><description>&lt;p>The Protegrity Data Security platform uses many keys to protect your sensitive data. The Protegrity Key Management solution manages these keys and this system is embedded into the fabric of the Protegrity Data Security Platform. For example, creating a cryptographic or data protection key is a part of the process of defining the way sensitive data is to be protected. There is not a specific user visible function to create a data protection key.&lt;/p></description></item><item><title>Working with Certificates</title><link>https://docs.protegrity.com/10.2/docs/aog/esag_ch_certificates_in_esa/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/10.2/docs/aog/esag_ch_certificates_in_esa/</guid><description>&lt;p>Digital certificates are used to encrypt online communication and authentication between two entities. For two entities exchanging sensitive information, the one that initiates the request for exchange can be called the client and the one that receives the request and constitutes the other entity can be called the server.&lt;/p>
&lt;p>The authentication of both the client and the server involves the use of digital certificates issued by the trusted Certificate Authorities (CAs). The client authenticates itself to a server using its client certificate. Similarly, the server also authenticates itself to the client using the server certificate. Thus, certificate-based communication and authentication involves a client certificate, server certificate, and a certifying authority that authenticates the client and server certificates.&lt;/p></description></item><item><title>Managing policies</title><link>https://docs.protegrity.com/10.2/docs/aog/esa_managing_policies/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/10.2/docs/aog/esa_managing_policies/</guid><description>&lt;p>The policy each organization creates within ESA is based on requirements with relevant regulations. A policy helps to determine, specify and enforce certain data security rules. These data security rules are as shown in the following figure.&lt;/p>
&lt;p>&lt;img src="https://docs.protegrity.com/10.2/docs/images/pmg_data_security_methodology.png" alt="Protegrity Data Security Methodology">&lt;/p>
&lt;h2 id="classification">Classification&lt;/h2>
&lt;p>This section discusses about the classification of Policy Management in ESA.&lt;/p>
&lt;ul>
&lt;li>
&lt;p>&lt;strong>What do you want to protect?&lt;/strong>&lt;/p>
&lt;p>The data that is to be protected needs to be classified. This step determines the type of data that the organization considers sensitive. The compliance or security team will choose to meet certain standard compliance requirements with specific law or regulation, such as the Payment Card Industry Data Security Standard (PCI DSS) or the Health Information Portability and Accessibility Act (HIPAA).&lt;/p></description></item></channel></rss>