<?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 An explicit deny allows one in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/deny-in-firewall/m-p/2535511#M237642</link>
    <description>&lt;P&gt;An explicit deny allows one to generate log messages for the packets that are denied.&lt;/P&gt;&lt;P&gt;Some organizations use those for analysis and/or blacklisting / shunning of the source IPs.&lt;/P&gt;&lt;P&gt;The other reason I have seen cited is that it keeps some auditors happier to see the explicit denies. &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 10 Jun 2014 02:00:36 GMT</pubDate>
    <dc:creator>Marvin Rhoads</dc:creator>
    <dc:date>2014-06-10T02:00:36Z</dc:date>
    <item>
      <title>Deny in firewall</title>
      <link>https://community.cisco.com/t5/network-security/deny-in-firewall/m-p/2535510#M237638</link>
      <description>Why do we write a 'deny' statement in the firewall, when there is always an 'implicit deny' at the end of the access list</description>
      <pubDate>Tue, 12 Mar 2019 04:18:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/deny-in-firewall/m-p/2535510#M237638</guid>
      <dc:creator>grapevine</dc:creator>
      <dc:date>2019-03-12T04:18:45Z</dc:date>
    </item>
    <item>
      <title>An explicit deny allows one</title>
      <link>https://community.cisco.com/t5/network-security/deny-in-firewall/m-p/2535511#M237642</link>
      <description>&lt;P&gt;An explicit deny allows one to generate log messages for the packets that are denied.&lt;/P&gt;&lt;P&gt;Some organizations use those for analysis and/or blacklisting / shunning of the source IPs.&lt;/P&gt;&lt;P&gt;The other reason I have seen cited is that it keeps some auditors happier to see the explicit denies. &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 10 Jun 2014 02:00:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/deny-in-firewall/m-p/2535511#M237642</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2014-06-10T02:00:36Z</dc:date>
    </item>
    <item>
      <title>further adding to marvin's</title>
      <link>https://community.cisco.com/t5/network-security/deny-in-firewall/m-p/2535512#M237646</link>
      <description>&lt;P&gt;further adding to marvin's post, we put an explicit deny (on 'outside' interface) in order to customize the logging level and interval of syslog message 106100.&lt;/P&gt;&lt;P&gt;http://www.cisco.com/en/US/docs/security/asa/asa80/system/message/logmsgs.html#wp4769049&lt;/P&gt;</description>
      <pubDate>Tue, 10 Jun 2014 07:08:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/deny-in-firewall/m-p/2535512#M237646</guid>
      <dc:creator>johnlloyd_13</dc:creator>
      <dc:date>2014-06-10T07:08:46Z</dc:date>
    </item>
  </channel>
</rss>

