<?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: FMC/FTD and Rule Latency Thresholding. in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/fmc-ftd-and-rule-latency-thresholding/m-p/4036601#M1067047</link>
    <description>Hi,&lt;BR /&gt;&lt;BR /&gt;The suspension will be for the snort rules not ACP rules. This means that&lt;BR /&gt;the packet will match the ACP rule and will be allowed (because your action&lt;BR /&gt;is allowed) but no inspection. All other actions will the rule will be&lt;BR /&gt;applied as well (for example generate event at beginning, end, etc).&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;**** please remember to rate useful posts.&lt;BR /&gt;</description>
    <pubDate>Thu, 27 Feb 2020 04:05:49 GMT</pubDate>
    <dc:creator>Mohammed al Baqari</dc:creator>
    <dc:date>2020-02-27T04:05:49Z</dc:date>
    <item>
      <title>FMC/FTD and Rule Latency Thresholding.</title>
      <link>https://community.cisco.com/t5/network-security/fmc-ftd-and-rule-latency-thresholding/m-p/4036535#M1067043</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a several ASAs converted to FTD, and I have enabled the latency rules 134:1 and 134:2 and I see several events generated .&lt;BR /&gt;I am not sure what happens to traffic once a rule is suspended. So, my question is:&lt;BR /&gt;If one rule is suspended because the latency threshold has been reached and the action for that rule is: allow, what would happen?&lt;BR /&gt;1. Traffic that should match that rule, does not match because it is suspended, and goes to the Default Action because does not match any other rule.&lt;BR /&gt;2. Traffic matches the rule, it is allowed, but it is not inspected.&lt;BR /&gt;3. None of the above.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Miguel&lt;/P&gt;</description>
      <pubDate>Wed, 26 Feb 2020 23:53:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fmc-ftd-and-rule-latency-thresholding/m-p/4036535#M1067043</guid>
      <dc:creator>maguiluzfr</dc:creator>
      <dc:date>2020-02-26T23:53:54Z</dc:date>
    </item>
    <item>
      <title>Re: FMC/FTD and Rule Latency Thresholding.</title>
      <link>https://community.cisco.com/t5/network-security/fmc-ftd-and-rule-latency-thresholding/m-p/4036601#M1067047</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;The suspension will be for the snort rules not ACP rules. This means that&lt;BR /&gt;the packet will match the ACP rule and will be allowed (because your action&lt;BR /&gt;is allowed) but no inspection. All other actions will the rule will be&lt;BR /&gt;applied as well (for example generate event at beginning, end, etc).&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;**** please remember to rate useful posts.&lt;BR /&gt;</description>
      <pubDate>Thu, 27 Feb 2020 04:05:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fmc-ftd-and-rule-latency-thresholding/m-p/4036601#M1067047</guid>
      <dc:creator>Mohammed al Baqari</dc:creator>
      <dc:date>2020-02-27T04:05:49Z</dc:date>
    </item>
    <item>
      <title>Re: FMC/FTD and Rule Latency Thresholding.</title>
      <link>https://community.cisco.com/t5/network-security/fmc-ftd-and-rule-latency-thresholding/m-p/4036639#M1067051</link>
      <description>Thanks Mohammed,&lt;BR /&gt;&lt;BR /&gt;The documentation is not clear about that behavior. Do you have more information, that explain that, besides de config guide?&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Miguel.</description>
      <pubDate>Thu, 27 Feb 2020 06:39:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fmc-ftd-and-rule-latency-thresholding/m-p/4036639#M1067051</guid>
      <dc:creator>maguiluzfr</dc:creator>
      <dc:date>2020-02-27T06:39:52Z</dc:date>
    </item>
  </channel>
</rss>

