<?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: Tips from the Abuse Department: Part 2 &#8211; Responding to Abuse Reports</title>
	<atom:link href="http://blog.softlayer.com/2012/tips-from-the-abuse-department-part-2-responding-to-abuse-reports/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.softlayer.com/2012/tips-from-the-abuse-department-part-2-responding-to-abuse-reports/</link>
	<description>A Behind the Scenes Look at the Best Hosting Provider in the World</description>
	<lastBuildDate>Fri, 24 May 2013 11:59:58 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.1</generator>
	<item>
		<title>By: Franklin</title>
		<link>http://blog.softlayer.com/2012/tips-from-the-abuse-department-part-2-responding-to-abuse-reports/comment-page-1/#comment-46862</link>
		<dc:creator>Franklin</dc:creator>
		<pubDate>Wed, 06 Mar 2013 21:20:22 +0000</pubDate>
		<guid isPermaLink="false">http://blog.softlayer.com/?p=8471#comment-46862</guid>
		<description>That&#039;s a fair point. The fact that some complaints are not acted on quickly doesn&#039;t mean that all complaints are, or that they always will be. 

I am particularly sensitive to malware and phish issues because too often it seems to me that large service providers are so apathetic, understaffed, or both that they end up complicit in criminal behavior. The worst example of that I&#039;ve ever encountered is a company called iPower Web. A few years ago, I discovered that a large number of sites hosted on their servers had been compromised through a gaping hole in their homebrewed Web control panel, and were being used to spread the W32/Zlob malware. Not only did they fail to take action against hacked sites, and leave the malware droppers in place, it took about sixteen months(!) for them to fix the security vulnerability...by which point more than 200,000 sites on their servers(!!) had been hacked and recruited to spread malware.

I&#039;m not saying that Softlayer is anywhere near as bad, of course. That&#039;s simply an example of the sort of intractability and indifference I deal with almost every day, and I tend to be particularly upset by service providers who allow malware and phish sites to linger on their servers for extended periods of time. I don&#039;t think that iPower was actually acting with malice, but past a certain point any sufficiently advanced incompetence is indistinguishable from malice. Either way, it still benefits organized crime to the detriment of people who use the Internet.

I&#039;m glad to see that you&#039;re willing to escalate problems like this, and that you seem to be proactive about dealing with this kind of abuse on your network.</description>
		<content:encoded><![CDATA[<p>That&#8217;s a fair point. The fact that some complaints are not acted on quickly doesn&#8217;t mean that all complaints are, or that they always will be. </p>
<p>I am particularly sensitive to malware and phish issues because too often it seems to me that large service providers are so apathetic, understaffed, or both that they end up complicit in criminal behavior. The worst example of that I&#8217;ve ever encountered is a company called iPower Web. A few years ago, I discovered that a large number of sites hosted on their servers had been compromised through a gaping hole in their homebrewed Web control panel, and were being used to spread the W32/Zlob malware. Not only did they fail to take action against hacked sites, and leave the malware droppers in place, it took about sixteen months(!) for them to fix the security vulnerability&#8230;by which point more than 200,000 sites on their servers(!!) had been hacked and recruited to spread malware.</p>
<p>I&#8217;m not saying that Softlayer is anywhere near as bad, of course. That&#8217;s simply an example of the sort of intractability and indifference I deal with almost every day, and I tend to be particularly upset by service providers who allow malware and phish sites to linger on their servers for extended periods of time. I don&#8217;t think that iPower was actually acting with malice, but past a certain point any sufficiently advanced incompetence is indistinguishable from malice. Either way, it still benefits organized crime to the detriment of people who use the Internet.</p>
<p>I&#8217;m glad to see that you&#8217;re willing to escalate problems like this, and that you seem to be proactive about dealing with this kind of abuse on your network.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Hazard</title>
		<link>http://blog.softlayer.com/2012/tips-from-the-abuse-department-part-2-responding-to-abuse-reports/comment-page-1/#comment-46861</link>
		<dc:creator>Kevin Hazard</dc:creator>
		<pubDate>Wed, 06 Mar 2013 16:15:04 +0000</pubDate>
		<guid isPermaLink="false">http://blog.softlayer.com/?p=8471#comment-46861</guid>
		<description>The concern is understandable. The challenge is that you&#039;re talking generally about the lack of abuse response (or delay in abuse response) based on specific example(s?) you&#039;ve reported. If you can forward the examples to our social media team, we can escalate them to the abuse department managers to look into why &lt;em&gt;those reports&lt;/em&gt; weren&#039;t handled quickly, and if we need to make changes to the way we prioritize or filter abuse messages, we&#039;re much better equipped to do so.

It&#039;s good to have an open dialogue about the most efficient ways to handle abuse, but it&#039;s difficult to continue the conversation when the primary concerns seem to be based on the sweeping generalization that SoftLayer abuse &lt;strong&gt;is&lt;/strong&gt; slow in general because SoftLayer abuse &lt;strong&gt;was&lt;/strong&gt; slow on specific occasions. To a certain extent, that position is based on confirmation bias.</description>
		<content:encoded><![CDATA[<p>The concern is understandable. The challenge is that you&#8217;re talking generally about the lack of abuse response (or delay in abuse response) based on specific example(s?) you&#8217;ve reported. If you can forward the examples to our social media team, we can escalate them to the abuse department managers to look into why <em>those reports</em> weren&#8217;t handled quickly, and if we need to make changes to the way we prioritize or filter abuse messages, we&#8217;re much better equipped to do so.</p>
<p>It&#8217;s good to have an open dialogue about the most efficient ways to handle abuse, but it&#8217;s difficult to continue the conversation when the primary concerns seem to be based on the sweeping generalization that SoftLayer abuse <strong>is</strong> slow in general because SoftLayer abuse <strong>was</strong> slow on specific occasions. To a certain extent, that position is based on confirmation bias.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Franklin</title>
		<link>http://blog.softlayer.com/2012/tips-from-the-abuse-department-part-2-responding-to-abuse-reports/comment-page-1/#comment-46847</link>
		<dc:creator>Franklin</dc:creator>
		<pubDate>Wed, 06 Mar 2013 00:29:24 +0000</pubDate>
		<guid isPermaLink="false">http://blog.softlayer.com/?p=8471#comment-46847</guid>
		<description>&quot;SoftLayer does not manage the content on our servers, and we have a team of representatives dedicated to investigating and taking action on abuse complaints when they are submitted.&quot;

I would expect the team of representatives to be quicker about dealing with abuse complaints, particularly with regard to phish and malware dropper sites. Leaving a bank phish or a ZeroAccess dropper active for days or weeks is bad policy. I don&#039;t know why you&#039;re so slow--whether it&#039;s a question of policy or procedure or simply understaffing--but when, say, a bank phish is active on your network for a week, you&#039;re potentially exposing many people to fraud. I&#039;m sure the criminals responsible for these kinds of abuse appreciate it.

&quot;In what way would you suggest we monitor the activity on a site that’s hosted by a customer of a customer of one of our customers?&quot;

Not monitoring activity on such sites is one thing. Not responding to abuse complaints in a timely fashion is another. Other large hosting providers who deal with many layers of resellers and customers don&#039;t move so slowly, so it&#039;s possible.

Look, I know the kinds of volumes of email that abuse addresses get. I know the numbers of sites we&#039;re talking about. I know how hard (read: impossible) it is for end users to be educated to update their vulnerable copies of WordPress and Joomla. But if it takes weeks to respond to abuse complaints, something&#039;s wrong.</description>
		<content:encoded><![CDATA[<p>&#8220;SoftLayer does not manage the content on our servers, and we have a team of representatives dedicated to investigating and taking action on abuse complaints when they are submitted.&#8221;</p>
<p>I would expect the team of representatives to be quicker about dealing with abuse complaints, particularly with regard to phish and malware dropper sites. Leaving a bank phish or a ZeroAccess dropper active for days or weeks is bad policy. I don&#8217;t know why you&#8217;re so slow&#8211;whether it&#8217;s a question of policy or procedure or simply understaffing&#8211;but when, say, a bank phish is active on your network for a week, you&#8217;re potentially exposing many people to fraud. I&#8217;m sure the criminals responsible for these kinds of abuse appreciate it.</p>
<p>&#8220;In what way would you suggest we monitor the activity on a site that’s hosted by a customer of a customer of one of our customers?&#8221;</p>
<p>Not monitoring activity on such sites is one thing. Not responding to abuse complaints in a timely fashion is another. Other large hosting providers who deal with many layers of resellers and customers don&#8217;t move so slowly, so it&#8217;s possible.</p>
<p>Look, I know the kinds of volumes of email that abuse addresses get. I know the numbers of sites we&#8217;re talking about. I know how hard (read: impossible) it is for end users to be educated to update their vulnerable copies of WordPress and Joomla. But if it takes weeks to respond to abuse complaints, something&#8217;s wrong.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Hazard</title>
		<link>http://blog.softlayer.com/2012/tips-from-the-abuse-department-part-2-responding-to-abuse-reports/comment-page-1/#comment-46844</link>
		<dc:creator>Kevin Hazard</dc:creator>
		<pubDate>Tue, 05 Mar 2013 23:29:06 +0000</pubDate>
		<guid isPermaLink="false">http://blog.softlayer.com/?p=8471#comment-46844</guid>
		<description>Interesting point, Franklin. Based on your experience, how would you &quot;secure&quot; SoftLayer&#039;s network of self-managed servers and cloud instances? SoftLayer does not manage the content on our servers, and we have a team of representatives dedicated to investigating and taking action on abuse complaints when they are submitted. 

In what way would you suggest we monitor the activity on a site that&#039;s hosted by a customer of a customer of one of our customers? When we receive a complaint, would you suggest we shut down our customer immediately if action isn&#039;t taken to stop the abusive behavior? If a reseller&#039;s shared hosting server houses a single spammer, would it be fair to the hundreds of other legitimate customers for us to disconnect the server when we get an abuse complaint about that single spammer? Or would you, as a customer of a hosting reseller, hope that we work with our customers (so that our customers can work with their customers) to get the abusive content removed?

As you&#039;ll note in several of the previous comments under this post, we&#039;re happy to help escalate concerns you feel have not been addressed in a timely manner. Just forward those abuse complaints to twitter@softlayer.com, and we&#039;ll look into them.</description>
		<content:encoded><![CDATA[<p>Interesting point, Franklin. Based on your experience, how would you &#8220;secure&#8221; SoftLayer&#8217;s network of self-managed servers and cloud instances? SoftLayer does not manage the content on our servers, and we have a team of representatives dedicated to investigating and taking action on abuse complaints when they are submitted. </p>
<p>In what way would you suggest we monitor the activity on a site that&#8217;s hosted by a customer of a customer of one of our customers? When we receive a complaint, would you suggest we shut down our customer immediately if action isn&#8217;t taken to stop the abusive behavior? If a reseller&#8217;s shared hosting server houses a single spammer, would it be fair to the hundreds of other legitimate customers for us to disconnect the server when we get an abuse complaint about that single spammer? Or would you, as a customer of a hosting reseller, hope that we work with our customers (so that our customers can work with their customers) to get the abusive content removed?</p>
<p>As you&#8217;ll note in several of the previous comments under this post, we&#8217;re happy to help escalate concerns you feel have not been addressed in a timely manner. Just forward those abuse complaints to <a href="mailto:twitter@softlayer.com">twitter@softlayer.com</a>, and we&#8217;ll look into them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Franklin</title>
		<link>http://blog.softlayer.com/2012/tips-from-the-abuse-department-part-2-responding-to-abuse-reports/comment-page-1/#comment-46842</link>
		<dc:creator>Franklin</dc:creator>
		<pubDate>Tue, 05 Mar 2013 22:10:42 +0000</pubDate>
		<guid isPermaLink="false">http://blog.softlayer.com/?p=8471#comment-46842</guid>
		<description>&quot;Best ISPs like *Bluehost*? omfg you’ve got to be kidding. I have had several clients on Bluehost and FTP has always been a nightmare.&quot;

I&#039;m talking about &quot;best hosts&quot; here in the context of hosts with the best response to spam and other issues, not with the best FTP. Bluehost consistently removes things like computer malware droppers and bank phish sites extremely quickly, typically within hours hours of an abuse complaint, rather than leaving them up for days or weeks.

&quot;This is great – your site is actually being hosted with websitewelcome, too, Franklin. Talk about the whole pot/kettle thing.&quot;

Websitewelcome is Hostgator. I use them in part because of their prompt attention to spam, malware, and phish complaints; they established an excellent track record of responding to these issues quickly before I ever started hosting with them.

Again, the issue here as I see it is that Softlayer is dismally poor at securing their network and in taking action to shut down phish and malware sites when notified of them, often leaving such sites active for days or even weeks. I find that indefensible.</description>
		<content:encoded><![CDATA[<p>&#8220;Best ISPs like *Bluehost*? omfg you’ve got to be kidding. I have had several clients on Bluehost and FTP has always been a nightmare.&#8221;</p>
<p>I&#8217;m talking about &#8220;best hosts&#8221; here in the context of hosts with the best response to spam and other issues, not with the best FTP. Bluehost consistently removes things like computer malware droppers and bank phish sites extremely quickly, typically within hours hours of an abuse complaint, rather than leaving them up for days or weeks.</p>
<p>&#8220;This is great – your site is actually being hosted with websitewelcome, too, Franklin. Talk about the whole pot/kettle thing.&#8221;</p>
<p>Websitewelcome is Hostgator. I use them in part because of their prompt attention to spam, malware, and phish complaints; they established an excellent track record of responding to these issues quickly before I ever started hosting with them.</p>
<p>Again, the issue here as I see it is that Softlayer is dismally poor at securing their network and in taking action to shut down phish and malware sites when notified of them, often leaving such sites active for days or even weeks. I find that indefensible.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shawn</title>
		<link>http://blog.softlayer.com/2012/tips-from-the-abuse-department-part-2-responding-to-abuse-reports/comment-page-1/#comment-46807</link>
		<dc:creator>Shawn</dc:creator>
		<pubDate>Fri, 01 Mar 2013 17:24:55 +0000</pubDate>
		<guid isPermaLink="false">http://blog.softlayer.com/?p=8471#comment-46807</guid>
		<description>This is great - your site is actually being hosted with websitewelcome, too, Franklin. Talk about the whole pot/kettle thing. I guess using the relationship you have with them already to help address the problem was lost on you?</description>
		<content:encoded><![CDATA[<p>This is great &#8211; your site is actually being hosted with websitewelcome, too, Franklin. Talk about the whole pot/kettle thing. I guess using the relationship you have with them already to help address the problem was lost on you?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shawn</title>
		<link>http://blog.softlayer.com/2012/tips-from-the-abuse-department-part-2-responding-to-abuse-reports/comment-page-1/#comment-46806</link>
		<dc:creator>Shawn</dc:creator>
		<pubDate>Fri, 01 Mar 2013 17:21:52 +0000</pubDate>
		<guid isPermaLink="false">http://blog.softlayer.com/?p=8471#comment-46806</guid>
		<description>Best ISPs like *Bluehost*? omfg you&#039;ve got to be kidding. I have had several clients on Bluehost and FTP has always been a nightmare. Just last month I had to fix a new clients site who was hosting with Bluehost. The site was only 380mb but even with the site disabled it took 17 **hours** on my 100MB connection to download it.

As far as the other sites you discuss, it would make a world of difference if you actually said whether you&#039;d reported them to the abuse dept. If not, then you&#039;re talking apples and oranges. More importantly, did you contact their actual provider (websitewelcome?). That ought to be included in your first step when reporting abuse.</description>
		<content:encoded><![CDATA[<p>Best ISPs like *Bluehost*? omfg you&#8217;ve got to be kidding. I have had several clients on Bluehost and FTP has always been a nightmare. Just last month I had to fix a new clients site who was hosting with Bluehost. The site was only 380mb but even with the site disabled it took 17 **hours** on my 100MB connection to download it.</p>
<p>As far as the other sites you discuss, it would make a world of difference if you actually said whether you&#8217;d reported them to the abuse dept. If not, then you&#8217;re talking apples and oranges. More importantly, did you contact their actual provider (websitewelcome?). That ought to be included in your first step when reporting abuse.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Franklin</title>
		<link>http://blog.softlayer.com/2012/tips-from-the-abuse-department-part-2-responding-to-abuse-reports/comment-page-1/#comment-46796</link>
		<dc:creator>Franklin</dc:creator>
		<pubDate>Wed, 27 Feb 2013 19:15:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.softlayer.com/?p=8471#comment-46796</guid>
		<description>You&#039;ll forgive me if I remain unconvinced. My experience with Softlayer continues to be quite poor; it seems to me that Softlayer is still incredibly slow to act on phish sites, malware droppers, and actively exploited servers, often leaving them up for days or weeks after being notified of the problem. 

For example, when the Web site datzwhatzup (dot) net was compromised, it was being used to spread the W32/ZeroAccess malware. A compromise of this type, like a phish page, should be a high priority. Yet the site remained infected and continued to spread the malware for more than a week(!) after Softlayer was notified of the problem.

To me, that is unconscionable. I realize that abuse teams are always understaffed because management sees the abuse teams as employees who cost money but don&#039;t generate revenue, but even so, to allow a serious security compromise that was actively being used to spread malware to remain on a server for a week or more is really, really bad. (By way of comparison, some of the best ISPs in the industry, such as Bluehost, will often take down phish sites and malware spreaders within an hour or two of being notified of the problem.)

It is also unfortunate that professional spam-for-hire outfits have taken up residence on Softlayer&#039;s network. For example, pushbuttonemailer (dot) com now lives on your network. This spam-for-hire site is advertised by means of link redirectors placed on other hacked sites. It plainly advertises spamming services and is spamming itself via a network of hacked sites, but has remained on Softlayer&#039;s network nonetheless, and in fact it seems like Softlayer is helping the spammer do listwashing.</description>
		<content:encoded><![CDATA[<p>You&#8217;ll forgive me if I remain unconvinced. My experience with Softlayer continues to be quite poor; it seems to me that Softlayer is still incredibly slow to act on phish sites, malware droppers, and actively exploited servers, often leaving them up for days or weeks after being notified of the problem. </p>
<p>For example, when the Web site datzwhatzup (dot) net was compromised, it was being used to spread the W32/ZeroAccess malware. A compromise of this type, like a phish page, should be a high priority. Yet the site remained infected and continued to spread the malware for more than a week(!) after Softlayer was notified of the problem.</p>
<p>To me, that is unconscionable. I realize that abuse teams are always understaffed because management sees the abuse teams as employees who cost money but don&#8217;t generate revenue, but even so, to allow a serious security compromise that was actively being used to spread malware to remain on a server for a week or more is really, really bad. (By way of comparison, some of the best ISPs in the industry, such as Bluehost, will often take down phish sites and malware spreaders within an hour or two of being notified of the problem.)</p>
<p>It is also unfortunate that professional spam-for-hire outfits have taken up residence on Softlayer&#8217;s network. For example, pushbuttonemailer (dot) com now lives on your network. This spam-for-hire site is advertised by means of link redirectors placed on other hacked sites. It plainly advertises spamming services and is spamming itself via a network of hacked sites, but has remained on Softlayer&#8217;s network nonetheless, and in fact it seems like Softlayer is helping the spammer do listwashing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Hazard</title>
		<link>http://blog.softlayer.com/2012/tips-from-the-abuse-department-part-2-responding-to-abuse-reports/comment-page-1/#comment-46792</link>
		<dc:creator>Kevin Hazard</dc:creator>
		<pubDate>Wed, 27 Feb 2013 15:00:57 +0000</pubDate>
		<guid isPermaLink="false">http://blog.softlayer.com/?p=8471#comment-46792</guid>
		<description>Hi Jamie, In Jennifer&#039;s previous post about &lt;a href=&quot;http://blog.softlayer.com/2012/tips-from-the-abuse-department-part-1-reporting-abuse/&quot; rel=&quot;nofollow&quot;&gt;reporting abuse&lt;/a&gt;, she explains, &quot;We work hard to investigate and resolve all complaints received however, due to volume, we typically do not respond to complaining parties.&quot; While you may not receive a response, that shouldn&#039;t suggest that we aren&#039;t taking action.

If the abusive activity persists, please feel free to forward the abuse report you submitted to abuse@softlayer.com to our social media team (twitter@softlayer.com), and we&#039;ll see if there&#039;s anything we can do to help.</description>
		<content:encoded><![CDATA[<p>Hi Jamie, In Jennifer&#8217;s previous post about <a href="http://blog.softlayer.com/2012/tips-from-the-abuse-department-part-1-reporting-abuse/" rel="nofollow">reporting abuse</a>, she explains, &#8220;We work hard to investigate and resolve all complaints received however, due to volume, we typically do not respond to complaining parties.&#8221; While you may not receive a response, that shouldn&#8217;t suggest that we aren&#8217;t taking action.</p>
<p>If the abusive activity persists, please feel free to forward the abuse report you submitted to <a href="mailto:abuse@softlayer.com">abuse@softlayer.com</a> to our social media team (twitter@softlayer.com), and we&#8217;ll see if there&#8217;s anything we can do to help.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jamie</title>
		<link>http://blog.softlayer.com/2012/tips-from-the-abuse-department-part-2-responding-to-abuse-reports/comment-page-1/#comment-46749</link>
		<dc:creator>Jamie</dc:creator>
		<pubDate>Tue, 26 Feb 2013 14:48:23 +0000</pubDate>
		<guid isPermaLink="false">http://blog.softlayer.com/?p=8471#comment-46749</guid>
		<description>Hi Softlayer, I appreciate you addressing this topic with a blog post- I have posted an abuse report with your team from one of your hosted websites, this is the second time now, because of spam and I hope to hear back from someone soon.</description>
		<content:encoded><![CDATA[<p>Hi Softlayer, I appreciate you addressing this topic with a blog post- I have posted an abuse report with your team from one of your hosted websites, this is the second time now, because of spam and I hope to hear back from someone soon.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
