ZDNet UK


Skip to Main Content

ZDNet.co.uk - Winner of Best Business Website 2007
  1. Home
  2. News
  3. Blogs
  4. Reviews
  5. Prices
  6. Resources
  7. Community
  8. My ZDNet

 

ZDNet UK RSS Feeds


IT Jobs

Security threats Toolkit

Virus writers need a new order

Leader ZDNet.co.uk

Published: 26 Nov 2004 13:30 GMT

  • Email
  • Trackback
  • Clip Link
  • Print friendly
  • Post Comment

It is with some trepidation that we report on the rise of the open-source virus. According to F-Secure's antivirus research team, open-source viruses can generate nearly as many variants in a day as the closed-source ones do in a month. This would seem to be a conclusive vindication for the benefits of open-source development -– freely available information leads to a vigorous and productive environment. Yet the closed viruses, such as Bagel and Mydoom, are much more effective. This suggests that the argument of the proprietary lobby -– closed software is higher quality -– has some weight.

These two observations are not necessarily at odds. After all, six hundred variants of the same code from a crowd of hackers are likely to be easy to recognise and filter en masse, while anyone with access to closed code is going to be motivated and able to make things significantly different for each release. Indeed, Sophos says that open-source variants are often caught by generic filters.

It's time for the virus writing community to listen to Microsoft, and do a proper TCO, time to market and deployment cost analysis. After all, what's the point of five hundred virus writers labouring for a month and only infecting twenty million computers, when one proprietary team of three can produce a virus in a week that hits fifty million? In terms of productivity, the latter approach is over a thousand times more effective. (These figures are entirely fictitious. Before committing to a strategy, we advise you to pay analysts to make up equivalent data professionally).

So open-source virus production is insecure, ineffective and more expensive in every way. The virus writers should immediately ban open source as a dangerous, cancerous distraction to their industry and institute a proper policy of IP management, backed up as necessary with legal sanctions and/or Ivan's Health & Safety Inspectorate. This is the only way to encourage innovation. Indeed, because the virus industry is comparatively small and self-contained, there is a good chance that it can evolve really effective techniques for controlling workers and data from which the wider world could profitably learn.

Without a proper structure of certification for skills, of course, even a well-drilled workforce will be ineffective. We suggest that concomitant with imposing controls on source code, the virus industry create a centralised qualification system with a well-defined career progression path. Promising youngsters can be pressed into a cadre while they are still open to correct ideas: an early start in the Viral Youth would provide a solid basis for the party -- sorry, industry -- leaders of the future.

The combination of discipline, proper structure and imposed motivation will revolutionise the virus world. Tomorrow could belong to them.

  • Email
  • Trackback
  • Clip Link
  • Print friendly Print with HP

Did you find this article useful?
18 out of 28 people found this useful


Full Talkback thread

0 comments


Company/Topic Alerts

Create a new alert from the list below:





Related Jobs

Analyst within Programme Control Services (PCS) part of Systems Integration & Technology Consulting-C37314

Academic Qualifications: Technical or science based degree courses are preferred (e.g.computer science and engineering) but we will accept an ...

Systems Support Engineer- London- 28k + bens

You will also minimise business risks associated with IT systems including downtime and viruses. The Systems Support Engineer will also maintain the ...

Graduate Opportunities in Technology

We recognise that your career aspirations and our business and technical environments are constantly changing; therefore we provide a broad portfolio ...

Sentry Posts Blog

Mobile Linux Better For Mobile Busines...

Mobile Linux Better For Mobile Business Apps? Author: Eric Everson, MyMobiSafe.com As mobile Linux is carving it’s footprint on the future of mobile application development, the... More

Post a comment

DWP downplays security breach

The Department for Work and Pensions (DWP) has admitted that some of its staff have been forwarding passwords with password protected material. An email that was leaked on the 'Dizzy... More

Post a comment

How many headshots does one chairperso...

We got a strange request last week from the head of PR from Russian security experts Kaspersky. It seems although the company was very happy with the interview we recently carried with... More

Post a comment

Featured Talkback

On the contrary, if vendors were forced to stand behind their products it should increase innovation. It would force more, and better , testing before hitting the sales floor, resulting in fewer updates and less downtime for the consumer. At present the EULA removes responsibility from the vendor, and moves it to the user, which is a step backward. Make the vendor responsibility for their code.

By: ator1940

Read full story:
RSA: Vendor liability may stifle innovation