|A component of|
|Other names||Windows Firewall|
Internet Connection Firewall
|Description||Windows Firewall helps protect your computer by preventing unauthorized users from gaining access to your computer through the Internet or a network.|
|Windows Security Center|
Windows Firewall (officially called Windows Defender Firewall in Windows 10), is a firewall component of Microsoft Windows. It was first included in Windows XP and Windows Server 2003. Prior to the release of Windows XP Service Pack 2 in 2004, it was known as Internet Connection Firewall. With the release of Windows 10 version 1709, in September 2017, it was renamed Windows Defender Firewall as part of the "Windows Defender" branding campaign.
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.[dead link] 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. Because of these incidents, as well as other criticisms that Microsoft was not being active in protecting customers from threats, Microsoft decided to significantly improve both the functionality and the interface of Windows XP's built-in firewall, rebrand it as Windows Firewall, and switched it on by default since Windows XP SP2.
One of three profiles is activated automatically for each network interface:
- Public assumes that the network is shared with the World and is the most restrictive profile.
- Private assumes that the network is isolated from the Internet and allows more inbound connections than public. A network is never assumed to be private unless designated as such by a local administrator.
- Domain profile is the least restrictive. It allows more inbound connections to allow for file sharing etc. The domain profile is selected automatically when connected to a network with a domain trusted by the local computer.
Security log capabilities are included, which can record IP addresses and other data relating to connections originating from the home or office network or the Internet. It can record both dropped packets and successful connections. This can be used, for instance, to track every time a computer on the network connects to a website. This security log is not enabled by default; the administrator must enable it.
Windows Firewall can be controlled/configured through a COM object-oriented API, scriptable through the netsh command, through the GUI administration tool or centrally through group policies. All features are available regardless of how it is configured.
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. 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. XP's 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) 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 backup and antivirus solutions) could communicate.
Note that the DCOM problem can be solved by moving applications to DComLab's ComBridge protocol.
- The firewall is based on the Windows Filtering Platform.
- A new management console snap-in named Windows Firewall with Advanced Security which provides access to many advanced options, and enables remote administration. This can be accessed via Start -> Control Panel -> Administrative Tools -> Windows Firewall with Advanced Security, or by running "wf.msc"
- Outbound packet filtering, reflecting increasing concerns about spyware and viruses that attempt to "phone home". Outbound rules are configured using the management console. Notifications are not shown however for outbound connections.
- 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.
- Improved interface for managing separate firewall profiles. Ability to have three separate firewall profiles for when computers are domain-joined, connected to a private network, or connected to a public network (XP SP2 supports two profiles—domain-joined and standard). Support for the creation of rules for enforcing server and domain isolation policies.
Windows Server 2008 and Windows 7
The only change to this component in Windows 10 is the change of name that occurred in the September 2017 update, known as the Fall Creators Update (codename Redstone 3).
- List of Microsoft Windows components
- Security and safety features new to Windows Vista
- Personal firewall
- Comparison of firewalls
- Lemos, Robert (August 17, 2004). "Study: Unpatched PCs compromised in 20 minutes". CNET. CBS Interactive.
- "Troubleshooting Windows Firewall settings in Windows XP Service Pack 2". Support. Microsoft. October 19, 2004. Archived from the original on October 20, 2004.
- "Network Location Awareness". TechNet. Microsoft. November 2, 2007.
- "Internet Connection Firewall security log". TechNet. Microsoft. January 21, 2005. Archived from the original on November 10, 2008.
- "Appendix B: Netsh Command Syntax for the Netsh Firewall Context". TechNet. Microsoft. December 17, 2004.
- "User Interface: Windows Firewall with Advanced Security". TechNet. Microsoft. January 20, 2009.
- "Deploying Windows Firewall Settings With Group Policy". TechNet. Microsoft. December 17, 2004.
- "Windows Firewall". Windows. Microsoft. Archived from the original on June 11, 2011. Retrieved 2015-11-30.
- "Manually Configuring Windows Firewall in Windows XP Service Pack 2". TechNet. Microsoft. February 2004.
- "Deploying Windows XP Service Pack 2 using Software Update Services". TechNet. Microsoft. August 18, 2004.
Factors to consider when using SUS to deploy Windows XP SP2
- "To configure IPv6 Internet Connection Firewall". TechNet. Microsoft. February 2, 2006.
- "The New Windows Firewall in Windows Vista and Windows Server 2008". TechNet. Microsoft. January 2006.
- "What's New in Windows Firewall with Advanced Security". TechNet. Microsoft. October 26, 2009.
- ^ These multiple vulnerabilities were fixed by Microsoft over the course of several months; Microsoft security bulletins MS03-026, MS03-039, and MS04-012 cover this in more detail.