Cisco managed applications in Firepower

[Danny Mainprize]

Out of curiosity, is there an easier way of keeping Firepower updated on application needs when ports change?  That or even the initial opening of ports?  For example: I will be soon migrating my phone service to Webex Calling from on-prem.  The port reference guide of stuff that needs opening is crazy long "https://help.webex.com/en-us/article/b2exve/Port-Reference-Information-for-Webex-Calling".  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?  At least keep their own products listed in their other products.

[Sheraz.Salim]

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.

Application Detectors/Custom Application Detectors and use of API Integration providing you the advanced users case API to programmatically update firewall rules.

Have you looked at the Firepower rules ACP where you can filter based on Application filtering?