<?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: Firewall Rules in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/firewall-rules/m-p/3602646#M557175</link>
    <description>Steven&lt;BR /&gt;&lt;BR /&gt;I am not a firewall admin but working with one as I am deeply involved in a project which contains dual personality servers looking up at the internet as well as internal database servers. As you can imagine, it is very firewall heavy.&lt;BR /&gt;&lt;BR /&gt;Yes the adaptive tuning is the method but quite the other way than how you are thinking of tuning it the way we do it for this project. Especially complex projects and developers of these projects do not always know which ports they need open all the time. And when something is not working, asking them does not really help.&lt;BR /&gt;&lt;BR /&gt;So what we do is, we start implementation with a firewall ruleset which is wide open, i.e. a NATing passthru conduit. Then once our app is working as expected, the network guys attach a sniffer and listen to the traffic during acceptance testing. Then tighten down the firewall on the last week of acceptance testing and watch the user complaints very closely for the fine tuning.&lt;BR /&gt;&lt;BR /&gt;Just my 2 cents.</description>
    <pubDate>Fri, 12 Aug 2005 08:21:58 GMT</pubDate>
    <dc:creator>Mel Burslan</dc:creator>
    <dc:date>2005-08-12T08:21:58Z</dc:date>
    <item>
      <title>Firewall Rules</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/firewall-rules/m-p/3602645#M557174</link>
      <description>Hi everyone&lt;BR /&gt;&lt;BR /&gt;Looking for any firewall admins out there. What is your default policy/theory when implementing rules. Can you point me in the direction of any official guidelines for a rule policy and why specific suggestions are made. &lt;BR /&gt;&lt;BR /&gt;My theory is to block everything then only allow access per port basis when requested&lt;BR /&gt;&lt;BR /&gt;Also,&lt;BR /&gt;&lt;BR /&gt;If you have a customer who has subnets open to specific hosts (any tcp/udp) what would be the best way to tighten this down without causing to much impact to the currently running services&lt;BR /&gt;&lt;BR /&gt;Any pointers/help appreciated&lt;BR /&gt;&lt;BR /&gt;Thanks in advance&lt;BR /&gt;&lt;BR /&gt;Steven</description>
      <pubDate>Fri, 12 Aug 2005 08:09:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/firewall-rules/m-p/3602645#M557174</guid>
      <dc:creator>steven Burgess_2</dc:creator>
      <dc:date>2005-08-12T08:09:49Z</dc:date>
    </item>
    <item>
      <title>Re: Firewall Rules</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/firewall-rules/m-p/3602646#M557175</link>
      <description>Steven&lt;BR /&gt;&lt;BR /&gt;I am not a firewall admin but working with one as I am deeply involved in a project which contains dual personality servers looking up at the internet as well as internal database servers. As you can imagine, it is very firewall heavy.&lt;BR /&gt;&lt;BR /&gt;Yes the adaptive tuning is the method but quite the other way than how you are thinking of tuning it the way we do it for this project. Especially complex projects and developers of these projects do not always know which ports they need open all the time. And when something is not working, asking them does not really help.&lt;BR /&gt;&lt;BR /&gt;So what we do is, we start implementation with a firewall ruleset which is wide open, i.e. a NATing passthru conduit. Then once our app is working as expected, the network guys attach a sniffer and listen to the traffic during acceptance testing. Then tighten down the firewall on the last week of acceptance testing and watch the user complaints very closely for the fine tuning.&lt;BR /&gt;&lt;BR /&gt;Just my 2 cents.</description>
      <pubDate>Fri, 12 Aug 2005 08:21:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/firewall-rules/m-p/3602646#M557175</guid>
      <dc:creator>Mel Burslan</dc:creator>
      <dc:date>2005-08-12T08:21:58Z</dc:date>
    </item>
    <item>
      <title>Re: Firewall Rules</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/firewall-rules/m-p/3602647#M557176</link>
      <description>sounds like a reasonable method, thanks Mel&lt;BR /&gt;&lt;BR /&gt;Steven</description>
      <pubDate>Fri, 12 Aug 2005 08:25:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/firewall-rules/m-p/3602647#M557176</guid>
      <dc:creator>steven Burgess_2</dc:creator>
      <dc:date>2005-08-12T08:25:51Z</dc:date>
    </item>
  </channel>
</rss>

