<?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 5508 - Block IP addresses doing Proxy scans in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-5508-block-ip-addresses-doing-proxy-scans/m-p/4470091#M1083838</link>
    <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/234642"&gt;@tpennington&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You can only attach 1 ACL to an interface in the same direction. So your ACL "External-Verizon_access_in_1" is the current ACL which is attached inbound on your outside interface, you'll need to add those IP networks to block in that ACL.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;access-list &lt;STRONG&gt;External-Verizon_access_in_1&lt;/STRONG&gt; extended deny ip 207.180.212.0 255.255.255.0 any log&lt;BR /&gt;access-list &lt;STRONG&gt;External-Verizon_access_in_1&lt;/STRONG&gt; extended deny ip 87.246.7.0 255.255.255.0 any log&lt;BR /&gt;access-list &lt;STRONG&gt;External-Verizon_access_in_1&lt;/STRONG&gt; extended deny ip 5.188.206.0 255.255.255.0 any log&lt;/PRE&gt;
&lt;P&gt;These rules will obviously need to be above the existing rules.&lt;/P&gt;</description>
    <pubDate>Mon, 20 Sep 2021 12:55:59 GMT</pubDate>
    <dc:creator>Rob Ingram</dc:creator>
    <dc:date>2021-09-20T12:55:59Z</dc:date>
    <item>
      <title>ASA 5508 - Block IP addresses doing Proxy scans</title>
      <link>https://community.cisco.com/t5/network-security/asa-5508-block-ip-addresses-doing-proxy-scans/m-p/4470086#M1083837</link>
      <description>&lt;P&gt;Over the past several months, I've noticed a lot of login attempts from Foreign IP addresses trying to log into my Exchange server.&amp;nbsp; The server is fully patched but I would like to block these IP's at the firewall so that they simply can't try the login attempt.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I thought I had the correct Extended ACL created, but I can still see the IP's hitting my Exchange server log.&amp;nbsp; Below are the ACL's I have, any suggestions are welcome.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;access-list External-Verizon_access_in_1 extended permit tcp any object MAIL-SERVER eq smtp&lt;BR /&gt;access-list External-Verizon_access_in_1 extended permit tcp any object MAIL-SERVER eq pop3&lt;BR /&gt;access-list External-Verizon_access_in_1 extended permit tcp any object MAIL-SERVER eq 995&lt;BR /&gt;access-list External-Verizon_access_in_1 extended permit tcp any object MAIL-SERVER eq 587&lt;BR /&gt;access-list External-Verizon_access_in_1 extended permit tcp any object MAIL-SERVER eq 465&lt;BR /&gt;access-list External-Verizon_access_in_1 extended permit tcp any object MAIL-SERVER eq 993&lt;BR /&gt;access-list External-Verizon_access_in_1 extended permit tcp any object MAIL-SERVER eq https&lt;BR /&gt;access-list External-Verizon_access_in_1 extended permit tcp any object MAIL-SERVER eq www&lt;BR /&gt;access-list External-Verizon_access_in_1 extended deny tcp any object MAIL-SERVER eq ftp&lt;BR /&gt;access-list External-Verizon_access_in_1 extended permit tcp any object MAIL-SERVER eq smtp&lt;BR /&gt;access-list External-Verizon_access_in_1 extended permit tcp any object MAIL-SERVER eq www&lt;BR /&gt;access-list External-Verizon_access_in_1 extended permit tcp any object MAIL-SERVER eq https&lt;BR /&gt;access-list External-Verizon_access_in_1 extended deny icmp any any&lt;BR /&gt;access-list External-Verizon_access_in_1 extended deny tcp any any eq 3389 log&lt;BR /&gt;access-list External-Verizon_access_in_1 extended deny ip any any log&lt;/P&gt;&lt;P&gt;access-list BLOCK-IP-RANGES extended deny ip 207.180.212.0 255.255.255.0 any log&lt;BR /&gt;access-list BLOCK-IP-RANGES extended deny ip 87.246.7.0 255.255.255.0 any log&lt;BR /&gt;access-list BLOCK-IP-RANGES extended deny ip 5.188.206.0 255.255.255.0 any log&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;as you can see, I'm trying to block the entire 5.188.206.0/24 subnet but it doesn't appear to be working.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thoughts?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 20 Sep 2021 12:50:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5508-block-ip-addresses-doing-proxy-scans/m-p/4470086#M1083837</guid>
      <dc:creator>tpennington</dc:creator>
      <dc:date>2021-09-20T12:50:22Z</dc:date>
    </item>
    <item>
      <title>Re: ASA 5508 - Block IP addresses doing Proxy scans</title>
      <link>https://community.cisco.com/t5/network-security/asa-5508-block-ip-addresses-doing-proxy-scans/m-p/4470091#M1083838</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/234642"&gt;@tpennington&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You can only attach 1 ACL to an interface in the same direction. So your ACL "External-Verizon_access_in_1" is the current ACL which is attached inbound on your outside interface, you'll need to add those IP networks to block in that ACL.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;access-list &lt;STRONG&gt;External-Verizon_access_in_1&lt;/STRONG&gt; extended deny ip 207.180.212.0 255.255.255.0 any log&lt;BR /&gt;access-list &lt;STRONG&gt;External-Verizon_access_in_1&lt;/STRONG&gt; extended deny ip 87.246.7.0 255.255.255.0 any log&lt;BR /&gt;access-list &lt;STRONG&gt;External-Verizon_access_in_1&lt;/STRONG&gt; extended deny ip 5.188.206.0 255.255.255.0 any log&lt;/PRE&gt;
&lt;P&gt;These rules will obviously need to be above the existing rules.&lt;/P&gt;</description>
      <pubDate>Mon, 20 Sep 2021 12:55:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5508-block-ip-addresses-doing-proxy-scans/m-p/4470091#M1083838</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2021-09-20T12:55:59Z</dc:date>
    </item>
    <item>
      <title>Re: ASA 5508 - Block IP addresses doing Proxy scans</title>
      <link>https://community.cisco.com/t5/network-security/asa-5508-block-ip-addresses-doing-proxy-scans/m-p/4470129#M1083839</link>
      <description>&lt;P&gt;I was afraid of this.&amp;nbsp; Thanks Rob!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 20 Sep 2021 13:53:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5508-block-ip-addresses-doing-proxy-scans/m-p/4470129#M1083839</guid>
      <dc:creator>tpennington</dc:creator>
      <dc:date>2021-09-20T13:53:23Z</dc:date>
    </item>
    <item>
      <title>Re: ASA 5508 - Block IP addresses doing Proxy scans</title>
      <link>https://community.cisco.com/t5/network-security/asa-5508-block-ip-addresses-doing-proxy-scans/m-p/4470136#M1083840</link>
      <description>&lt;P&gt;Rob,&lt;/P&gt;&lt;P&gt;so what is the point of the Extended Access List then or is this a limitation/feature of the ASA?&lt;/P&gt;</description>
      <pubDate>Mon, 20 Sep 2021 13:59:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5508-block-ip-addresses-doing-proxy-scans/m-p/4470136#M1083840</guid>
      <dc:creator>tpennington</dc:creator>
      <dc:date>2021-09-20T13:59:20Z</dc:date>
    </item>
  </channel>
</rss>

