<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Policy Management on</title><link>https://docs.protegrity.com/10.2/docs/pmg/</link><description>Recent content in Policy Management on</description><generator>Hugo</generator><language>en</language><atom:link href="https://docs.protegrity.com/10.2/docs/pmg/index.xml" rel="self" type="application/rss+xml"/><item><title>Protegrity Data Security Methodology</title><link>https://docs.protegrity.com/10.2/docs/pmg/pmg_data_security_policy_management_esa/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/10.2/docs/pmg/pmg_data_security_policy_management_esa/</guid><description>&lt;p>Protegrity&amp;rsquo;s Data Security Methodology consists of the following stages:&lt;/p>
&lt;ul>
&lt;li>Classification&lt;/li>
&lt;li>Discovery&lt;/li>
&lt;li>Protection&lt;/li>
&lt;li>Enforcement&lt;/li>
&lt;li>Monitoring&lt;/li>
&lt;/ul>
&lt;p>The following diagram summarizes each stage:&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" title="Protegrity Data Security Methodology">&lt;/p>
&lt;h2 id="classification">Classification&lt;/h2>
&lt;p>In the Classification stage, determine which data is considered sensitive for the enterprise, and why it needs to be protected. At this stage, it is important to understand the regulatory landscape in which the company is operating and the risk measurement framework associated with the privacy risk. An enterprise may need to meet certain regulatory compliance requirements or laws, such as:&lt;/p></description></item><item><title>Policy Management Dashboard</title><link>https://docs.protegrity.com/10.2/docs/pmg/pmg_policy_deployment_feedback/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/10.2/docs/pmg/pmg_policy_deployment_feedback/</guid><description>&lt;!-- The following figure shows the **Dashboard** screen for Policy Management.

![Policy Management Dashboard Screen](/docs/images/pmg_policy_management_dashboard_screen.png "Policy Management Dashboard Screen") -->
&lt;p>The Policy Management dashboard consists of the following three areas:&lt;/p>
&lt;ul>
&lt;li>Summary&lt;/li>
&lt;li>Keys&lt;/li>
&lt;li>Statuses&lt;/li>
&lt;/ul>
&lt;blockquote>
&lt;p>&lt;strong>Note:&lt;/strong> The &lt;strong>Statuses&lt;/strong> area is a &lt;a href="https://docs.protegrity.com/10.2/docs/pmg/pmg_legacy_features/">legacy feature&lt;/a> that is not applicable for 10.0.x protectors and later. For 10.0.x protectors and later, you can access the information about the protector statuses from the &lt;a href="https://docs.protegrity.com/10.2/docs/aog/audit_store/iag_dash_wrap/">Protegrity Dashboard&lt;/a>.&lt;/p>&lt;/blockquote>
&lt;h2 id="policy_deployment_summary">Summary&lt;/h2>
&lt;p>The &lt;strong>Summary&lt;/strong> area displays an overview of the number of policy components created using the Policy Management Web UI. The following policy components appear under the &lt;strong>Summary&lt;/strong> area:&lt;/p></description></item><item><title>Package Deployment</title><link>https://docs.protegrity.com/10.2/docs/pmg/pmg_policy_management_in_protector/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/10.2/docs/pmg/pmg_policy_management_in_protector/</guid><description>&lt;p>Starting with version 10.0.x artifacts such as the Data Security Policy or the DSG CoP rulesets, are distributed to Protectors through Packages. Packages in the ESA are resilient. Protectors store the resilient Packages using dynamic memory allocation, allowing for high scalability and performance.&lt;/p>
&lt;p>A Data Security Policy is deployed in the ESA either using the ESA Web UI or the &lt;a href="https://docs.protegrity.com/10.2/docs/protegrity_rest_apis/using_pmg_rest_apis/#devops_api_deploying_a_policy">Policy Management API&lt;/a>. A deployed policy indicates that it is ready to be distributed to the Protectors. If multiple policies exist in one data store, then the policies are merged on deployment. A deployed policy can be distributed to the Protectors using one of the following methods:&lt;/p></description></item><item><title>Legacy Features</title><link>https://docs.protegrity.com/10.2/docs/pmg/pmg_legacy_features/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/10.2/docs/pmg/pmg_legacy_features/</guid><description>&lt;p>The following Policy Management features are not applicable for 10.0.x protectors and later:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Policy Management &amp;gt; Nodes&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Policy Management &amp;gt; Dashboard &amp;gt; Statuses&lt;/strong>&lt;/li>
&lt;/ul>
&lt;p>For more information about these Legacy features for your supported Protectors earlier than 10.0.x, refer to a corresponding version of the Policy Management Guide from the &lt;a href="https://my.protegrity.com/login/?next=/">My.Protegrity website&lt;/a>.&lt;/p>
&lt;p>For 10.0.x protectors and later, you can access the information about the protector nodes and statuses from the &lt;a href="https://docs.protegrity.com/10.2/docs/aog/audit_store/iag_dash_wrap/">Protegrity Dashboard&lt;/a>.&lt;/p></description></item></channel></rss>