Shunning attempts to break into a VPN account on a ASA5510
From some testing on the 5510 it appears that the following events are tripped when authentication fails for an AnyConnect or SSL clientless session.
716039 Group <GroupPolicy> User <asdf> IP <source ip address> Authentication: rejected, Session Type: SSLVPN.
For IPSec VPN attempts, 3 or 4 events are tripped. The ones that provide the most information about the incident are listed below.
715001 Group = GroupName, Username = asdf, IP = source ip address, Processing MODE_CFG Reply attributes. 113015 AAA user authentication Rejected : reason = Invalid password : local database : user = asdf
Can the ASA (with or without IPS module) automatically shun the source ip address when this event is triggered? Obviously, my goal is to reduce the potenail for break in attempts. Automatically shunning the source would assist in doing this.
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...