<?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>article Security Bulletin CA19-04 - FAQs in PAM Self-Hosted Articles</title>
    <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-articles/security-bulletin-ca19-04-faqs/ta-p/1427381</link>
    <description>Please see below some Frequently Asked Questions and Responses regarding&amp;nbsp;Security Bulletin CA19-04.

&lt;H3&gt;Steps&lt;/H3&gt;
&lt;SPAN style="font-family: verdana,geneva,sans-serif;"&gt;&lt;B&gt;Q: Why have we set the severity to HIGH?&lt;/B&gt;&lt;BR /&gt;A: Idira uses a published security policy, which they can find here: &lt;A href="https://www.cyberark.com/product-security/" target="_blank"&gt;https://www.cyberark.com/product-security/&lt;/A&gt;. This policy explains how we assess the security severity rating of an issue we find. Look for "Severity Rating" in the policy to find an explanation on how it is determined.&lt;BR /&gt;&lt;BR /&gt;&lt;B&gt;Q: Can you also please provide some information on how we can validate the vulnerability CA19-014 ? We would like to validate that the vulnerability exists in v 9.10 and then look at the remediation in v10.8 of the PSM.&lt;/B&gt;&lt;BR /&gt;A: The vulnerability exists also in V9.10 if the customer uses the KeystrokesAudit or KeystrokesTextRecorder capabilities.&lt;BR /&gt;&amp;nbsp;&lt;BR /&gt;&lt;B&gt;Q: How does PSM v10.8 resolve the issue with keystroke logs described in CA19-04? Are the keystroke logs encrypted or no longer cached on the PSM server?&lt;/B&gt;&lt;BR /&gt;A: The issue described in the bulletin was discovered internally by CyberArk. We cannot provide more details on the mitigation without revealing possible attack vectors and exposing customers to risk. I can share that we added additional restrictions in PSM v10.8 that prevent an administrative user, who was granted permissions to connect to the PSM Server, from accessing the keystrokes logs.&lt;BR /&gt;&amp;nbsp;&lt;BR /&gt;&lt;B&gt;Q: What can I do in the mean time while I get approvals to upgrade to 10.8?&lt;/B&gt;&lt;BR /&gt;A: Delete or disable the KeystrokeAudit and KeystrokesTextRecorder settings in one of the following 3 ways:&lt;BR /&gt;&lt;B&gt;Option 1: Globally&lt;/B&gt;&lt;BR /&gt;Disabling the capability under &lt;B&gt;Options -&amp;gt; Privileged Session Manager -&amp;gt; Connection client settings -&amp;gt; Capabilities&lt;/B&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="eid=ka32J000000bn0q&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000001Ei06.jpg"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/96467i36E16A8194893F8A/image-size/large?v=v2&amp;amp;px=999" role="button" title="eid=ka32J000000bn0q&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000001Ei06.jpg" alt="eid=ka32J000000bn0q&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000001Ei06.jpg" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;B&gt;Option 2: In each connection component:&lt;/B&gt;&lt;BR /&gt;See highlighted below an example for OS390 connector. They can be manually added back later after the PSMs are upgraded to restore this functionality:&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="eid=ka32J000000bn0q&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000001Ei0B.jpg"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/96468i369CD700D380F0D8/image-size/large?v=v2&amp;amp;px=999" role="button" title="eid=ka32J000000bn0q&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000001Ei0B.jpg" alt="eid=ka32J000000bn0q&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000001Ei0B.jpg" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;B&gt;Option 3: At platform level:&lt;/B&gt;&lt;/SPAN&gt;
&lt;OL&gt;&lt;LI style="color: black;"&gt;&lt;SPAN style="font-family: verdana,geneva,sans-serif;"&gt;Click&amp;nbsp;&lt;B&gt;ADMINISTRATION&amp;nbsp;&lt;/B&gt;to display the&amp;nbsp;&lt;B&gt;System Configuration&amp;nbsp;&lt;/B&gt;page, then click&amp;nbsp;&lt;B&gt;Platform Management&amp;nbsp;&lt;/B&gt;to display a list of supported target account platforms.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="color: black;"&gt;&lt;SPAN style="font-family: verdana,geneva,sans-serif;"&gt;Select the platform to configure, then click&amp;nbsp;&lt;B&gt;Edit&lt;/B&gt;; the settings page for the selected platform appears.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="color: black;"&gt;&lt;SPAN style="font-family: verdana,geneva,sans-serif;"&gt;Expand&amp;nbsp;&lt;B&gt;UI &amp;amp; Workflows&lt;/B&gt;, and right-click&amp;nbsp;&lt;B&gt;Privileged Session Management&lt;/B&gt;.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="color: black;"&gt;&lt;SPAN style="font-family: verdana,geneva,sans-serif;"&gt;From the pop-up menu, select&amp;nbsp;&lt;B&gt;Add Audit Settings&lt;/B&gt;; a new parameter is added to the Privileged Session Management settings.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="color: black;"&gt;&lt;SPAN style="font-family: verdana,geneva,sans-serif;"&gt;Select&amp;nbsp;&lt;B&gt;Audit Settings&lt;/B&gt;, then from the pop-up menu, select&amp;nbsp;&lt;B&gt;Add Keystrokes Audit&lt;/B&gt;.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="color: black;"&gt;&lt;SPAN style="font-family: verdana,geneva,sans-serif;"&gt;In the Properties list, set the value of&amp;nbsp;&lt;B&gt;Enable&amp;nbsp;&lt;/B&gt;to&amp;nbsp;&lt;B&gt;No&lt;/B&gt;.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="color: black;"&gt;&lt;SPAN style="font-family: verdana,geneva,sans-serif;"&gt;Right-click&amp;nbsp;&lt;B&gt;Privileged Session Management&lt;/B&gt;, a pop-up menu displays the parameter sets that you can add and customize to manage your PSM recordings.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="color: black;"&gt;&lt;SPAN style="font-family: verdana,geneva,sans-serif;"&gt;From the pop-up menu, select&amp;nbsp;&lt;B&gt;Add Recorder Settings&lt;/B&gt;; a new set of parameters called Recorder Settings is added&lt;/SPAN&gt;&lt;/LI&gt;&lt;/OL&gt;
&lt;OL style="list-style-type: lower-alpha;"&gt;&lt;LI style="color: black;"&gt;&lt;SPAN style="font-family: verdana,geneva,sans-serif;"&gt;Right-click&amp;nbsp;&lt;B&gt;Recorder Settings&lt;/B&gt;, then select&amp;nbsp;&lt;B&gt;Add Keystrokes Text Recorder&lt;/B&gt;; a new set of parameters called Keystrokes Text Recorder is added.&lt;/SPAN&gt;&lt;/LI&gt;&lt;/OL&gt;
&lt;OL&gt;&lt;LI style="color: black;"&gt;&lt;SPAN style="font-family: verdana,geneva,sans-serif;"&gt;To disable auditing for any component, in the Properties list, set the value of&amp;nbsp;&lt;B&gt;Enable&amp;nbsp;&lt;/B&gt;to&amp;nbsp;&lt;B&gt;No&lt;/B&gt;.&lt;/SPAN&gt;&lt;/LI&gt;&lt;/OL&gt;
&lt;SPAN style="font-family: verdana,geneva,sans-serif;"&gt;&lt;B&gt;Q: Are all types of PSM connections exposed?&lt;/B&gt;&lt;BR /&gt;A: No. Only PSM connection components that are configured with the KeystrokesAudit or KeystrokesTextRecorder parameters are exposed.&lt;BR /&gt;&lt;BR /&gt;&lt;B&gt;Q: My PSM server is not hardened according to CyberArk’s hardening procedure. Does this increase my exposure to this issue?&lt;/B&gt;&lt;BR /&gt;A: PSM hardening is designed to deny unauthorized users the ability to connect directly to the PSM Server and therefore limits this issue to authorized administrative users. If the PSM is not hardened, the issue may be exploited by a larger range of users.&lt;BR /&gt;&lt;BR /&gt;&lt;B&gt;Q: Is there a need to upgrade any PAS components other than the PSM?&lt;/B&gt;&lt;BR /&gt;A:No, PSM v10.8 is compatible with previous versions of PAS components.&lt;BR /&gt;&lt;BR /&gt;&lt;B&gt;Q:&amp;nbsp;I’m not using the keystrokes logging capability, do I still need to upgrade my PSM?&lt;/B&gt;&lt;BR /&gt;A: While the issue does not affect customers who are not using the keystrokes logging capability, Idira recommends that you upgrade to v10.8 or higher to be protected in case of future use of this capability.&lt;BR /&gt;&lt;BR /&gt;&lt;B&gt;Q: Does this issue put the Vault Server at risk?&lt;/B&gt;&lt;BR /&gt;A: No.&lt;BR /&gt;&lt;BR /&gt;&lt;B&gt;Q: Can this issue be exploited remotely?&lt;/B&gt;&lt;BR /&gt;A: No. An exploit requires that a user logs in to the PSM server.&lt;BR /&gt;&lt;BR /&gt;&lt;B&gt;Q: Is there a public exploit for this issue?&lt;/B&gt;&lt;BR /&gt;A: No. This vulnerability was discovered by CyberArk. Idira has not received any information that indicates that this issue has been publicly exploited.&lt;/SPAN&gt;</description>
    <pubDate>Thu, 05 Nov 2026 20:12:44 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2026-11-05T20:12:44Z</dc:date>
    <item>
      <title>Security Bulletin CA19-04 - FAQs</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-articles/security-bulletin-ca19-04-faqs/ta-p/1427381</link>
      <description>Please see below some Frequently Asked Questions and Responses regarding&amp;nbsp;Security Bulletin CA19-04.

&lt;H3&gt;Steps&lt;/H3&gt;
&lt;SPAN style="font-family: verdana,geneva,sans-serif;"&gt;&lt;B&gt;Q: Why have we set the severity to HIGH?&lt;/B&gt;&lt;BR /&gt;A: Idira uses a published security policy, which they can find here: &lt;A href="https://www.cyberark.com/product-security/" target="_blank"&gt;https://www.cyberark.com/product-security/&lt;/A&gt;. This policy explains how we assess the security severity rating of an issue we find. Look for "Severity Rating" in the policy to find an explanation on how it is determined.&lt;BR /&gt;&lt;BR /&gt;&lt;B&gt;Q: Can you also please provide some information on how we can validate the vulnerability CA19-014 ? We would like to validate that the vulnerability exists in v 9.10 and then look at the remediation in v10.8 of the PSM.&lt;/B&gt;&lt;BR /&gt;A: The vulnerability exists also in V9.10 if the customer uses the KeystrokesAudit or KeystrokesTextRecorder capabilities.&lt;BR /&gt;&amp;nbsp;&lt;BR /&gt;&lt;B&gt;Q: How does PSM v10.8 resolve the issue with keystroke logs described in CA19-04? Are the keystroke logs encrypted or no longer cached on the PSM server?&lt;/B&gt;&lt;BR /&gt;A: The issue described in the bulletin was discovered internally by CyberArk. We cannot provide more details on the mitigation without revealing possible attack vectors and exposing customers to risk. I can share that we added additional restrictions in PSM v10.8 that prevent an administrative user, who was granted permissions to connect to the PSM Server, from accessing the keystrokes logs.&lt;BR /&gt;&amp;nbsp;&lt;BR /&gt;&lt;B&gt;Q: What can I do in the mean time while I get approvals to upgrade to 10.8?&lt;/B&gt;&lt;BR /&gt;A: Delete or disable the KeystrokeAudit and KeystrokesTextRecorder settings in one of the following 3 ways:&lt;BR /&gt;&lt;B&gt;Option 1: Globally&lt;/B&gt;&lt;BR /&gt;Disabling the capability under &lt;B&gt;Options -&amp;gt; Privileged Session Manager -&amp;gt; Connection client settings -&amp;gt; Capabilities&lt;/B&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="eid=ka32J000000bn0q&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000001Ei06.jpg"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/96467i36E16A8194893F8A/image-size/large?v=v2&amp;amp;px=999" role="button" title="eid=ka32J000000bn0q&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000001Ei06.jpg" alt="eid=ka32J000000bn0q&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000001Ei06.jpg" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;B&gt;Option 2: In each connection component:&lt;/B&gt;&lt;BR /&gt;See highlighted below an example for OS390 connector. They can be manually added back later after the PSMs are upgraded to restore this functionality:&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="eid=ka32J000000bn0q&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000001Ei0B.jpg"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/96468i369CD700D380F0D8/image-size/large?v=v2&amp;amp;px=999" role="button" title="eid=ka32J000000bn0q&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000001Ei0B.jpg" alt="eid=ka32J000000bn0q&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000001Ei0B.jpg" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;B&gt;Option 3: At platform level:&lt;/B&gt;&lt;/SPAN&gt;
&lt;OL&gt;&lt;LI style="color: black;"&gt;&lt;SPAN style="font-family: verdana,geneva,sans-serif;"&gt;Click&amp;nbsp;&lt;B&gt;ADMINISTRATION&amp;nbsp;&lt;/B&gt;to display the&amp;nbsp;&lt;B&gt;System Configuration&amp;nbsp;&lt;/B&gt;page, then click&amp;nbsp;&lt;B&gt;Platform Management&amp;nbsp;&lt;/B&gt;to display a list of supported target account platforms.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="color: black;"&gt;&lt;SPAN style="font-family: verdana,geneva,sans-serif;"&gt;Select the platform to configure, then click&amp;nbsp;&lt;B&gt;Edit&lt;/B&gt;; the settings page for the selected platform appears.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="color: black;"&gt;&lt;SPAN style="font-family: verdana,geneva,sans-serif;"&gt;Expand&amp;nbsp;&lt;B&gt;UI &amp;amp; Workflows&lt;/B&gt;, and right-click&amp;nbsp;&lt;B&gt;Privileged Session Management&lt;/B&gt;.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="color: black;"&gt;&lt;SPAN style="font-family: verdana,geneva,sans-serif;"&gt;From the pop-up menu, select&amp;nbsp;&lt;B&gt;Add Audit Settings&lt;/B&gt;; a new parameter is added to the Privileged Session Management settings.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="color: black;"&gt;&lt;SPAN style="font-family: verdana,geneva,sans-serif;"&gt;Select&amp;nbsp;&lt;B&gt;Audit Settings&lt;/B&gt;, then from the pop-up menu, select&amp;nbsp;&lt;B&gt;Add Keystrokes Audit&lt;/B&gt;.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="color: black;"&gt;&lt;SPAN style="font-family: verdana,geneva,sans-serif;"&gt;In the Properties list, set the value of&amp;nbsp;&lt;B&gt;Enable&amp;nbsp;&lt;/B&gt;to&amp;nbsp;&lt;B&gt;No&lt;/B&gt;.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="color: black;"&gt;&lt;SPAN style="font-family: verdana,geneva,sans-serif;"&gt;Right-click&amp;nbsp;&lt;B&gt;Privileged Session Management&lt;/B&gt;, a pop-up menu displays the parameter sets that you can add and customize to manage your PSM recordings.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="color: black;"&gt;&lt;SPAN style="font-family: verdana,geneva,sans-serif;"&gt;From the pop-up menu, select&amp;nbsp;&lt;B&gt;Add Recorder Settings&lt;/B&gt;; a new set of parameters called Recorder Settings is added&lt;/SPAN&gt;&lt;/LI&gt;&lt;/OL&gt;
&lt;OL style="list-style-type: lower-alpha;"&gt;&lt;LI style="color: black;"&gt;&lt;SPAN style="font-family: verdana,geneva,sans-serif;"&gt;Right-click&amp;nbsp;&lt;B&gt;Recorder Settings&lt;/B&gt;, then select&amp;nbsp;&lt;B&gt;Add Keystrokes Text Recorder&lt;/B&gt;; a new set of parameters called Keystrokes Text Recorder is added.&lt;/SPAN&gt;&lt;/LI&gt;&lt;/OL&gt;
&lt;OL&gt;&lt;LI style="color: black;"&gt;&lt;SPAN style="font-family: verdana,geneva,sans-serif;"&gt;To disable auditing for any component, in the Properties list, set the value of&amp;nbsp;&lt;B&gt;Enable&amp;nbsp;&lt;/B&gt;to&amp;nbsp;&lt;B&gt;No&lt;/B&gt;.&lt;/SPAN&gt;&lt;/LI&gt;&lt;/OL&gt;
&lt;SPAN style="font-family: verdana,geneva,sans-serif;"&gt;&lt;B&gt;Q: Are all types of PSM connections exposed?&lt;/B&gt;&lt;BR /&gt;A: No. Only PSM connection components that are configured with the KeystrokesAudit or KeystrokesTextRecorder parameters are exposed.&lt;BR /&gt;&lt;BR /&gt;&lt;B&gt;Q: My PSM server is not hardened according to CyberArk’s hardening procedure. Does this increase my exposure to this issue?&lt;/B&gt;&lt;BR /&gt;A: PSM hardening is designed to deny unauthorized users the ability to connect directly to the PSM Server and therefore limits this issue to authorized administrative users. If the PSM is not hardened, the issue may be exploited by a larger range of users.&lt;BR /&gt;&lt;BR /&gt;&lt;B&gt;Q: Is there a need to upgrade any PAS components other than the PSM?&lt;/B&gt;&lt;BR /&gt;A:No, PSM v10.8 is compatible with previous versions of PAS components.&lt;BR /&gt;&lt;BR /&gt;&lt;B&gt;Q:&amp;nbsp;I’m not using the keystrokes logging capability, do I still need to upgrade my PSM?&lt;/B&gt;&lt;BR /&gt;A: While the issue does not affect customers who are not using the keystrokes logging capability, Idira recommends that you upgrade to v10.8 or higher to be protected in case of future use of this capability.&lt;BR /&gt;&lt;BR /&gt;&lt;B&gt;Q: Does this issue put the Vault Server at risk?&lt;/B&gt;&lt;BR /&gt;A: No.&lt;BR /&gt;&lt;BR /&gt;&lt;B&gt;Q: Can this issue be exploited remotely?&lt;/B&gt;&lt;BR /&gt;A: No. An exploit requires that a user logs in to the PSM server.&lt;BR /&gt;&lt;BR /&gt;&lt;B&gt;Q: Is there a public exploit for this issue?&lt;/B&gt;&lt;BR /&gt;A: No. This vulnerability was discovered by CyberArk. Idira has not received any information that indicates that this issue has been publicly exploited.&lt;/SPAN&gt;</description>
      <pubDate>Thu, 05 Nov 2026 20:12:44 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-articles/security-bulletin-ca19-04-faqs/ta-p/1427381</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2026-11-05T20:12:44Z</dc:date>
    </item>
  </channel>
</rss>

