Commentary

George Hulme
 

Network Solutions Hack Highlights Hosting Risks

Website hosting vendor Network Solutions Inc. (NSI) has been forced to cleanse its customer Websites after a few "thousand" sites where attacked after an unspecified number of NSI's shared servers were infiltrated.

Website hosting vendor Network Solutions Inc. (NSI) has been forced to cleanse its customer Websites after a few "thousand" sites where attacked after an unspecified number of NSI's shared servers were infiltrated.While NSI is still evaluating the damage, according to this story in Dark Reading, the company believes it has found the root of the problem, but isn't saying much more:

NSI's [Shashi] Bellamkonda in a blog post on Sunday said the company had been getting reports of malware spreading on customers' Websites. "At this time since anything we say in public may help the perpetrators, we are unable to provide details. It may not be accurate to categorize this as a single issue such as 'file permissions,'" he blogged.


More Security Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

This is the second revelation in a week of a hack of NSI's servers. Hundreds of NSI-hosted WordPress blogs were hit with malicious iframes that would automatically infect visitors to the blogsites, and in some cases, spread fake antivirus software. The attackers pilfered blogger credentials which had been stored in plain text in the WordPress database.

What we do know is that the bulk of the attacks against NSI employed iFrames, an all-too-easy and common attack technique today. At the end of the Dark Reading story, Eddie Swartz, CSO at NetWitness asks great question about who is responsible: the ISP or the end customer:

The hacks raise an issue increasingly being faced by Website owners: what's the responsibility of the ISP or service or cloud provider to provide more application-layer security, NetWitness' Schwartz says.

"If people are understanding that the adversaries are injecting iframes and JavaScript and other code and crimeware at the application layer, potentially on a massive scale, is there any responsibility on the part of the ISP or service provider?" he says. "You can't expect your customers to have the technical capability" to address this, he says.

He's right: one can't expect retail hosting customers to have the technical acumen to stop all of these types of attacks. And, while all of the details aren't out yet, if the attack is the result of NSI's shared servers being infiltrated: there's not much their customers could do to protect themselves anyway.

For my security and business observations throughout the day, find me on Twitter.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links