Dr Carl Reynolds of UCL's Centre for Health Informatics and Multiprofessional Education said: "Software bought or otherwise distributed under a licence which require it to come bundled with the source code and the right to freely edit, reuse, and share it is called free or open source software. Such a licensing arrangement leaves the buyer in a very strong position when compared with the usual proprietary licences. The buyer is less prone to lock-in, where a buyer loses the ability to switch software products because of the use of proprietary data formats or restrictive licensing conditions. When the buyer chooses an open or free licence he or she can take the code to a rival code developer if they offer a better deal. If the code is in the public domain, and the user and programmer community are engaged, then the buyer can profit from more people inspecting and fixing the code leading to higher quality source code and in turn software."

Professor Jeremy Wyatt of the University of Warwick's Institute for Digital Healthcare said: "Critics of Open Source often argue that, because the code is public, an attacker can more easily find and exploit vulnerabilities. But our work at the University of Warwick and UCL shows that the evidence does not bear this out and in fact Open Source Software (OSS) may be more secure than other systems.

"Proprietary systems often rely on a 'security through obscurity' argument, ie that systems that hide their inner workings from potential attackers are more secure. However security through obscurity alone completely fails when code is disclosed or otherwise discovered using tools such as debuggers or dissemblers. Worse, it has been suggested that the cloak of obscurity tends to encourage poor-quality code. Opening the source allows independent assessment of the security of a system, makes bug patching easier and more likely, and forces developers to spend more effort on the quality of their code."

The researchers also refute the argument that using Open Source Software (OSS) is inherently riskier because one automatically becomes liable for any failings of the software. They say that "typically a large organization will pay a contractor for an OSS implementation and support package. Many contractors providing OSS implementation and support offer legal indemnity to clients in exactly the same way as proprietary vendors."

Note: If no author is given, the source is cited instead.

• Today's Healthcare
• Health Policy

• Software
• Computer Programming

• Privacy Issues
• Security and Defense

• Computer software
• Malware
• Application software
• Computer insecurity
• Security engineering
• Computer security