Source Code Indemnity

By Peter Coffee  |  Posted 2004-11-22 Print this article Print

Company source code must be thoroughly insured.

Whats worth almost any price to protect if its the only one you have, but is almost worthless as long as even a single other copy exists? The answer: source code for a critical enterprise application or for firmware in a manufactured product. The corollary: You and your insurance company had better share a common understanding of what protection youve bought, against what hazards, for any source code on which your organization depends.

The risk of losing source code is fundamentally different, in one key way, from the risk to any other asset. If you have multiple copies of a Picasso print and you lose all but one, youve clearly suffered harm. In contrast, if you lose all but one of several copies of your source code ... well, you make new backups and go on. No harm.

This has a dangerous implication: If you have multiple copies of your code that you lose in separate events and even one of those events is not your insurers problem, then you might be completely out of luck—if its found that you suffered no harm at all until the last, uninsured copy was lost.

Additional copies of code are created and preserved not for intrinsic value but for their role in reducing the risk of losing the last one. Risk is the language of insurance providers, and risk reduction is what you think youre getting when you write a check for coverage. Its therefore essential that you and your insurance provider sing from the same page. You dont want to suffer the fate of U.K.-based Tektrol, a maker of energy-saving devices for electric motors whose source code all went missing—but whose loss, the court ruled late last month, wont be covered by business-interruption insurance.

No one would say that Tektrol was careless: Its managers stored the code in different forms, including a hard-copy listing, and at different locations. Even so, the combination of a virus attack and a burglary was enough to leave the company with no uncorrupted source code for the firmware in its products.

Click here to read about the theft of Ciscos PIX firewall source code. As noted by the Hon. Mr. Justice Langley, of the Royal Courts of Justice, in London, this left the company unable to do anything but continue to produce "exact replicas of existing machines"—essentially starting from scratch on any further refinements or customizations of those devices.

Executable code is useful, to be sure, but its source code that enables copying of the good parts and easy updating of the changing parts. Tektrol had failed, however, to review the provisions of its business-interruption insurance with an eye toward the kinds of things that can happen to source code. The companys representatives found themselves in court disputing whether a virus writer "deliberately" caused erasure or corruption of data. If so, then the company was not indemnified by its policy—which covered only accidental events or specifically defined perils such as a riot during a labor dispute.

And yes, the court did find that a virus writer "deliberately" causes damage. One could hardly call the damage from a virus an "accident," and the court held that simple interpretations of simple words are all that one can expect when old language has to enter new territory.

The essential and irreplaceable nature of source code is not a new discovery. For more than 15 years, my office bulletin board has featured a cartoon in which a nondescript fellow in a trench coat and fedora approaches a widow and her children—still standing at the graveside, in the rain—and says, "I realize that this may be an awkward moment, but did he ever happen to mention source code?" Most of the people who wind up in my office are torn between two simultaneous reactions: a chuckle and a wince. Source code inspires that sort of tension in anyone whose livelihood has ever depended on the stuff. If you create value by crafting code, or by managing those who do, you should be part of the process of protecting your organization against its loss or destruction. The Tektrol case is a warning never to take that protection for granted.

Technology Editor Peter Coffee can be reached at

To read more Peter Coffee, subscribe to eWEEK magazine. Check out eWEEK.coms for the latest security news, reviews and analysis. And for insights on security coverage around the Web, take a look at Security Center Editor Larry Seltzers Weblog.
Peter Coffee is Director of Platform Research at, where he serves as a liaison with the developer community to define the opportunity and clarify developers' technical requirements on the company's evolving Apex Platform. Peter previously spent 18 years with eWEEK (formerly PC Week), the national news magazine of enterprise technology practice, where he reviewed software development tools and methods and wrote regular columns on emerging technologies and professional community issues.Before he began writing full-time in 1989, Peter spent eleven years in technical and management positions at Exxon and The Aerospace Corporation, including management of the latter company's first desktop computing planning team and applied research in applications of artificial intelligence techniques. He holds an engineering degree from MIT and an MBA from Pepperdine University, he has held teaching appointments in computer science, business analytics and information systems management at Pepperdine, UCLA, and Chapman College.

Submit a Comment

Loading Comments...
Manage your Newsletters: Login   Register My Newsletters

Rocket Fuel