<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2enclosuresfull.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss 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:media="http://search.yahoo.com/mrss/" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">

<channel>
	<title>securitystreams.tv</title>
	
	<link>http://securitystreams.tv</link>
	<description>securitystreams.tv</description>
	<lastBuildDate>Sun, 18 Oct 2009 04:30:51 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/securitystreamstv" /><feedburner:info uri="securitystreamstv" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><media:thumbnail url="http://securitystreams.tv/images/securitystreams.png" /><media:keywords>security,hacking,information,security</media:keywords><media:category scheme="http://www.itunes.com/dtds/podcast-1.0.dtd">Technology</media:category><itunes:owner><itunes:email>contact@securitystreams.tv</itunes:email></itunes:owner><itunes:explicit>no</itunes:explicit><itunes:image href="http://securitystreams.tv/images/securitystreams.png" /><itunes:keywords>security,hacking,information,security</itunes:keywords><itunes:subtitle>Cutting edge information security presentations in high quality video</itunes:subtitle><itunes:summary>securitystreams.tv brings information security presentations, in high quality video, to you.</itunes:summary><itunes:category text="Technology" /><item>
		<title>REST for the Wicked</title>
		<link>http://feedproxy.google.com/~r/securitystreamstv/~3/Uj_hEvU-Q48/</link>
		<comments>http://securitystreams.tv/talks/rest-for-the-wicked/#comments</comments>
		<pubDate>Tue, 15 Sep 2009 00:09:59 +0000</pubDate>
		<dc:creator>contact@securitystreams.tv</dc:creator>
				<category><![CDATA[Application Security]]></category>
		<category><![CDATA[Featured]]></category>
		<category><![CDATA[JSON]]></category>
		<category><![CDATA[REST]]></category>
		<category><![CDATA[XSRF]]></category>
		<category><![CDATA[XSS]]></category>

		<guid isPermaLink="false">http://securitystreams.tv/?p=34</guid>
		<description><![CDATA[REST can be especially susceptible to attacks like Cross-Site Request Forgery and JavaScript Hijacking; and worse, the usual remediation tactics that developers use to defend their apps against these attacks do not apply to REST services. In this presentation, Bryan Sullivan will demonstrate threats facing RESTful web services, myth-bust commonly proposed defense techniques, and provide appropriate development practices for defending REST.]]></description>
			<content:encoded><![CDATA[<p>Let&#8217;s face it: SOAP sucks. Especially when it comes to Web 2.0 applications. 										Many high-profile web sites have come to this same conclusion: Amazon, MySpace, 										Yahoo, and others are abandoning SOAP in favor of REST. REST (Representational 										State Transfer), and particularly REST used in combination with JSON, is faster, 										more scalable, and easier to implement than SOAP. But, do all these benefits 										come at the cost of security?</p>
<p>REST can be especially susceptible to attacks like Cross-Site Request 										Forgery and JavaScript Hijacking; and worse, the usual remediation tactics that 										developers use to defend their apps against these attacks do not apply to REST 										services. In this presentation, I will demonstrate threats facing RESTful web 										services, myth-bust commonly proposed defense techniques, and provide 										appropriate development practices for defending REST.</p>
]]></content:encoded>
			<wfw:commentRss>http://securitystreams.tv/talks/rest-for-the-wicked/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>

		<media:content url="http://feedproxy.google.com/~r/securitystreamstv/~5/JAPgIrV3jZc/bryan-sullivan-rest-for-the-wicked_dvd.mp4" type="video/mp4" /><itunes:explicit>no</itunes:explicit><itunes:subtitle>REST can be especially susceptible to attacks like Cross-Site Request Forgery and JavaScript Hijacking; and worse, the usual remediation tactics that developers use to defend their apps against these attacks do not apply to REST services. In this presenta</itunes:subtitle><itunes:summary>REST can be especially susceptible to attacks like Cross-Site Request Forgery and JavaScript Hijacking; and worse, the usual remediation tactics that developers use to defend their apps against these attacks do not apply to REST services. In this presentation, Bryan Sullivan will demonstrate threats facing RESTful web services, myth-bust commonly proposed defense techniques, and provide appropriate development practices for defending REST.</itunes:summary><itunes:keywords>security,hacking,information,security</itunes:keywords><feedburner:origLink>http://securitystreams.tv/talks/rest-for-the-wicked/</feedburner:origLink><enclosure url="http://feedproxy.google.com/~r/securitystreamstv/~5/JAPgIrV3jZc/bryan-sullivan-rest-for-the-wicked_dvd.mp4" length="0" type="video/mp4" /><feedburner:origEnclosureLink>http://cdn.videos.wordpress.com/rLQeMUBK/bryan-sullivan-rest-for-the-wicked_dvd.mp4</feedburner:origEnclosureLink></item>
		<item>
		<title>Defensive Rewriting</title>
		<link>http://feedproxy.google.com/~r/securitystreamstv/~3/QFH0lZutpB4/</link>
		<comments>http://securitystreams.tv/talks/defensive-rewriting/#comments</comments>
		<pubDate>Sun, 13 Sep 2009 19:39:06 +0000</pubDate>
		<dc:creator>contact@securitystreams.tv</dc:creator>
				<category><![CDATA[Application Security]]></category>
		<category><![CDATA[Featured]]></category>
		<category><![CDATA[XSRF]]></category>
		<category><![CDATA[XSS]]></category>

		<guid isPermaLink="false">http://securitystreams.tv/?p=31</guid>
		<description><![CDATA[Attacks like cross-site scripting (XSS), cross-site request forgery (XSRF), and open-redirect phishing are routinely propagated through malicious hyperlinks sent in e-mail messages. We could mitigate much of the risk of these vulnerabilities by frequently changing our URLs, not once every 200 years like Tim Berners-Lee suggests, but once every 10 minutes. Attackers would no longer be able to exploit application vulnerabilities by mass e-mailing poisoned hyperlinks because the links would be broken and invalid by the time the messages reached their intended victims.]]></description>
			<content:encoded><![CDATA[<p>Attacks like cross-site scripting (XSS), cross-site request forgery (XSRF), and open-redirect phishing are routinely propagated through malicious hyperlinks sent in e-mail messages. We could mitigate much of the risk of these vulnerabilities by frequently changing our URLs, not once every 200 years like Tim Berners-Lee suggests, but once every 10 minutes. Attackers would no longer be able to exploit application vulnerabilities by mass e-mailing poisoned hyperlinks because the links would be broken and invalid by the time the messages reached their intended victims.</p>
<p>This presentation will explore the possibilities of using various forms of URL rewriting techniques as defensive measures against XSS, XSRF and any other known or 0-day attack methods that use email as a propagation vector. I will release source and binaries for an ASP.NET rewriting module and will demonstrate source/pseudocode to accomplish the same functionality for other platforms.</p>
]]></content:encoded>
			<wfw:commentRss>http://securitystreams.tv/talks/defensive-rewriting/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>

		<media:content url="http://feedproxy.google.com/~r/securitystreamstv/~5/zulT0oPQAGY/bryan-sullivan-defensive-rewriting_dvd.mp4" type="video/mp4" /><itunes:explicit>no</itunes:explicit><itunes:subtitle>Attacks like cross-site scripting (XSS), cross-site request forgery (XSRF), and open-redirect phishing are routinely propagated through malicious hyperlinks sent in e-mail messages. We could mitigate much of the risk of these vulnerabilities by frequently</itunes:subtitle><itunes:summary>Attacks like cross-site scripting (XSS), cross-site request forgery (XSRF), and open-redirect phishing are routinely propagated through malicious hyperlinks sent in e-mail messages. We could mitigate much of the risk of these vulnerabilities by frequently changing our URLs, not once every 200 years like Tim Berners-Lee suggests, but once every 10 minutes. Attackers would no longer be able to exploit application vulnerabilities by mass e-mailing poisoned hyperlinks because the links would be broken and invalid by the time the messages reached their intended victims.</itunes:summary><itunes:keywords>security,hacking,information,security</itunes:keywords><feedburner:origLink>http://securitystreams.tv/talks/defensive-rewriting/</feedburner:origLink><enclosure url="http://feedproxy.google.com/~r/securitystreamstv/~5/zulT0oPQAGY/bryan-sullivan-defensive-rewriting_dvd.mp4" length="0" type="video/mp4" /><feedburner:origEnclosureLink>http://cdn.videos.wordpress.com/RmSdyF6A/bryan-sullivan-defensive-rewriting_dvd.mp4</feedburner:origEnclosureLink></item>
		<item>
		<title>OWASP Top 10</title>
		<link>http://feedproxy.google.com/~r/securitystreamstv/~3/LdAF9Xm9vxU/</link>
		<comments>http://securitystreams.tv/talks/owasp-top-10/#comments</comments>
		<pubDate>Fri, 11 Sep 2009 23:02:14 +0000</pubDate>
		<dc:creator>contact@securitystreams.tv</dc:creator>
				<category><![CDATA[Application Security]]></category>
		<category><![CDATA[OWASP]]></category>
		<category><![CDATA[SSL]]></category>
		<category><![CDATA[XSRF]]></category>
		<category><![CDATA[XSS]]></category>

		<guid isPermaLink="false">http://securitystreams.tv/?p=27</guid>
		<description><![CDATA[The purpose of this presentation is to discuss the OWASP Top 10 2007 list of common vulnerabilities so that organizations are able to have insights into these issues in order to understand potential consequences.]]></description>
			<content:encoded><![CDATA[<p>The purpose of this presentation is to discuss the OWASP Top 10 2007 list of common vulnerabilities so that organizations are able to have insights into these issues in order to understand potential consequences.</p>
]]></content:encoded>
			<wfw:commentRss>http://securitystreams.tv/talks/owasp-top-10/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>

		<media:content url="http://feedproxy.google.com/~r/securitystreamstv/~5/la8xXdBW4gI/brett-hardin-owasp-top-10-2007_dvd.mp4" type="video/mp4" /><itunes:explicit>no</itunes:explicit><itunes:subtitle>The purpose of this presentation is to discuss the OWASP Top 10 2007 list of common vulnerabilities so that organizations are able to have insights into these issues in order to understand potential consequences.</itunes:subtitle><itunes:summary>The purpose of this presentation is to discuss the OWASP Top 10 2007 list of common vulnerabilities so that organizations are able to have insights into these issues in order to understand potential consequences.</itunes:summary><itunes:keywords>security,hacking,information,security</itunes:keywords><feedburner:origLink>http://securitystreams.tv/talks/owasp-top-10/</feedburner:origLink><enclosure url="http://feedproxy.google.com/~r/securitystreamstv/~5/la8xXdBW4gI/brett-hardin-owasp-top-10-2007_dvd.mp4" length="0" type="video/mp4" /><feedburner:origEnclosureLink>http://cdn.videos.wordpress.com/k1P9IAx8/brett-hardin-owasp-top-10-2007_dvd.mp4</feedburner:origEnclosureLink></item>
		<item>
		<title>OWASP Top 10 [Executive Briefing]</title>
		<link>http://feedproxy.google.com/~r/securitystreamstv/~3/6J8fLZYbe2U/</link>
		<comments>http://securitystreams.tv/talks/owasp-top-10-executive-briefing/#comments</comments>
		<pubDate>Tue, 08 Sep 2009 07:50:48 +0000</pubDate>
		<dc:creator>contact@securitystreams.tv</dc:creator>
				<category><![CDATA[Application Security]]></category>
		<category><![CDATA[Executive Briefing]]></category>
		<category><![CDATA[OWASP]]></category>
		<category><![CDATA[SSL]]></category>
		<category><![CDATA[XSRF]]></category>
		<category><![CDATA[XSS]]></category>

		<guid isPermaLink="false">http://securitystreams.tv/?p=18</guid>
		<description><![CDATA[The purpose of this presentation is to discuss the OWASP Top 10 2007 list of common vulnerabilities so that organizations are able to have insights into these issues in order to understand potential consequences.]]></description>
			<content:encoded><![CDATA[<p>The purpose of this presentation is to discuss the OWASP Top 10 2007 list of common vulnerabilities so that organizations are able to have insights into these issues in order to understand potential consequences.</p>
]]></content:encoded>
			<wfw:commentRss>http://securitystreams.tv/talks/owasp-top-10-executive-briefing/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>

		<media:content url="http://feedproxy.google.com/~r/securitystreamstv/~5/KH659jFS9lA/brett-hardin-owasp-top-10-2007-executive-briefing_dvd.mp4" type="video/mp4" /><itunes:explicit>no</itunes:explicit><itunes:subtitle>The purpose of this presentation is to discuss the OWASP Top 10 2007 list of common vulnerabilities so that organizations are able to have insights into these issues in order to understand potential consequences.</itunes:subtitle><itunes:summary>The purpose of this presentation is to discuss the OWASP Top 10 2007 list of common vulnerabilities so that organizations are able to have insights into these issues in order to understand potential consequences.</itunes:summary><itunes:keywords>security,hacking,information,security</itunes:keywords><feedburner:origLink>http://securitystreams.tv/talks/owasp-top-10-executive-briefing/</feedburner:origLink><enclosure url="http://feedproxy.google.com/~r/securitystreamstv/~5/KH659jFS9lA/brett-hardin-owasp-top-10-2007-executive-briefing_dvd.mp4" length="0" type="video/mp4" /><feedburner:origEnclosureLink>http://cdn.videos.wordpress.com/pXTHzz0d/brett-hardin-owasp-top-10-2007-executive-briefing_dvd.mp4</feedburner:origEnclosureLink></item>
		<item>
		<title>Cross Domain Leakiness [Executive Briefing]</title>
		<link>http://feedproxy.google.com/~r/securitystreamstv/~3/LqPqn8g6XRc/</link>
		<comments>http://securitystreams.tv/talks/cross-domain-leakiness-executive-briefing/#comments</comments>
		<pubDate>Tue, 08 Sep 2009 07:28:27 +0000</pubDate>
		<dc:creator>contact@securitystreams.tv</dc:creator>
				<category><![CDATA[Executive Briefing]]></category>
		<category><![CDATA[browsers]]></category>
		<category><![CDATA[SSL]]></category>
		<category><![CDATA[XSRF]]></category>
		<category><![CDATA[XSS]]></category>

		<guid isPermaLink="false">http://securitystreams.tv/?p=15</guid>
		<description><![CDATA[In this presentation, we’ll see that cross-domain issues are still relatively common in browsers. The cross-domain issues can be split into two groups. First, there are out-and-out bugs that can be fixed relatively easily. These bugs tend to be in the less common cross-domain functional areas, and are often introduced with new cross-domain capable features. Interesting examples of such bugs will be discussed, and some new examples released. Secondly, there are cross-domain leakages resulting from how browsers generally work by design or intent. These are unfortunately hard to fix without breaking things, and the regrettable consequence is often that web app developers have to beware of an increasing list of dangers. We will look at some new pitfalls here in the areas of cross-domain CSS, scripting and cookie handling. Finally, there will be an interesting diversion that takes “sidejacking” to the max — looking at what you really can do if you are an active man-in-the-middle attacker looking to attack a victim who is carefully using only SSL sessions.]]></description>
			<content:encoded><![CDATA[<p>In this presentation, we’ll see that cross-domain issues are still relatively common in browsers. The cross-domain issues can be split into two groups. First, there are out-and-out bugs that can be fixed relatively easily. These bugs tend to be in the less common cross-domain functional areas, and are often introduced with new cross-domain capable features. Interesting examples of such bugs will be discussed, and some new examples released.</p>
<p>Secondly, there are cross-domain leakages resulting from how browsers generally work by design or intent. These are unfortunately hard to fix without breaking things, and the regrettable consequence is often that web app developers have to beware of an increasing list of dangers. We will look at some new pitfalls here in the areas of cross-domain CSS, scripting and cookie handling.</p>
<p>Finally, there will be an interesting diversion that takes “sidejacking” to the max — looking at what you really can do if you are an active man-in-the-middle attacker looking to attack a victim who is carefully using only SSL sessions.</p>
]]></content:encoded>
			<wfw:commentRss>http://securitystreams.tv/talks/cross-domain-leakiness-executive-briefing/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>

		<media:content url="http://feedproxy.google.com/~r/securitystreamstv/~5/KgQlpxblEwI/billy-rios-cross-domain-leakage-executive-briefing_dvd.mp4" type="video/mp4" /><itunes:explicit>no</itunes:explicit><itunes:subtitle>In this presentation, we’ll see that cross-domain issues are still relatively common in browsers. The cross-domain issues can be split into two groups. First, there are out-and-out bugs that can be fixed relatively easily. These bugs tend to be in the les</itunes:subtitle><itunes:summary>In this presentation, we’ll see that cross-domain issues are still relatively common in browsers. The cross-domain issues can be split into two groups. First, there are out-and-out bugs that can be fixed relatively easily. These bugs tend to be in the less common cross-domain functional areas, and are often introduced with new cross-domain capable features. Interesting examples of such bugs will be discussed, and some new examples released. Secondly, there are cross-domain leakages resulting from how browsers generally work by design or intent. These are unfortunately hard to fix without breaking things, and the regrettable consequence is often that web app developers have to beware of an increasing list of dangers. We will look at some new pitfalls here in the areas of cross-domain CSS, scripting and cookie handling. Finally, there will be an interesting diversion that takes “sidejacking” to the max — looking at what you really can do if you are an active man-in-the-middle attacker looking to attack a victim who is carefully using only SSL sessions.</itunes:summary><itunes:keywords>security,hacking,information,security</itunes:keywords><feedburner:origLink>http://securitystreams.tv/talks/cross-domain-leakiness-executive-briefing/</feedburner:origLink><enclosure url="http://feedproxy.google.com/~r/securitystreamstv/~5/KgQlpxblEwI/billy-rios-cross-domain-leakage-executive-briefing_dvd.mp4" length="0" type="video/mp4" /><feedburner:origEnclosureLink>http://cdn.videos.wordpress.com/5mGcdkis/billy-rios-cross-domain-leakage-executive-briefing_dvd.mp4</feedburner:origEnclosureLink></item>
		<item>
		<title>Cross Domain Leakiness</title>
		<link>http://feedproxy.google.com/~r/securitystreamstv/~3/2PJihmVTWc4/</link>
		<comments>http://securitystreams.tv/talks/cross-domain-leakiness/#comments</comments>
		<pubDate>Tue, 08 Sep 2009 06:57:52 +0000</pubDate>
		<dc:creator>contact@securitystreams.tv</dc:creator>
				<category><![CDATA[Application Security]]></category>
		<category><![CDATA[Featured]]></category>
		<category><![CDATA[browsers]]></category>
		<category><![CDATA[SSL]]></category>

		<guid isPermaLink="false">http://securitystreams.tv/?p=3</guid>
		<description><![CDATA[In this presentation, we’ll see that cross-domain issues are still relatively common in browsers. The cross-domain issues can be split into two groups. First, there are out-and-out bugs that can be fixed relatively easily. These bugs tend to be in the less common cross-domain functional areas, and are often introduced with new cross-domain capable features. Interesting examples of such bugs will be discussed, and some new examples released. Secondly, there are cross-domain leakages resulting from how browsers generally work by design or intent. These are unfortunately hard to fix without breaking things, and the regrettable consequence is often that web app developers have to beware of an increasing list of dangers. We will look at some new pitfalls here in the areas of cross-domain CSS, scripting and cookie handling. Finally, there will be an interesting diversion that takes “sidejacking” to the max — looking at what you really can do if you are an active man-in-the-middle attacker looking to attack a victim who is carefully using only SSL sessions.]]></description>
			<content:encoded><![CDATA[<p>In this presentation, we’ll see that cross-domain issues are still relatively common in browsers. The cross-domain issues can be split into two groups. First, there are out-and-out bugs that can be fixed relatively easily. These bugs tend to be in the less common cross-domain functional areas, and are often introduced with new cross-domain capable features. Interesting examples of such bugs will be discussed, and some new examples released.</p>
<p>Secondly, there are cross-domain leakages resulting from how browsers generally work by design or intent. These are unfortunately hard to fix without breaking things, and the regrettable consequence is often that web app developers have to beware of an increasing list of dangers. We will look at some new pitfalls here in the areas of cross-domain CSS, scripting and cookie handling.</p>
<p>Finally, there will be an interesting diversion that takes “sidejacking” to the max — looking at what you really can do if you are an active man-in-the-middle attacker looking to attack a victim who is carefully using only SSL sessions.</p>
]]></content:encoded>
			<wfw:commentRss>http://securitystreams.tv/talks/cross-domain-leakiness/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>

		<media:content url="http://feedproxy.google.com/~r/securitystreamstv/~5/S08Q3k3E4x8/billy-rios-cross-domain-leakage_dvd.mp4" type="video/mp4" /><itunes:explicit>no</itunes:explicit><itunes:subtitle>In this presentation, we’ll see that cross-domain issues are still relatively common in browsers. The cross-domain issues can be split into two groups. First, there are out-and-out bugs that can be fixed relatively easily. These bugs tend to be in the les</itunes:subtitle><itunes:summary>In this presentation, we’ll see that cross-domain issues are still relatively common in browsers. The cross-domain issues can be split into two groups. First, there are out-and-out bugs that can be fixed relatively easily. These bugs tend to be in the less common cross-domain functional areas, and are often introduced with new cross-domain capable features. Interesting examples of such bugs will be discussed, and some new examples released. Secondly, there are cross-domain leakages resulting from how browsers generally work by design or intent. These are unfortunately hard to fix without breaking things, and the regrettable consequence is often that web app developers have to beware of an increasing list of dangers. We will look at some new pitfalls here in the areas of cross-domain CSS, scripting and cookie handling. Finally, there will be an interesting diversion that takes “sidejacking” to the max — looking at what you really can do if you are an active man-in-the-middle attacker looking to attack a victim who is carefully using only SSL sessions.</itunes:summary><itunes:keywords>security,hacking,information,security</itunes:keywords><feedburner:origLink>http://securitystreams.tv/talks/cross-domain-leakiness/</feedburner:origLink><enclosure url="http://feedproxy.google.com/~r/securitystreamstv/~5/S08Q3k3E4x8/billy-rios-cross-domain-leakage_dvd.mp4" length="0" type="video/mp4" /><feedburner:origEnclosureLink>http://cdn.videos.wordpress.com/WigPXbD2/billy-rios-cross-domain-leakage_dvd.mp4</feedburner:origEnclosureLink></item>
	<media:rating>nonadult</media:rating><media:description type="plain">Cutting edge information security presentations in high quality video</media:description></channel>
</rss>

