<?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 Control-plane ACL on Firepower 4110 in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/control-plane-acl-on-firepower-4110/m-p/4697580#M1093898</link>
    <description>&lt;P&gt;We have a 4110 managed by an FMC that we need to configure to block IKE traffic from. That's easy enough to do with a control-plane ACL, but I was looking at this:&lt;/P&gt;&lt;P&gt;&lt;A href="https://integratingit.wordpress.com/2021/06/26/ftd-control-plane-acl/" target="_blank"&gt;https://integratingit.wordpress.com/2021/06/26/ftd-control-plane-acl/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;It shows a deny statement followed by as explicit "permit ip any any". Is the permit statement needed? I've always understood the control-planes to having an implicit "permit ip any any". If there is an implicit, I realize the explicit statement won't matter, so it's a matter of satisfying my curiosity. Thanks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 03 Oct 2022 15:05:43 GMT</pubDate>
    <dc:creator>ABaker94985</dc:creator>
    <dc:date>2022-10-03T15:05:43Z</dc:date>
    <item>
      <title>Control-plane ACL on Firepower 4110</title>
      <link>https://community.cisco.com/t5/network-security/control-plane-acl-on-firepower-4110/m-p/4697580#M1093898</link>
      <description>&lt;P&gt;We have a 4110 managed by an FMC that we need to configure to block IKE traffic from. That's easy enough to do with a control-plane ACL, but I was looking at this:&lt;/P&gt;&lt;P&gt;&lt;A href="https://integratingit.wordpress.com/2021/06/26/ftd-control-plane-acl/" target="_blank"&gt;https://integratingit.wordpress.com/2021/06/26/ftd-control-plane-acl/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;It shows a deny statement followed by as explicit "permit ip any any". Is the permit statement needed? I've always understood the control-planes to having an implicit "permit ip any any". If there is an implicit, I realize the explicit statement won't matter, so it's a matter of satisfying my curiosity. Thanks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 03 Oct 2022 15:05:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/control-plane-acl-on-firepower-4110/m-p/4697580#M1093898</guid>
      <dc:creator>ABaker94985</dc:creator>
      <dc:date>2022-10-03T15:05:43Z</dc:date>
    </item>
    <item>
      <title>Re: Control-plane ACL on Firepower 4110</title>
      <link>https://community.cisco.com/t5/network-security/control-plane-acl-on-firepower-4110/m-p/4697588#M1093900</link>
      <description>&lt;P&gt;A&lt;SPAN&gt;dding 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;/SPAN&gt;&lt;/P&gt;
&lt;P style="margin: 0px 0px 6px; padding: 0px; border: 0px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-variant-numeric: inherit; font-variant-east-asian: inherit; font-weight: 400; font-stretch: inherit; font-size: 14px; line-height: 1.375em; font-family: CiscoSans, Arial, sans-serif; vertical-align: baseline; color: #58585b; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: #ffffff; text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;"&gt;The&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG style="margin: 0px; padding: 0px; border: 0px; font-style: inherit; font-variant: inherit; font-weight: bold; font-stretch: inherit; font-size: inherit; line-height: inherit; font-family: inherit; vertical-align: baseline;"&gt;control-plane&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;keyword specifies if the ACL is used to control to-the-box traffic. Access control rules for to-the-box management traffic (defined by such commands as&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG style="margin: 0px; padding: 0px; border: 0px; font-style: inherit; font-variant: inherit; font-weight: bold; font-stretch: inherit; font-size: inherit; line-height: inherit; font-family: inherit; vertical-align: baseline;"&gt;http&lt;/STRONG&gt;,&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG style="margin: 0px; padding: 0px; border: 0px; font-style: inherit; font-variant: inherit; font-weight: bold; font-stretch: inherit; font-size: inherit; line-height: inherit; font-family: inherit; vertical-align: baseline;"&gt;ssh&lt;/STRONG&gt;, or&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG style="margin: 0px; padding: 0px; border: 0px; font-style: inherit; font-variant: inherit; font-weight: bold; font-stretch: inherit; font-size: inherit; line-height: inherit; font-family: inherit; vertical-align: baseline;"&gt;telnet&lt;/STRONG&gt;) have higher precedence than a management access rule applied with the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG style="margin: 0px; padding: 0px; border: 0px; font-style: inherit; font-variant: inherit; font-weight: bold; font-stretch: inherit; font-size: inherit; line-height: inherit; font-family: inherit; vertical-align: baseline;"&gt;control-plane&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;option. Therefore, &lt;STRONG&gt;such permitted management traffic will be allowed to come in even if explicitly denied by the to-the-box ACL&lt;/STRONG&gt;.&lt;/P&gt;
&lt;P style="margin: 0px 0px 6px; padding: 0px; border: 0px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-variant-numeric: inherit; font-variant-east-asian: inherit; font-weight: 400; font-stretch: inherit; font-size: 14px; line-height: 1.375em; font-family: CiscoSans, Arial, sans-serif; vertical-align: baseline; color: #58585b; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: #ffffff; text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;"&gt;Unlike regular access rules, there is no implicit deny at the end of a set of management rules for an interface. Instead, any connection that does not match a management access rule is then evaluated by regular access control rules. Alternatively, you can use ICMP rules to control ICMP traffic to the device.&lt;/P&gt;
&lt;P style="margin: 0px 0px 6px; padding: 0px; border: 0px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-variant-numeric: inherit; font-variant-east-asian: inherit; font-weight: 400; font-stretch: inherit; font-size: 14px; line-height: 1.375em; font-family: CiscoSans, Arial, sans-serif; vertical-align: baseline; color: #58585b; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: #ffffff; text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;"&gt;&lt;A href="https://www.cisco.com/c/en/us/support/docs/security/adaptive-security-appliance-asa-software/217679-asa-access-control-list-configuration-ex.html" target="_blank" rel="noopener"&gt;ASA Access Control List Configuration Examples for Various Scenarios - Cisco&lt;/A&gt;&lt;/P&gt;
&lt;P style="margin: 0px 0px 6px; padding: 0px; border: 0px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-variant-numeric: inherit; font-variant-east-asian: inherit; font-weight: 400; font-stretch: inherit; font-size: 14px; line-height: 1.375em; font-family: CiscoSans, Arial, sans-serif; vertical-align: baseline; color: #58585b; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: #ffffff; text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P style="margin: 0px 0px 6px; padding: 0px; border: 0px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-variant-numeric: inherit; font-variant-east-asian: inherit; font-weight: 400; font-stretch: inherit; font-size: 14px; line-height: 1.375em; font-family: CiscoSans, Arial, sans-serif; vertical-align: baseline; color: #58585b; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: #ffffff; text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;"&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 03 Oct 2022 19:05:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/control-plane-acl-on-firepower-4110/m-p/4697588#M1093900</guid>
      <dc:creator>Sheraz.Salim</dc:creator>
      <dc:date>2022-10-03T19:05:10Z</dc:date>
    </item>
    <item>
      <title>Re: Control-plane ACL on Firepower 4110</title>
      <link>https://community.cisco.com/t5/network-security/control-plane-acl-on-firepower-4110/m-p/4697591#M1093902</link>
      <description>&lt;P&gt;&lt;SPAN&gt;""For&lt;STRONG&gt; management (control plane) ACLs&lt;/STRONG&gt;, which control to-the-box traffic, there is no implicit deny at the end of a set of management rules for an interface. Instead, any connection that does not match a management access rule is then evaluated by regular &lt;STRONG&gt;access control rules&lt;/STRONG&gt;.""&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;from cisco ASA ACL&amp;nbsp;&lt;BR /&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config/access-acls.html" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config/access-acls.html&lt;/A&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 03 Oct 2022 15:20:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/control-plane-acl-on-firepower-4110/m-p/4697591#M1093902</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2022-10-03T15:20:49Z</dc:date>
    </item>
    <item>
      <title>Re: Control-plane ACL on Firepower 4110</title>
      <link>https://community.cisco.com/t5/network-security/control-plane-acl-on-firepower-4110/m-p/4697659#M1093906</link>
      <description>&lt;P&gt;Thank you both for the replies, and I read both links prior to posting. I realize there is normally a default "deny ip any any" at the end of a normal access list, but if I leave the "permit ip any any" off the control-plane ACL, it shouldn't matter, correct, given there is no implicit deny?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 03 Oct 2022 17:39:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/control-plane-acl-on-firepower-4110/m-p/4697659#M1093906</guid>
      <dc:creator>ABaker94985</dc:creator>
      <dc:date>2022-10-03T17:39:16Z</dc:date>
    </item>
    <item>
      <title>Re: Control-plane ACL on Firepower 4110</title>
      <link>https://community.cisco.com/t5/network-security/control-plane-acl-on-firepower-4110/m-p/4697690#M1093910</link>
      <description>&lt;P&gt;&lt;SPAN&gt; There is no implicit deny at the end of control plane ACL.&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 03 Oct 2022 19:03:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/control-plane-acl-on-firepower-4110/m-p/4697690#M1093910</guid>
      <dc:creator>Sheraz.Salim</dc:creator>
      <dc:date>2022-10-03T19:03:29Z</dc:date>
    </item>
  </channel>
</rss>

