<?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: Leveraging Varying Level of Assurance</title>
	<atom:link href="http://nosheep.net/story/leveraging-varying-level-of-assurance/feed/" rel="self" type="application/rss+xml" />
	<link>http://nosheep.net/story/leveraging-varying-level-of-assurance/</link>
	<description>Comic book guy, tech geek, and father of two...</description>
	<lastBuildDate>Thu, 09 Feb 2012 02:58:30 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
	<item>
		<title>By: zbtirrell</title>
		<link>http://nosheep.net/story/leveraging-varying-level-of-assurance/comment-page-1/#comment-1370</link>
		<dc:creator>zbtirrell</dc:creator>
		<pubDate>Fri, 10 Mar 2006 01:51:49 +0000</pubDate>
		<guid isPermaLink="false">http://nosheep.net/story/leveraging-varying-level-of-assurance/#comment-1370</guid>
		<description>It is also important to note how much people always want us to increase the timeout.  In an all or nothing situation, as you put it, making a change like that is a huge sacrifice in security.  Even now they way we have it, 60 minutes, it&#039;s probably a bit to long for a lot of the apps I&#039;d put in Level 4.</description>
		<content:encoded><![CDATA[<p>It is also important to note how much people always want us to increase the timeout.  In an all or nothing situation, as you put it, making a change like that is a huge sacrifice in security.  Even now they way we have it, 60 minutes, it&#8217;s probably a bit to long for a lot of the apps I&#8217;d put in Level 4.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon</title>
		<link>http://nosheep.net/story/leveraging-varying-level-of-assurance/comment-page-1/#comment-1369</link>
		<dc:creator>Jon</dc:creator>
		<pubDate>Fri, 10 Mar 2006 01:30:27 +0000</pubDate>
		<guid isPermaLink="false">http://nosheep.net/story/leveraging-varying-level-of-assurance/#comment-1369</guid>
		<description>It makes sense to have the broadest level (lowest LOA) to be 0.  That makes it more clear.

There will be many people who will see this as making things &lt;em&gt;less secure&lt;/em&gt; but I think it&#039;s important to notice how this makes things &lt;strong&gt;more secure&lt;/strong&gt;.

In an all-or-nothing security paradigm, if you just want to check your &quot;cartoon of the day&quot; you must log in.  If you walk away leaving yourself logged in you have exposed &lt;em&gt;all&lt;/em&gt; your access.

Alternately, if your &quot;cartoon of the day&quot; is considered a Level 1 service, you can look at your cartoon and walk away without logging out you have only exposed a very basic level of access.

Every time we add another service to our portal we have this consideration, so we warn people, keep timeouts low, and take the complaints.</description>
		<content:encoded><![CDATA[<p>It makes sense to have the broadest level (lowest LOA) to be 0.  That makes it more clear.</p>
<p>There will be many people who will see this as making things <em>less secure</em> but I think it&#8217;s important to notice how this makes things <strong>more secure</strong>.</p>
<p>In an all-or-nothing security paradigm, if you just want to check your &#8220;cartoon of the day&#8221; you must log in.  If you walk away leaving yourself logged in you have exposed <em>all</em> your access.</p>
<p>Alternately, if your &#8220;cartoon of the day&#8221; is considered a Level 1 service, you can look at your cartoon and walk away without logging out you have only exposed a very basic level of access.</p>
<p>Every time we add another service to our portal we have this consideration, so we warn people, keep timeouts low, and take the complaints.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

