<?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 hardening in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/firewall-hardening/m-p/2000544#M439324</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Andrea,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any firewalls should do the below mentioned things to keep the network secured.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) You real IP's of the internal network should not be exposed to outside world.&lt;/P&gt;&lt;P&gt;2) Always its mandate to block as much as possible on the outside interface i.e the traffic that comes from the outside world to your internal network.&lt;/P&gt;&lt;P&gt;3)Always keep focus on the encrypted way of communication.... VPN/Some other encryption especially when it accesed from unprotected zone.&lt;/P&gt;&lt;P&gt;4) Block the vulnerable protocols example icmp...&lt;/P&gt;&lt;P&gt;5) Preferred to use CLI instead of GUI.&lt;/P&gt;&lt;P&gt;6) Inspection to be performed on critical protocols.&lt;/P&gt;&lt;P&gt;7) Make it specific instead of any any traffic.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":smiling_face_with_sunglasses:"&gt;😎&lt;/span&gt; Syslog should be available for the logs... for artifacts and for the regular audits.&lt;/P&gt;&lt;P&gt;9) IPS/IDS should be inplace incase of internet firewall.&lt;/P&gt;&lt;P&gt;10) Update the patches whenever to match with the latest standards and well protected as required for your network.&lt;/P&gt;&lt;P&gt;11) Keep the management access very specfic i.e it should on the seperate interface or on a well protected zone.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We can keep on adding like this...... when we talk about hardening&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;By&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Karthik&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 07 Aug 2012 17:52:07 GMT</pubDate>
    <dc:creator>nkarthikeyan</dc:creator>
    <dc:date>2012-08-07T17:52:07Z</dc:date>
    <item>
      <title>Firewall hardening</title>
      <link>https://community.cisco.com/t5/network-security/firewall-hardening/m-p/2000543#M439323</link>
      <description>&lt;P&gt;Hello guys,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; I must do a node hardening on a firewall. The firewall is not from Cisco, but the vendor name is not essential for my question. I would like to know your opinions on which are the key points for a firewall hardening? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; I'm addressing this question here as this is a large community where many of you have a lot of experience and can provide some guidelines. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; Could you please help me?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you!&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 23:39:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-hardening/m-p/2000543#M439323</guid>
      <dc:creator>andr2ea_g</dc:creator>
      <dc:date>2019-03-11T23:39:12Z</dc:date>
    </item>
    <item>
      <title>Firewall hardening</title>
      <link>https://community.cisco.com/t5/network-security/firewall-hardening/m-p/2000544#M439324</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Andrea,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any firewalls should do the below mentioned things to keep the network secured.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) You real IP's of the internal network should not be exposed to outside world.&lt;/P&gt;&lt;P&gt;2) Always its mandate to block as much as possible on the outside interface i.e the traffic that comes from the outside world to your internal network.&lt;/P&gt;&lt;P&gt;3)Always keep focus on the encrypted way of communication.... VPN/Some other encryption especially when it accesed from unprotected zone.&lt;/P&gt;&lt;P&gt;4) Block the vulnerable protocols example icmp...&lt;/P&gt;&lt;P&gt;5) Preferred to use CLI instead of GUI.&lt;/P&gt;&lt;P&gt;6) Inspection to be performed on critical protocols.&lt;/P&gt;&lt;P&gt;7) Make it specific instead of any any traffic.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":smiling_face_with_sunglasses:"&gt;😎&lt;/span&gt; Syslog should be available for the logs... for artifacts and for the regular audits.&lt;/P&gt;&lt;P&gt;9) IPS/IDS should be inplace incase of internet firewall.&lt;/P&gt;&lt;P&gt;10) Update the patches whenever to match with the latest standards and well protected as required for your network.&lt;/P&gt;&lt;P&gt;11) Keep the management access very specfic i.e it should on the seperate interface or on a well protected zone.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We can keep on adding like this...... when we talk about hardening&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;By&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Karthik&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 07 Aug 2012 17:52:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-hardening/m-p/2000544#M439324</guid>
      <dc:creator>nkarthikeyan</dc:creator>
      <dc:date>2012-08-07T17:52:07Z</dc:date>
    </item>
  </channel>
</rss>

