<?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 Methods for creating security policies in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/methods-for-creating-security-policies/m-p/44952#M32998</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;When creating security policies would it be better to create a separate policy for inbound and outbound traffic, trusted and untrusted, per user group or one policy to manage both ways to minimize number of policies&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 17 Dec 2013 01:07:04 GMT</pubDate>
    <dc:creator>MemphisBrothers</dc:creator>
    <dc:date>2013-12-17T01:07:04Z</dc:date>
    <item>
      <title>Methods for creating security policies</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/methods-for-creating-security-policies/m-p/44952#M32998</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;When creating security policies would it be better to create a separate policy for inbound and outbound traffic, trusted and untrusted, per user group or one policy to manage both ways to minimize number of policies&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Dec 2013 01:07:04 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/methods-for-creating-security-policies/m-p/44952#M32998</guid>
      <dc:creator>MemphisBrothers</dc:creator>
      <dc:date>2013-12-17T01:07:04Z</dc:date>
    </item>
    <item>
      <title>Re: Methods for creating security policies</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/methods-for-creating-security-policies/m-p/44953#M32999</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello MemphisBrothers,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Most deployments choose to have separate rules for inbound and outbound traffic in order to properly log the security rule permitting the respective traffic.&lt;/P&gt;&lt;P&gt;By doing this, you could also be more granular and selective in the traffic permitted in or out of your network.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you only need to permit the same type of traffic in and out, and don't care too much about individual control on either of the directions, then you can create one policy for both directions to minimize number of policies.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;tasonibare&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Dec 2013 06:56:27 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/methods-for-creating-security-policies/m-p/44953#M32999</guid>
      <dc:creator>tasonibare</dc:creator>
      <dc:date>2013-12-17T06:56:27Z</dc:date>
    </item>
    <item>
      <title>Re: Methods for creating security policies</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/methods-for-creating-security-policies/m-p/44954#M33000</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello guys&lt;/P&gt;&lt;P&gt;a good way is:&lt;/P&gt;&lt;P&gt;you don't have to create on both direction the rule. &lt;/P&gt;&lt;P&gt;you need to create only a rule to allow the traffic base on the initiation side of this traffic, on which you could activate log at start or at end session, we prefere&amp;nbsp; at end session to minimise logs.&lt;/P&gt;&lt;P&gt;and If you want to have a log for all drop packet, create at the bottom of rule list a deny all rule base on any zone src, any zone dst, and any app with a deny action and log at start session.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Dec 2013 11:23:50 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/methods-for-creating-security-policies/m-p/44954#M33000</guid>
      <dc:creator>Gregoux</dc:creator>
      <dc:date>2013-12-17T11:23:50Z</dc:date>
    </item>
    <item>
      <title>Re: Methods for creating security policies</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/methods-for-creating-security-policies/m-p/44955#M33001</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;That's how we are doing it.&amp;nbsp; I do like more granular management to troubleshoot the apps attached to multimedia sites better.&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 18 Dec 2013 00:57:45 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/methods-for-creating-security-policies/m-p/44955#M33001</guid>
      <dc:creator>MemphisBrothers</dc:creator>
      <dc:date>2013-12-18T00:57:45Z</dc:date>
    </item>
    <item>
      <title>Re: Methods for creating security policies</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/methods-for-creating-security-policies/m-p/44956#M33002</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ok in this case you just have to follow the deny action in the log traffic, that could show you what application is reconized by palo even multimedia apps or website multimedia if you have the url categorization enabled.&lt;/P&gt;&lt;P&gt; and create rule base on application or url categorie&amp;nbsp; or service to allow that you want to allow.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regard's&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 18 Dec 2013 08:16:47 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/methods-for-creating-security-policies/m-p/44956#M33002</guid>
      <dc:creator>Gregoux</dc:creator>
      <dc:date>2013-12-18T08:16:47Z</dc:date>
    </item>
  </channel>
</rss>

