Public concerned about security flaws in government open source code

Some members of the public are already expressing concern about the security implications

Earlier this month, the White House released a draft of an open source code policy for public review which would require agencies to share code with each other and with the public, but some experts are concerned about possible security implications.

Under the proposed new policy, new software developed specifically for or by the federal government must be made available to other federal agencies. In addition, under a pilot program, a portion of the federally-funded code must be released to the public as open source.

"We can save taxpayer dollars by avoiding duplicative custom software purchases and promote innovation and collaboration across federal agencies," said Tony Scott, the U.S. chief information officer, in the announcement. "We will also enable the brightest minds inside and outside of government to review and improve our code, and work together to ensure that the code is secure, reliable, and effective."

[ ALSO ON CSO: The state of open source security ]

Some members of the public are already expressing concern about the security implications, however.

"The world does not need more insecure code," said John Pescatore, director of emerging trends at SANS Institute, in a comment submitted via the project's GitHub page. "This process needs to as a minimum require common process for code to be tested for basic app development hygiene before being submitted or at least before being accepted."

Code should undergo quality review before it is used, agreed John Scott, founder and co-chair at Washington, D.C.-based Open Source for America, an effort to encourage more government use of open source software.

But agencies shouldn't be required to use code review tools before releasing it to the public, he added.

"Testing of the code before release will just create a bottleneck and could stop progress," he said in his comment.

Many commenters pointed out that public scrutiny by itself will help catch security problems.

But vulnerabilities are regularly found in open source projects, even ones that have been around for a while.

In addition, open source code poses two additional security problems, said Mike Pittenger, vice president of security strategy at Black Duck Software. "Open source projects are often ubiquitous, so if there's a vulnerability it creates a target-rich environment for attackers," he said.

Attackers who spot a vulnerability in a popular tool can simply keep trying it against different organizations until they find one who uses it.

The other problem is that open source code often doesn't have an organization behind it to push out updates, Pittenger added.

"With open source, there's a lower up front cost, and you don't have to pay for support," he said. "But it's up to you to monitor the open source community and see if there's a vulnerability and pull the patch. You multiply that by the number of open source projects and components used in an environment, and you quickly have a problem."

Black Duck is currently tracking more than 1.5 million different open source projects, he added.

"And we're seeing the pace of development increasing because it's more and more accepted and no longer viewed as a scary, bad thing," he added.

The public comment period ends on April 11.

Join the CSO newsletter!

Error: Please check your email address.

More about CSOSANS Institute

Show Comments

Featured Whitepapers

Editor's Recommendations

Solution Centres

Stories by Maria Korolov

Latest Videos

  • 150x50

    CSO Webinar: Will your data protection strategy be enough when disaster strikes?

    Speakers: - Paul O’Connor, Engagement leader - Performance Audit Group, Victorian Auditor-General’s Office (VAGO) - Nigel Phair, Managing Director, Centre for Internet Safety - Joshua Stenhouse, Technical Evangelist, Zerto - Anthony Caruana, CSO MC & Moderator

    Play Video

  • 150x50

    CSO Webinar: The Human Factor - Your people are your biggest security weakness

    ​Speakers: David Lacey, Researcher and former CISO Royal Mail David Turner - Global Risk Management Expert Mark Guntrip - Group Manager, Email Protection, Proofpoint

    Play Video

  • 150x50

    CSO Webinar: Current ransomware defences are failing – but machine learning can drive a more proactive solution

    Speakers • Ty Miller, Director, Threat Intelligence • Mark Gregory, Leader, Network Engineering Research Group, RMIT • Jeff Lanza, Retired FBI Agent (USA) • Andy Solterbeck, VP Asia Pacific, Cylance • David Braue, CSO MC/Moderator What to expect: ​Hear from industry experts on the local and global ransomware threat landscape. Explore a new approach to dealing with ransomware using machine-learning techniques and by thinking about the problem in a fundamentally different way. Apply techniques for gathering insight into ransomware behaviour and find out what elements must go into a truly effective ransomware defence. Get a first-hand look at how ransomware actually works in practice, and how machine-learning techniques can pick up on its activities long before your employees do.

    Play Video

  • 150x50

    CSO Webinar: Get real about metadata to avoid a false sense of security

    Speakers: • Anthony Caruana – CSO MC and moderator • Ian Farquhar, Worldwide Virtual Security Team Lead, Gigamon • John Lindsay, Former CTO, iiNet • Skeeve Stevens, Futurist, Future Sumo • David Vaile - Vice chair of APF, Co-Convenor of the Cyberspace Law And Policy Community, UNSW Law Faculty This webinar covers: - A 101 on metadata - what it is and how to use it - Insight into a typical attack, what happens and what we would find when looking into the metadata - How to collect metadata, use this to detect attacks and get greater insight into how you can use this to protect your organisation - Learn how much raw data and metadata to retain and how long for - Get a reality check on how you're using your metadata and if this is enough to secure your organisation

    Play Video

  • 150x50

    CSO Webinar: How banking trojans work and how you can stop them

    CSO Webinar: How banking trojans work and how you can stop them Featuring: • John Baird, Director of Global Technology Production, Deutsche Bank • Samantha Macleod, GM Cyber Security, ME Bank • Sherrod DeGrippo, Director of Emerging Threats, Proofpoint (USA)

    Play Video

More videos

Blog Posts

Market Place