<?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 firewall lockdown in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/firewall-lockdown/m-p/2100299#M393018</link>
    <description>&lt;P&gt;I've to lockdown the firewall by ip address and port.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i.e. I've to lock down the firewall from OUTSIDE to INSIDE based on ip address &amp;amp; port. we don't know what ports we need to lock down so we would have to do logging and than find out which desinate ip and port those source IP addresses communicate to.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;what logging do we have to enable to get that level of detail?&lt;/P&gt;</description>
    <pubDate>Tue, 12 Mar 2019 00:46:08 GMT</pubDate>
    <dc:creator>gavin han</dc:creator>
    <dc:date>2019-03-12T00:46:08Z</dc:date>
    <item>
      <title>firewall lockdown</title>
      <link>https://community.cisco.com/t5/network-security/firewall-lockdown/m-p/2100299#M393018</link>
      <description>&lt;P&gt;I've to lockdown the firewall by ip address and port.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i.e. I've to lock down the firewall from OUTSIDE to INSIDE based on ip address &amp;amp; port. we don't know what ports we need to lock down so we would have to do logging and than find out which desinate ip and port those source IP addresses communicate to.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;what logging do we have to enable to get that level of detail?&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 00:46:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-lockdown/m-p/2100299#M393018</guid>
      <dc:creator>gavin han</dc:creator>
      <dc:date>2019-03-12T00:46:08Z</dc:date>
    </item>
    <item>
      <title>firewall lockdown</title>
      <link>https://community.cisco.com/t5/network-security/firewall-lockdown/m-p/2100300#M393025</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you have an ACL permitting some traffic from the OUTSIDE to INSIDE, all the rest of the traffic should already be blocked by the Implicit Deny at the end of every ACL (doesnt show in the CLI format of the configuration but shows on the ASDM side)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is you OUTSIDE interface ACL very open at the moment?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Your logging level should be atleast "informational"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This would mean configurations like&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;logging on&lt;/P&gt;&lt;P&gt;logging device-id hostname&lt;/P&gt;&lt;P&gt;logging timestamp&lt;/P&gt;&lt;P&gt;logging trap informational&lt;/P&gt;&lt;P&gt;logging host &lt;INTERFACE&gt; &lt;IP address=""&gt;&lt;/IP&gt;&lt;/INTERFACE&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Which would&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Enabled logging&lt;/LI&gt;&lt;LI&gt;Add your firewall "hostname" to the log messages sent&lt;/LI&gt;&lt;LI&gt;Add "timestamp" to your log messages&lt;/LI&gt;&lt;LI&gt;Send log messages up to "informational" level&lt;UL&gt;&lt;LI&gt;which would log Connection/NAT forming and teardown and denied connections&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;Would specify a Syslog server behind &lt;INTERFACE&gt; with the IP address of &lt;IP address=""&gt;&lt;/IP&gt;&lt;/INTERFACE&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Jouni&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 12 Jan 2013 16:58:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-lockdown/m-p/2100300#M393025</guid>
      <dc:creator>Jouni Forss</dc:creator>
      <dc:date>2013-01-12T16:58:26Z</dc:date>
    </item>
    <item>
      <title>firewall lockdown</title>
      <link>https://community.cisco.com/t5/network-security/firewall-lockdown/m-p/2100301#M393029</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Is this ASA or FWSM? If this is ASA then, high to low security traffic (inside to outside) is automatically allowed without an ACL applied on the inside interface. From outside to inside, you would have to allow what is needed via ACL.&lt;/P&gt;&lt;P&gt;If you have webservers behind the ASA then, you would have allow people on the internet to be able to access it and can't restrict it based on source IP addresses on the internet unless you know who you need to allow permission from the internet to access your web server. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As far as logging is concerned, pls. follow what Jouni has suggested. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Pls. join me on Tuesday.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="https://community.cisco.com/community/netpro/expert-corner"&gt;https://supportforums.cisco.com/community/netpro/expert-corner#view=webcasts&lt;/A&gt;&lt;/P&gt;&lt;P style="background-color: #ffffff; border-collapse: collapse; font-size: 12px; list-style: none; margin: 10px 0px; color: #333333; font-family: Arial, Helvetica, sans-serif; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: 16px; orphans: 2; text-align: left; text-transform: none; white-space: normal; widows: 2;"&gt;&lt;STRONG style="border-collapse: collapse; font-size: 12px; list-style: none;"&gt;&lt;SPAN style="font-size: 14pt;"&gt;Upcoming Live Webcast in&lt;/SPAN&gt; English&lt;SPAN style="font-size: 14pt;"&gt;:&lt;/SPAN&gt; January 15, 2013&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG style="border-collapse: collapse; font-size: 14pt; list-style: none; "&gt;Troubleshooting ASA and Firewall Service Modules&lt;/STRONG&gt;&lt;/P&gt;&lt;P style="background-color: #ffffff; border-collapse: collapse; font-size: 12px; list-style: none; margin: 10px 0px; color: #333333; font-family: Arial, Helvetica, sans-serif; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: 16px; orphans: 2; text-align: left; text-transform: none; white-space: normal; widows: 2;"&gt;&lt;A href="http://tools.cisco.com/gems/cust/customerQA.do?METHOD=E&amp;amp;LANGUAGE_ID=E&amp;amp;SEMINAR_CODE=S17664&amp;amp;PRIORITY_CODE=cisco%20" style="border-collapse: collapse; font-size: 12px; list-style: none; outline: none; color: #2f6681;"&gt;Register today for this Cisco Support Community live webcast.&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Kureli&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 13 Jan 2013 03:37:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-lockdown/m-p/2100301#M393029</guid>
      <dc:creator>Kureli Sankar</dc:creator>
      <dc:date>2013-01-13T03:37:15Z</dc:date>
    </item>
  </channel>
</rss>

