<?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: Custom threat signature- search full TCP payload of any AppId in Custom Signatures</title>
    <link>https://live.paloaltonetworks.com/t5/custom-signatures/custom-threat-signature-search-full-tcp-payload-of-any-appid/m-p/349466#M361</link>
    <description>&lt;P&gt;Replying to myself here...&lt;/P&gt;&lt;P&gt;Per this thread, it looks like my initial assumption was correct: &lt;A href="https://live.paloaltonetworks.com/t5/custom-signatures/need-help-with-creating-signature-for-pop3/m-p/74176#M4" target="_blank"&gt;https://live.paloaltonetworks.com/t5/custom-signatures/need-help-with-creating-signature-for-pop3/m-p/74176&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;...So is there any way to search the payload of a TCP datagram of a known application - but an application lacking a pre-built Context?&amp;nbsp; I think we need a Context called "raw-req-tcp-payload".&amp;nbsp; I find it hard to believe that PAN would assume that someone who goes to the trouble of creating a custom vulnerability signature would only do so for traffic that is not classified as a known application.&amp;nbsp; In fact, these are the type of people who will also go to the trouble of creating a custom application signature to eliminate unknown-tcp from their environment.&lt;/P&gt;</description>
    <pubDate>Tue, 15 Sep 2020 18:44:22 GMT</pubDate>
    <dc:creator>John.Petrucci</dc:creator>
    <dc:date>2020-09-15T18:44:22Z</dc:date>
    <item>
      <title>Custom threat signature- search full TCP payload of any AppId</title>
      <link>https://live.paloaltonetworks.com/t5/custom-signatures/custom-threat-signature-search-full-tcp-payload-of-any-appid/m-p/349450#M360</link>
      <description>&lt;P&gt;I'm trying to write a custom threat signature.&amp;nbsp; The pattern matches just fine if I send it using netcat, but it does not match the actual application traffic.&amp;nbsp; I believe that this is because the actual traffic is processed and detected as a known application, whereas the signature Context is "unknown-req-tcp-payload".&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is this context only for traffic that is application = unknown-tcp?&amp;nbsp; If a known application is detected, does "unknown-req-tcp-payload" not apply?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 15 Sep 2020 18:30:57 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/custom-signatures/custom-threat-signature-search-full-tcp-payload-of-any-appid/m-p/349450#M360</guid>
      <dc:creator>John.Petrucci</dc:creator>
      <dc:date>2020-09-15T18:30:57Z</dc:date>
    </item>
    <item>
      <title>Re: Custom threat signature- search full TCP payload of any AppId</title>
      <link>https://live.paloaltonetworks.com/t5/custom-signatures/custom-threat-signature-search-full-tcp-payload-of-any-appid/m-p/349466#M361</link>
      <description>&lt;P&gt;Replying to myself here...&lt;/P&gt;&lt;P&gt;Per this thread, it looks like my initial assumption was correct: &lt;A href="https://live.paloaltonetworks.com/t5/custom-signatures/need-help-with-creating-signature-for-pop3/m-p/74176#M4" target="_blank"&gt;https://live.paloaltonetworks.com/t5/custom-signatures/need-help-with-creating-signature-for-pop3/m-p/74176&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;...So is there any way to search the payload of a TCP datagram of a known application - but an application lacking a pre-built Context?&amp;nbsp; I think we need a Context called "raw-req-tcp-payload".&amp;nbsp; I find it hard to believe that PAN would assume that someone who goes to the trouble of creating a custom vulnerability signature would only do so for traffic that is not classified as a known application.&amp;nbsp; In fact, these are the type of people who will also go to the trouble of creating a custom application signature to eliminate unknown-tcp from their environment.&lt;/P&gt;</description>
      <pubDate>Tue, 15 Sep 2020 18:44:22 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/custom-signatures/custom-threat-signature-search-full-tcp-payload-of-any-appid/m-p/349466#M361</guid>
      <dc:creator>John.Petrucci</dc:creator>
      <dc:date>2020-09-15T18:44:22Z</dc:date>
    </item>
    <item>
      <title>Re: Custom threat signature- search full TCP payload of any AppId</title>
      <link>https://live.paloaltonetworks.com/t5/custom-signatures/custom-threat-signature-search-full-tcp-payload-of-any-appid/m-p/349467#M362</link>
      <description>&lt;P&gt;Hi John,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You are correct in that versions prior to 10.0 you can not write a custom signature against a known application unless the decoder for that protocol/context is "exposed" in the user interface.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In 10.0, there is more flexibility, including a "context-less" signature that may meet your requirements.&amp;nbsp; Be advised that there can be performance penalties when using these expanded capabilities.&amp;nbsp; More info here:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.paloaltonetworks.com/pan-os/10-0/pan-os-new-features/content-inspection-features/enhanced-pattern-matching-engine.html#iddc51c078-bc5c-4c95-bba4-dd5763f2b549" target="_blank"&gt;https://docs.paloaltonetworks.com/pan-os/10-0/pan-os-new-features/content-inspection-features/enhanced-pattern-matching-engine.html#iddc51c078-bc5c-4c95-bba4-dd5763f2b549&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 15 Sep 2020 18:57:54 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/custom-signatures/custom-threat-signature-search-full-tcp-payload-of-any-appid/m-p/349467#M362</guid>
      <dc:creator>claudec</dc:creator>
      <dc:date>2020-09-15T18:57:54Z</dc:date>
    </item>
  </channel>
</rss>

