<?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: Cisco managed applications in Firepower in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/cisco-managed-applications-in-firepower/m-p/5274258#M1120236</link>
    <description>&lt;P&gt;according to my knowledge Cisco provides pre-built application detectors for many services, they do not currently offer a comprehensive solution for automatically updating Firepower with changing port requirements for services like Webex Calling. However, there are few strategies/way that can help streamline the process/es.&lt;/P&gt;&lt;P&gt;Application Detectors/Custom Application Detectors and use of API Integration providing you the advanced users case API to programmatically update firewall rules.&lt;/P&gt;&lt;P&gt;Have you looked at the Firepower rules ACP where you can filter based on Application filtering?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Sun, 23 Mar 2025 04:42:27 GMT</pubDate>
    <dc:creator>Sheraz.Salim</dc:creator>
    <dc:date>2025-03-23T04:42:27Z</dc:date>
    <item>
      <title>Cisco managed applications in Firepower</title>
      <link>https://community.cisco.com/t5/network-security/cisco-managed-applications-in-firepower/m-p/5273985#M1120227</link>
      <description>&lt;P&gt;Out of curiosity, is there an easier way of keeping Firepower updated on application needs when ports change?&amp;nbsp; That or even the initial opening of ports?&amp;nbsp; For example: I will be soon migrating my phone service to Webex Calling from on-prem.&amp;nbsp; The port reference guide of stuff that needs opening is crazy long "&lt;A href="https://help.webex.com/en-us/article/b2exve/Port-Reference-Information-for-Webex-Calling&amp;quot;" target="_blank" rel="noopener"&gt;https://help.webex.com/en-us/article/b2exve/Port-Reference-Information-for-Webex-Calling"&lt;/A&gt;.&amp;nbsp; If Cisco can publish 7,000+ pre-built applications, why not add ones like calling so I can permit that app once and as Cisco changes the required ports I won't have to go hunt at what changed and start updating firewalls on multiple sites?&amp;nbsp; At least keep their own products listed in their other products.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Mar 2025 17:11:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-managed-applications-in-firepower/m-p/5273985#M1120227</guid>
      <dc:creator>Danny Mainprize</dc:creator>
      <dc:date>2025-03-21T17:11:51Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco managed applications in Firepower</title>
      <link>https://community.cisco.com/t5/network-security/cisco-managed-applications-in-firepower/m-p/5274258#M1120236</link>
      <description>&lt;P&gt;according to my knowledge Cisco provides pre-built application detectors for many services, they do not currently offer a comprehensive solution for automatically updating Firepower with changing port requirements for services like Webex Calling. However, there are few strategies/way that can help streamline the process/es.&lt;/P&gt;&lt;P&gt;Application Detectors/Custom Application Detectors and use of API Integration providing you the advanced users case API to programmatically update firewall rules.&lt;/P&gt;&lt;P&gt;Have you looked at the Firepower rules ACP where you can filter based on Application filtering?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 23 Mar 2025 04:42:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-managed-applications-in-firepower/m-p/5274258#M1120236</guid>
      <dc:creator>Sheraz.Salim</dc:creator>
      <dc:date>2025-03-23T04:42:27Z</dc:date>
    </item>
  </channel>
</rss>

