<?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 Hello Krishna- in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/control-plane-acl-on-asa/m-p/2952929#M920252</link>
    <description>&lt;P&gt;Hello Krishna-&lt;/P&gt;
&lt;P&gt;Take a look at the link below that I think will help you configure control-plane based ACL for your Firewall:&lt;/P&gt;
&lt;P&gt;&lt;A href="http://www.cisco.com/c/en/us/td/docs/security/asa/asa95/configuration/firewall/asa-95-firewall-config/access-rules.html"&gt;http://www.cisco.com/c/en/us/td/docs/security/asa/asa95/configuration/firewall/asa-95-firewall-config/access-rules.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;So by adding the control-plane keyword to the ACL entry, the traffic inspection applies to traffic destined to the ASA. Without the control-plane keyword, the ACL entries will apply to traffic traversing through the ASA.&lt;/P&gt;
&lt;P&gt;Also, keep in mind that ASA based control-plane ACLs (telnet, ssh, http, etc) will override the control-plane ACL applied on the interface.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I hope this helps!&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;Thank you for rating helpful posts!&lt;/EM&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 20 Oct 2016 21:57:34 GMT</pubDate>
    <dc:creator>nspasov</dc:creator>
    <dc:date>2016-10-20T21:57:34Z</dc:date>
    <item>
      <title>Control plane ACL on ASA</title>
      <link>https://community.cisco.com/t5/network-security/control-plane-acl-on-asa/m-p/2952928#M920249</link>
      <description>&lt;P&gt;Hi!&lt;/P&gt;
&lt;P&gt;On ASA, suppose I apply a inbound control plane ACL on outside interface; what will be the impact / consequence to the inbound traffic that is using outside interface IP for PAT or Static PAT.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Control plan ACL is applied to restrict to-the-box traffic.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks in advance&lt;/P&gt;
&lt;P&gt;Krishna&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 13:56:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/control-plane-acl-on-asa/m-p/2952928#M920249</guid>
      <dc:creator>krishnadig</dc:creator>
      <dc:date>2020-02-21T13:56:30Z</dc:date>
    </item>
    <item>
      <title>Hello Krishna-</title>
      <link>https://community.cisco.com/t5/network-security/control-plane-acl-on-asa/m-p/2952929#M920252</link>
      <description>&lt;P&gt;Hello Krishna-&lt;/P&gt;
&lt;P&gt;Take a look at the link below that I think will help you configure control-plane based ACL for your Firewall:&lt;/P&gt;
&lt;P&gt;&lt;A href="http://www.cisco.com/c/en/us/td/docs/security/asa/asa95/configuration/firewall/asa-95-firewall-config/access-rules.html"&gt;http://www.cisco.com/c/en/us/td/docs/security/asa/asa95/configuration/firewall/asa-95-firewall-config/access-rules.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;So by adding the control-plane keyword to the ACL entry, the traffic inspection applies to traffic destined to the ASA. Without the control-plane keyword, the ACL entries will apply to traffic traversing through the ASA.&lt;/P&gt;
&lt;P&gt;Also, keep in mind that ASA based control-plane ACLs (telnet, ssh, http, etc) will override the control-plane ACL applied on the interface.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I hope this helps!&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;Thank you for rating helpful posts!&lt;/EM&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 20 Oct 2016 21:57:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/control-plane-acl-on-asa/m-p/2952929#M920252</guid>
      <dc:creator>nspasov</dc:creator>
      <dc:date>2016-10-20T21:57:34Z</dc:date>
    </item>
  </channel>
</rss>

