While WAP (Wireless Application Protocol) applications are ...
Virtual Private Networks
By Ramakrishnan Subramanian,Scuola Sant’Anna,Pisa,Italy.
Abstract
The paper aims to give the reader, the technical know-how of a VPN. It is a tutorial for junior students. A virtual private network (VPN) is the extension of a private network that encompasses links across shared or public networks like the Internet. VPNs using the Internet have the potential to solve many of these business networking problems .The data security is the most important aspect in VPN and the focus must be on the areas of Authentication, Access Control, Confidentiality, and Data integrity. The paper discusses these security areas in brief and the various measures taken in different standards. The protocols used are PPTP, L2F, L2TP, and IPSec. PPTP, L2F, and L2TP are largely aimed at dial-up VPNs, while IPSec's main focus has been LAN-to-LAN solutions. The paper discusses these with a perspective to compare and distinguish the protocols and possible applications and drawbacks. Finally the Wireless VPN and it’s requirements,Simple implementation and future scope is analyzed.
Table Of Contents:
1.VPN-Introduction and Need
2.VPN Technologies
3.Tunneling Protocols For VPN
4.VPN Solutions
5.Wireless VPN
6.Conclusion
7.Bibliography.
1.1VPN-Virtual Private Networks. An Introduction
“VPN can be defined as a secure private network not open to public but one which uses the resources of the Internet”.
A virtual private network (VPN) is the extension of a private network that encompasses links across shared or public networks like the Internet. A VPN enables you to send data between two computers across a shared or public internet work in a manner that emulates the properties of a point-to-point private link. The act of configuring and creating a virtual private network is known as virtual private networking.
To emulate a point-to-point link, data is encapsulated, or wrapped, with a header that provides routing information allowing it to traverse the shared or public internet work to reach its endpoint. To emulate a private link, the data being sent is encrypted for confidentiality. Packets that are intercepted on the shared or public network are indecipherable without the encryption keys. The link in which the private data is encapsulated and encrypted is known as a virtual private network (VPN) connection.
1.2.NEED FOR VPN
It is necessary in Mobile telecommunication today that data is available to the seeker from any corner of the world. Employees are looking to access the resources of their corporate intranets as they take to the road, telecommute, or dial in from customer sites. Business partners are joining together in extranets to share business information, either for a joint project of a few months' duration or for long-term strategic advantage.
VPNs using the Internet have the potential to solve many of these business networking problems. VPNs allow network managers to connect remote branch offices and project teams to the main corporate network economically and provide remote access to employees while reducing the in-house requirements for equipment and support.
3.VPN Technologies
VPNs need to provide the following four critical functions to ensure security for data:
·Authentication-: ensuring that the data originates at the source that it claims
·Access control-: restricting unauthorized users from gaining admission to the network
·Confidentiality-: preventing anyone from reading or copying data as it travels across the Internet
·Data integrity-: ensuring that no one tampers with data as it travels across the Internet
Data Encryption
To ensure confidentiality of the data as it traverses the shared or public transit internetwork, it is encrypted by the sender and decrypted by the receiver. The encryption and decryption processes depend on both the sender and the receiver having knowledge of a common encryption key.
Intercepted packets sent along the VPN connection in the transit internetwork are unintelligible to anyone who does not have the common encryption key. The length of the encryption key is an important security parameter. Computational techniques can be used to determine the encryption key. Such techniques require more computing power and computational time as the encryption key gets larger. Therefore, it is important to use the largest possible key size.
Various password-based systems, (password needed for connection)and challenge-response systems-such as challenge handshake authentication protocol (CHAP) and remote authentication dial-in user service (RADIUS)-as well as hardware-based tokens and digital certificates can be used to authenticate users on a VPN and control access to network resources. The privacy of corporate information as it travels through the VPN is guarded by encrypting the data.There are many encryption methods available.
3.TUNNELING PROTOCOLS FOR VPN
Four different protocols have been suggested for creating VPNs over the Internet: point-to-point tunneling protocol (PPTP), layer-2 forwarding (L2F), layer-2 tunneling protocol (L2TP), and IP security protocol (IPSec).
One reason for the number of protocols is that, for some companies, a VPN is a substitute for remote-access servers, allowing mobile users and branch offices to dial into the protected corporate network via their local ISP. For others, a VPN may consist of traffic traveling in secure tunnels over the Internet between protected LANs. The protocols that have been developed for VPNs reflect this dichotomy.
PPTP, L2F, and L2TP are largely aimed at dial-up VPNs, while IPSec's main focus has been LAN-to-LAN solutions.
The most commonly used protocol for remote access to the Internet is point-to-point protocol (PPP). PPTP builds on the functionality of PPP to provide remote access that can be tunneled through the Internet to a destination site. As currently implemented, PPTP encapsulates PPP packets using a modified version of the generic routing encapsulation (GRE) protocol, which gives PPTP the flexibility of handling protocols also other than IP.
Because of its dependence on PPP, PPTP relies on the authentication mechanisms within PPP, namely password authentication protocol (PAP) and CHAP. Aside from the relative simplicity of client support for PPTP, one of the protocol's main advantages is that PPTP is designed to run at open systems interconnection (OSI) Layer 2, or the link layer, as opposed to IPSec, which runs at Layer 3. By supporting data communications at Layer 2, PPTP can transmit protocols other than IP over its tunnels. PPTP does have some limitations. For example, it does not provide strong encryption for protecting data nor does it support any token-based methods for authenticating users.
L2F also arose in the early stages of VPN development. Like PPTP, L2F was designed as a protocol for tunneling traffic from users to their corporate sites. One major difference between PPTP and L2F is that, because L2F tunneling is not dependent on IP, it is able to work directly with other media, such as frame relay or asynchronous transfer mode (ATM). Like PPTP, L2F uses PPP for authentication of the remote user, but it also includes support for terminal access controller access control system (TACACS) + and RADIUS for authentication. L2F also differs from PPTP in that it allows tunnels to support more than one connection.
Paralleling PPTP's design, L2F utilized PPP for authentication of the dial-up user, but it also included support for TACACS+ and RADIUS for authentication from the beginning. L2F differs from PPTP because it defines connections within a tunnel, allowing a tunnel to support more than one connection. There are also two levels of authentication of the user, first by the ISP prior to setting up the tunnel and then when the connection is set up at the corporate gateway. Because L2TP is a layer-2 protocol, it offers users the same flexibility as PPTP for handling protocols other than IP, such as IPX and NetBEUI.
L2TP is being designed by an IETF working group as the heir apparent to PPTP and L2F, designed to address the shortcomings of these past protocols and become an IETF-approved standard. L2TP uses PPP to provide dial-up access that can be tunneled through the Internet to a site. However, L2TP defines its own tunneling protocol, based on the work done on L2F. L2TP transport is being defined for a variety of packet media, including X.25, frame-relay and ATM. To strengthen the encryption of the data it handles, L2TP uses IPSec's encryption methods.
Because it uses PPP for dial-up links, L2TP includes the authentication mechanisms within PPP, namely PAP and CHAP. Similar to PPTP, L2TP supports PPP's use of the extensible authentication protocol for other authentication systems, such as RADIUS. PPTP, L2F, and L2TP all do not include encryption or processes for managing the cryptographic keys required for encryption in their specifications. The current L2TP draft standard recommends that IPSec be used for encryption and key management in IP environments; future drafts of the PPTP standard may do the same.
The last, but perhaps most important protocol, IPSec, grew out of efforts to secure IP packets as the next generation of IP (IPv6) was being developed; it can now be used with IPv4 protocols as well. Although the requests for comment (RFCs) defining the IPSec protocols have already been part of the IETF's standards track since mid-1995, the protocols are still being refined as engineers learn more as more products appear in the marketplace. The question of which methods to employ for exchanging and managing the cryptographic keys used to encrypt session data has taken more than a year to answer. This challenge has been largely resolved and the ISAKMP/Oakley scheme (now also called Internet key exchange [IKE]) is being readied for acceptance as an IETF standard.
IPSec allows the sender (or a security gateway acting on his behalf) to authenticate or encrypt each IP packet or apply both operations to the packet. Separating the application of packet authentication and encryption has led to two different methods of using IPSec, called modes. In transport mode, only the transport-layer segment of an IP packet is authenticated or encrypted. The other approach, authenticating or encrypting the entire IP packet, is called tunnel mode. While transport-mode IPSec can prove useful in many situations, tunnel-mode IPSec provides even more protection against certain attacks and traffic monitoring that might occur on the Internet.
IPSec is built around a number of standardized cryptographic technologies to provide confidentiality, data integrity, and authentication. For example, IPSec uses:
·Diffie-Hellman key exchanges to deliver secret keys between peers on a public net
·public-key cryptography for signing Diffie-Hellman exchanges, to guarantee the identities of the two parties and avoid man-in-the-middle attacks
·data encryption standard (DES) and other bulk encryption algorithms for encrypting data
·keyed hash algorithms (HMAC, MD5, SHA) for authenticating packets
·Digital certificates for validating public keys.
There are currently two ways to handle key exchange and management within IPSec's architecture: manual keying and IKE for automated key management. Both of these methods-manual keying and IKE-are mandatory requirements of IPSec. While manual key exchange might be suitable for a VPN with a small number of sites, VPNs covering a large number of sites or supporting many remote users benefit from automated key management.
IPSec is often considered the best VPN solution for IP environments, as it includes strong security measures-notably encryption, authentication, and key management-in its standards set. Because IPSec is designed to handle only IP packets, PPTP and L2TP are more suitable for use in multiprotocol non-IP environments, such as those using NetBEUI, IPX, and AppleTalk.
4.VPN Solutions
To conclude there are four main components of an Internet-based VPN: the Internet, security gateways, security policy servers, and certificate authorities. The Internet provides the fundamental route/facility for a VPN. Security gateways sit between public and private networks, preventing unauthorized intrusions into the private network. They may also provide tunneling capabilities and encrypt private data before it is transmitted on the public network. In general, a security gateway for a VPN fits into one of the following categories: routers, firewalls, integrated VPN hardware, and VPN software.
5.Wireless- VPN A Fresh Perspective on the Happenings
It is possible to have a wireless VPN connection between Handheld Devices. WVPNs take advantage of two major business trends: the growth of e-business and the prevalence of VPN technology over wireline today. Wireless VPN Support is available for Palm 3.5 operating system, the Win CE operating system and the Symbian consortium's Epoc operating systems. Companies like Certicom,Columbitech,RSA Security Inc are already out with solutions or are planning to do so, soon. One can provide a secure encrypted link based on the IP Security protocol to VPN gateways or firewalls supporting IP Security (IPSec).Digital certificates can be supported Using IPSec standards. Security is the primary concern in adoption of wireless data. Wireless virtual private networks (WVPNs) offer a secure means of penetrating corporate firewalls for remote access.
WVPNs can extend the reach of wireless data beyond vertical applications into a broader horizontal market that encompasses any mainstream business (sales, insurance, and finance, health care) that must provide mobile access to standard enterprise-wide applications. Just as enterprises were able to leverage the value proposition of a VPN for voice communications when remote users could link in to voice mail and forward messages, data VPNs can be justified on the basis of database access, messaging, and providing least-cost routing across wireless and wireline transports
Issues under Focus are:
·Importance of VPNs for wireless remote access;
·Unique requirements for wireless connections and the degree to which current VPN technologies serve these requirements;
·Interoperability of VPNs with Wireless Application Protocol (WAP);
·Benefits in the wireless environment of end-to-end VPNs versus carrier-to-customer VPNs; and
·VPN enhancements to 2.5G and 3G networks.
·Integration with diverse wireless technologies including wireless local area networks (WLANs), Bluetooth, CDMA, CDPD, GSM and GPRS
A sample Wireless Application using VPN:
A simple solution would be to use a proxy server browser with a constant IP address supporting say SSL Encryption.To put in a higher level of security It is possible to have a checkpoint firewall with L2TP and PPTP Encryption. This makes multiuser authentication possible.There are still some companies which might not be happy with the idea of sensitive data being allowed to traverse through the Internet(public domain). In such a case the company intranet must have a dedicated port and must be connected to VPN service provider through a router. A permanent Virtual circuit is used and access is through say frame relay technique.
Firewall
L2TP
PPTP
Encryption
Fig:8 A basic VPN Scheme Implementation.
.
Wireless Devices
Fig:9 An Advanced VPN Implementation
8.Conclusion
The VPN essentially is a harbinger for many more things to come in the field of connectivity as companies and mobile users clamor for more and more information anywhere, anyplace, anytime. Wireless VPN is a reality today with some solutions already available and more products in the pipeline. The next generation of Mobile computing will certainly include (already included in fact) VPN and related technologies. Thank You.
10.Bibliography
1)U. Black, "Mobile and Wireless Networks," Prentice-Hall, 1996,.
2)William C. Y. Lee, "Lee’s Essentials to wireless Communications," McGraw-Hill Professional Publishing, November 2000.
3)J. Gardiner, B. West, "Personal Communication Systems and Technologies," Artech House: Norwood
4)Juha Korhonen, "Introduction to 3G Mobile Communications," Artech House, June 2001.
5)Mansoor Shafi, "Wireless Communications in the 21st Century," IEEE, January 2001
6)Scn Education Bv, "Mobile Networking With Wap: The Ultimate Guide to the Efficient Use of Wireless Application Protocol," Morgan Kaufmann Publishers, July 2000.
7)Gilbert Held, "Data Over Wireless Networks: Bluetooth, WAP, and Wireless Lans," McGraw-Hill Professional Publishing, November 2000
8)R.A. Dayem, "Mobile Data & Wireless LAN Technologies," Prentice-Hall: Upper Saddle River, NJ, 1997.
9)B. Bates, "Wireless Networked Communications: Concepts, Technology, and Implementation," McGraw-Hill: New York, NY, 1994.
10)R. Schneiderman, "Future Talk: Changing the Wireless Game," IEEE Press: Piscataway, NJ, 1997.
11)A. D. Hadden, "Personal Communications Networks: Practical Implementation," Artech House: Norwood, MA, 1995,
12)Chander Dhawan, "Remote Access Networks" McGraw-Hill, 1998.
13)Vijay K. Garg, Joseph E. Wilkes, "Wireless and Personal Communication Systems" IEEE, November 2000.
14) Jason Smolek, "Striving for a VPN-Based Wireless LAN: Cisco Aironet 350 Series," IDC.
-----------------------
Router
Router
Company Intranet
Company
Server
Proxy
Server
Wireless
Devices
Proxy server
Internet
Company
Server
Firewall
Check
Point
................
................
In order to avoid copyright disputes, this page is only a partial summary.
To fulfill the demand for quickly locating and searching documents.
It is intelligent file search solution for home and business.
Related download
- ffiv zacks investment research
- schedule 11 softtestpays
- isap lab 479ec08054
- while wap wireless application protocol applications are
- college of science and engineering university of houston
- encryption otava
- teaching wireless local area network security performance
- gsa contract gs 35f 0913n
- first time setup registering your devices
- peds vpn anyconnect installation instructions for windows pc
Related searches
- aip protocol food list printable
- betadine protocol viral conjunctivitis
- aip protocol food list
- autoimmune protocol diet print out
- autoimmune protocol food list
- sample protocol template
- time out protocol in surgery
- crps physical therapy protocol pdf
- joint commission universal protocol checklist
- universal protocol standard
- universal protocol checklist
- joint commission protocol orders