We've created a new custom app ID (custom-sql) for the SQL server with the ports TCP/10001- TCP/10004 with the Parent app as 'mssql-db-base'. Below are the firewall rules we've in place and noticed the application is correctly classified as the parent app when checking in monitor logs but instead of the below rule, it's hitting deny rule.
Any idea why is it so and what should be corrected. Thanks in advance
Source Zone: Inside
Destination Zone: DMZ
it's how APP-ID works:
1. first a syn packet comes un, firewall checks if the source zone/ip, destination zone/ip, destination port and protocol are allowed somewhere (skips app for now)
if yes: session is created, if no, packet is discarded
2. handshake completes and first payload is transferred, app-id checks if anything can be identified (eg. http GET = web-browsing)
at this stage most of the parent apps will be identified as they display the most basic behavio.
Security rules are re-evaluated to see if this app is allowed to pass, if yoes, the session carris on, if no, the session is discarded
This is where dependencies require their parent app to be allowed somewhere in the rulebase
3. session continues to transfer payload and a child-app is detected, security rules are evaluated once more to see if child-app is allowed
if yes, sesion is allowed to complete, if no session is discarded
hope this helps
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!