Windows Firewall

From Wikipedia, the free encyclopedia

Windows Firewall icon in Windows Vista

Computer security Portal

Windows Firewall is a personal firewall, included with Microsoft's Windows XP, Windows Server 2003, and Windows Vista operating systems.

1 Overview
2 Versions
3 References
4 See also
5 External links

[edit] Overview

When Windows XP was originally shipped in October 2001, it included a limited firewall called "Internet Connection Firewall". It was disabled by default due to concerns with backward compatibility, and the configuration screens were buried away in network configuration screens that many users never looked at. As a result, it was rarely used. In mid-2003, the Blaster worm attacked a large number of Windows machines, taking advantage of flaws in the RPC Windows service.^[1] Several months later, the Sasser worm did something similar. The ongoing prevalence of these worms through 2004 resulted in unpatched machines being infected within a matter of minutes.^[2] Because of these incidents, as well as other criticisms that Microsoft was not being proactive in protecting customers from threats, Microsoft decided to significantly improve both the functionality and the interface of Windows XP's built-in firewall, and rebrand it as, simply, "Windows Firewall".

[edit] Versions

[edit] Windows XP

Windows Firewall settings in Windows XP Service Pack 2

Windows Firewall was first introduced as part of Windows XP Service Pack 2. Every type of network connection, whether it is wired, wireless, VPN, or even Firewire, has the firewall enabled by default, with some built-in exceptions to allow connections from machines on the local network. It also fixed a problem whereby the firewall policies would not be enabled on a network connection until several seconds after the connection itself was created, thereby creating a window of vulnerability.^[3] A number of additions were made to Group Policy, so that Windows system administrators could configure the Windows Firewall product on a company-wide level. Windows Firewall cannot block outbound connections; it is only capable of blocking inbound ones.

Windows Firewall turned out to be one of the two most significant reasons (the other being DCOM activation security^[4]) that many corporations did not upgrade to Service Pack 2 in a timely fashion. Around the time of SP2's release, a number of Internet sites were reporting significant application compatibility issues, though the majority of those ended up being nothing more than ports that needed to be opened on the firewall so that components of distributed systems (typically back-up and antivirus solutions) could communicate.

[edit] Windows Server 2003

In March 2005, Microsoft released Windows Server 2003 Service Pack 1, which incorporated the same improvements to the firewall product into their server operating system.

[edit] Windows Vista

Windows Firewall in Windows Vista

Windows Vista significantly improves the firewall^[5] to address a number of concerns around the flexibility of Windows Firewall in a corporate environment:

IPv6 connection filtering
Outbound packet filtering, reflecting increasing concerns about spyware and viruses that attempt to "phone home"
With the advanced packet filter, rules can also be specified for source and destination IP addresses and port ranges
Rules can be configured for services by its service name chosen by a list, without needing to specify the full path file name.
IPsec is fully integrated, allowing connections to be allowed or denied based on security certificates, Kerberos authentication, etc. Encryption can also be required for any kind of connection.
A new management console snap-in named Windows Firewall with Advanced Security which provides access to many advanced options, and enables remote administration.
Ability to have separate firewall profiles for when computers are domain-joined or connected to a private or public network. Support for the creation of rules for enforcing server and domain isolation policies