Security Policy

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Please sign in to see details of an important advisory in our Customer Advisories area.

Security Policy

L1 Bithead

Hello,

 

I have created a security policy with the below details. I am the hitting following URL https://10.x.x.x:15671 and I see the 'connection is reset' in the browser. I see traffic is hitting the policy (Hit count) but it's not logging. When I set the action to Deny/Drop/reset-client\reset-server the traffic is logging when hits the rule. What could be the reason why traffic is not logging for action 'Allow' and why traffic is not passing through? 

 

Application - Any

Services - Application default

Action - Allow

Logging - Log st session start and end

 

Thanks,

Srikar

 

srikarpuligandla_0-1701627610318.pngsrikarpuligandla_1-1701627668060.png

 

1 accepted solution

Accepted Solutions

Cyber Elite
Cyber Elite

Your service is set to application default while you're using port 15671 for ssl traffic (default port 443)

This means you will not be using this security rule to handle the traffic. You're most likely dropping down to the default intrazone deny rule, which has logging disabled

 

 

reason you're seeing the hit counter increase is when the SYN paxcket arrives there's no app-id yet, so no default port to enforce, the policy match goes by the 6tuple (source zone, source ip, destination zone, destination ip, destination port, protocol)

since you have an any any rule, the syn packet is allowed through until app-id kicks in, the rulebase is chcked again, this rule no longer matches and the next best match is de default rule

Tom Piens
PANgurus - Strata specialist; config reviews, policy optimization

View solution in original post

2 REPLIES 2

Cyber Elite
Cyber Elite

Your service is set to application default while you're using port 15671 for ssl traffic (default port 443)

This means you will not be using this security rule to handle the traffic. You're most likely dropping down to the default intrazone deny rule, which has logging disabled

 

 

reason you're seeing the hit counter increase is when the SYN paxcket arrives there's no app-id yet, so no default port to enforce, the policy match goes by the 6tuple (source zone, source ip, destination zone, destination ip, destination port, protocol)

since you have an any any rule, the syn packet is allowed through until app-id kicks in, the rulebase is chcked again, this rule no longer matches and the next best match is de default rule

Tom Piens
PANgurus - Strata specialist; config reviews, policy optimization

L1 Bithead

Thank you @reaper 

  • 1 accepted solution
  • 522 Views
  • 2 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

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!