<?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/"
		xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: Network Disruptions: VNC and TCP Port 5405</title>
	<atom:link href="http://ddos.arbornetworks.com/2007/07/network-disruptions-vnc-and-tcp-port-5405/feed/" rel="self" type="application/rss+xml" />
	<link>http://ddos.arbornetworks.com/2007/07/network-disruptions-vnc-and-tcp-port-5405/</link>
	<description>A weblog dedicated to educating the community on security threats that matter</description>
	<lastBuildDate>Sun, 29 Jan 2012 02:23:23 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: Carl</title>
		<link>http://ddos.arbornetworks.com/2007/07/network-disruptions-vnc-and-tcp-port-5405/comment-page-1/#comment-33648</link>
		<dc:creator>Carl</dc:creator>
		<pubDate>Wed, 04 Jul 2007 03:23:44 +0000</pubDate>
		<guid isPermaLink="false">http://asert.arbornetworks.com/2007/07/network-disruptions-vnc-and-tcp-port-5405/#comment-33648</guid>
		<description>Hello Jose,

I was the author of the original report, which was released mid-afternoon GMT on 30 June, in the midst of the irregularities noticed over at the Internet Traffic Report.  The reason why I raised the question about what could be responsible was that there was nothing that we could see as being responsible for such a significant lengthy deviation (compared to the normal traffic deviation of 3-4 hours).

I suggested 5901 as a possible (note the use of the word possible) cause, given the Top 10 ISC trend, and the availability of a full remote code execution exploit a few days prior.  I wasn&#039;t convinced that it was the cause, given that Europe and the US were effectively left out of the traffic deviation.

I have read many of the comments that this has generated across the net and wrote a quick summary (http://www.beskerming.com/commentary/2007/07/04/200/A_Quick_Update_on_Global_Internet_Traffic_Observations) which indicates that there is no observed cause for the deviation, which has now effectively disappeared.  I am glad that ATLAS has shown its value in corroborating this information.

I am fully aware of the risks of over-reacting to spikes and dips, along with variation of traffic to various ports, but this seemed out of the ordinary, with no readily available cause.  The link to 5901 was more of a loose inference than a formal link.

Thanks for taking the time to respond to the issues raised in my report.</description>
		<content:encoded><![CDATA[<p>Hello Jose,</p>
<p>I was the author of the original report, which was released mid-afternoon GMT on 30 June, in the midst of the irregularities noticed over at the Internet Traffic Report.  The reason why I raised the question about what could be responsible was that there was nothing that we could see as being responsible for such a significant lengthy deviation (compared to the normal traffic deviation of 3-4 hours).</p>
<p>I suggested 5901 as a possible (note the use of the word possible) cause, given the Top 10 ISC trend, and the availability of a full remote code execution exploit a few days prior.  I wasn&#8217;t convinced that it was the cause, given that Europe and the US were effectively left out of the traffic deviation.</p>
<p>I have read many of the comments that this has generated across the net and wrote a quick summary (<a href="http://www.beskerming.com/commentary/2007/07/04/200/A_Quick_Update_on_Global_Internet_Traffic_Observations" rel="nofollow">http://www.beskerming.com/commentary/2007/07/04/200/A_Quick_Update_on_Global_Internet_Traffic_Observations</a>) which indicates that there is no observed cause for the deviation, which has now effectively disappeared.  I am glad that ATLAS has shown its value in corroborating this information.</p>
<p>I am fully aware of the risks of over-reacting to spikes and dips, along with variation of traffic to various ports, but this seemed out of the ordinary, with no readily available cause.  The link to 5901 was more of a loose inference than a formal link.</p>
<p>Thanks for taking the time to respond to the issues raised in my report.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

