How to configure FWSM to prevent malicious scanning
Recently there have been some malicious attempts in scanning our corporate network to detect vulnerabilities (open ports) for attack and while the ACL was doing its job of blocking them off the level and intensity of scanning actually caused a hiccup in the FWSM. I was looking at configuring a policy and class map to put in measures to prevent SYN Floood or IP spoofying to setting connections limits as follows:
class-map network_moat match access-list network_moat
access-list network_moat remark Monitors Session connections access-list network_moat permit ip any object-group colo_address_space
policy-map network_moat class network_moat set connection timeout embryonic 0:00:05 set connection timeout half-closed 0:01:00 set connection timeout idle 0:30:00
service-policy network_moat interface outside
ip verify reverse-path interface outside
But without having a maximum number of connection (simultaneous TCP or UDP connections) or having a conn-rate-limit to control the number of TCP or UDP connections per sec I don't know if I can stop those scanning again. Please advise on how I should set a good maximum number of connections or setting a connection rate limit to prevent scanning. Thanks.
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...