<?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 Locking down inside interface in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/locking-down-inside-interface/m-p/2606210#M203121</link>
    <description>&lt;P&gt;So my journey of configuring the ASA5505 I bought used off eBay continues.&lt;/P&gt;&lt;P&gt;So far I have complete functionality and everything is working but now I'd like to lock things down a little tighter. Since this is a home firewall I would imagine the amount of outgoing traffic for tivos and xboxes and iphones/ipads and the like will probably be pretty overwhelming. Are there any suggestions on how I could work towards getting a baseline of what traffic I should expect to see leaving my network out to the internet?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Would it just be as simple as logging all outgoing traffic for say a week to see what services are going out or does anyone have a more elegant solution. I think my old Asus firewall was just letting all traffic out which is how my ASA is configured now.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 12 Mar 2019 05:08:03 GMT</pubDate>
    <dc:creator>scotteberl</dc:creator>
    <dc:date>2019-03-12T05:08:03Z</dc:date>
    <item>
      <title>Locking down inside interface</title>
      <link>https://community.cisco.com/t5/network-security/locking-down-inside-interface/m-p/2606210#M203121</link>
      <description>&lt;P&gt;So my journey of configuring the ASA5505 I bought used off eBay continues.&lt;/P&gt;&lt;P&gt;So far I have complete functionality and everything is working but now I'd like to lock things down a little tighter. Since this is a home firewall I would imagine the amount of outgoing traffic for tivos and xboxes and iphones/ipads and the like will probably be pretty overwhelming. Are there any suggestions on how I could work towards getting a baseline of what traffic I should expect to see leaving my network out to the internet?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Would it just be as simple as logging all outgoing traffic for say a week to see what services are going out or does anyone have a more elegant solution. I think my old Asus firewall was just letting all traffic out which is how my ASA is configured now.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 05:08:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/locking-down-inside-interface/m-p/2606210#M203121</guid>
      <dc:creator>scotteberl</dc:creator>
      <dc:date>2019-03-12T05:08:03Z</dc:date>
    </item>
    <item>
      <title>There are a couple ow ways to</title>
      <link>https://community.cisco.com/t5/network-security/locking-down-inside-interface/m-p/2606211#M203122</link>
      <description>&lt;P&gt;There are a couple ow ways to find out how much traffic these devices will consume. But all need a network-device that "sees" the traffic. And with the ASA in place, the statistics that you can enable on the ASDM-Dashboard are a quite good starting point.&lt;/P&gt;</description>
      <pubDate>Wed, 26 Nov 2014 07:46:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/locking-down-inside-interface/m-p/2606211#M203122</guid>
      <dc:creator>Karsten Iwen</dc:creator>
      <dc:date>2014-11-26T07:46:58Z</dc:date>
    </item>
  </channel>
</rss>

