• Skip to main content
  • Skip to primary sidebar
  • Skip to footer

Technologous - Managed IT Solutions Bryan/College Station

  • Home
  • About
    • Areas We Serve
    • Our Leadership
      • Chris Dawson
      • Ian Soares
  • IT Services
    • Managed IT
    • Support IT
    • Cloud IT
  • Blog
  • Request a Consultation
  • Contact
You are here: Home / Blog / Security Is Now A Concern For Open Source Software

Security Is Now A Concern For Open Source Software

This year’s Open Source Security and Risk Analysis Report analyzed the anonymized data of more than 1,200 commercial codebases from 2018. According to the report, managing open source risk continues to pose a significant challenge for industry.

The Synopsys Cybersecurity Research Center produces the report, and found that 96 percent of the code bases they analyzed contained open source components.

These were found with an average of 298 open source components per codebase.  This is an increase from an average of 257 found in 2017. Disturbingly, the research center found more than 16,500 vulnerabilities over the course of their research, with more than 40 percent of the codebases analyzed having been found to contain at least one high-risk open source vulnerability.

The major problem does not stem from the fact that open source components are more prone to bugs. Rather, it stems from the fact that while companies are often quick to embrace open source software, they tend to do a relatively poor job of keeping it up to date.

The research group summarizes their findings as follows:

“At the end of the day, all software is vulnerable to attack – without exception – and the nature of open source software is to shine a light on the issues it has, leading to increased visibility of bugs, not an increase in bugs.

The security risk is significantly diminished by increasing visibility.  If you’re not using open source components, you’d be using closed source components – either commercially available or hand-rolled – that have just as high of a likelihood of being vulnerable.  Except that you just don’t know about the bugs, unlike with open source components.”

The group recommends the following actions. First, make regular use of readily available tools that can be used to scan your codebase to identify the open source components and their version numbers. Then check this data against one or more vulnerability databases to be sure you’re adequately protected.  If you’re not currently doing so, the time is now.

May 24, 2019 Filed Under: Blog Tagged With: #Open Source Software, Bugs, Risk, Visibility

Primary Sidebar

GET OUR BLOG IN YOUR EMAIL!

Archives

  • November 2020
  • October 2020
  • September 2020
  • August 2020
  • July 2020
  • June 2020
  • April 2020
  • March 2020
  • February 2020
  • December 2019
  • November 2019
  • October 2019
  • September 2019
  • August 2019
  • July 2019
  • June 2019
  • May 2019
  • April 2019
  • March 2019
  • February 2019
  • January 2019
  • December 2018
  • August 2018

Tags

adobe android App Apple attack Attacks Breach Browser Chrome Compromised Credit Card Dark Web Data Database Data Breach Email Facebook gmail Google government hacker Hackers information Internet iOS iPhone malware Microsoft Microsoft Windows 10 office 365 Password Passwords patch Phishing ransomeware Ransomware Scam security Social Media Update Vulnerability Vulnerable Wifi Windows Windows 10

Footer

Contact Us

Address: 3091 University Drive, Unit 210, Bryan, Texas 77802
Phone: 979-217-1226

Our Blog

  • JM Bullion Announces a Breach November 17, 2020
  • New Phishing Attack Uses Unique Method To Avoid Security November 16, 2020
  • Mattel’s Response to Ransomware November 14, 2020
  • Corporate Networks Left Vulnerable November 13, 2020
  • Adobe Addresses 14 Security Flaws November 12, 2020

Search

Follow Us

  • Facebook
  • Home
  • About
  • Resources
  • Contact
  • Our Leadership
  • Why Choose Us?
  • IT Services
  • Request a Consultation

Copyright © 2021| All Rights Reserved | Powered By Technologous, LLC | Log in