Advanced Search
CS Search Google Search
Subscribers, please login

Published Articles >> Table of Contents >> Abstract

Publication Home Page
March/April 2004 (Vol. 21, No. 2)   pp. 94-99
In the News

Full Article Text: View linked HTML of full textDownload PDF of full textBuy this articleGet full text from IEEE Xplore

DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/MS.2004.1270771
Send link to a friend

Abstract

In the News

Whose Bug Is It Anyway: The Battle over Handling Software Flaws

Attacks exploit vulnerabilities in software code. They come in many forms: logic attacks, Trojan horses, worms and viruses, and variants of each. They serve a host of purposes: corporate espionage, white-collar crime, social "hacktivism," terrorism, and notoriety. Greater connectivity, more complex software, and the persistence of older protocols ensure growing vulnerability. Although marathon patching sessions have become the norm for harried IT administrators, even top-of-the-line patch management can’t keep up with malicious code’s growing sophistication. What happens when a software vulnerability is discovered? To establish agreed-on "best practices" to guide the process of reporting bugs, several companies have come together to form the Organization for Internet Safety. There is also a set of informal guidelines called RFPolicy, the open source equivalent of the OIS recommendations.

A Trip to South Africa

Alan Davis describes his sabbatical teaching in Cape Town, South Africa.

Additional Information

Citation:  Ashton Applewhite, Alan Davis, "In the News," IEEE Software, vol. 21,  no. 2,  pp. 94-99,  Mar/Apr,  2004

RSS Feed

Similar Articles

Abstract Contents
Abstract
Citation




Free access to

  • Abstracts
  • Selected PDFs

Electronic subscribers login to:

  • Access HTML/PDFs of full text articles

Subscription information

Get a Web account

PDFs require Adobe Acrobat Reader.

Peer Review Notice

Give us Feedback