<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Best Practices - Safe Structure in Privilege Cloud Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/best-practices-safe-structure/m-p/1358483#M3358</link>
    <description>&lt;P&gt;Object Level Access Control&lt;/P&gt;&lt;P&gt;The&amp;nbsp;Privileged Access Security&amp;nbsp;solution provides granular access control for passwords and files that are stored in the Vault. Object level access enables you to control who can retrieve and use specific passwords and files in the Safe, regardless of Safe level member authorizations. For example, an external vendor or technician can be given retrieve or use authorizations for a specific password which he will be able to use without being aware of any other passwords or files in the Safe. (supported in Self hosted CyberArk)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The above option is not recommended as @Jon Musker​ mentioned.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But this is not supported in PCloud CyberArk.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For your scenarios, you can opt for safe creation per team wise and load their accounts in the same safe with Dual control enabled in case account has admin level access&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 13 Mar 2025 07:11:30 GMT</pubDate>
    <dc:creator>T.Ramasamy969505</dc:creator>
    <dc:date>2025-03-13T07:11:30Z</dc:date>
    <item>
      <title>Best Practices - Safe Structure</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/best-practices-safe-structure/m-p/1358480#M3355</link>
      <description>&lt;P&gt;We are a little over a year into our CyberArk journey and are trying to mature some of our practices. One area we struggle with is safe organization/permissions.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are an agile shop and at times users need access to different accounts within CyberArk, so we end up having to create new safes and move accounts into them to avoid granting over-permissions.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;A thought that has come to mind is creating a safe for each account to grant us the ability to control access on a per-account (or safe) basis without having to move the account to a new safe each time. This also stops the account ID from changing, which we leverage regularly with automation.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Has anyone else had experience going down this 1 to 1 (account to safe) ratio path? And if so, was it a nightmare?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Appreciate any thoughts or suggestions that others have.&lt;/P&gt;</description>
      <pubDate>Wed, 12 Mar 2025 13:41:22 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/best-practices-safe-structure/m-p/1358480#M3355</guid>
      <dc:creator>T.Raadt292380</dc:creator>
      <dc:date>2025-03-12T13:41:22Z</dc:date>
    </item>
    <item>
      <title>Re: Best Practices - Safe Structure</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/best-practices-safe-structure/m-p/1358481#M3356</link>
      <description>&lt;P&gt;It really sounds like a significant operational overhead to map accounts -&amp;gt; safes 1:1. It sounds something akin to OLAC which I would NEVER recommend because of the operational overhead.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm not really sure what the issue is with over-permissions here, but from what you are describing it may be that once a user is granted access to a safe then they have both Use and Show permissions, thus effectively granting them full access to the target systems.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;A couple of approaches might assist that are fairly common patterns. At a very high level really&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;"Show Password" should not be permitted for normal users, only very highly privileged (platform admins) users and accessing "show password" should require approvals and be a breakglass activity that raises alarms, and ensure one-time password workflows.&lt;/LI&gt;&lt;LI&gt;Have the safes grouped logically with a small number of items in them, perhaps organised by the owning application for that target. Create a "users" group/role and an "auditors" group/role for each safe, but do not have any users statically assigned to those groups. Have users go through some automation/approval workflow that can temporarily add them to the appropriate group/role for a limited time and then automatically revoke the access, perhaps using IGA or ServiceNow. Approval could be peer-approval or from the application owner.&lt;/LI&gt;&lt;LI&gt;Grant users access to all the safes they &lt;I&gt;might &lt;/I&gt;need to use (View/Use permissions only). Then configure either Approval workflows or Ticket Integration on every request to ensure that they only get access at appropriate times for a specific task. . Approval could be peer-approval or from the application owner.&lt;/LI&gt;&lt;/OL&gt;</description>
      <pubDate>Wed, 12 Mar 2025 16:18:56 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/best-practices-safe-structure/m-p/1358481#M3356</guid>
      <dc:creator>Jon_Musker</dc:creator>
      <dc:date>2025-03-12T16:18:56Z</dc:date>
    </item>
    <item>
      <title>Re: Best Practices - Safe Structure</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/best-practices-safe-structure/m-p/1358482#M3357</link>
      <description>&lt;P&gt;Appreciate the reply, as well as the approaches to consider.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The over-permissioning comes into play when adding a new user to an existing safe. For example:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Safe 01 - holds:&lt;/P&gt;&lt;P&gt;Account 01&lt;/P&gt;&lt;P&gt;Account 02&lt;/P&gt;&lt;P&gt;Account 03&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If a new user needs access to only Account 02, I would need to move it to it's own safe, to avoid granting access to Account 01 and Account 03 as well.&lt;/P&gt;</description>
      <pubDate>Wed, 12 Mar 2025 22:09:29 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/best-practices-safe-structure/m-p/1358482#M3357</guid>
      <dc:creator>T.Raadt292380</dc:creator>
      <dc:date>2025-03-12T22:09:29Z</dc:date>
    </item>
    <item>
      <title>Re: Best Practices - Safe Structure</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/best-practices-safe-structure/m-p/1358483#M3358</link>
      <description>&lt;P&gt;Object Level Access Control&lt;/P&gt;&lt;P&gt;The&amp;nbsp;Privileged Access Security&amp;nbsp;solution provides granular access control for passwords and files that are stored in the Vault. Object level access enables you to control who can retrieve and use specific passwords and files in the Safe, regardless of Safe level member authorizations. For example, an external vendor or technician can be given retrieve or use authorizations for a specific password which he will be able to use without being aware of any other passwords or files in the Safe. (supported in Self hosted CyberArk)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The above option is not recommended as @Jon Musker​ mentioned.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But this is not supported in PCloud CyberArk.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For your scenarios, you can opt for safe creation per team wise and load their accounts in the same safe with Dual control enabled in case account has admin level access&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 13 Mar 2025 07:11:30 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/best-practices-safe-structure/m-p/1358483#M3358</guid>
      <dc:creator>T.Ramasamy969505</dc:creator>
      <dc:date>2025-03-13T07:11:30Z</dc:date>
    </item>
    <item>
      <title>Re: Best Practices - Safe Structure</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/best-practices-safe-structure/m-p/1358484#M3359</link>
      <description>&lt;P&gt;I would look at privileged access in terms of categorising the types of access (effectively risk levels), and also the controls that we have. Then draw up a matrix of which controls are required for which types of access. Then the safe structure and policies will follow from your matrix.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Example:&lt;/P&gt;&lt;P&gt;Types of access&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;app admin logs on to *nix server with root-equivalent account using ssh. Server is production&lt;/LI&gt;&lt;LI&gt;infrastructure admin logs on to *nix with root account using ssh. Server is production&lt;/LI&gt;&lt;LI&gt;operational support logs on to *nix server with low-privilege account using ssh. Server is production&lt;/LI&gt;&lt;LI&gt;infrastructure admin retrieves *nix server root account credentials (eg to fix sshd issue over iLO). Server is non-production&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Types of control&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Login with 2FA&lt;/LI&gt;&lt;LI&gt;Login with Biometric MFA&lt;/LI&gt;&lt;LI&gt;Pre-approval/onboarding process to grant user eligibility for access&lt;/LI&gt;&lt;LI&gt;Approval from peer&lt;/LI&gt;&lt;LI&gt;Approval from owner&lt;/LI&gt;&lt;LI&gt;Approval from senior approver&lt;/LI&gt;&lt;LI&gt;User must declare the reason for access&lt;/LI&gt;&lt;LI&gt;Time-limited access&lt;/LI&gt;&lt;LI&gt;Minimum permissions on minimum targets to achieve the declared reason&lt;/LI&gt;&lt;LI&gt;Password/secret is hidden from user&lt;/LI&gt;&lt;LI&gt;Recording of session&lt;/LI&gt;&lt;LI&gt;Just-in-time provisioning of access&lt;/LI&gt;&lt;LI&gt;Zero-standing privileges&lt;/LI&gt;&lt;LI&gt;Access restricted to come from certain network zones&lt;/LI&gt;&lt;LI&gt;Access restricted to come from devices meeting compliance criteria&lt;/LI&gt;&lt;LI&gt;Access restricted to come from specific devices&lt;/LI&gt;&lt;LI&gt;Access restricted to physical console only&lt;/LI&gt;&lt;LI&gt;Alerting of access to security response team&lt;/LI&gt;&lt;LI&gt;Review of session (retrospective)&lt;/LI&gt;&lt;LI&gt;Live monitoring of session (four-eyes)&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;etc&lt;/P&gt;</description>
      <pubDate>Thu, 13 Mar 2025 09:31:13 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/best-practices-safe-structure/m-p/1358484#M3359</guid>
      <dc:creator>Jon_Musker</dc:creator>
      <dc:date>2025-03-13T09:31:13Z</dc:date>
    </item>
    <item>
      <title>Re: Best Practices - Safe Structure</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/best-practices-safe-structure/m-p/1358485#M3360</link>
      <description>&lt;P&gt;@T R​&amp;nbsp;With all the suggestions and good recommendations provided here, I would also like to suggest trying a workflow. In that case, you can list the accounts in the user's account list, but only the required user will get access with approval.&lt;/P&gt;</description>
      <pubDate>Mon, 17 Mar 2025 01:33:12 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/best-practices-safe-structure/m-p/1358485#M3360</guid>
      <dc:creator>A.Weerasinghe346640</dc:creator>
      <dc:date>2025-03-17T01:33:12Z</dc:date>
    </item>
  </channel>
</rss>

