Clientless SSL VPN using ASDM And GNS3

Get 30% off with PROMO CODE CCNADT

Follow me on Twitter:

Previous Video:

web_java GNS3 Appliance:

Mozilla Firefox Appliance:


3.2.a Implement basic clientless SSL VPN using ASDM

What is an SSL Certificate?

SSL stands for Secure Sockets Layer and, in short, it’s the standard technology for keeping an internet connection secure and safeguarding any sensitive data that is being sent between two systems, preventing criminals from reading and modifying any information transferred, including potential personal details. The two systems can be a server and a client (for example, a shopping website and browser) or server to server (for example, an application with personal identifiable information or with payroll information).

It does this by making sure that any data transferred between users and sites, or between two systems remain impossible to read. It uses encryption algorithms to scramble data in transit, preventing hackers from reading it as it is sent over the connection. This information could be anything sensitive or personal which can include credit card numbers and other financial information, names and addresses.

3.2 Remote access VPN

3.2.a Implement basic clientless SSL VPN using ASDM

Clientless SSL VPN enables end users to securely access resources on the corporate network from anywhere using an SSL-enabled Web browser. The user first autehnticates with a Clientless SSL VPN gateway, which then allows the user to access pre-configured network resources.

Note Security contexts (also called firewall multimode) and Active/Active stateful failover are not supported when Clientless SSL VPN is enabled.

Clientless SSL VPN creates a secure, remote-access VPN tunnel to an ASA using a Web browser without requiring a software or hardware client. It provides secure and easy access to a broad range of Web resources and both web-enabled and legacy applications from almost any device that can connect to the Internet via HTTP. They include:

  • Internal websites.
  • Web-enabled applications.
  • NT/Active Directory file shares.
  • email proxies, including POP3S, IMAP4S, and SMTPS.
  • Microsoft Outlook Web Access Exchange Server 2000, 2003, and 2007.
  • Microsoft Web App to Exchange Server 2010 in 8.4(2) and later.
  • Application Access (smart tunnel or port forwarding access to other TCP-based applications)
Share the Post:

Related Posts

Help Us By Donating