See correction to this article

Today’s personal-firewall debates focus on how well firewalls determine whether an application that requests Internet access is legitimate. Some firewalls show only the application’s filename, and the user has to make the decision whether to let the application access the Internet. Other firewalls contain a database of application filenames. When an application requests Internet access, the firewalls compare the application’s filename against the filenames in the database. If a match occurs, the firewalls permit the application access. Although this strategy worked initially, malicious intruders soon discovered that if their malware had the same name as an allowed legitimate application, the malware could masquerade as that legitimate application and gain access to the Internet. Firewall vendors responded to these types of attacks by creating a database that contained the application’s filename and some sort of stored checksum that could prove the application was what it said it was. Although intruders learned how to defeat the checksum application control, adding the database and checksum controls were steps in the right direction.

Feature 5: Protection Zones
Most home networks don’t need the same level of protection inside the home that they need against the Internet and outside intruders. Some firewalls let you define different protection zones (usually local and Internet) with particular levels of default security. Hence, PCs on your LAN might need accessibility to file- and print-sharing services but not to outside machines. Protection zones allow this type of control. Some firewalls automatically detect the local network machines, and others wait for the user to define the machines.

Feature 6: Logs and Alerts
A good firewall automatically logs malicious activity for the user to analyze. Logging should contain enough information to be helpful during future investigations. At a bare minimum, the average log records the event’s date and time and provides a brief description of which event caught the firewall’s attention. The best logs offer configurable levels of detail or links to more information that describes the attack. The firewall should alert the user with a pop-up message whenever an attack is high risk or consistent. Most people don’t have the time to research every attack; I’ve successfully stopped persistent attackers by calling my ISP. On the downside, firewalls can alert you to every suspicious packet even when nothing is wrong (i.e., a false-positive).

The Test Laboratory
Besides a personal firewall’s features, a firewall’s efficiency is crucial, so I decided to test the six popular person firewalls I mentioned earlier. I set up four victim machines typical of today’s home networks: XP Home Edition, Windows 2000 Professional, Windows Me, and Windows 98. I installed the latest crucial patches on each machine as Microsoft’s Windows Update indicated. My attack machine ran Windows NT Server 4.0; I installed professional security-vulnerability scanners and malicious cracker-attack tools. Tests simulated popular external attacks and scans against the firewall, and internal tests simulated how the firewall handled locally executed malicious code (e.g., Trojan horses, worms).

The assessment and attack tools I used included Gibson Research’s ShieldsUp!! and LeakTest applications, ISS's Internet Scanner 6.2.1, Foundstone’s SuperScan 3.0, Security Software Technologies’ (SST's) Cerberus Internet Scanner (CIS) 5.0.02, an Internet Control Message Protocol (ICMP) bomber, a TCP, and a UDP port flooder. The malware I used for the internal tests included the NetBus Trojan horse, Back Orifice 2000 Trojan horse, Magistr virus, Strange Brew (a Java virus), Hybris worm, Badtrans worm, CIH virus, SubSeven Trojan horse, VBS.LoveLetter worm, Exploder (a malicious ActiveX control), and Keydropper (a boot virus). Although these external-attack and internal-attack tests are far from scientific, they gave the firewalls a good trial and demonstrated their weaknesses.

The Overall Test Results
Overall, how did the personal firewalls do? Except for one contender, ICF, each personal firewall I reviewed provided significant protection for a Windows-based PC. The other firewalls seemed to hopelessly outclass ICF, Microsoft’s first consumer firewall product. All the personal firewalls installed themselves as services, which is important because they provide security anytime you turn on your machine. Each firewall did its job, although false-positive alerts were a problem. I expect vendors to spend the coming year better identifying legitimate threats and providing more information to users so that they can identify the real problems.

All the firewalls I tested prevented most known external attacks from causing problems on the victim machines. Even my largest Denial of Service (DoS) attempts caused only a slight slowing on each PC. The firewalls did their job, and the machines didn’t encounter any large exploits. Although the firewalls provided the needed protection, they didn’t log all the malicious attempts. This deficiency could permit cracking activity to continue unnoticed and let intruders succeed in future efforts.

I wish I could be as upbeat about the internal tests. Most of the firewalls stopped locally executed Trojan horses and worms from connecting to the Internet, but in their default configurations failed to stop any other type of local malicious activity. Viruses, worms, and Trojan horses still executed and were free to manipulate the local computer system without fear of firewall interference. Malicious ActiveX controls and Java applets went untouched through the browser. Visual Basic (VB) worms still executed and attached themselves to Microsoft Outlook email. I expected this result and, to be honest, it was great to see the firewalls preventing malicious connections to the Internet. Last year, half the personal firewalls would have failed this test. This result is evidence of tougher firewall rules and application controls. Clearly, however, no PC is secure without a locally installed antivirus program, too.

Prev. page     1 [2] 3 4 5 6     next page
CORRECTIONS TO THIS ARTICLE:
The print version of "Personal Firewalls" (InstantDoc ID 25348) includes an incorrect URL for the expanded version of the article. The correct URL is http://www.winnetmag.com/articles/index.cfm?articleid=25348. We apologize for any inconvenience this error might have caused.




You must log on before posting a comment.

If you don't have a username & password, please register now.

Reader Comments

Tiny used to be my firewall of choice, until I discovered Kerio Personal Firewall (www.kerio.com), which is Tiny v2 that has actually been developed further by the same people who originally put Tiny together. So if you like Tiny, you'll like Kerio just as much or even more... and it's still free.

Nick

Great article

Vincent Acheson

I was very disappointed that you didn't cover the Sygate Personal Firewall. It blows Norton's away as badly as Panda Antivirus blows away Norton's Antivirus program. A firewall review without it just doesn't make sense.

Joel Munt

I used Norton's product, but switched to ZoneAlarm Pro v.3 about 6 months ago. After applying the most recent patch (3.0.118.001), my computers stopped accepting cookies. This persisted even after I put the browser's privacy settings at their lowest--allow all cookies. This brings me to my point--ZoneAlarm's tech support is abysmal. It's email-only and they take anywhere from 5-10 days to respond. The only way for me to do any online shopping is to shut down ZAP completely, which defeats the purpose. I'm chalking this up to "lessons learned" and just received the newest version of Norton's Internet Security. I'll be installing that right away.

Paul Edwards

What about the personal firewall from SyGate called Personal Firewall PRO?

MP3ster

Why is Tiny Version 2.0 used when version 3.0 is available? Version 3 adds a ton of new features like sandboxing, script blocking, registry protection, application groups, etc., and has preset levels of protection for novices. I used AtGuard before Symantec bought the rights to the program (a la Ghost) because of the advanced rules that could be created, then I switched to Tiny 2.0. Tiny 3.0 blows version 2.0 out of the water. You can download a 30 day trial at their website.

Kevin Sussex

With XP Pro, does one have to disable the built-in firewall with these products or can they run in parallel?

John Joslin

Does anyone have trouble with Norton's Firewall causing your computer to automatically shutdown when opening certain websites? Trying to visit my Insurance providers website and some other sites, will send my computer to Restart.

Linda D

 
 

ADS BY GOOGLE