<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:series="http://unfoldingneurons.com/"
		>
<channel>
	<title>Comments on: Windows 7 multiple active firewall profiles</title>
	<atom:link href="http://4sysops.com/archives/windows-7-multiple-active-firewall-profiles/feed/" rel="self" type="application/rss+xml" />
	<link>http://4sysops.com/archives/windows-7-multiple-active-firewall-profiles/</link>
	<description>For Windows Administrators</description>
	<lastBuildDate>Fri, 19 Mar 2010 19:02:26 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Wilbur Parker</title>
		<link>http://4sysops.com/archives/windows-7-multiple-active-firewall-profiles/comment-page-1/#comment-142870</link>
		<dc:creator>Wilbur Parker</dc:creator>
		<pubDate>Sun, 29 Nov 2009 16:59:46 +0000</pubDate>
		<guid isPermaLink="false">http://4sysops.com/?p=2509#comment-142870</guid>
		<description>Searching for this for some time now, Thank you.</description>
		<content:encoded><![CDATA[<p>Searching for this for some time now, Thank you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anon</title>
		<link>http://4sysops.com/archives/windows-7-multiple-active-firewall-profiles/comment-page-1/#comment-125294</link>
		<dc:creator>Anon</dc:creator>
		<pubDate>Wed, 18 Mar 2009 02:19:47 +0000</pubDate>
		<guid isPermaLink="false">http://4sysops.com/?p=2509#comment-125294</guid>
		<description>This is a definitely an interesting topic to cover, but I think that the Multiple Active Firewall Profiles feature has been misunderstood. 

It seems that this article is demonstrating the &quot;Windows Firewall with Advanced Security&quot; feature that allows users to configure (per-profile) whether or not each network interface should be protected by Windows Firewall. This is useful in situations where you only want Firewall to be active if your interface is connected to a certain type of network (e.g. protect my wireless interface when I am connected to a Public network, but not when I am connected to a Domain network). This is useful, but it is not the same as Multiple Active Firewall Profiles.

In Windows Vista only one firewall profile could be active at any time. This meant that even if you were connected to a &quot;private&quot; network and a &quot;public&quot; network on the same machine, the overall firewall policy being enforced on the machine was &quot;public&quot; (public is selected because it is meant to be the more secure profile of the two).

For example, say my computer has:

A Wired interface connected to Private network
and
A Wireless interface connected to Public network

On both interfaces the &quot;public&quot; firewall rules would be applied. This isn&#039;t ideal because it means that to get things working correctly on my wired (private) network I might need to add firewall rules to the &quot;public&quot; profile...but then those rules will also apply to the wireless (public) network too...which I may not want!

In Windows 7 this behavior has been much improved due to a new feature called &quot;Multiple Active Firewall Profiles&quot;. With the new behavior you will see that Firewall is now capable of enforcing different profile policies on each interface! 

If you take the same example as above, the behavior in Windows 7 will be to enforce the &quot;Private&quot; profile firewall policy on the wired interface, and it will enforce the &quot;Public&quot; profile firewall policy on the wireless interface. This is a really great improvement because it means that you can keep your Public networks secured with a restrictive firewall policy while at the same time applying a less-restrictive policy to your private network.</description>
		<content:encoded><![CDATA[<p>This is a definitely an interesting topic to cover, but I think that the Multiple Active Firewall Profiles feature has been misunderstood. </p>
<p>It seems that this article is demonstrating the &#8220;Windows Firewall with Advanced Security&#8221; feature that allows users to configure (per-profile) whether or not each network interface should be protected by Windows Firewall. This is useful in situations where you only want Firewall to be active if your interface is connected to a certain type of network (e.g. protect my wireless interface when I am connected to a Public network, but not when I am connected to a Domain network). This is useful, but it is not the same as Multiple Active Firewall Profiles.</p>
<p>In Windows Vista only one firewall profile could be active at any time. This meant that even if you were connected to a &#8220;private&#8221; network and a &#8220;public&#8221; network on the same machine, the overall firewall policy being enforced on the machine was &#8220;public&#8221; (public is selected because it is meant to be the more secure profile of the two).</p>
<p>For example, say my computer has:</p>
<p>A Wired interface connected to Private network<br />
and<br />
A Wireless interface connected to Public network</p>
<p>On both interfaces the &#8220;public&#8221; firewall rules would be applied. This isn&#8217;t ideal because it means that to get things working correctly on my wired (private) network I might need to add firewall rules to the &#8220;public&#8221; profile&#8230;but then those rules will also apply to the wireless (public) network too&#8230;which I may not want!</p>
<p>In Windows 7 this behavior has been much improved due to a new feature called &#8220;Multiple Active Firewall Profiles&#8221;. With the new behavior you will see that Firewall is now capable of enforcing different profile policies on each interface! </p>
<p>If you take the same example as above, the behavior in Windows 7 will be to enforce the &#8220;Private&#8221; profile firewall policy on the wired interface, and it will enforce the &#8220;Public&#8221; profile firewall policy on the wireless interface. This is a really great improvement because it means that you can keep your Public networks secured with a restrictive firewall policy while at the same time applying a less-restrictive policy to your private network.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Pietroforte</title>
		<link>http://4sysops.com/archives/windows-7-multiple-active-firewall-profiles/comment-page-1/#comment-125175</link>
		<dc:creator>Michael Pietroforte</dc:creator>
		<pubDate>Sun, 15 Mar 2009 13:11:09 +0000</pubDate>
		<guid isPermaLink="false">http://4sysops.com/?p=2509#comment-125175</guid>
		<description>Samantha, thanks!

William, thanks! I was unsure when I wrote the article, but I didn&#039;t find a clarifying description on the web. I corrected the article now.</description>
		<content:encoded><![CDATA[<p>Samantha, thanks!</p>
<p>William, thanks! I was unsure when I wrote the article, but I didn&#8217;t find a clarifying description on the web. I corrected the article now.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: William</title>
		<link>http://4sysops.com/archives/windows-7-multiple-active-firewall-profiles/comment-page-1/#comment-125171</link>
		<dc:creator>William</dc:creator>
		<pubDate>Sun, 15 Mar 2009 09:08:06 +0000</pubDate>
		<guid isPermaLink="false">http://4sysops.com/?p=2509#comment-125171</guid>
		<description>AFAIK, public = public; private = home+work; domain is applied automatically when a domain controller of the domain the workstation belongs to is detected on the network.</description>
		<content:encoded><![CDATA[<p>AFAIK, public = public; private = home+work; domain is applied automatically when a domain controller of the domain the workstation belongs to is detected on the network.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Samantha</title>
		<link>http://4sysops.com/archives/windows-7-multiple-active-firewall-profiles/comment-page-1/#comment-125062</link>
		<dc:creator>Samantha</dc:creator>
		<pubDate>Thu, 12 Mar 2009 09:49:55 +0000</pubDate>
		<guid isPermaLink="false">http://4sysops.com/?p=2509#comment-125062</guid>
		<description>If you have a small company and need an all in one solution that I would look at something like unified threat managment also known as a UTM.Cyberoam firewall is the only UTM firewall that embeds user identity in firewall rule matching criteria, enabling enterprises to configure policies and identify users directly by the username rather than through IP addresses. Cyberoam?s powerful hardware firewall provides stateful and deep packet inspection, access control, user authentication, network and application-level protection.

The ICSA-certified Cyberoam firewall is available along with VPN, gateway anti-virus and anti-spyware, gateway anti-spam, intrusion prevention system, content filtering, bandwidth management and multiple link management, providing comprehensive security to small, medium and large enterprises, including remote and branch offices. Cyberoam is a Check Mark Level 5 certified UTM solution.

Key Features

1.Stateful Inspection Firewall
2.Centralized management for multiple security features
3.Embeds user identity in rule-matching criteria
4.Multiple zone security
5.Granular IM, P2P controls
6.ICSA certified</description>
		<content:encoded><![CDATA[<p>If you have a small company and need an all in one solution that I would look at something like unified threat managment also known as a UTM.Cyberoam firewall is the only UTM firewall that embeds user identity in firewall rule matching criteria, enabling enterprises to configure policies and identify users directly by the username rather than through IP addresses. Cyberoam?s powerful hardware firewall provides stateful and deep packet inspection, access control, user authentication, network and application-level protection.</p>
<p>The ICSA-certified Cyberoam firewall is available along with VPN, gateway anti-virus and anti-spyware, gateway anti-spam, intrusion prevention system, content filtering, bandwidth management and multiple link management, providing comprehensive security to small, medium and large enterprises, including remote and branch offices. Cyberoam is a Check Mark Level 5 certified UTM solution.</p>
<p>Key Features</p>
<p>1.Stateful Inspection Firewall<br />
2.Centralized management for multiple security features<br />
3.Embeds user identity in rule-matching criteria<br />
4.Multiple zone security<br />
5.Granular IM, P2P controls<br />
6.ICSA certified</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 4sysops - Windows 7 multiple active bfirewall/b profiles &#124; Software Downloads</title>
		<link>http://4sysops.com/archives/windows-7-multiple-active-firewall-profiles/comment-page-1/#comment-125024</link>
		<dc:creator>4sysops - Windows 7 multiple active bfirewall/b profiles &#124; Software Downloads</dc:creator>
		<pubDate>Wed, 11 Mar 2009 17:03:05 +0000</pubDate>
		<guid isPermaLink="false">http://4sysops.com/?p=2509#comment-125024</guid>
		<description>[...] Read more here:  4sysops - Windows 7 binary astir bfirewall/b profiles [...]</description>
		<content:encoded><![CDATA[<p>[...] Read more here:  4sysops &#8211; Windows 7 binary astir bfirewall/b profiles [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 4sysops - Windows 7 multiple active firewall profiles &#124; WinSe7en</title>
		<link>http://4sysops.com/archives/windows-7-multiple-active-firewall-profiles/comment-page-1/#comment-125015</link>
		<dc:creator>4sysops - Windows 7 multiple active firewall profiles &#124; WinSe7en</dc:creator>
		<pubDate>Wed, 11 Mar 2009 15:04:11 +0000</pubDate>
		<guid isPermaLink="false">http://4sysops.com/?p=2509#comment-125015</guid>
		<description>[...] networks at once time and enforce the proper firewall settings on each. See the original post at: 4sysops - Windows 7 multiple active firewall profiles        Tags: Firewall Categories: WebLinks  Views: 1 views   Posted By: Joe Last Edit: 11 Mar 2009 [...]</description>
		<content:encoded><![CDATA[<p>[...] networks at once time and enforce the proper firewall settings on each. See the original post at: 4sysops &#8211; Windows 7 multiple active firewall profiles        Tags: Firewall Categories: WebLinks  Views: 1 views   Posted By: Joe Last Edit: 11 Mar 2009 [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
