There have been a lot of great tips from this forum, so I figured I would offer this as well:
Saturday's SQL slammer worm is a perfect example of why everyone should ignore Cisco's default "allow everything out" policy and apply an access-list to your INSIDE interface.
Not only would this conform better to firewall best practices (that which is not expressly permitted is denied), but also helps to impede the propagation of worms like this.
You might be very surprised at just how much traffic is trying to go from the inside out. We have always had access-lists on our inside interfaces of our PIXES. We have caught a number of trojans, spyware, and other unwanted goodies just by watching the logs for what gets denied trying to leave our firewalls.
OK. I'm off my soap box now
Saturday's SQL slammer worm is a perfect example of why everyone should ignore Cisco's default "allow everything out" policy and apply an access-list to your INSIDE interface.
Not only would this conform better to firewall best practices (that which is not expressly permitted is denied), but also helps to impede the propagation of worms like this.
You might be very surprised at just how much traffic is trying to go from the inside out. We have always had access-lists on our inside interfaces of our PIXES. We have caught a number of trojans, spyware, and other unwanted goodies just by watching the logs for what gets denied trying to leave our firewalls.
OK. I'm off my soap box now