<?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: [PTA] Detection Evasion: Command Normalization Limitation with Inline Comments and Escape Characters in PAM Self-Hosted Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/pta-detection-evasion-command-normalization-limitation-with/m-p/1300050#M3576</link>
    <description>&lt;P&gt;Hi @Italo Freitas​&amp;nbsp;,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Would you mind opening a support ticket and sharing the ticket number with me? &lt;/P&gt;&lt;P&gt;I have contacted the PTA R&amp;amp;D team, and they would like to investigate this further.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Eviatar&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 06 Jan 2026 17:55:14 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2026-01-06T17:55:14Z</dc:date>
    <item>
      <title>[PTA] Detection Evasion: Command Normalization Limitation with Inline Comments and Escape Characters</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/pta-detection-evasion-command-normalization-limitation-with/m-p/1300047#M3573</link>
      <description>&lt;P&gt;Hello everyone,&lt;/P&gt;&lt;P&gt;During recent security testing and tuning of our CyberArk Privilege Threat Analytics (PTA) implementation for monitored SSH sessions, we identified a limitation in how the engine normalizes command lines before applying detection rules.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It appears that the detection logic relies heavily on the specific syntactic form of the command and fails to handle certain shell interpretations, specifically regarding &lt;B&gt;inline comments combined with escape characters&lt;/B&gt;.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;B&gt;The Issue:&lt;/B&gt; When a high-risk command is executed in its standard form, PTA correctly triggers an alert. However, if the command is appended with a comment character (#) followed by an escape character (\), the alert is &lt;B&gt;not generated&lt;/B&gt;, even though the OS shell executes the command successfully.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;B&gt;Steps to Reproduce / Example:&lt;/B&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;B&gt;Standard Execution (Detected):&lt;/B&gt; Command: &lt;U&gt;cat /etc/passwd&lt;/U&gt;&lt;/LI&gt;&lt;LI&gt;&lt;I&gt;Result:&lt;/I&gt; PTA triggers the expected security alert.&lt;/LI&gt;&lt;LI&gt;&lt;B&gt;Obfuscated Execution (Not Detected):&lt;/B&gt; Command: &lt;U&gt;cat /etc/passwd #\&lt;/U&gt;&lt;/LI&gt;&lt;LI&gt;&lt;I&gt;Result:&lt;/I&gt; The command is executed by the OS (the shell treats the rest as a comment/continuation), but &lt;B&gt;PTA does not trigger an alert&lt;/B&gt;.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;B&gt;Analysis:&lt;/B&gt; This behavior suggests that the PTA parsing engine is not fully normalizing the command line (stripping comments or handling end-of-line escapes) before matching it against the risk patterns. This allows for simple syntactic evasion (MITRE T1562.006) of critical monitoring rules.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;B&gt;Questions for the Community:&lt;/B&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Has anyone else observed this behavior in recent PTA versions?&lt;/LI&gt;&lt;LI&gt;Is there a configuration setting or a regex adjustment within the&lt;/LI&gt;&lt;LI&gt;systemparm&lt;/LI&gt;&lt;LI&gt;or local rules definition that forces stricter normalization?&lt;/LI&gt;&lt;LI&gt;Is this a known limitation currently on the roadmap for a fix?&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any advice on how to mitigate this detection gap within the PTA configuration would be appreciated.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;</description>
      <pubDate>Tue, 06 Jan 2026 16:17:15 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/pta-detection-evasion-command-normalization-limitation-with/m-p/1300047#M3573</guid>
      <dc:creator>italo_freitas</dc:creator>
      <dc:date>2026-01-06T16:17:15Z</dc:date>
    </item>
    <item>
      <title>Re: [PTA] Detection Evasion: Command Normalization Limitation with Inline Comments and Escape Characters</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/pta-detection-evasion-command-normalization-limitation-with/m-p/1300048#M3574</link>
      <description>&lt;P&gt;Hi @Italo Freitas​&amp;nbsp;,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This is not a limitation. If the default security rules have not been modified or extended, this behavior is expected.&lt;/P&gt;&lt;P&gt;For example, if you want to trigger an alert for the scenario you described, you can update the existing security rule for&lt;/P&gt;&lt;P&gt;passwd to a pattern such as:  ^cat\s+/etc/passwd\s+#\\$    &lt;/P&gt;&lt;P&gt;&lt;A alt="https://docs.cyberark.com/pam-self-hosted/latest/en/content/pta/security-configuration.htm#Privilegedsessionanalysisandresponse" href="https://docs.cyberark.com/pam-self-hosted/latest/en/content/pta/security-configuration.htm#Privilegedsessionanalysisandresponse" target="_blank"&gt;Privileged session analysis and response&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;*Please note that regular expressions are case-sensitive across all categories, except for SQL and Windows titles.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Eviatar&lt;/P&gt;</description>
      <pubDate>Tue, 06 Jan 2026 16:43:26 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/pta-detection-evasion-command-normalization-limitation-with/m-p/1300048#M3574</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2026-01-06T16:43:26Z</dc:date>
    </item>
    <item>
      <title>Re: [PTA] Detection Evasion: Command Normalization Limitation with Inline Comments and Escape Characters</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/pta-detection-evasion-command-normalization-limitation-with/m-p/1300049#M3575</link>
      <description>&lt;P&gt;Hi &lt;A alt="https://community.cyberark.com/s/profile/0052J000009TNQEQA4" href="https://community.cyberark.com/s/profile/0052J000009TNQEQA4" target="_blank"&gt;EviatarD&lt;/A&gt;,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you for the suggestion. I tested exactly as you recommended, but unfortunately, the evasion behavior persists.&lt;/P&gt;&lt;P&gt;As shown in the attached screenshots:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;I updated the security rule by adding the suggested pattern: &lt;U&gt;^cat\s+/etc/passwd\s+#\\$&lt;/U&gt;.&lt;/LI&gt;&lt;LI&gt;I executed the command again (&lt;U&gt;cat /etc/passwd #\&lt;/U&gt;).&lt;/LI&gt;&lt;LI&gt;The command was successfully executed by the shell, but &lt;B&gt;no alert was triggered&lt;/B&gt; by PTA, even with the new rule enabled.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Beyond the fact that this specific rule did not work in my test, I believe this reinforces the original finding regarding the limitation. Attempting to manually create a RegEx for every possible syntactic variation of comments or escape characters (e.g., #\, ##, #, etc.) is not scalable or efficient.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The core issue seems to be that the engine relies on exact matching rather than performing command-line normalization (stripping comments/escapes) before inspection.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Has anyone else successfully triggered an alert for this specific end-of-line escape (#\) scenario using custom rules?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="Field_Content_versions_oct20__068Vy000016cf7vIAA.png"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/94665i240345BA77DC330B/image-size/large?v=v2&amp;amp;px=999" role="button" title="Field_Content_versions_oct20__068Vy000016cf7vIAA.png" alt="Field_Content_versions_oct20__068Vy000016cf7vIAA.png" /&gt;&lt;/span&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="Field_Content_versions_oct20__068Vy000016c4l5IAA.png"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/94663i8D826CE571FB7A41/image-size/large?v=v2&amp;amp;px=999" role="button" title="Field_Content_versions_oct20__068Vy000016c4l5IAA.png" alt="Field_Content_versions_oct20__068Vy000016c4l5IAA.png" /&gt;&lt;/span&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 06 Jan 2026 17:03:06 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/pta-detection-evasion-command-normalization-limitation-with/m-p/1300049#M3575</guid>
      <dc:creator>italo_freitas</dc:creator>
      <dc:date>2026-01-06T17:03:06Z</dc:date>
    </item>
    <item>
      <title>Re: [PTA] Detection Evasion: Command Normalization Limitation with Inline Comments and Escape Characters</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/pta-detection-evasion-command-normalization-limitation-with/m-p/1300050#M3576</link>
      <description>&lt;P&gt;Hi @Italo Freitas​&amp;nbsp;,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Would you mind opening a support ticket and sharing the ticket number with me? &lt;/P&gt;&lt;P&gt;I have contacted the PTA R&amp;amp;D team, and they would like to investigate this further.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Eviatar&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 06 Jan 2026 17:55:14 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/pta-detection-evasion-command-normalization-limitation-with/m-p/1300050#M3576</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2026-01-06T17:55:14Z</dc:date>
    </item>
    <item>
      <title>Re: [PTA] Detection Evasion: Command Normalization Limitation with Inline Comments and Escape Characters</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/pta-detection-evasion-command-normalization-limitation-with/m-p/1300051#M3577</link>
      <description>&lt;P&gt;Hi @Eviatar David​,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you for your assistance and for escalating this to the R&amp;amp;D team.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have opened the support ticket as requested. Here is the &lt;B&gt;Case Number: 04169891&lt;/B&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I look forward to hearing their findings.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Best regards, Italo Freitas&lt;/P&gt;</description>
      <pubDate>Wed, 07 Jan 2026 14:02:27 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/pta-detection-evasion-command-normalization-limitation-with/m-p/1300051#M3577</guid>
      <dc:creator>italo_freitas</dc:creator>
      <dc:date>2026-01-07T14:02:27Z</dc:date>
    </item>
    <item>
      <title>Re: [PTA] Detection Evasion: Command Normalization Limitation with Inline Comments and Escape Characters</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/pta-detection-evasion-command-normalization-limitation-with/m-p/1300052#M3578</link>
      <description>&lt;P&gt;Hi @Italo Freitas​&amp;nbsp;,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;&lt;P&gt;I’ve already contacted the support engineer assigned to your case and provided instructions for the next steps.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Eviatar&lt;/P&gt;</description>
      <pubDate>Wed, 07 Jan 2026 14:14:56 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/pta-detection-evasion-command-normalization-limitation-with/m-p/1300052#M3578</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2026-01-07T14:14:56Z</dc:date>
    </item>
  </channel>
</rss>

