<?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 InterVLAN Firewall Options in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/intervlan-firewall-options/m-p/2332641#M342463</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What security policy are you tring to implement?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I ask becasue we seldom see small-medium networks restricting inter-VLAN traffic. We see it sometimes on larger enterprises (with dedicated firewalls for that purpose) and increasingly in data centers separating VMs or subnets ("east-west" firewalling).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;An alternative approach is separate VRF instances if the subnets never talk to one another yet share a single core.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 27 Sep 2013 00:06:46 GMT</pubDate>
    <dc:creator>Marvin Rhoads</dc:creator>
    <dc:date>2013-09-27T00:06:46Z</dc:date>
    <item>
      <title>InterVLAN Firewall Options</title>
      <link>https://community.cisco.com/t5/network-security/intervlan-firewall-options/m-p/2332640#M342461</link>
      <description>&lt;P&gt;Good morning,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am seeking advice regarding firewall capabilities between internal VLANs.&amp;nbsp; I currently have a collapsed core architecture with a single core switch (4500 series).&amp;nbsp; All internal VLAN SVIs reside on the core switch.&amp;nbsp; I'm using access lists to restrict interVLAN communications, but I am wondering what other options I have.&amp;nbsp; The only thing I can think of is to move the VLAN SVIs to an ASA.&amp;nbsp; Is that a recommended approach?&amp;nbsp; Any other suggestions would be greatly appreciated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 02:44:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/intervlan-firewall-options/m-p/2332640#M342461</guid>
      <dc:creator>Jason Fraioli</dc:creator>
      <dc:date>2019-03-12T02:44:09Z</dc:date>
    </item>
    <item>
      <title>InterVLAN Firewall Options</title>
      <link>https://community.cisco.com/t5/network-security/intervlan-firewall-options/m-p/2332641#M342463</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What security policy are you tring to implement?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I ask becasue we seldom see small-medium networks restricting inter-VLAN traffic. We see it sometimes on larger enterprises (with dedicated firewalls for that purpose) and increasingly in data centers separating VMs or subnets ("east-west" firewalling).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;An alternative approach is separate VRF instances if the subnets never talk to one another yet share a single core.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 27 Sep 2013 00:06:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/intervlan-firewall-options/m-p/2332641#M342463</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2013-09-27T00:06:46Z</dc:date>
    </item>
  </channel>
</rss>

