<?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: Incomplete application matching app-id rule in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/incomplete-application-matching-app-id-rule/m-p/79075#M43138</link>
    <description>&lt;P&gt;Thanks for the quick response Tom!&lt;/P&gt;</description>
    <pubDate>Fri, 03 Jun 2016 14:21:23 GMT</pubDate>
    <dc:creator>bdugger</dc:creator>
    <dc:date>2016-06-03T14:21:23Z</dc:date>
    <item>
      <title>Incomplete application matching app-id rule</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/incomplete-application-matching-app-id-rule/m-p/79032#M43116</link>
      <description>&lt;P&gt;I have a rule matching for ms-update app-id, but when looking at logs I see sessions hitting the rule that have an imcomplete application.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;How is this possible?&lt;/P&gt;</description>
      <pubDate>Thu, 02 Jun 2016 17:52:10 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/incomplete-application-matching-app-id-rule/m-p/79032#M43116</guid>
      <dc:creator>bdugger</dc:creator>
      <dc:date>2016-06-02T17:52:10Z</dc:date>
    </item>
    <item>
      <title>Re: Incomplete application matching app-id rule</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/incomplete-application-matching-app-id-rule/m-p/79051#M43122</link>
      <description>&lt;P&gt;hi bdugger,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;That behavior is explained in this article :&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://live.paloaltonetworks.com/t5/Management-Articles/Not-Applicable-Incomplete-Insufficient-Data-in-the-Application/ta-p/65711" target="_blank"&gt;Not-Applicable-Incomplete-Insufficient-Data-in-the-Application&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Incomplete means that either the three-way TCP handshake did &lt;/SPAN&gt;&lt;STRONG&gt;not&lt;/STRONG&gt;&lt;SPAN&gt; complete or the three-way TCP handshake did complete but there was no data after the handshake to identify the application. &lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 03 Jun 2016 07:12:05 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/incomplete-application-matching-app-id-rule/m-p/79051#M43122</guid>
      <dc:creator>kiwi</dc:creator>
      <dc:date>2016-06-03T07:12:05Z</dc:date>
    </item>
    <item>
      <title>Re: Incomplete application matching app-id rule</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/incomplete-application-matching-app-id-rule/m-p/79052#M43123</link>
      <description>&lt;P&gt;a single session will actually go through the security policy twice&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;When a new session is initiated, the SYN packet does not contain a lot of information that can be used for AppID, so it will be parsed against the security policy based on the 5 tuples: source zone, source subnet, destination zone, destination subnet, destination port&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;in the security policy the configured applications will be ignored in this stage (as we don't know the app yet) and sessions wil be matched based on the destination port (this is why setting 'application-default' in the service is important!)&lt;/P&gt;
&lt;P&gt;if a rule is matched that allows the 5 tuples, the handshake is allowed through and a session is created in the session table&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;if then after the handshake nothing happens, the session will timeout and be discarded, the application will be set as incomplete because it never continued.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;however, because the session was created, we still want to have a log entry in the traffic log to indicate the session was there, but because it never managed to reach the next stage where AppID could be applied, it was never matched against a different policy so it will be logged as a hit on the first policy that simply let the session be created&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;hope this makes sense&lt;/P&gt;
&lt;P&gt;Tom&lt;/P&gt;</description>
      <pubDate>Fri, 03 Jun 2016 07:14:53 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/incomplete-application-matching-app-id-rule/m-p/79052#M43123</guid>
      <dc:creator>reaper</dc:creator>
      <dc:date>2016-06-03T07:14:53Z</dc:date>
    </item>
    <item>
      <title>Re: Incomplete application matching app-id rule</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/incomplete-application-matching-app-id-rule/m-p/79075#M43138</link>
      <description>&lt;P&gt;Thanks for the quick response Tom!&lt;/P&gt;</description>
      <pubDate>Fri, 03 Jun 2016 14:21:23 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/incomplete-application-matching-app-id-rule/m-p/79075#M43138</guid>
      <dc:creator>bdugger</dc:creator>
      <dc:date>2016-06-03T14:21:23Z</dc:date>
    </item>
  </channel>
</rss>

