Why Bother with Windows Firewall?
Microsoft users probably encounter the Windows Firewall while surfing the net; on several occasions it alerts them about changes in the connections of online or local networks and asks permission before connections are made. Regrettably, the majority of these users opt not to look over these warnings and ignore Windows Firewall entirely. Why should you bother with Windows Firewall, anyway? What are they missing?
Windows Firewall is a built-in protection first introduced as part of Windows XP Service Pack 2. The firewall supports a security log which records IP addresses and other data pertaining to local connections originating from the home or office network or from the Internet. The security log can record both dropped packets and successful connections. This information can be used to track every time a computer on the network connects to another computer within the network or to a website. This security log is not enabled by default; the administrator must enable it. XP’s Windows Firewall cannot block outbound connections; it is only capable of blocking inbound ones.
Admittedly, the Windows Firewall needed a lot of improvements when it came out for the first time. However, the latest incarnation of this application, offered with Windows Vista comes with the necessary updates and upgrades. It has a new management console called ‘Windows Firewall with Advanced Security’ which provides access to many advanced options and enables remote administration. It enables outbound packet filtering, rules can also be specified for source and destination IP addresses and port ranges. Increasing concerns about spyware and viruses are readily announced. Outbound rules are configured using the management console.