Tuesday, June 28, 2011

Seeking a Secure Migration from Cisco IPSec to Cisco SSL VPN Remote Access?



One of the vexing issues facing enterprises today - is how you can recognize the administrative cost savings and improve user functionality of Cisco's ASA SSL VPN providing. Lots of CIO's have trouble using the implementation of a migration answer. Ensuring secure remote access with user and enterprise friendly solutions can be a challenging challenge indeed. In search of a answer can be time consuming. I recently learned of some new solutions that not merely support facilitate the transition to cisco vpn client from a classic IPsec-based answer, but that make the entire process a lot more user and administrator friendly.

Ensuring a secure user authentication within the process, 1 which is deployable to both the enterprise and end user has been a challenge for several CIO's until recently. Once you have a NON-X.509 Authentication via Cisco IPSec VPN, the connection is developed through the VPN tunnel through the Cisco IPSec client plus a Cisco IPSec supporting appliance (cisco vpn client windows 7, PIX Firewall, Cisco Routers, and so on). In this scenario, the authentication is currently username/password or tokens. In using an IPSec User VPN Deployment, the Cisco IPSec client utilizes authentication apart from secure X.509 bilateral authentication.
Furthermore to the authentication becoming insecure - the organization is also at risk with a "Shared Authentication" key becoming utilized for encryption. This means that even if the organization is utilizing tokens (difficult or soft) for authentication - the encryption is still a mere password - and therefore vulnerable to attack.

Frequently times by adding a Cisco ASA and secure authentication appliance into the enterprise, the CIO can enroll users with X.509 Certificates and new user IPSec profiles. By enabling X.509 Authentication on the Cisco IPSec appliance using the new certificates and user profiles, an enterprise can a lot more effectively generate secure remote access. One of the advantages here is that the enterprise, at this time, does not will need to acquire a massive SSL VPN license - a easy two to 25 user license will suffice. The enterprise merely utilizes the ASA for the deployment of X.509 credentials and new IPSec user profiles. Utilizing a secure 2-factor authentication makes it possible for a fast a plug into the enterprise in a matter of hours. Certificate creation, SMS Text Messages and Telephony OTPs can be handled via secure and world-unique set of WSE three.0 Web Services.

Enterprises have been searching for a methodology to migrate from classic IPSec VPNs to the nimbler and more-user friendly cisco vpn client download solutions. There several resources out there that support with migrations. Signing up for a webinar series on IPSec and SSL VPNs would be a fast strategy to get as much as speed and learn about the possible challenges and get ideas for addressing them. Moreover you might discover info on the technical requirements for deploying a secure, productive, scalable, and reliable remote access VPN environment.
As an avid technology lover, Sam Brown follows tech movements within network security solutions, which includes two factor authentication, tokenless and strong SSL VPN authentication solutions.



No comments:

Post a Comment