Cisco AnyConnect SSL VPN Client on Cisco ASA 5500
The convenience and advantages of secure VPNs has driven the specific technology to keep evolving continuously. Several years ago we only had the standardized IPSec VPN (which still strongly exists today). IPSec is a pure IP network VPN technology for connecting distant LAN networks over unsecured paths. Also, IPSec is used for client VPNs connecting remote teleworkers to their central site network. The characteristic of IPSec VPNs is that it provides FULL network connectivity between the VPN peers. That is, a remote access client IPSec VPN will connect the remote user to the central network just like the user would be locally connected.
After IPsec, the Web SSL VPN made its appearance. The remote user needs just a Web Browser with HTTPs to connect to the central site network. After authentication, the user is presented with a Web portal with links to the applications he is allowed to run. That is, the Web SSL VPN does not provide full network visibility to the remote user. The user has access only to specific applications (like internal email, internal files etc). Both IPSec VPNs and SSL VPNs are supported by Cisco ASA 5500 firewalls.
The newest generation of remote access VPNs is offered from Cisco AnyConnect SSL VPN client. This is supported by Cisco ASA 8.x. The AnyConnect SSL VPN provides the best features from both of the other VPN technologies (IPSec and Web SSL). With AnyConnect, the remote user has full network connectivity to the central site. Also, it offers the convenience of the Web SSL since there is no need to install an IPSec VPN client permanently to the user’s computer. Instead, there is an SSL client stored in the ASA flash memory which is downloaded to the remote user’s computer on demand.
How AnyConnect SSL VPN Client works
For first time user connection, the remote teleworker just opens a browser pointing to https://<ASA-outside-public-IP>. The browser connects to the ASA firewall and presents the user with a login screen. The user enters his credentials (username/password) and the ASA identifies that the user does not have the SSL client installed. Therefore it pushes the SSL client to the user’s computer. The client installs itself to the remote PC and establishes a secure SSL VPN connection between the remote user and the ASA. The user is also assigned an IP address from an address pool configured on the ASA and has full network access to the central site. When the SSL connection is stopped, the SSL client either uninstalls itself or remains on the user’s PC (depending on the configuration of the ASA).
In the case of a previously installed client, when the user authenticates, the security appliance examines the revision of the client, and upgrades the client as necessary.
The AnyConnect SSL client can be downloaded from the security appliance, or it can be installed manually on the remote PC by the system administrator.
In another post I will explain how to configure the AnyConnect SSL VPN on a Cisco ASA 5500 firewall.
Related posts:
- How To Configure AnyConnect SSL VPN on Cisco ASA 5500
- VPN client Error -Syslog ID 305006
- Comparison Between Cisco ASA WebVPN Technologies
Tagged with: anyconnect ssl vpn • anyconnect vpn • asa anyconnect vpn
Filed under: Cisco ASA General
Like this post? Subscribe to my RSS feed and get loads more!


Pretty nice post. I just stumbled upon your blog and wanted to say
that I’ve really liked browsing your posts. In any case
I’ll be subscribing to your feed and I hope you write again soon!
Hello Mary,
Thanks for stopping by my blog and look around. I appreciate your comments.
Have a nice day
Harris
Hi, I wonder if you can answer a brief question: my institution provides the old Cisco VPN Client, but it does not seem to work on x64 machines. If I use the anyconnect client, and transfer the settings, would that allow me to establish a VPN connection (it is an IPSEC/UDP transport)?
Thanks for the well thought out tech blog.
J
Yes, the anyconnect client establishes also a VPN connection to your central site, using SSL however (not ipsec/udp)