<?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 Break glass design in Privilege Cloud Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/break-glass-design/m-p/1410972#M6239</link>
    <description>&lt;P&gt;How can i make centralize safe and how can i add available safes of organization into that.So in case of break glass scenario that can be accessed. &lt;/P&gt;</description>
    <pubDate>Thu, 06 Mar 2025 17:34:44 GMT</pubDate>
    <dc:creator>N.Choudhary532311</dc:creator>
    <dc:date>2025-03-06T17:34:44Z</dc:date>
    <item>
      <title>Break glass design</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/break-glass-design/m-p/1410972#M6239</link>
      <description>&lt;P&gt;How can i make centralize safe and how can i add available safes of organization into that.So in case of break glass scenario that can be accessed. &lt;/P&gt;</description>
      <pubDate>Thu, 06 Mar 2025 17:34:44 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/break-glass-design/m-p/1410972#M6239</guid>
      <dc:creator>N.Choudhary532311</dc:creator>
      <dc:date>2025-03-06T17:34:44Z</dc:date>
    </item>
    <item>
      <title>Re: Break glass design</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/break-glass-design/m-p/1410973#M6240</link>
      <description>&lt;P&gt;Make particular safe and onboard the accounts over there. Distribute the Safe name and object name to the teams which accounts resides there. Thereafter, it would be easier to retrieve the password from Back up incase if anything wrong happens. Did i get you clearly?&lt;/P&gt;</description>
      <pubDate>Thu, 06 Mar 2025 18:29:49 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/break-glass-design/m-p/1410973#M6240</guid>
      <dc:creator>Sanzu</dc:creator>
      <dc:date>2025-03-06T18:29:49Z</dc:date>
    </item>
    <item>
      <title>Re: Break glass design</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/break-glass-design/m-p/1410974#M6241</link>
      <description>&lt;P&gt;Could you expand on what the break-glass scenario in this case is? Is it orphaned safes? &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You can't add a safe to another safe and you can't have one account in multiple safes. To ensure you don't end up with orphaned safes, you could maybe consider having a few break-glass users added to all safes and review and test at regular intervals. Alternatively, a great solution is to create a break-glass role in Identity and don't add any users to it. Add the role to all safes with the 'Full' permission preset, this way there's no standing access to the accounts in the safe. If and when required (in a break-glass scenario) you can add a user to the role and they will automatically be able to access all safes.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Here is a discussion on a similar scenario, Elijah's answer is quite in-depth and should give you a lot more to go on: https://community.cyberark.com/s/question/0D5Ht0000ADM8D0KQL/the-user-creating-the-safe-in-privilege-cloud-has-full-control-on-the-safe-how-can-we-recover-full-rights-on-the-safe-if-that-user-was-deleted&lt;/P&gt;</description>
      <pubDate>Thu, 06 Mar 2025 20:54:06 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/break-glass-design/m-p/1410974#M6241</guid>
      <dc:creator>Tanishq</dc:creator>
      <dc:date>2025-03-06T20:54:06Z</dc:date>
    </item>
  </channel>
</rss>

