Third-party code should not be taken on trust and installed without a security test, claimed Veracode at the RSA Security Conference in London this week.
Veracode, an application risk management cloud service company, has issued a report on the findings of its software testing over the past 18 months. It showed that applications from all types of third-party suppliers were less secure than internally developed applications.
"Third-party suppliers failed to achieve acceptable levels of security 81 per cent of the time," the report stated.
As if to illustrate Veracode's point, earlier this week UK company Omniquad, a cloud-based email and web access filtering service, fell victim to a flaw in third-party software it was using to manage helpdesk calls.
The exploit resulted in customer log-in details being published online. Omniquad said that as soon as the problem was discovered the information was removed and the system put offline.
Daniel Sobstel, managing director of Omniquad denied negligence on his company's part. He said that action was swift and all affected customers had been notified. The software had been in use for "a few years" without any previous incidents, he added.
Privacy International has reported the incident to the Information Commissioner for investigation.
"Breaches such as this demonstrates all too well the dire consequences that follow from failing to assess the risks that come from third party software," commented Chris Eng, senior director for security research at Veracode.
Both Safecode.org and Secunia, security testing organisations, have also recently pointed out the elevated risks associated with third-party software in the supply chain.
In Veracode's State of Software Security report, 2,922 applications were tested and more than half (57 per cent), both third-party and in-house, failed to meet an acceptable level of security. In the case of
web applications, 80 per cent failed to comply with the Open Web Application Security Project (OWASP) standards.
OWASP is a reference for US government departments and the PCI standards body for software security. It has listed ten security risks that should be tested for before software is brought online.
