- What does Cisco have against Quebec?
- Attrition.org nails another nitwit
- Diary of a deliberately spammed housewife
- Seven cloud-computing security risks
- 20 great Windows open source projects
News | Newsletters | Podcasts | Chats | Opinions | RSS Feeds | This Week In Print | IT Careers | Community | Reports | Downloads | Slideshows | New Data Center
Partner Sites:App Performance | On Demand Security | Networking Solution | SOA | Value of WDS
Last time, we mentioned that the current generation of WAN firewalls has not advanced as rapidly as the security threats that the firewalls are supposed to protect against. Today we'll examine that in greater detail and identify some of the key weaknesses in the current generation of firewalls.
In the last newsletter, we pointed out that the current generation of WAN firewalls focuses on the packet header. One reason for that is that the current generation of firewalls generally have limited processing capacity due to architectures that are based on software that runs on an industry standard CPU. While there certainly are advantages to using an industry standard CPU, their ability to perform intense processing is definitely not one of them.
To overcome these limitations, many of the current firewall vendors have souped up their products with the addition of some limited forms of hardware assistance or acceleration. For example, some current generation firewalls have been augmented with intrusion protection and/or intrusion protection functionality that uses Deep Packet Inspection (DPI) to screen suspicious-looking traffic. However, the limitations in the processing power of current generation firewalls prevents DPI from being applied to more than a small minority of the packets traversing the device.
In addition, current generation firewalls make two fundamental assumptions, both of which are flawed. The first assumption is that the information contained in the first packet in a connection is sufficient to identify the application and the functions being performed by the application. In many cases, it takes a number of packets to make this identification because the application end points can negotiate a change in port number or perform a range of functions over a single connection.
The second assumption concerns the use of well-known ports. In IP networks, TCP and UDP ports are endpoints to logical connections and provide the multiplexing mechanism to allow multiple applications to share a single connection to the IP network. Port numbers range from 0 to 65535. The ports that are numbered from 0 to 1023 are reserved for privileged system-level services and are designated as well-known ports. Both TCP and UDP have well-known and registered port numbers. The typical current-generation firewall makes the assumption that these port numbers are always used as specified.. As we discussed in a previous newsletter a growing number of applications such as AOL's Instant Messenger don't always use the well-known ports that were assigned to them. Hence, while this assumption may have been valid 20 years ago, it is not valid today.
www.google-alba.ch faqja e intrnetit me e mira ku mund te gjeni gjithcka vizitojeni dhe do te mbeteni...- Anonymous
Partner Content
Simplify Your Branch Infrastructure
Learn how to simplify your branch infrastructure while dramatically increasing app performance with Citrix Branch Repeater.
Download the Free Info Kit
Next-Gen Load Balancing
Free Guide: “Next Gen Load Balancing: 8 Things You Need to Handle Today’s Network Traffic” shows you the functionality needed in your next load balancer.
Download the Free Guide
Accelerate Your Web Apps by up to 5x
Free Guide: “The Secret to Getting Maximum Speed from your Web Applications.” Learn how you can deliver Web apps up to 5x faster.
Download the Free Guide
Comment