<?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: No findings yet, Neno. Sorry. in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/firepower-not-blocking-while-pruning/m-p/3705553#M43642</link>
    <description>&lt;P&gt;Peter,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Were you able to find any such information for your query?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 12 Sep 2018 13:20:53 GMT</pubDate>
    <dc:creator>pro_engineering</dc:creator>
    <dc:date>2018-09-12T13:20:53Z</dc:date>
    <item>
      <title>FirePOWER not blocking while pruning?</title>
      <link>https://community.cisco.com/t5/network-security/firepower-not-blocking-while-pruning/m-p/2970266#M43636</link>
      <description>&lt;P&gt;I&amp;nbsp;have found&amp;nbsp;some events of type&amp;nbsp;&lt;STRONG&gt;Would have dropped&lt;/STRONG&gt; in ASA-Firepower FMC logs. The guide explains&lt;/P&gt;
&lt;BLOCKQUOTE&gt;
&lt;P&gt;The event type is always &lt;STRONG&gt;Would have dropped&lt;/STRONG&gt; for packets seen while the system is pruning, regardless of deployment.&lt;/P&gt;
&lt;P&gt;[...]&lt;/P&gt;
&lt;P&gt;&amp;nbsp;the system sometimes prunes older event details to manage disk space usage.&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;
&lt;P&gt;The module is inline and IPS policy is set to &lt;STRONG&gt;Drop when Inline &lt;/STRONG&gt;so I can think of no other explanation.&lt;/P&gt;
&lt;P&gt;Would&amp;nbsp;Firepower really&amp;nbsp;pass traffic matching a threat pattern while it is busy pruning?? Were these packets really &lt;STRONG&gt;not&lt;/STRONG&gt; dropped?&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 13:40:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-not-blocking-while-pruning/m-p/2970266#M43636</guid>
      <dc:creator>Peter Koltl</dc:creator>
      <dc:date>2019-03-10T13:40:08Z</dc:date>
    </item>
    <item>
      <title>I would like to know the</title>
      <link>https://community.cisco.com/t5/network-security/firepower-not-blocking-while-pruning/m-p/2970267#M43638</link>
      <description>&lt;P&gt;I would like to know the answer to that question as well. Peter, were you able to find anything about this?&lt;/P&gt;
&lt;P&gt;Thanks!&lt;/P&gt;
&lt;P&gt;Neno&lt;/P&gt;</description>
      <pubDate>Wed, 24 Aug 2016 00:57:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-not-blocking-while-pruning/m-p/2970267#M43638</guid>
      <dc:creator>nspasov</dc:creator>
      <dc:date>2016-08-24T00:57:11Z</dc:date>
    </item>
    <item>
      <title>No findings yet, Neno. Sorry.</title>
      <link>https://community.cisco.com/t5/network-security/firepower-not-blocking-while-pruning/m-p/2970268#M43640</link>
      <description>&lt;P&gt;No findings yet, Neno. Sorry.&lt;/P&gt;</description>
      <pubDate>Wed, 24 Aug 2016 11:30:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-not-blocking-while-pruning/m-p/2970268#M43640</guid>
      <dc:creator>Peter Koltl</dc:creator>
      <dc:date>2016-08-24T11:30:55Z</dc:date>
    </item>
    <item>
      <title>Re: No findings yet, Neno. Sorry.</title>
      <link>https://community.cisco.com/t5/network-security/firepower-not-blocking-while-pruning/m-p/3705553#M43642</link>
      <description>&lt;P&gt;Peter,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Were you able to find any such information for your query?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 12 Sep 2018 13:20:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-not-blocking-while-pruning/m-p/3705553#M43642</guid>
      <dc:creator>pro_engineering</dc:creator>
      <dc:date>2018-09-12T13:20:53Z</dc:date>
    </item>
  </channel>
</rss>

