- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
02-21-2024 11:15 AM - edited 02-21-2024 11:21 AM
For this discussion, we created custom appID `myApp`, it has NO signature.
If `myApp` uses port 22, the port of another known app (SSH), then to use `myApp`, it must be applied to an App Override policy.
But what if `myApp` uses unique port 2121, can then `myApp` be applied directly to a security policy or does it still need to be added to an App Override policy?
We want to create simple appIDs, with no signature, to be applied to various security policies so we can A) ID the app in the policy without having to reference a service port and B) to be able to cleanly/clearly ID the traffic in traffic logs.
All the existing documentation I have found references creating custom appIDs using a port of a known app, but I can't find references to unique ports. As well, the documentation seems to imply that any apps applied to a security policy must have a signature while also implying custom apps without a signature must still use App Override policies. Its not very clear...IMO.
Thanks
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!