<?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/"
		>
<channel>
	<title>Comments on: A Firewall Quiz</title>
	<atom:link href="http://spiresecurity.com/?feed=rss2&#038;p=270" rel="self" type="application/rss+xml" />
	<link>http://spiresecurity.com/?p=270</link>
	<description>Risk and Cybersecurity Analysis</description>
	<lastBuildDate>Wed, 21 Aug 2013 23:28:51 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: afshin lamei</title>
		<link>http://spiresecurity.com/?p=270&#038;cpage=1#comment-373</link>
		<dc:creator>afshin lamei</dc:creator>
		<pubDate>Thu, 11 Oct 2007 09:51:29 +0000</pubDate>
		<guid isPermaLink="false">http://spiresecurity.com/blog/?p=270#comment-373</guid>
		<description><![CDATA[A firewall with a single &quot;allow any&quot; can increase the security if we assume that it is an stateful firewall and &quot;allow any&quot; means from internal network to external. Because there is not any other assumption , such as logging or Intrusion detection capability, we can say that from the internal network point of view, it is more secure. also we must notice that any firewall  is a single point of failure, specially when working in router (non-transparent) mode.
]]></description>
		<content:encoded><![CDATA[<p>A firewall with a single &#8220;allow any&#8221; can increase the security if we assume that it is an stateful firewall and &#8220;allow any&#8221; means from internal network to external. Because there is not any other assumption , such as logging or Intrusion detection capability, we can say that from the internal network point of view, it is more secure. also we must notice that any firewall  is a single point of failure, specially when working in router (non-transparent) mode.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kraigus</title>
		<link>http://spiresecurity.com/?p=270&#038;cpage=1#comment-372</link>
		<dc:creator>kraigus</dc:creator>
		<pubDate>Thu, 27 Sep 2007 11:59:54 +0000</pubDate>
		<guid isPermaLink="false">http://spiresecurity.com/blog/?p=270#comment-372</guid>
		<description><![CDATA[No worries.  :)
]]></description>
		<content:encoded><![CDATA[<p>No worries.  <img src='http://spiresecurity.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kraigus</title>
		<link>http://spiresecurity.com/?p=270&#038;cpage=1#comment-371</link>
		<dc:creator>kraigus</dc:creator>
		<pubDate>Wed, 26 Sep 2007 00:01:27 +0000</pubDate>
		<guid isPermaLink="false">http://spiresecurity.com/blog/?p=270#comment-371</guid>
		<description><![CDATA[a - if it&#039;s one or the other, then it&#039;s less.  As others have said, you&#039;re increasing your attack surface with no extra gain.

Extra credit 1 - makes no difference.  Labels are meaningless; if your firewall protects people then it protects them, if it doesn&#039;t, it doesn&#039;t.  People are going to do stupid things, regardless of whether or not they know they have a firewall.

Extra credit 2 - the schools your kids go to may not teach arithmetic like they used to, but how about the rules of punctuation?  :-)
]]></description>
		<content:encoded><![CDATA[<p>a &#8211; if it&#8217;s one or the other, then it&#8217;s less.  As others have said, you&#8217;re increasing your attack surface with no extra gain.</p>
<p>Extra credit 1 &#8211; makes no difference.  Labels are meaningless; if your firewall protects people then it protects them, if it doesn&#8217;t, it doesn&#8217;t.  People are going to do stupid things, regardless of whether or not they know they have a firewall.</p>
<p>Extra credit 2 &#8211; the schools your kids go to may not teach arithmetic like they used to, but how about the rules of punctuation?  <img src='http://spiresecurity.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Weber</title>
		<link>http://spiresecurity.com/?p=270&#038;cpage=1#comment-370</link>
		<dc:creator>Dan Weber</dc:creator>
		<pubDate>Tue, 25 Sep 2007 14:25:42 +0000</pubDate>
		<guid isPermaLink="false">http://spiresecurity.com/blog/?p=270#comment-370</guid>
		<description><![CDATA[*First question:*

This device can lower your security, if either:

a) the users/operators assume that the network is now protected

b) the device has its own vulnerabilities, giving attackers a new potential launching pad.

I&#039;m not sure you can assume &#039;a&#039;, if everyone knows that the device has no rules.

I&#039;m not sure &#039;b&#039; applies, either, if you say that vulnerabilities are only the result of rules.  That&#039;s probably not accurate, but we&#039;re making up suppositions so why not?

*Bonus question:*

Well, &quot;firewall&quot; is merely a label that describes where you are going to make your stand.  Could be the network, could be the host, could be the CPU, could be the hard drive.

But, as I said in &#039;1a&#039;, if users/operators think &quot;there&#039;s a firewall&quot; they could unfairly decrease their risk assessment of the local network.

]]></description>
		<content:encoded><![CDATA[<p>*First question:*</p>
<p>This device can lower your security, if either:</p>
<p>a) the users/operators assume that the network is now protected</p>
<p>b) the device has its own vulnerabilities, giving attackers a new potential launching pad.</p>
<p>I&#8217;m not sure you can assume &#8216;a&#8217;, if everyone knows that the device has no rules.</p>
<p>I&#8217;m not sure &#8216;b&#8217; applies, either, if you say that vulnerabilities are only the result of rules.  That&#8217;s probably not accurate, but we&#8217;re making up suppositions so why not?</p>
<p>*Bonus question:*</p>
<p>Well, &#8220;firewall&#8221; is merely a label that describes where you are going to make your stand.  Could be the network, could be the host, could be the CPU, could be the hard drive.</p>
<p>But, as I said in &#8217;1a&#8217;, if users/operators think &#8220;there&#8217;s a firewall&#8221; they could unfairly decrease their risk assessment of the local network.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Clint Laskowski</title>
		<link>http://spiresecurity.com/?p=270&#038;cpage=1#comment-369</link>
		<dc:creator>Clint Laskowski</dc:creator>
		<pubDate>Tue, 25 Sep 2007 13:54:22 +0000</pubDate>
		<guid isPermaLink="false">http://spiresecurity.com/blog/?p=270#comment-369</guid>
		<description><![CDATA[Okay, I&#039;ll post my answers:

My first reaction was to say that the fireall (with a single &quot;allow any&quot; rule an no NAT) would still make the network more secure because it would provide some logging which might be useful as a detective control. But, assuming logging is a result of a rule, it appears there would be no logging (since there are no other rules). So, I&#039;d say it would (c) have no impact on the security of the environment.

As to the extra credit question, I would say the label &quot;firewall&quot; makes no difference on the security impact of a device with firewall-like capabilities. Then again, a device that resolves to a network name of something like &quot;firewall.victim.com&quot; might scare some attackers away because they&#039;d think victim.com must have some defenses in place if they have a firewall; at the same time, it might invite more aggressive attackers interested in the challenge of defeating the firewall.

Okay, how&#039;d I do?
]]></description>
		<content:encoded><![CDATA[<p>Okay, I&#8217;ll post my answers:</p>
<p>My first reaction was to say that the fireall (with a single &#8220;allow any&#8221; rule an no NAT) would still make the network more secure because it would provide some logging which might be useful as a detective control. But, assuming logging is a result of a rule, it appears there would be no logging (since there are no other rules). So, I&#8217;d say it would (c) have no impact on the security of the environment.</p>
<p>As to the extra credit question, I would say the label &#8220;firewall&#8221; makes no difference on the security impact of a device with firewall-like capabilities. Then again, a device that resolves to a network name of something like &#8220;firewall.victim.com&#8221; might scare some attackers away because they&#8217;d think victim.com must have some defenses in place if they have a firewall; at the same time, it might invite more aggressive attackers interested in the challenge of defeating the firewall.</p>
<p>Okay, how&#8217;d I do?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
