|
|
Firewalls permit or deny applications based upon a set of rules and other criteria. And for the longest time, the ‘set of rules or other criteria’ was simply source and destination IP address and port number. FTP traffic was on port 21, telnet 23, SMTP 25, and on and on—The Internet Assigned Numbers Authority (IANA) maintains an exhaustive list for any security guru who doesn’t know it by heart. At one point, a list like this formed the basis of the very cutting-edge in enterprise network firewall technology. But times have changed.
Today many applications are designed with the ability to hop between ports. AOL Instant Messenger has assigned ports that can be found on the IANA well-known port numbers list, but it can and will revert to port 80 if these are blocked by a network firewall. And no matter how badly a security admin wants to control AIM traffic, blocking port 80 is simply not an option. AIM is by no means the only application using this method to bypass traditional firewalls, and attack traffic has also evolved to hop between ports. It’s begun spreading via Internet and Intranet links using applications like streaming audio, VoIP and P2P file-sharing. If a firewall lacks the ability to look deeper than standard port numbers in order to determine the true nature of the traffic being inspected, then the protection provided by this firewall is woefully inadequate.
McAfee’s AppPrism technology has the ability to distinguish AIM traffic running over port 80 from regular HTTP traffic, and it goes a step further. In Version 8 of McAfee Firewall Enterprise, AppPrism allows a security administrator to go beyond simple identification of traffic and enables a granularity of control that truly allows for the construction of a ‘set of rules’ capable of protecting today’s enterprise network. An example of this can be seen in a recent video review in which David Strom highlights McAfee’s ability to allow IM traffic while specifically disallowing its file transfer capabilities in order to enforce corporate policy. The video can be seen here and is a perfect example of McAfee Firewall Enterprise’s ability to identify applications, control functionality, protect the enterprise and enforce corporate policy.
|
|
Gartner claims mashups and personalized portals may be reborn as the next big IT thing after social networking. Will the firewall/AppPrism be able to set effective policies for these sorts of complex streams (which could certainly include IM and VoIP)?
Barbara-
McAfee knows that enforcing corporate policy and providing real protection hinge on the ability to distinguish between protocols and address the security of each as necessary. I believe their commitment to real security will be evident and that their application signatures will keep pace with the evolving communications landscape.
Hi Joe-
Very interesting comment. I’d say that DLP today is more about stopping people from accidentally leaking information rather than those trying to do so deliberately. You’re right about the PSTN though, and I’d never thought of it in quite that way.
Thanks-
William
William
In addition to the apps you mention bypassing the FW infrastructure…we see something even more persistent and more pervasive….in the enterprise the whole voice infrastructure by-passes the packet based security in place. Whether it be DLP via modems, voice, fax…it is a pervasive way to circumvent millions of dollars of perfectly good packet only security techniques. We see it in every customer we have assessed and sold to. Is it MFE’s intent to address the PSTN as an untrusted global network? Ok…so it’s narrowband…but nodally there are more vectors of ingress or egress than an enterprise’s Internet data centers.
Great post by the way!
Joe
Submit your own comments / message for this post