<?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 We are having some issues decrypting Support Info files on agents that have not yet registered with the tenant, how does the agent get the default encryption key? in Endpoint Privilege Manager (EPM) Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/we-are-having-some-issues-decrypting-support-info-files-on/m-p/1422269#M9118</link>
    <description>&lt;P&gt;Because each set has a unique decryption key, the corresponding encryption key of the set we’re intending to register a new agent to must be included in the CyberArkEPMAgentSetupMacos.config or some other file included in the install package &lt;B&gt;or&lt;/B&gt; it must get the encryption key when it registers with the tenant. The config file looks like it’s got a handful of keys in it, but based on the labels in the xml, they look more like the keys/certs to actually reach out and register with the cloud. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If that unique set encryption key is not included in the installation package, then the agent must get it &lt;I&gt;after&lt;/I&gt; its first registration with the cloud where it can actually pull the key from the set’s agent configuration settings. If that’s the case, then a pre-registration client either has a hard-coded universal encryption key that all clients have by default prior to registration that it uses to encrypt the support info file or it just generates one for itself to have something to encrypt the support file with. With the former option, it is probably not ideal to publicly share the corresponding universal decryption key, but it must exist. With the latter option, it would be impossible to decrypt the support info file of a pre-registered EPM agent without some way to access that key.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In our case, we have installed the agent, run the activation script successfully, but the agent isn't checking in to the tenant and we would like to gather the Support Info archive to see what is happening, but using the decrypt key for the set the agent is activated for isn't working. Am I doing something wrong or how can I get that Support Info file decrypted?&lt;/P&gt;</description>
    <pubDate>Mon, 23 Mar 2026 20:16:26 GMT</pubDate>
    <dc:creator>SWurgler</dc:creator>
    <dc:date>2026-03-23T20:16:26Z</dc:date>
    <item>
      <title>We are having some issues decrypting Support Info files on agents that have not yet registered with the tenant, how does the agent get the default encryption key?</title>
      <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/we-are-having-some-issues-decrypting-support-info-files-on/m-p/1422269#M9118</link>
      <description>&lt;P&gt;Because each set has a unique decryption key, the corresponding encryption key of the set we’re intending to register a new agent to must be included in the CyberArkEPMAgentSetupMacos.config or some other file included in the install package &lt;B&gt;or&lt;/B&gt; it must get the encryption key when it registers with the tenant. The config file looks like it’s got a handful of keys in it, but based on the labels in the xml, they look more like the keys/certs to actually reach out and register with the cloud. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If that unique set encryption key is not included in the installation package, then the agent must get it &lt;I&gt;after&lt;/I&gt; its first registration with the cloud where it can actually pull the key from the set’s agent configuration settings. If that’s the case, then a pre-registration client either has a hard-coded universal encryption key that all clients have by default prior to registration that it uses to encrypt the support info file or it just generates one for itself to have something to encrypt the support file with. With the former option, it is probably not ideal to publicly share the corresponding universal decryption key, but it must exist. With the latter option, it would be impossible to decrypt the support info file of a pre-registered EPM agent without some way to access that key.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In our case, we have installed the agent, run the activation script successfully, but the agent isn't checking in to the tenant and we would like to gather the Support Info archive to see what is happening, but using the decrypt key for the set the agent is activated for isn't working. Am I doing something wrong or how can I get that Support Info file decrypted?&lt;/P&gt;</description>
      <pubDate>Mon, 23 Mar 2026 20:16:26 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/we-are-having-some-issues-decrypting-support-info-files-on/m-p/1422269#M9118</guid>
      <dc:creator>SWurgler</dc:creator>
      <dc:date>2026-03-23T20:16:26Z</dc:date>
    </item>
    <item>
      <title>Re: We are having some issues decrypting Support Info files on agents that have not yet registered with the tenant, how does the agent get the default encryption key?</title>
      <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/we-are-having-some-issues-decrypting-support-info-files-on/m-p/1422270#M9119</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for the detailed question. The key point is that the&amp;nbsp;&lt;B&gt;Support Info password is provided to the agent by the server as part of the policies;&lt;/B&gt;&amp;nbsp;it is&amp;nbsp;&lt;B&gt;not&lt;/B&gt;&amp;nbsp;taken from the macOS installation package, and there is no separate customer-facing pre-registration key.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;That means if an agent has never successfully connected to the tenant, it should not encrypt the Support Info archive at all; it should generate a regular ZIP file instead.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So if you are seeing an encrypted Support Info archive before the first successful check-in, the most likely explanation is that the machine had previously connected and already received policies, or that there are leftovers from an earlier installation on the endpoint.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In this case, I’d recommend performing a full uninstall and clean reinstall of the agent, then collecting Support Info again. On a freshly installed agent that has never connected, the expected result is a plain ZIP file.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If the endpoint still produces an encrypted archive after a clean reinstall and before the first successful registration, the next step would be to open a CyberArk Support case so the specific machine state can be reviewed.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For reference, the public documentation describes the standard Support Info decryption flow for agents that already have the configured Support Info password.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Best Regards,&lt;/P&gt;&lt;P&gt;Roey Aharon&lt;/P&gt;</description>
      <pubDate>Thu, 26 Mar 2026 15:18:28 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/we-are-having-some-issues-decrypting-support-info-files-on/m-p/1422270#M9119</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2026-03-26T15:18:28Z</dc:date>
    </item>
  </channel>
</rss>

