Cisco ASA / AnyConnect VPN Brute Force: How to Stop It

Seeing failed Cisco Secure Client logins or an ASA password spray? Apply Cisco's own controls first. Then deny IPs already attacking VPN portals with a control-plane ACL before they reach your VPN service.

Start a 14-day free trialOr test 200 entries first: free, no signup
5.4M+
IPv4 Addresses Blocked
Checked for New Attackers Every 6 Hours
$19.99
Per Month, No Card for the Trial
By CalMax Systems Security Research · Last updated: October 28, 2026

The Short Answer

To stop Cisco ASA / AnyConnect VPN brute force, enable logging and supported Remote Access VPN threat detection, harden default connection profiles, and use certificates or supported MFA. Then block known attacker IPv4 sources in a control-plane ACL. On FMC-managed FTD, Remote Access VPN is to-the-box traffic, so use FlexConfig rather than an access-control Security Intelligence feed.

Test first: free 200-entry sample, no signup.

What Cisco AnyConnect Brute Force Looks Like

Cisco now calls the client Cisco Secure Client, but admins still search for AnyConnect. The headend is the ASA or FTD.

A Cisco ASA password spray tries passwords across a set of usernames. Cisco says unusually large volumes of syslog IDs 113005, 113015 and 716039 can indicate this activity. These messages report AAA or WebVPN authentication rejection and require informational logging level 6.

Run show aaa-server more than once. A fast rise in authentication requests and rejects is another Cisco-documented sign. Failed attempts can consume firewall and AAA resources even when no login succeeds.

Cisco's Own Fixes (Do These First)

Cisco recommends Remote Access VPN threat detection first on supported releases. Tune thresholds carefully when legitimate users share a public IP through hotel Wi-Fi, carrier NAT or another PAT service.

Fix What to do Limit
Log the attack Send logs to a remote syslog server. Enable 113005, 113015 and 716039 at informational level 6. Shows the attack; does not block it.
Remote Access VPN threat detection Enable remote-access-authentication, remote-access-client-initiations and invalid-vpn-access on a supported ASA or FTD release. Disabled by default. IPv4 only. SAML failures are not counted by remote-access-authentication. Shared NAT IPs need careful thresholds.
Harden connection profiles Disable AAA authentication on DefaultWEBVPNGroup and DefaultRAGroup, remove group aliases, and use group URLs for intended profiles. Reduces exposed login paths; Cisco says hardening is not a preventive measure for Remote Access VPN DoS.
Certificates or supported MFA Use client certificates for default profiles and certificate mapping for intended profiles. Use supported two-factor authentication for password-based access. Protects accounts; unauthenticated connection attempts can still reach the headend.
Do not misuse max-failed-attempts aaa-server ... max-failed-attempts controls when ASA marks an AAA server unresponsive and tries another server. It is not an attacker or user-login lockout.

Version and vulnerability check

An IP feed cannot fix an ASA or FTD vulnerability. Check your exact release in Cisco's Software Checker, then follow the fixed-release and incident-response guidance in Cisco's continued-attacks event response. Do not rely on a copied affected-version table. Verified October 28, 2026.

Cisco's ASA example uses a 10-minute hold-down and threshold of 20. Choose values for your own traffic. Cisco allows 1–1440 minutes and a threshold of 1–100 for authentication failures; client initiations require a threshold of 5–100.

threat-detection service invalid-vpn-access
threat-detection service remote-access-client-initiations hold-down 10 threshold 20
threat-detection service remote-access-authentication hold-down 10 threshold 20

Why a Block List Helps

Cisco's threshold control reacts after one source generates enough failures or incomplete starts. A maintained block list can deny a source already observed attacking other VPN portals before its first attempt on yours.

ThreatListPro covers 5.4M+ IPv4 addresses from real attacks on live production Palo Alto GlobalProtect VPN portals in the US. It is checked for new attackers every 6 hours. The URL serves plain text with one IPv4 address or CIDR per line; single IPs are written as /32.

On ASA and FTD, the relevant enforcement point is a control-plane ACL. Cisco documents Remote Access VPN traffic to an interface as to-the-box traffic. An FMC Security Intelligence feed used by an access-control policy handles through-the-box traffic, so it is not the documented control for the VPN listener itself.

Cisco ASA / FTD Block List Setup, Step by Step

Cisco's ASA procedure uses CLI. For FMC-managed FTD, Cisco's procedure uses FlexConfig; the cited note describes this requirement as of 7.0 and validates its example on 7.2.5.

01

Get the feed URL

Test with the free sample above, or use your subscription URL:
https://api.threatlistpro.com/v1/YOUR_API_KEY/blocklist.txt

02

Check your users and current control-plane ACL

Compare trusted user source networks with the feed. Exclude trusted networks from the generated group or place an explicit permit before the deny. Run show running-config access-group and inspect any ACL already bound to outside control-plane. Update that ACL instead of replacing it blindly.

03

Generate an ASA network object-group

The documented control-plane ACL takes an extended ACL and network objects, not a remote feed URL. Use a scheduled script or configuration-management job outside the firewall to fetch the feed over HTTPS, validate each IPv4 or CIDR line, convert /32 entries to network-object host, and convert CIDRs to a network address and IPv4 mask. Refresh every 60 minutes. Reject an empty or malformed download and retain the last known-good configuration.

object-group network ThreatListPro
 network-object host 192.0.2.10
 network-object 198.51.100.0 255.255.255.0
04

Apply the ASA control-plane ACL

Merge the deny into your existing control-plane ACL. Cisco says a control-plane ACL has no implicit deny, so unmatched traffic remains outside this explicit block. The sample deny ip ACE applies to control-plane traffic from listed sources, not only Remote Access VPN; Cisco notes that SSH, ICMP and Telnet use separate higher-precedence controls. Check trusted management and site-to-site VPN peers as well as remote users, and apply the ACL only to the interface receiving Remote Access VPN connections.

access-list VPN-CONTROL extended deny ip object-group ThreatListPro any
access-group VPN-CONTROL in interface outside control-plane
05

For FMC-managed FTD, use Cisco's FlexConfig procedure

Go to Objects > Object Management > Access List > Extended and create the deny ACE with the generated source object. Then go to Objects > Object Management > FlexConfig > FlexConfig Object, insert the extended ACL policy object, and add access-group $ACL_VARIABLE in interface outside control-plane. Apply it under Devices > FlexConfig, preview the generated configuration, save and deploy. Cisco notes that object-group search optimization does not work for control-plane ACLs.

06

Verify without locking yourself out

Run show running-config access-group and show access-list VPN-CONTROL. Cisco documents using packet-tracer with a TCP 443 test to the outside IP; confirm the expected deny and hit-count increase. Existing connections are not affected by a newly edited control-plane ACL unless you clear them, so validate new test connections separately.

FTD/FMC Security Intelligence Custom IP Feed

Use this for traffic passing through FTD. It does not replace the control-plane ACL for the Remote Access VPN listener, and it does not patch ASA or FTD software.

01

Create the custom network feed

In FMC 7.x, go to Objects > Object Management > Security Intelligence > Network Lists and Feeds, choose Add Network Lists and Feeds, set Type to Feed, and enter the feed URL. Cisco requires the IPS license for this on Threat Defense. In cloud-delivered FMC, start at Objects > Security Intelligence, choose the network feed type, and add a Network List or Feed.

02

Set the update frequency

Cisco requires an MD5 URL for update intervals shorter than 30 minutes; without one, set the interval to at least 30 minutes. Choose an Update Frequency of 1 hour for this feed. Click Save; unless feed updates are disabled, FMC downloads and verifies the feed.

03

Add it to the access control policy

In FMC 7.x, open Policies > Access Control > Access Control; in cloud-delivered FMC, open Policies > Security Policies > Access Control. Edit the policy, open Security Intelligence > Networks, select the feed, and add it to the Block list. Leave Security Intelligence logging enabled (it is on by default), then save and deploy.

04

Verify the block

After the policy deploys, open Analysis > Connections > Security Intelligence Events in FMC. Look for blocked events whose Reason is IP Block and whose Security Intelligence Category is the custom feed name. Events appear only when a listed source sends traffic through the device.

What a Block List Can't Do

  • It blocks sources already observed attacking VPN portals. A new IP's first attempt still arrives, so certificates, MFA and Cisco's threat detection still come first.
  • It is IPv4 only. Protect any IPv6 listener separately.
  • CIDR ranges include addresses that did not each attack. Check your own users' source IPs first and allow-list trusted networks.
  • On ASA and FTD, external automation must translate and deploy the feed safely. A bad deployment can affect legitimate VPN access.

Which Fix Stops What

Certificates / MFA RAVPN threat detection Hardened profiles Control-plane block list
Stops a guessed password from logging in Yes No Certificate-only defaults do No
Blocks before the first attempt on your firewall No No No For listed IPv4 sources
Reacts to failures on your firewall No Yes, at your threshold No No
Handles SAML authentication failures MFA is handled by the identity system Not counted Limits exposed profiles For listed sources
Cost Depends on your identity system Included on supported software Included $19.99/mo or free 200-entry sample

Frequently Asked Questions

How do I spot a Cisco AnyConnect brute force or password spray?

Look for unusual volumes of ASA syslog IDs 113005, 113015 and 716039. Cisco identifies all three as authentication-rejection messages associated with password spraying. They must be enabled at informational level 6. Compare repeated show aaa-server output to see whether authentication requests and rejects are rising.

How do I block failed VPN login attempts on Cisco ASA?

On a supported ASA release, enable remote-access-authentication threat detection so an IPv4 source is shunned after your threshold. Use a control-plane ACL for addresses you already want to deny. Cisco documents control-plane ACLs for traffic destined to the ASA itself, including Remote Access VPN.

Can FMC Security Intelligence block FTD remote access VPN brute force?

Do not use an access-control Security Intelligence feed as the VPN-edge control. Cisco says access-control policies manage through-the-box traffic, while Remote Access VPN traffic destined to an FTD interface is to-the-box traffic managed by that interface's control plane. Follow Cisco's control-plane ACL procedure; its current note says that as of FMC/FTD 7.0 the ACL must be configured with FlexConfig.

How do I add a custom IP feed to Cisco FTD?

In FMC 7.x, create a network feed under Objects > Object Management > Security Intelligence > Network Lists and Feeds. In cloud-delivered FMC, use Objects > Security Intelligence and add a Network List or Feed. Add it to the access control policy's Security Intelligence > Networks block list, enable logging, save and deploy.

Can an IP feed fix a vulnerability in Cisco ASA 9.20(2)2 or another release?

No. An IP feed can block known sources, but it cannot remediate an ASA or FTD software vulnerability. Enter your exact release in Cisco Software Checker, review Cisco's continued-attacks event response, and follow the current fixed-release and incident-response guidance. This guidance was verified October 28, 2026.

Does aaa-server max-failed-attempts stop Cisco ASA password spray?

No. That setting counts failed transactions with an AAA server. When the count reaches the configured value, ASA marks that server unresponsive and tries another server. It is not a per-user or per-attacker login lockout. Use remote-access-authentication threat detection, MFA or certificates, and edge filtering for password spray.

Can I test the Cisco ASA block list for free?

Yes. The free sample has 200 entries and requires no signup. The full ThreatListPro feed is $19.99 per month with a 14-day free trial and no card needed. It is checked for new attackers every 6 hours.

Sources

Block IPs Already Attacking VPN Portals

14-day free trial, no card needed. Monthly $19.99, yearly $200, enterprise $99.99/mo. 14-day money-back guarantee.

Start a 14-day free trialOr test 200 entries first: free, no signup

Firewall Setup Guides

ThreatListPro is a plain-text IPv4 feed. Each platform needs its own supported import or automation method.

Palo Alto FortiGate pfSense OPNsense SonicWall Cisco ASA Sophos XG UniFi

Related Resources

Learn more about IP blocklists, VPN security, and how ThreatListPro compares to alternatives.

What Is an External Dynamic List (EDL)? Password Spraying on VPNs: Detect and Stop It VPN Brute Force Attacks Explained IP Blocklist vs Enterprise Threat Feed Stop Account Lockouts from Brute Force ThreatListPro vs FireHOL ThreatListPro vs AbuseIPDB Best VPN Brute Force Protection 2026 All Firewall Setup Guides