11-13-2014 01:28 PM - edited 03-11-2019 10:04 PM
Hey all,
I have just started getting to grips with my new ASA. Unfortunately i am having alot of pain at present. The firewall keeps shunning internal people on the network which is resulting in alot of calls to the service desk.
I have done some reading and understand that shunning particular hosts is a good idea in the event of an attack. This is not an attack, How best can i mitigate these false positives? Why does it think they are attacking the firewall when they are just surfing?
Any help would be greatly appreciated.
Regards
Daniel
11-13-2014 04:02 PM
You need to post your config (remove sensitive information). Or at the very least post the output of
show run threat
11-14-2014 01:31 AM
threat-detection basic-threat
threat-detection statistics
threat-detection statistics tcp-intercept rate-interval 30 burst-rate 400 averag
e-rate 200
11-14-2014 02:35 AM
Hi,
These commands alone would not be able to SHUN the ip addresses on the ASA device.
How are you able to find if the hosts are being shunned or not ?
http://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/113685-asa-threat-detection.html
Thanks and Regards,
Vibhor Amrodia
11-14-2014 02:37 AM
Vibhor thanks for your reply.
I have configured alerts and receive these alerts alot. I think this may be the cause.
<164>Nov 14 2014 10:00:59 W138AG-ASA5520-1 : %ASA-4-733100: [ Scanning] drop rate-1 exceeded. Current burst rate is 4 per second, max configured rate is 10; Current average rate is 6 per second, max configured rate is 5; Cumulative total count is 4098
<164>Nov 14 2014 10:00:49 W138AG-ASA5520-1 : %ASA-4-733100: [ Scanning] drop rate-2 exceeded. Current burst rate is 8 per second, max configured rate is 8; Current average rate is 1 per second, max configured rate is 4; Cumulative total count is 6774
I am trying to work out what this means at present :)
11-14-2014 02:42 AM
Hi,
These are just informational. These would not cause the hosts to be shunned on the ASA device.
These are normal and you can ignore these :)
Thanks and Regards,
Vibhor Amrodia
11-14-2014 07:01 AM
In the future HS69, if you want to check for shunned hosts (obviously you will see in the logs as well) you can use the following commands
sh shun
sh threat-detection shun
11-24-2017 10:51 AM
Hi David,
What is the difference between those two commands?
I ask because I have found that when some hosts are being shunned, they show up in the sh shun output but not the other. Furthermore, I have taken steps to exclude some of the hosts from threat-detection, and yet they still show up under show shun.
I need to fix this permanently, especially for my network monitoring servers.
Thanks.
John
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