Set Rule on ASA5510 for specific user/IP address to connect to VPN

I would like to setup a rule for a specific user at our organization so that she can only connect to our VPN from a specific IP address(s). These will be static IP addresses.

We have a Cisco ASA5510 and I have the IP address in question.

Would someone be kind enough to assist? Thanks!
LVL 1
nick_kesslerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Patrick BogersDatacenter platform engineer LindowsCommented:
Hi

For one specific user only can bring a lot of burden but please have a read on this topic here.

Bottom line, include ALL ip's permitted and deny all others.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
rauenpcCommented:
To allow the ASA to do this, you would need to disable the default option to bypass interface ACL's for IPSEC communications.

http://www.cisco.com/en/US/docs/security/asa/asa84/configuration/guide/vpn_ike.html
Using Interface Access Lists

By default, the ASA lets IPsec packets bypass interface ACLs. If you want to apply interface access lists to IPsec traffic, use the no form of the sysopt connection permit-vpn command.

Once you do this you would need to add specific ACL statements to allow any IPSEC traffic. This is for ANY remote access vpn, and ANY site to site vpn. This would be an OK option if the user is the only remote access client that you'll ever have. I can't say that I would suggest this as I would think this is going to cause you headaches in the future.

The other method would be to let a radius server control this. If you authenticate this user via radius, you can add certain conditions to authentication. The condition "Calling-Station-Id" is the source IP address of the client. You could specify this specific user, the specific Calling-Station-Id, and put that policy above the other vpn authentication policies on the radius server. You might need to follow that policy with one that only specifies username and denies access so that the user doesn't accidentally fall down to another more broad policy.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Cisco

From novice to tech pro — start learning today.