<?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: How to allow any traffic destined for ASA firewall itself. in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/how-to-allow-any-traffic-destined-for-asa-firewall-itself/m-p/3329904#M550285</link>
    <description>&lt;P&gt;There is no single switch to allow this. You have to allow it service by service like that:&lt;/P&gt;
&lt;PRE&gt;ssh IP-OF-VUL-SCANNER 255.255.255.255 inside
http IP-OF-VUL-SCANNER 255.255.255.255 inside&lt;/PRE&gt;</description>
    <pubDate>Tue, 13 Feb 2018 09:34:49 GMT</pubDate>
    <dc:creator>Karsten Iwen</dc:creator>
    <dc:date>2018-02-13T09:34:49Z</dc:date>
    <item>
      <title>How to allow any traffic destined for ASA firewall itself.</title>
      <link>https://community.cisco.com/t5/network-access-control/how-to-allow-any-traffic-destined-for-asa-firewall-itself/m-p/3329882#M550283</link>
      <description>&lt;P&gt;Hi - We have ASA 5516-X firewall in our infra; we have a requirement to allow any service from vulnerability scanner to scan the ASA firewall device.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;What is the way to allow this traffic as we cannot use interface ACL to restrict the acccess&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;
&lt;P&gt;Senthil Murugan&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 18:45:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/how-to-allow-any-traffic-destined-for-asa-firewall-itself/m-p/3329882#M550283</guid>
      <dc:creator>Senthil Murugan</dc:creator>
      <dc:date>2020-02-21T18:45:21Z</dc:date>
    </item>
    <item>
      <title>Re: How to allow any traffic destined for ASA firewall itself.</title>
      <link>https://community.cisco.com/t5/network-access-control/how-to-allow-any-traffic-destined-for-asa-firewall-itself/m-p/3329904#M550285</link>
      <description>&lt;P&gt;There is no single switch to allow this. You have to allow it service by service like that:&lt;/P&gt;
&lt;PRE&gt;ssh IP-OF-VUL-SCANNER 255.255.255.255 inside
http IP-OF-VUL-SCANNER 255.255.255.255 inside&lt;/PRE&gt;</description>
      <pubDate>Tue, 13 Feb 2018 09:34:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/how-to-allow-any-traffic-destined-for-asa-firewall-itself/m-p/3329904#M550285</guid>
      <dc:creator>Karsten Iwen</dc:creator>
      <dc:date>2018-02-13T09:34:49Z</dc:date>
    </item>
    <item>
      <title>Re: How to allow any traffic destined for ASA firewall itself.</title>
      <link>https://community.cisco.com/t5/network-access-control/how-to-allow-any-traffic-destined-for-asa-firewall-itself/m-p/3329909#M550287</link>
      <description>&lt;P&gt;Thanks Karsten, unfortunately that is not practically possible for all 65535 service&amp;nbsp;and that too both TCP &amp;amp; UDP.&lt;/P&gt;
&lt;P&gt;Is there anyway i can give "any" service for those scanner IPs to scan the Firewall.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 13 Feb 2018 09:37:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/how-to-allow-any-traffic-destined-for-asa-firewall-itself/m-p/3329909#M550287</guid>
      <dc:creator>Senthil Murugan</dc:creator>
      <dc:date>2018-02-13T09:37:54Z</dc:date>
    </item>
  </channel>
</rss>

