<?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: ASA access group in and out on same interface in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-access-group-in-and-out-on-same-interface/m-p/3394633#M955810</link>
    <description>&lt;P&gt;Got it thanks. There's a couple of inside networks and all have some services permitted in common to go outside. So I thought its easier (makes more sense) to put that on outside out once than to put it on every network and deny each other networks from reaching to all other networks on these services. Thats the idea behind it. I didint go to this detail with the example, sorry.&lt;/P&gt;</description>
    <pubDate>Tue, 05 Jun 2018 21:57:47 GMT</pubDate>
    <dc:creator>venger</dc:creator>
    <dc:date>2018-06-05T21:57:47Z</dc:date>
    <item>
      <title>ASA access group in and out on same interface</title>
      <link>https://community.cisco.com/t5/network-security/asa-access-group-in-and-out-on-same-interface/m-p/3393331#M955808</link>
      <description>&lt;P&gt;ASA CLI Book says: "&lt;SPAN&gt;You can configure one &lt;/SPAN&gt;&lt;STRONG class="ph b" id="ID-2124-0000010d__ID-2124-00000126"&gt;access-group&lt;/STRONG&gt;&lt;SPAN&gt; command per ACL type per interface per direction."&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Does this mean one command per interface, or one command per direction?&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Can we add two rules on outside interface? Sg like this:&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;access-list&amp;nbsp;OUTSIDE_IN permit tcp any host 209.165.201.3 eq 80&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;access-group&amp;nbsp;OUTSIDE_IN in interface outside&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;access-list INSIDE_OUT permit ip any any&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;access-group&amp;nbsp;INSIDE_OUT out interface outside&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 15:50:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-access-group-in-and-out-on-same-interface/m-p/3393331#M955808</guid>
      <dc:creator>venger</dc:creator>
      <dc:date>2020-02-21T15:50:41Z</dc:date>
    </item>
    <item>
      <title>Re: ASA access group in and out on same interface</title>
      <link>https://community.cisco.com/t5/network-security/asa-access-group-in-and-out-on-same-interface/m-p/3393351#M955809</link>
      <description>&lt;P&gt;you could do it the way you described, but typically you wouldnt find that way of configuring.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;so for instance, if you are internal and want to go to the internet, using the outside interface of your FW. you would stick an ACL . access-group in on your inside interface to restrict traffic to the internet this way you dont need to define an access-group out on your outside, because you have already restricted traffic on your inside interface.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;typically on a FW you have an access group in on: DMZ if. inside if and outside if, so 3 in total&lt;/P&gt;</description>
      <pubDate>Mon, 04 Jun 2018 00:35:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-access-group-in-and-out-on-same-interface/m-p/3393351#M955809</guid>
      <dc:creator>Dennis Mink</dc:creator>
      <dc:date>2018-06-04T00:35:01Z</dc:date>
    </item>
    <item>
      <title>Re: ASA access group in and out on same interface</title>
      <link>https://community.cisco.com/t5/network-security/asa-access-group-in-and-out-on-same-interface/m-p/3394633#M955810</link>
      <description>&lt;P&gt;Got it thanks. There's a couple of inside networks and all have some services permitted in common to go outside. So I thought its easier (makes more sense) to put that on outside out once than to put it on every network and deny each other networks from reaching to all other networks on these services. Thats the idea behind it. I didint go to this detail with the example, sorry.&lt;/P&gt;</description>
      <pubDate>Tue, 05 Jun 2018 21:57:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-access-group-in-and-out-on-same-interface/m-p/3394633#M955810</guid>
      <dc:creator>venger</dc:creator>
      <dc:date>2018-06-05T21:57:47Z</dc:date>
    </item>
  </channel>
</rss>

