VPN
Issue 3.4.1 June 2005
309
The application of firewall technologies only represents a portion of an overall security strategy.
Firewall solutions do not guarantee 100% security by themselves. These technologies must be
complemented with other security measures, such as user authentication and encryption, to
achieve a complete solution.
The three technologies that are most commonly used in firewall products are packet filtering,
proxy servers, and hybrid. These technologies operate at different levels of detail, and thus they
provide varying degrees of network access protection. That means that these technologies are
not mutually exclusive. A firewall product may implement several of these technologies
simultaneously.
Network management and outsourcing models
While enterprises acknowledge the critical role that the Internet and IP VPNs can play in their
strategic eBusiness initiatives, they face a range of choices for implementing their VPNs. The
options range from enterprise-based or “do-it-yourself” VPNs that are fully built, owned, and
operated by the enterprise, to VPNs that are fully outsourced to a carrier or other partner. In the
near term, it is generally believed that enterprise-operated and managed VPN services will
hover around a 50/50 split, including hybrid approaches.
Increasingly, enterprises are assessing their VPN implementation options across a spectrum of
enterprise-based, carrier-based/outsourced, or hybrid models. Each approach offers a unique
business advantage.
●
Enterprise based. This option operates over a public network facility (most commonly the
Internet) using equipment that is owned and operated by the enterprise. Its greatest
benefit to the enterprise is the degree of flexibility and control it offers over VPN
deployment, administration, and adaptability or change.
●
Fully outsourced. This managed service could be implemented by a collection of
partners, including an ISP and a security integration partner. Its advantages include quick
deployment, easy global scalability, and freedom from overhead network management.
●
Shared management. With this hybrid approach, a partner can take responsibility for
major elements of infrastructure deployment and management, but the enterprise retains
control over key aspects of policy definition and security management.
Conclusion
Moving to a multipurpose packet-based VPN that transports both voice and data with high
quality poses a number of significant management challenges. Managers must determine
whether to operate the network using an enterprise-based model, an outsourced or
carrier-based model, or a hybrid model. They must settle security issues that involve several
layers of the network. And they must ensure that they and their vendors can achieve the
required QoS levels across these complex networks. Yet the advantages of converged,
multipurpose VPNs remain a strong attraction. The opportunity to eliminate separate, duplicate
networks and costly dedicated facilities, avoid costly public network long distance charges, and
Summary of Contents for Application Solutions
Page 1: ...Avaya Application Solutions IP Telephony Deployment Guide 555 245 600 Issue 3 4 1 June 2005 ...
Page 20: ...About This Book 20 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 21: ...Issue 3 4 1 June 2005 21 Section 1 Avaya Application Solutions product guide ...
Page 22: ...22 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 106: ...Call processing 106 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 124: ...Avaya LAN switching products 124 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 139: ...Issue 3 4 1 June 2005 139 Section 2 Deploying IP Telephony ...
Page 140: ...140 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 186: ...Traffic engineering 186 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 204: ...Security 204 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 228: ...Avaya Integrated Management 228 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 274: ...Reliability and Recovery 274 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 275: ...Issue 3 4 1 June 2005 275 Section 3 Getting the IP network ready for telephony ...
Page 276: ...276 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 356: ...Network recovery 356 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 366: ...Network assessment offer 366 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 367: ...Issue 3 4 1 June 2005 367 Appendixes ...
Page 368: ...Appendixes 368 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 394: ...Access list 394 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 414: ...DHCP TFTP 414 Avaya Application Solutions IP Telephony Deployment Guide ...