<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
<title>VoIP and UC Security Blog</title>
<link>http://blog.tmcnet.com/voip-and-uc-security-blog/</link>
<description></description>
<dc:language>en-us</dc:language>
<dc:rights>Copyright 2013</dc:rights>
<dc:date>2008-11-18T15:12:43-05:00</dc:date>
<admin:generatorAgent rdf:resource="http://www.movabletype.org/?v=4.38" />
<sy:updatePeriod>hourly</sy:updatePeriod>
<sy:updateFrequency>1</sy:updateFrequency>
<sy:updateBase>2000-01-01T12:00+00:00</sy:updateBase>

<item>
<title>Hello, I am calling to tell you that you've been hacked</title>
<link>http://blog.tmcnet.com/voip-and-uc-security-blog/2008/11/hello_my_name_is_joe_doe_and_youve_been_hacked.html</link>
<guid isPermaLink="false">38361@http://blog.tmcnet.com/voip-and-uc-security-blog/</guid>
<description><![CDATA[When one year ago I looked at the long term VoIP and UC security trends I discovered that most of the VoIP security research and attention was devoted to the signaling protocols and their vulnerabilities. SIP, Skinny, UNIStim and H.323 are being fuzzed, reverse engineered, spoofed and dissected in hundreds of ways. In the process we discovered a lot of vulnerabilities, fixed most of them and made these protocols more secure. And that's a good thing. <br /><br />But I knew we were missing something. This something is another family of protocols (Real-time Transport Protocol (RTP) and its sister protocol Real-time Transport Control Protocol (RTCP). These protocols are used to carry actual content of voice calls, video or audio over IP networks.They have a few interesting properties that warrant closer look at them from the security point of view. <br /><br />First, they are ubiquitous. VoIP and UC vendors use different signaling protocols in their products - standard SIP and H.323 or proprietary Skinny and UNIStim. But all of them are using standard based RTP/RTCP to carry voice, video and audio. The list of common applications using RTP/RTCP is very long. Some of them are deployed in very large numbers: <a href="http://www.tmcnet.com/tmcnet/snapshots/snapshots.aspx?Company=Microsoft">Microsoft</a> Communicator, any VoIP softphones and hardphones,&#160; Live Windows Messenger, wireless VoIP and video clients and&#160; QuickTime. We are talking about hundreds of millions of end-points.<br /><br />Secondly, after signaling protocol establishes a connection between calling parties, in most cases RTP/RTCP is carried between endpoints in peer-to-peer mode thus bypassing PBX/Call Managers/softswitches.&#160; <br /><br />Thirdly, the ports used by RTP/RTCP are assigned dynamically during the signaling phase. <br /><br />Fourth, RTP is a binary protocol carrying information in real-time. Since VoIP and video are sensitive to delay, packet loss&#160; and jitter it is very difficult to analyze the content of RTP streams fast enough to not cause QoS to deteriorate. <br /><br />Let's put it all in the context of VoIP and UC security. I asked my research team to look closer at RTP and RTCP implementations. Well, now we know that RTP/RTCP implementations have security vulnerabilities, some of them very serious. It is quite feasible that some of the exploits could be used to create massive attacks on telecommunication and business infrastructure as a part of cyberwarfare or they could be used selectively to steal information and penetrate enterprise security through a simple phone call. <br /><br />Your laptop running a softphone could be taken over by someone simply calling you and exploiting a specific RTP vulnerability. And this attack could traverse PSTN networks. Even transferring sensitive data from inside of the enterprise is possible within the RTP streams. <br /><br />In most cases RTP works in the peer-to-peer mode bypassing any centralized applications and devices. In many organizations any peer-to-peer traffic is simply blocked but this is not possible if VoIP or UC infrastructure is implemented. <br /><br />And let's don't forget&#160; about SPAM over Internet Telephony (SPIT). It is basically an equivalent to email SPAM but with a twist. Anti-spam applications have full access to email headers and the content so they can analyze the entire message and make an appropriate decision in non real-time. While in the case of SPIT we can easily analyze the signaling protocols but it is almost impossible to do it for RTP streams. Imagine buffering a conversation, analyzing the speech against certain rules and keywords (not everyone in the world speaks English), making a decision and inserting the content back into the RTP stream. All that in real-time for thousands of conversations at the time.<br /><br />Securing RTP is our next challenge. Let's start working on it now.<br /><br /><br /><br /><br />]]><![CDATA[<p>
Tags: 
Related tags: <a href="http://blog.tmcnet.com/voip-and-uc-security-blog/tag/signaling protocols" title="signaling protocols" rel="tag">signaling protocols</a>, <a href="http://blog.tmcnet.com/voip-and-uc-security-blog/tag/skinny unistim" title="skinny unistim" rel="tag">skinny unistim</a>, <a href="http://blog.tmcnet.com/voip-and-uc-security-blog/tag/video audio" title="video audio" rel="tag">video audio</a>, <a href="http://blog.tmcnet.com/voip-and-uc-security-blog/tag/security" title="security" rel="tag">security</a>, <a href="http://blog.tmcnet.com/voip-and-uc-security-blog/tag/protocols" title="protocols" rel="tag">protocols</a>, <a href="http://blog.tmcnet.com/voip-and-uc-security-blog/tag/protocol" title="protocol" rel="tag">protocol</a>
<br><br>
<ul>

</ul>
<b>Related Entries</b>

 <a href="http://blog.tmcnet.com/voip-and-uc-security-blog/2008/11/hello_my_name_is_joe_doe_and_youve_been_hacked.html#trackback">TrackBacks</a>
 | <a href="http://blog.tmcnet.com/voip-and-uc-security-blog/2008/11/hello_my_name_is_joe_doe_and_youve_been_hacked.html#comments" title="Comment on: Hello, I am calling to tell you that you've been hacked">Comments</a> | <a href="http://del.icio.us/post?url=http://blog.tmcnet.com/voip-and-uc-security-blog/2008/11/hello_my_name_is_joe_doe_and_youve_been_hacked.html&title=Hello%2C%20I%20am%20calling%20to%20tell%20you%20that%20you%27ve%20been%20hacked">Tag with del.icio.us</a> | <a href="http://blog.tmcnet.com/voip-and-uc-security-blog/">VoIP and UC Security Blog Home</a> | Permalink: <a href="http://blog.tmcnet.com/voip-and-uc-security-blog/2008/11/hello_my_name_is_joe_doe_and_youve_been_hacked.html" title="Hello, I am calling to tell you that you've been hacked">Hello, I am calling to tell you that you've been hacked</a></p>
<!--end-->
Copyright <a href="http://blog.tmcnet.com/voip-and-uc-security-blog/">VoIP and UC Security Blog</a>

<p><map name="google_ad_map_081118151243">
<area shape="rect" href="http://imageads.googleadservices.com/pagead/imgclick/081118151243?pos=0" coords="1,2,367,28"/>
<area shape="rect" href="http://services.google.com/feedback/abg" coords="384,10,453,23"/></map>
<img usemap="#google_ad_map_081118151243" border="0" src="http://imageads.googleadservices.com/pagead/ads?format=468x30_aff_img&client=ca-pub-8317963745003590&channel=0771188340Call with FONcall™0771188340Connecting...Connected!Error: could not place callbug?&output=png&cuid=081118151243&amp;url=http%3A%2F%2Fblog.tmcnet.com%2Fvoip-and-uc-security-blog%2F2008%2F11%2Fhello_my_name_is_joe_doe_and_youve_been_hacked.html"/></p>]]></description>
<dc:subject>signaling protocols</dc:subject>
<dc:subject>skinny unistim</dc:subject>
<dc:subject>video audio</dc:subject>
<dc:subject>security</dc:subject>
<dc:subject>protocols</dc:subject>
<dc:subject>protocol</dc:subject>

<pubDate>Tue, 18 Nov 2008 15:12:43 -0500</pubDate>
<dc:date>2008-11-18T15:12:43-05:00</dc:date>

</item>

 

<item>
<title>VoIP and UC security - Is it important?</title>
<link>http://blog.tmcnet.com/voip-and-uc-security-blog/2008/11/voip_and_uc_security_-_whats_next.html</link>
<guid isPermaLink="false">38356@http://blog.tmcnet.com/voip-and-uc-security-blog/</guid>
<description><![CDATA[I've been involved in VoIP and UC security for a number of years now and lately, people have been asking me one simple question; "Why are VoIP and UC security not perceived as important as data network security?"&#160; <br /><br />Good question!<br /><br />Unfortunately there is no simple answer. First, given their emerging nature, there is a lack of knowledge and understanding of VoIP and UC technologies. It is true that VoIP or UC are new technologies that combine the old communication mediums such as voice and video with the newer networking technologies such as IP and 3G networks. For many years these two different worlds co-existed, rarely crossing well defined demarcation lines. Converged networks are changing all of this, but we know it is much easier to change technologies than it is to change people. The result is that we have IT folks that understand very well data networking and applications, but they are not really VoIP or UC experts. Then we have the telecommunications experts that could configure your entire PBX in no time, but their knowledge of IP networking and applications is fairly basic. Then we have the IT security professionals who know a great deal about how to secure data and IP networks, but securing a VoIP and UC network falls outside their area of expertise.<br /><br />VoIP and UC security have yet to be widely addressed from a regulatory compliance perspective, and as a result, many organizations do not include&#160; guidance relating to their framework and processes. Most of the organization have a strong framework and processes in place to deal with security issues for data networking and applications, but VoIP and UC are not yet part of this framework. <br /><br />Risk assessment and risk management practitioners have just started to focus on&#160; VoIP and UC security as demonstrated by the increasing number of firms including them as part of the risk assessment analysis they do for securing any IT infrastructure. There is recognition now that it is almost impossible to properly secure converged enterprise networks, including VoIP and UC, without a proper strategy that looks beyond the data centric model used in the past.<br /><br />Making the business case for VoIP and UC and coming up with an ROI is difficult. Adding requirements for proper security could make them unacceptable to business decision makers given the perceived extra costs. Also,&#160; VoIP and UC vendors are not interested in putting sales at risk so they either avoid talking about security entirely, or try and assure customers that their solutions are fully secure.<br /><br />I would think that&#160; IT security groups should be proactively implementing VoIP and UC security infrastructures using well known processes and methodologies developed and proven for data networks and applications. The reality, though, is that there are not very many VoIP or UC security incidents reported that have had a major impact on businesses besides a couple of toll fraud type attacks, PBX/Voice mail hacking and few SIP DoS attacks. A number of organizations, including my company, VoIPshield Systems, have published a number of VoIP and UC vulnerabilities that potentially could be used to attack the VoIP and UC infrastructure. <br /><br />I should note that perhaps the bottom line here is that there is not a significant enough level of "pain" in the market to elevate the importance of VoIP and UC security to the level similar to something like bank card fraud, or email security, etc.. As it's stands today, while VoIP and UC security are gaining in awareness and importance for future budgeting purposes, relatively few organizations have it as their number one priority for IT security related investments.<br /><br />Back the original question "Is VoIP and UC security important?" If history can be used to predict future, I think that we will start to see VoIP and UC security appear as part of the security mainstream when the number of "painful" events that disrupt business operations increases and causes measurable damage. When downtime, lost sales, information theft or negative influences on brand equity start to cause real financial loses, both mind share and budgets will focus more on VoIP and UC security risks. <br /> <br /><br /><br /><br />]]><![CDATA[<p>
Tags: <a href="http://blog.tmcnet.com/voip-and-uc-security-blog/tag/risk%20assessment" rel="tag">risk assessment</a>, <a href="http://blog.tmcnet.com/voip-and-uc-security-blog/tag/risk%20management" rel="tag">risk management</a>, <a href="http://blog.tmcnet.com/voip-and-uc-security-blog/tag/unified%20communications%20security" rel="tag">unified communications security</a>, <a href="http://blog.tmcnet.com/voip-and-uc-security-blog/tag/voip%20security" rel="tag">voip security</a>, <a href="http://blog.tmcnet.com/voip-and-uc-security-blog/tag/voipshield" rel="tag">voipshield</a>
Related tags: <a href="http://blog.tmcnet.com/voip-and-uc-security-blog/tag/networking applications" title="networking applications" rel="tag">networking applications</a>, <a href="http://blog.tmcnet.com/voip-and-uc-security-blog/tag/security important" title="security important" rel="tag">security important</a>, <a href="http://blog.tmcnet.com/voip-and-uc-security-blog/tag/framework processes" title="framework processes" rel="tag">framework processes</a>, <a href="http://blog.tmcnet.com/voip-and-uc-security-blog/tag/security" title="security" rel="tag">security</a>, <a href="http://blog.tmcnet.com/voip-and-uc-security-blog/tag/number" title="number" rel="tag">number</a>, <a href="http://blog.tmcnet.com/voip-and-uc-security-blog/tag/networks" title="networks" rel="tag">networks</a>
<br><br>
<ul>

</ul>

<b>Related Entries</b>

 <a href="http://blog.tmcnet.com/voip-and-uc-security-blog/2008/11/voip_and_uc_security_-_whats_next.html#trackback">TrackBacks</a>
 | <a href="http://blog.tmcnet.com/voip-and-uc-security-blog/2008/11/voip_and_uc_security_-_whats_next.html#comments" title="Comment on: VoIP and UC security - Is it important?">Comments</a> | <a href="http://del.icio.us/post?url=http://blog.tmcnet.com/voip-and-uc-security-blog/2008/11/voip_and_uc_security_-_whats_next.html&title=VoIP%20and%20UC%20security%20-%20Is%20it%20important%3F">Tag with del.icio.us</a> | <a href="http://blog.tmcnet.com/voip-and-uc-security-blog/">VoIP and UC Security Blog Home</a> | Permalink: <a href="http://blog.tmcnet.com/voip-and-uc-security-blog/2008/11/voip_and_uc_security_-_whats_next.html" title="VoIP and UC security - Is it important?">VoIP and UC security - Is it important?</a></p>
<!--end-->
Copyright <a href="http://blog.tmcnet.com/voip-and-uc-security-blog/">VoIP and UC Security Blog</a>


<p><map name="google_ad_map_081118095709">
<area shape="rect" href="http://imageads.googleadservices.com/pagead/imgclick/081118095709?pos=0" coords="1,2,367,28"/>
<area shape="rect" href="http://services.google.com/feedback/abg" coords="384,10,453,23"/></map>
<img usemap="#google_ad_map_081118095709" border="0" src="http://imageads.googleadservices.com/pagead/ads?format=468x30_aff_img&client=ca-pub-8317963745003590&channel=0771188340Call with FONcall™0771188340Connecting...Connected!Error: could not place callbug?&output=png&cuid=081118095709&amp;url=http%3A%2F%2Fblog.tmcnet.com%2Fvoip-and-uc-security-blog%2F2008%2F11%2Fvoip_and_uc_security_-_whats_next.html"/></p>]]></description>
<dc:subject>risk assessment</dc:subject>
<dc:subject>risk management</dc:subject>
<dc:subject>unified communications security</dc:subject>
<dc:subject>voip security</dc:subject>
<dc:subject>voipshield</dc:subject>
<dc:subject>networking applications</dc:subject>
<dc:subject>security important</dc:subject>
<dc:subject>framework processes</dc:subject>
<dc:subject>security</dc:subject>
<dc:subject>number</dc:subject>
<dc:subject>networks</dc:subject>

<pubDate>Tue, 18 Nov 2008 09:57:09 -0500</pubDate>
<dc:date>2008-11-18T09:57:09-05:00</dc:date>

</item>

</channel>
</rss>