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

Court case shines light on security ethics

Dan Ilet ZDNet.co.uk

Published: 13 Jan 2005 13:45 GMT

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

The legal action currently being brought by French software company Tegam International against Guillaume Tena, who claimed to have found flaws in its software, has sparked a debate on how the reporting of security vulnerabilities should be handled.

Software companies already face an uphill battle providing good quality patches as fast as possible. But researchers who publish vulnerabilities without informing the software firm beforehand could be making this task harder. This can give hackers a longer lead time to work on an exploit, experts warned on Wednesday

"This is a controversial subject," said Richard Starnes, president of the Information Systems Security Association UK. "The general feeling among the industry is that vulnerability researchers should report problems to the company first and wait a reasonable amount of time before deciding whether to release it or not. The question is how long 'a reasonable amount of time' is."

Patches can be difficult to develop and often take between three and six months to perfect, Starnes said. And there can be backlogs of old vulnerabilities that need to be developed. But this doesn't always sit well with researchers who often like to see immediate results.

"It's about self-gratification for researchers," said Jason Hart, head of security for Whitehat UK. "Companies need to act upon independent researchers' findings. But sometimes researchers give two fingers and say 'your baby's ugly, your software's got holes in it'. No one likes being told their baby is ugly, so they don't take notice. There needs to be a better process."

But while Thomas Kristensen, chief technical officer of Secunia, a Danish company that publishes vulnerabilities, agreed with Starnes and Hart, he also believes that sometimes it is necessary for researchers to disclose vulnerabilities without delay. He said it was better that the public was informed than left ignorant.

"While it's unfortunate when vulnerability details are published without a proper solution from the vendor, it's my opinion that everyone is better off," said Kristensen. "System administrators and private users can reconfigure their systems or discontinue the use of the vulnerable product. Hopefully, this results in the vendor responding in a proper manner in future cases."

At present, no software companies provide financial rewards for those who report valid vulnerabilities to them. But Hart said such a process is needed.

"There are no financial incentives," he said. "If there were incentives, you'd find the software would become very secure overnight. And you'd turn a lot of malicious hackers into good hackers. If there were rewards for vulnerability reporting and they were valid it could work. There just needs to be a proper mechanism in place."

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

Did you find this article useful?
70 out of 150 people found this useful


Company/Topic Alerts

Create a new alert from the list below:




Related Jobs

Security Consultant - Immediate start

The desired candidate will have the following skillset: * Network Vulnerability Internal & External Testing * Configuration of Cisco switches / ...

Statistician Research and Development.

Integral member of the project teams along side researchers and commercial colleagues to offer statistical consulting and advice. Newly graduated ...

AIX administrator- Fife- Circa- 50,000

Providing Unix technical expertise, guidance, installing and configuring Unix (AIX), installing software patches, develop and maintain scripts and ...

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