<?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"
	>
<channel>
	<title>Comments on: SANS Top 20 Internet Security Attack Target List for 2006 includes VoIP for the first time</title>
	<atom:link href="http://voipsa.org/blog/2006/11/15/sans-top-20-internet-security-attack-target-list-for-2006-includes-voip-for-the-first-time/feed/" rel="self" type="application/rss+xml" />
	<link>http://voipsa.org/blog/2006/11/15/sans-top-20-internet-security-attack-target-list-for-2006-includes-voip-for-the-first-time/</link>
	<description>Collective thoughts and musings on the state of VoIP security today.</description>
	<pubDate>Thu, 07 Aug 2008 23:51:41 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Telecom,Security and P2P &#187; Blog Archive &#187; SANS Top 20 Internet Security Attack Target List for 2006 includes VoIP for the first time</title>
		<link>http://voipsa.org/blog/2006/11/15/sans-top-20-internet-security-attack-target-list-for-2006-includes-voip-for-the-first-time/#comment-16552</link>
		<dc:creator>Telecom,Security and P2P &#187; Blog Archive &#187; SANS Top 20 Internet Security Attack Target List for 2006 includes VoIP for the first time</dc:creator>
		<pubDate>Sun, 28 Jan 2007 15:44:58 +0000</pubDate>
		<guid isPermaLink="false">http://voipsa.org/blog/2006/11/15/sans-top-20-internet-security-attack-target-list-for-2006-includes-voip-for-the-first-time/#comment-16552</guid>
		<description>[...] See more comments and report at VoIPsa blog. [...]</description>
		<content:encoded><![CDATA[<p>[...] See more comments and report at VoIPsa blog. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: VoIP: Security Threat #5 -- Alec Saunders .LOG</title>
		<link>http://voipsa.org/blog/2006/11/15/sans-top-20-internet-security-attack-target-list-for-2006-includes-voip-for-the-first-time/#comment-5232</link>
		<dc:creator>VoIP: Security Threat #5 -- Alec Saunders .LOG</dc:creator>
		<pubDate>Thu, 16 Nov 2006 13:21:17 +0000</pubDate>
		<guid isPermaLink="false">http://voipsa.org/blog/2006/11/15/sans-top-20-internet-security-attack-target-list-for-2006-includes-voip-for-the-first-time/#comment-5232</guid>
		<description>[...] Dan York has written a lengthy post on how SANS (SysAdmin, Audit, Network, Security) Insitute has identified VoIP among their top 20 Internet Security Threats for 2006.Â  They&#8217;ve identified six major trends in Internet security attacks, and VoIP is one of them, primarily via vulnerabilities in systems like Asterisk and Cisco Call Manager.Â  [...]</description>
		<content:encoded><![CDATA[<p>[...] Dan York has written a lengthy post on how SANS (SysAdmin, Audit, Network, Security) Insitute has identified VoIP among their top 20 Internet Security Threats for 2006.Â  They&#8217;ve identified six major trends in Internet security attacks, and VoIP is one of them, primarily via vulnerabilities in systems like Asterisk and Cisco Call Manager.Â  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard</title>
		<link>http://voipsa.org/blog/2006/11/15/sans-top-20-internet-security-attack-target-list-for-2006-includes-voip-for-the-first-time/#comment-5189</link>
		<dc:creator>Richard</dc:creator>
		<pubDate>Thu, 16 Nov 2006 04:41:10 +0000</pubDate>
		<guid isPermaLink="false">http://voipsa.org/blog/2006/11/15/sans-top-20-internet-security-attack-target-list-for-2006-includes-voip-for-the-first-time/#comment-5189</guid>
		<description>This does help improve the awareness of security vulnerabilities and threats related to VoIP, for engineers, managers, vendors, users and etc.</description>
		<content:encoded><![CDATA[<p>This does help improve the awareness of security vulnerabilities and threats related to VoIP, for engineers, managers, vendors, users and etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SANS Top 20 Internet Security Attack Target List for 2006 includes VoIP for the first time &#171; Telecom, Security and P2P</title>
		<link>http://voipsa.org/blog/2006/11/15/sans-top-20-internet-security-attack-target-list-for-2006-includes-voip-for-the-first-time/#comment-5187</link>
		<dc:creator>SANS Top 20 Internet Security Attack Target List for 2006 includes VoIP for the first time &#171; Telecom, Security and P2P</dc:creator>
		<pubDate>Thu, 16 Nov 2006 04:34:44 +0000</pubDate>
		<guid isPermaLink="false">http://voipsa.org/blog/2006/11/15/sans-top-20-internet-security-attack-target-list-for-2006-includes-voip-for-the-first-time/#comment-5187</guid>
		<description>[...] See more comments and report at VoIPsa blog. [...]</description>
		<content:encoded><![CDATA[<p>[...] See more comments and report at VoIPsa blog. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shawn Merdinger</title>
		<link>http://voipsa.org/blog/2006/11/15/sans-top-20-internet-security-attack-target-list-for-2006-includes-voip-for-the-first-time/#comment-5124</link>
		<dc:creator>Shawn Merdinger</dc:creator>
		<pubDate>Wed, 15 Nov 2006 16:39:10 +0000</pubDate>
		<guid isPermaLink="false">http://voipsa.org/blog/2006/11/15/sans-top-20-internet-security-attack-target-list-for-2006-includes-voip-for-the-first-time/#comment-5124</guid>
		<description>I find it very interesting that SANS is now recommending folks run security tools like PROTOS against their VoIP products.  This could indicate the beginning of a new level of due diligence in IT shops.

One of many potential issues concerns the complexity of these fuzzing tools.  Aside from setup and running them correctly, there's also the very challenging aspects of determining *exactly* what the attack causing the problem actually was -- for example running these voip fuzzer testcases in different ways (forward, backward, random) can place a device under test in a strange one-off state.  An example of this is from the README in the J. Oquendo's recently released Asteroid SIP tool: http://www.infiltrated.net/asteroid/

"Anyhow, I have found that by sending a certain sequence of these packets, in a certain order, servers react differently. Sometimes it will
crash faster, sometimes more extensions are subscribe, etc, etc. I will not post any sequencing until vendors have patched their programs
against this lame attack but, I will release the packet samples I've been working with."

For those about to embark on this brave new world of customer-done QA, a "first run" of SIP tools I'd suggest running against your SIP device is the SIPSAK tool with some of the flooding options, the PROTOS SIP suite, the Asteroid suite, and ISIC (udpsic and tcpsic) against the SIP ports.</description>
		<content:encoded><![CDATA[<p>I find it very interesting that SANS is now recommending folks run security tools like PROTOS against their VoIP products.  This could indicate the beginning of a new level of due diligence in IT shops.</p>
<p>One of many potential issues concerns the complexity of these fuzzing tools.  Aside from setup and running them correctly, there&#8217;s also the very challenging aspects of determining *exactly* what the attack causing the problem actually was &#8212; for example running these voip fuzzer testcases in different ways (forward, backward, random) can place a device under test in a strange one-off state.  An example of this is from the README in the J. Oquendo&#8217;s recently released Asteroid SIP tool: <a href="http://www.infiltrated.net/asteroid/" rel="nofollow">http://www.infiltrated.net/asteroid/</a></p>
<p>&#8220;Anyhow, I have found that by sending a certain sequence of these packets, in a certain order, servers react differently. Sometimes it will<br />
crash faster, sometimes more extensions are subscribe, etc, etc. I will not post any sequencing until vendors have patched their programs<br />
against this lame attack but, I will release the packet samples I&#8217;ve been working with.&#8221;</p>
<p>For those about to embark on this brave new world of customer-done QA, a &#8220;first run&#8221; of SIP tools I&#8217;d suggest running against your SIP device is the SIPSAK tool with some of the flooding options, the PROTOS SIP suite, the Asteroid suite, and ISIC (udpsic and tcpsic) against the SIP ports.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
