12-13-2022 08:02 PM - edited 12-14-2022 01:36 AM
Having issues with rule conflicts and traffic behavior, so I created a new AC policy with default posture to deny all traffic, but when you examine the new policy there is no default deny rule. Where is this rule seen so I can confirm its existence?
Other issues. I have a geolocation rule at the very top of my AC policy that purportedly conflicted with an explicit default deny rule at the bottom. The geo rule simply states any traffic in any zone or network or port destined for blocked countries will be blocked. With that rule at the top and an explicit default deny at the bottom, I do not understand the conflict.
I also have a QUIC rule below the geo rule. Same thing. Any zone, any network, etc. that sends UDP/443 is blocked. Conflicts with explicit default deny rule at bottom.
I also have a URL rule. Same problem.
I also have an Intrusion rule. Same problem.
Very simple test policy
1 geo-rule
2 quic-rule
3 url-rule
4 intrusion-rule
5 inside-rule
6 default-deny-rule
Before I added the inside-rule, I had inside traffic getting out without the rule allowing it. I have no idea how that was even possible. Is there a single guide that brings it all together?
Solved! Go to Solution.
12-14-2022 05:49 AM
I'm not sure about your specific issue not having seen the actual ACP.
Regarding a general guiding document, please refer to the following:
https://secure.cisco.com/secure-firewall/docs/access-control-policy
12-14-2022 05:49 AM
I'm not sure about your specific issue not having seen the actual ACP.
Regarding a general guiding document, please refer to the following:
https://secure.cisco.com/secure-firewall/docs/access-control-policy
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide