10-13-2025 03:15 AM
Hello,
We have a Cisco ASA 5516 running 9.16(1). With the vulnerability that came out last week (https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-asaftd-webvpn-z5xP8EUB#vp), we want to restrict Anyconnect access to the firewall based on IP-adres. There are multiple reasons why we don't upgrade the firmware to the lastest version.
I did some research and found out that it is possible to add an ACL on the control-plane. This should affect access to the ASA itself. I am not sure how to configure the ACL itself, should it be something like this:
hosts that need to be allowed are: x.x.x.x and y.y.y.y
access-list OUTSIDE_MGMT_IN extended permit tcp host x.x.x.x interface outside eq 443
access-list OUTSIDE_MGMT_IN extended permit tcp host y.y.y.y interface outside eq 443
access-list OUTSIDE_MGMT_IN extended deny tcp any interface outside eq 443
access-list OUTSIDE_MGMT_IN extended permit ip any any
And doesn't this affect the management access rules that are configured in ASDM showed down below:
Solved! Go to Solution.
10-13-2025 05:13 AM
yes you can allow required IP to connect to Remote VPN
Below example and guide :
10-13-2025 05:13 AM
yes you can allow required IP to connect to Remote VPN
Below example and guide :
10-14-2025 05:50 AM
Thank you @balaji.bandi , I tested it on a spare ASA we had lying around, and it worked perfectly.
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