<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
>

<channel>
	<title>Path Security &#187; In Progress</title>
	<atom:link href="http://www.pathsecurity.com/category/research/inprogress/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pathsecurity.com</link>
	<description>Security is a Journey, not a destination.</description>
	<lastBuildDate>Fri, 18 Jun 2010 21:43:27 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<!-- podcast_generator="podPress/8.8" - maintenance_release="8.8.4" -->
		<copyright>Copyright &#xA9; 2010 Path Security </copyright>
		<managingEditor>Webmaster@pathsecurity.com ()</managingEditor>
		<webMaster>Webmaster@pathsecurity.com ()</webMaster>
		<category>posts</category>
		<itunes:keywords></itunes:keywords>
		<itunes:subtitle></itunes:subtitle>
		<itunes:summary>Security is a Journey, not a destination.</itunes:summary>
		<itunes:author></itunes:author>
		<itunes:category text="Society &amp; Culture"/>
		<itunes:owner>
			<itunes:name></itunes:name>
			<itunes:email>Webmaster@pathsecurity.com</itunes:email>
		</itunes:owner>
		<itunes:block>No</itunes:block>
		<itunes:explicit>no</itunes:explicit>
		<itunes:image href="http://www.pathsecurity.com/wp-content/plugins/podpress/images/powered_by_podpress_large.jpg" />
		<image>
			<url>http://www.pathsecurity.com/wp-content/plugins/podpress/images/powered_by_podpress.jpg</url>
			<title>Path Security</title>
			<link>http://www.pathsecurity.com</link>
			<width>144</width>
			<height>144</height>
		</image>
		<item>
		<title>Portable Power: Fun with SD Cards</title>
		<link>http://www.pathsecurity.com/2009/06/portable-power/</link>
		<comments>http://www.pathsecurity.com/2009/06/portable-power/#comments</comments>
		<pubDate>Fri, 12 Jun 2009 23:10:02 +0000</pubDate>
		<dc:creator>Richard E. Baker</dc:creator>
				<category><![CDATA[In Progress]]></category>
		<category><![CDATA[Research]]></category>
		<category><![CDATA[Updates]]></category>

		<guid isPermaLink="false">http://www.pathsecurity.com/?p=197</guid>
		<description><![CDATA[I have been reading a support article by Apple about the SD slot on the new MacBook Pro&#8217;s (LINK), and I think I have come up with an excellent way to use it.
Most netbooks feature a SD card slot that can be booted from&#8230; why not load an OS onto the SD card that is [...]]]></description>
			<content:encoded><![CDATA[<p>I have been reading a support article by Apple about the SD slot on the new MacBook Pro&#8217;s (<a href="http://support.apple.com/kb/HT3553">LINK</a>), and I think I have come up with an excellent way to use it.</p>
<p>Most netbooks feature a SD card slot that can be booted from&#8230; why not load an OS onto the SD card that is tweaked for both the boot camp/fusion/parallels environment and the native netbook.  Then you can take the netbook for IR and such&#8230; collect your data&#8230; and then easily come back to a more powerful rig for analysis.  </p>
<p>Also with the ease of swapping SD cards you can keep different responses separate and cataloged for future review&#8230;</p>
<p>Its all just floating in my head&#8230; but more will come of this&#8230;</p>
<p>Let me know what you think in the comments.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.pathsecurity.com/2009/06/portable-power/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Degrees of Vulnerability</title>
		<link>http://www.pathsecurity.com/2009/06/degrees-of-vulnerability/</link>
		<comments>http://www.pathsecurity.com/2009/06/degrees-of-vulnerability/#comments</comments>
		<pubDate>Wed, 03 Jun 2009 07:47:17 +0000</pubDate>
		<dc:creator>Richard E. Baker</dc:creator>
				<category><![CDATA[In Progress]]></category>
		<category><![CDATA[Research]]></category>

		<guid isPermaLink="false">http://www.pathsecurity.com/?p=176</guid>
		<description><![CDATA[The Path to Information Security sometimes seems like the road to hell.  Security is not something that has a completely flat path.  There are layers, not like the desirable parfait, but like an onion.  Like the hell that Dante discribed at each layer lives an even worth threat, a worse sin committed. [...]]]></description>
			<content:encoded><![CDATA[<p>The Path to Information Security sometimes seems like the road to hell.  Security is not something that has a completely flat path.  There are layers, not like the desirable parfait, but like an onion.  Like the hell that Dante <a href="http://www.wsu.edu/~alake/the_circles_of_hell.htm">discribed</a> at each layer lives an even worth threat, a worse sin committed.  </p>
<p>Threats and vulnerabilities do not seem to be categorized the same way.  LOW, MEDIUM, HIGH&#8230; RED, YELLOW, GREEN&#8230; It doesn&#8217;t mean anything.  Threats should be categorized and ranked based on the ease of exploit, the level of automation available, and the ease of remediation.</p>
<p>And thats where HELL comes in&#8230;<br />
<img src="http://www.wsu.edu/~alake/Upper%20Hell.jpg" width="346" height="370" alt="The rings of HELL" /><br />
Nine Levels with the center being the dreaded 0-day&#8230; with limbo or level 1 populated by 100% automated attacks&#8230; things &#8220;script kiddies&#8221; use and should always be plugged because its super easy.  Each level gets harder.  Each level of attack requires a increasing level of skill to accomplish, but can also have a higher degree of remediation.  I propose such a scale due to the complaints Ive seen, and heard about some testers ignoring &#8220;script kiddie&#8221; stuff, or claiming &#8220;you don&#8217;t test for that, because anyone can do it&#8221;&#8230; But thats the point&#8230; If any one can do it you need to fix it first, you need to fix it faster, and then you get to move onto the &#8220;l33t&#8221; hacks.  30 minutes to hack with a super &#8220;l33t&#8221; 0-day or 5 minutes with a script&#8230; </p>
<p>Its Up to us the InfoSec community to make these issues meaningful to the suits and systems admins we work with.  Its our JOB to do the basic&#8217;s, because there are plenty of people who will try the basic&#8217;s on us.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.pathsecurity.com/2009/06/degrees-of-vulnerability/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
