<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Configure Policy on</title><link>https://docs.protegrity.com/aiteam-edition/docs/gov_policy/policy/configuration/</link><description>Recent content in Configure Policy on</description><generator>Hugo</generator><language>en</language><atom:link href="https://docs.protegrity.com/aiteam-edition/docs/gov_policy/policy/configuration/index.xml" rel="self" type="application/rss+xml"/><item><title>Policy Security Settings</title><link>https://docs.protegrity.com/aiteam-edition/docs/gov_policy/policy/configuration/security-settings/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/aiteam-edition/docs/gov_policy/policy/configuration/security-settings/</guid><description>&lt;p>Policy separates authenticated users, command capabilities, resource grants,
and integration identities. Each controls a different boundary.
Successful network access does not establish permission to approve or repair policies.
The application programming interface (API) and Policy Integration Manager (PIM)
also enforce different authority boundaries.&lt;/p>
&lt;h2 id="security-controls">Security Controls&lt;/h2>
&lt;p>The chart uses non-root workloads, restricted container contexts, dropped Linux
capabilities, and read-only filesystems where applicable.
It disables privilege escalation and limits network paths.
These settings do not replace gateway authentication or cluster network enforcement.&lt;/p></description></item></channel></rss>