<?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: Security for Web Meetings?</title>
	<atom:link href="http://www.infosecpodcast.com/2008/06/security-for-web-meetings/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.infosecpodcast.com/2008/06/security-for-web-meetings/</link>
	<description>Information Security related news, opinions and ramblings</description>
	<lastBuildDate>Sun, 25 Jul 2010 08:44:08 -0600</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: John Kennedy</title>
		<link>http://www.infosecpodcast.com/2008/06/security-for-web-meetings/comment-page-1/#comment-28004</link>
		<dc:creator>John Kennedy</dc:creator>
		<pubDate>Mon, 14 Jul 2008 21:44:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.infosecpodcast.com/?p=174#comment-28004</guid>
		<description>Hi,

Happened to run across this post and just wanted to add that with GoToMeeting we utilize true end-to-end encryption between the participaring endpoints which provides fundamental protection against monitoring by Citrix Online.  Our communication servers are only routing opaque, encrypted packets.  If the session is recorded, it is recorded in the same encrypted format.  

This is in contrast to services such as WebEx that only use SSL on the links between endpoints and their data centers and decrypt-switch-then-reencrypt meeting data.
(Morale: all claims of &quot;end-to-end&quot; encryption are definitely not equal.)

For more details, checkout our security white paper: https://www1.gotomeeting.com/default/downloads/pdf/p/GoToMeeting%5fSecurity%5fWhite%5fPaper.pdf 

Regards,

-John Kennedy
Chief Security Architect
Citrix Online</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>Happened to run across this post and just wanted to add that with GoToMeeting we utilize true end-to-end encryption between the participaring endpoints which provides fundamental protection against monitoring by Citrix Online.  Our communication servers are only routing opaque, encrypted packets.  If the session is recorded, it is recorded in the same encrypted format.  </p>
<p>This is in contrast to services such as WebEx that only use SSL on the links between endpoints and their data centers and decrypt-switch-then-reencrypt meeting data.<br />
(Morale: all claims of &#8220;end-to-end&#8221; encryption are definitely not equal.)</p>
<p>For more details, checkout our security white paper: <a href="https://www1.gotomeeting.com/default/downloads/pdf/p/GoToMeeting%5fSecurity%5fWhite%5fPaper.pdf">https://www1.gotomeeting.com/default/downloads/pdf/p/GoToMeeting%5fSecurity%5fWhite%5fPaper.pdf</a> </p>
<p>Regards,</p>
<p>-John Kennedy<br />
Chief Security Architect<br />
Citrix Online</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Harrington</title>
		<link>http://www.infosecpodcast.com/2008/06/security-for-web-meetings/comment-page-1/#comment-27995</link>
		<dc:creator>Chris Harrington</dc:creator>
		<pubDate>Thu, 26 Jun 2008 03:29:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.infosecpodcast.com/?p=174#comment-27995</guid>
		<description>Thanks Roger. I definitely understand the dangers of any electronic communication. I used to wear that trench coat :) My reason for asking the question was to try and gauge the level of risk people are willing to accept in dealing with these technologies. 

The bigger concern for me is the ability for participants to share desktops and give control of desktops as part of many web collaboration offerings.

Thanks!

--Chris</description>
		<content:encoded><![CDATA[<p>Thanks Roger. I definitely understand the dangers of any electronic communication. I used to wear that trench coat <img src='http://www.infosecpodcast.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  My reason for asking the question was to try and gauge the level of risk people are willing to accept in dealing with these technologies. </p>
<p>The bigger concern for me is the ability for participants to share desktops and give control of desktops as part of many web collaboration offerings.</p>
<p>Thanks!</p>
<p>&#8211;Chris</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roger Courville</title>
		<link>http://www.infosecpodcast.com/2008/06/security-for-web-meetings/comment-page-1/#comment-27994</link>
		<dc:creator>Roger Courville</dc:creator>
		<pubDate>Thu, 26 Jun 2008 03:09:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.infosecpodcast.com/?p=174#comment-27994</guid>
		<description>If you have a conference call, how secure is it?  Can AT&amp;T or Verizon listen in?  If so, is it overt or covert?  Is the conference call recorded on their servers?  Is there any audit trail?

Answer those questions, and you&#039;ll have a general idea of how transmitting web data is no different than transmitting audio data.  Different providers do accomplish it in different ways, so if it&#039;s a concern, we should include those questions in our RFPs.

I might suggest a better question would be &quot;What data in your organization would you want protected to what degree?&quot;  

Don&#039;t hold a public web seminar if you don&#039;t want a competitor to figure out how to attend.  Don&#039;t have a telephone call (or web meeting) if you don&#039;t want to have a chance that someone, legally or illegally, could figure out how to listen in.  

Arguably web data being encrypted is significantly more secure...  Live, private web communications are arguably as secure as the same on a telephone - it&#039;s just a different appliance.  Governance - if that&#039;s your concern - should be no different.  

If you want to have really private communications, don&#039;t send a letter, make a telephone call, or trust a courier.  Meet the recipient in an unused part of a large local park and speak in code...  wearing a trenchcoat of course :-)  !

Good questions ;-)

Roger Courville
1080 Group, LLC
roger@1080group.com</description>
		<content:encoded><![CDATA[<p>If you have a conference call, how secure is it?  Can AT&amp;T or Verizon listen in?  If so, is it overt or covert?  Is the conference call recorded on their servers?  Is there any audit trail?</p>
<p>Answer those questions, and you&#8217;ll have a general idea of how transmitting web data is no different than transmitting audio data.  Different providers do accomplish it in different ways, so if it&#8217;s a concern, we should include those questions in our RFPs.</p>
<p>I might suggest a better question would be &#8220;What data in your organization would you want protected to what degree?&#8221;  </p>
<p>Don&#8217;t hold a public web seminar if you don&#8217;t want a competitor to figure out how to attend.  Don&#8217;t have a telephone call (or web meeting) if you don&#8217;t want to have a chance that someone, legally or illegally, could figure out how to listen in.  </p>
<p>Arguably web data being encrypted is significantly more secure&#8230;  Live, private web communications are arguably as secure as the same on a telephone &#8211; it&#8217;s just a different appliance.  Governance &#8211; if that&#8217;s your concern &#8211; should be no different.  </p>
<p>If you want to have really private communications, don&#8217;t send a letter, make a telephone call, or trust a courier.  Meet the recipient in an unused part of a large local park and speak in code&#8230;  wearing a trenchcoat of course <img src='http://www.infosecpodcast.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' />   !</p>
<p>Good questions <img src='http://www.infosecpodcast.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
<p>Roger Courville<br />
1080 Group, LLC<br />
<a href="mailto:roger@1080group.com">roger@1080group.com</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
