- CheckMates
- :
- Products
- :
- Quantum
- :
- Threat Prevention
- :
- Traffic prevented on Anti-Bot but accepted on fire...
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Traffic prevented on Anti-Bot but accepted on firewall
Hi
I am wondering if this is something that I should be worry about ? I assume that it should be alright that traffic is accepted on implied rule and next is stopped by Anti-bot
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
the traffic is accepted by the Firewall blade access (implied rules) but dropped by AB.
you can double check it with tcpdump/fw monitor/fw ctl zdebug + drop | grep x.x.x.x
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Looks normal behavior. Sometimes the firewall needs to allow a bit of traffic in order to further check it. It can happen that firewall decides to block it in a later stadium.
Also some policy’s are separate. For example firewall policy and app / url filtering can be separate. So traffic first passes firewall rule base and it is allowed. But then I check the application filtering rulebase and then it could be blocked.
If you like this post please give a thumbs up(kudo)! 🙂
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
As Amir had said, I would also do zdebug to confirm.
Best,
Andy
