<?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: Finding ACLS in FMC in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/finding-acls-in-fmc/m-p/3773249#M1011561</link>
    <description>Hi,&lt;BR /&gt;In the FMC you configure what you refer to the ACLs in an Access Control Policy (ACP). In the FMC you navigate to Policies &amp;gt; Access Control &amp;gt; Access Control.&lt;BR /&gt;&lt;BR /&gt;HTH</description>
    <pubDate>Fri, 04 Jan 2019 20:31:24 GMT</pubDate>
    <dc:creator>Rob Ingram</dc:creator>
    <dc:date>2019-01-04T20:31:24Z</dc:date>
    <item>
      <title>Finding ACLS in FMC</title>
      <link>https://community.cisco.com/t5/network-security/finding-acls-in-fmc/m-p/3773228#M1011559</link>
      <description>&lt;P&gt;Ok I have to admit I am an old CLI guy and a medicore FW guy at best anyway. So, saying that, I can see specific ACLS when I issue "the show access-list command" on the CLI on my FWS. however since this is Firepower/FMC we have to use FMC to modify them. For the life of me I cant find THEM!!!&amp;nbsp; I have no problem identifying objects, ports and policies but specific ACLS might as well be on an the Dead Sea Scrolls. I checked all the docs and I just cant find it..&amp;nbsp; Help !!&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 16:37:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/finding-acls-in-fmc/m-p/3773228#M1011559</guid>
      <dc:creator>JJEOROME</dc:creator>
      <dc:date>2020-02-21T16:37:55Z</dc:date>
    </item>
    <item>
      <title>Re: Finding ACLS in FMC</title>
      <link>https://community.cisco.com/t5/network-security/finding-acls-in-fmc/m-p/3773249#M1011561</link>
      <description>Hi,&lt;BR /&gt;In the FMC you configure what you refer to the ACLs in an Access Control Policy (ACP). In the FMC you navigate to Policies &amp;gt; Access Control &amp;gt; Access Control.&lt;BR /&gt;&lt;BR /&gt;HTH</description>
      <pubDate>Fri, 04 Jan 2019 20:31:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/finding-acls-in-fmc/m-p/3773249#M1011561</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2019-01-04T20:31:24Z</dc:date>
    </item>
    <item>
      <title>Re: Finding ACLS in FMC</title>
      <link>https://community.cisco.com/t5/network-security/finding-acls-in-fmc/m-p/3773295#M1011564</link>
      <description>&lt;P&gt;Hello&amp;nbsp;JJEOROME,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;As RJI say, the main access lists are found under Policies &amp;gt; Access Control.&lt;/P&gt;
&lt;P&gt;If you are looking for other standard or extended ACLs (like for identifying split tunnel or VPN filters, etc) you need to look under the main&amp;nbsp;OBJECTS tab. On the left you will find a section for standard and extended access lists.&lt;/P&gt;
&lt;P&gt;Hope this helps,&lt;/P&gt;
&lt;P&gt;Matt.&lt;/P&gt;</description>
      <pubDate>Fri, 04 Jan 2019 22:10:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/finding-acls-in-fmc/m-p/3773295#M1011564</guid>
      <dc:creator>matty-boy</dc:creator>
      <dc:date>2019-01-04T22:10:04Z</dc:date>
    </item>
    <item>
      <title>Re: Finding ACLS in FMC</title>
      <link>https://community.cisco.com/t5/network-security/finding-acls-in-fmc/m-p/3773415#M1011567</link>
      <description>&lt;P&gt;Hi,&lt;BR /&gt;In FTD you can create ACL's in two way's - &lt;STRONG&gt;Access Control Policy&lt;/STRONG&gt; &amp;amp; &lt;STRONG&gt;Pre-Filter Policy&lt;/STRONG&gt;.&lt;BR /&gt;You can check the ACL's from FMC:&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Policy&amp;nbsp;&amp;gt; Access Control Policy&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Policy&amp;nbsp;&amp;gt; Pre-Filter Policy&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;FTD is not like to manage easy like ASA, as most of the Folks are familiar to manage&amp;nbsp;via cli for configuration and tshoot. On FTD case its everything changed and we need to do all the configuration/verification's via the management console and we can tshoot via FTD cli.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;HTH&lt;/P&gt;
&lt;P&gt;Abheesh&lt;/P&gt;</description>
      <pubDate>Sat, 05 Jan 2019 10:35:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/finding-acls-in-fmc/m-p/3773415#M1011567</guid>
      <dc:creator>Abheesh Kumar</dc:creator>
      <dc:date>2019-01-05T10:35:29Z</dc:date>
    </item>
    <item>
      <title>Re: Finding ACLS in FMC</title>
      <link>https://community.cisco.com/t5/network-security/finding-acls-in-fmc/m-p/3775087#M1011957</link>
      <description>&lt;P&gt;You can still can run the "show access-list" or "show running-config access-list" command from the LINA CLI of the FTD device. However, you can only view the ACL and not edit it from there. (Unless you know the super-secret TAC method :))&lt;/P&gt;
&lt;P&gt;Also note that the ACL in FTD is global, so you don’t need to use a different ACL per interface.&lt;/P&gt;</description>
      <pubDate>Tue, 08 Jan 2019 13:55:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/finding-acls-in-fmc/m-p/3775087#M1011957</guid>
      <dc:creator>Chess Norris</dc:creator>
      <dc:date>2019-01-08T13:55:30Z</dc:date>
    </item>
    <item>
      <title>Re: Finding ACLS in FMC</title>
      <link>https://community.cisco.com/t5/network-security/finding-acls-in-fmc/m-p/3775156#M1011958</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/256705"&gt;@Chess Norris&lt;/a&gt;&amp;nbsp;&lt;STRONG&gt;(Unless you know the super-secret TAC method :))&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Is there a way like this...?????&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 08 Jan 2019 15:15:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/finding-acls-in-fmc/m-p/3775156#M1011958</guid>
      <dc:creator>Abheesh Kumar</dc:creator>
      <dc:date>2019-01-08T15:15:45Z</dc:date>
    </item>
    <item>
      <title>Re: Finding ACLS in FMC</title>
      <link>https://community.cisco.com/t5/network-security/finding-acls-in-fmc/m-p/3775163#M1011959</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/256705"&gt;@Chess Norris&lt;/a&gt;kindly please share this super command with us too&lt;/P&gt;</description>
      <pubDate>Tue, 08 Jan 2019 15:22:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/finding-acls-in-fmc/m-p/3775163#M1011959</guid>
      <dc:creator>Sheraz.Salim</dc:creator>
      <dc:date>2019-01-08T15:22:26Z</dc:date>
    </item>
    <item>
      <title>Re: Finding ACLS in FMC</title>
      <link>https://community.cisco.com/t5/network-security/finding-acls-in-fmc/m-p/3775800#M1011960</link>
      <description>&lt;P&gt;TAC helped us with this before when one FTD 4100 appliance went berserk after a FXOS upgrade and shut down all sub interfaces – including the management interface - of the device.&lt;/P&gt;
&lt;P&gt;This resulted in that we lost all communication between the FMC and the FTD and there was no way we could bring the interfaces up again from the FMC.&lt;/P&gt;
&lt;P&gt;To resolve this, TAC had to get config access from the CLI and manually do a “no shut” on all sub interfaces.&lt;/P&gt;
&lt;P&gt;I am not sure exactly how they did it, but it was a quite complicated process and you had to modify the /mnt/disk0/enable_configure file from expert mode.&lt;/P&gt;
&lt;P&gt;You will then get a warning message when you type the “config terminal” command saying something like “This command is not supported and should not be used”&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I therefore don’t recommend anyone to mess with this. The chance that you will end up with a broken&amp;nbsp;configuration is probably huge and you will most likely not be getting any help from TAC.&lt;/P&gt;</description>
      <pubDate>Wed, 09 Jan 2019 08:54:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/finding-acls-in-fmc/m-p/3775800#M1011960</guid>
      <dc:creator>Chess Norris</dc:creator>
      <dc:date>2019-01-09T08:54:27Z</dc:date>
    </item>
  </channel>
</rss>

