Open source code

Open source code

• 1.
  Intetics Inc. www.intetics.com intetics@intetics.com Office: +1-239-217-4907 OpenSource Code In Product Development Best Practices And Risk Mitigation
• 2.
  © Сopyright, 1995-20202 Modern software development involves the increased use of open source code 72% of organizations make non- commercial use of open source code and 55% use it for commercial product development But it’s crucial to make sure every component is well scrutinized before it’s integrated into your project Open source code in product development
• 3.
  © Сopyright, 1995-20203 3 key problems related to the use of open source code Violation of license agreement for commercial uses Use of outdated open source components causing vulnerability risks Use of libraries without community support How to manage these issues?
• 4.
  © Сopyright, 1995-20204 Problem 1 – Violation of license agreement for commercial uses Using unlicensed open source сode is unsafe. You might end up violating intellectual property rights or bringing security vulnerabilities and risks into your project, which can translate into financial and legal consequences.
• 5.
  © Сopyright, 1995-20205 1 Document the use of all third-party resources on the project Although it requires time and resources, you get to know where all your open source elements come from. 2 Import libraries only after getting approval from the project tech lead Solution - Watch out for hidden inconsistencies
• 6.
  © Сopyright, 1995-20206 Problem 2 – Use of libraries without community support A lot of open source code libraries might often fail to comply with security standards, work incorrectly with other open source components, be out-of-date or have no license at all.
• 7.
  © Сopyright, 1995-20207 1 Start with scrutinizing the library component you need: сheck its license, source and version before you use it. 2 Try to only use libraries from official sites, and if possible, do not import code manually Solution - Check the origin of the libraries you use
• 8.
  © Сopyright, 1995-2020 Problem3 – Use of outdated open source components causing vulnerability risks 91% of product development projects use outdated open source components, thus jeopardizing project security significantly. 82% of codebases have four-year-old parts and 88% have had no add-ons during the last two years. 8
• 9.
  © Сopyright, 1995-20209 Solution - Track the software versions you use 1 Be sure the software you use is brand new and receives vendor support and upgrades In case you work with different frameworks, check that all libraries work together correctly. 2 Choose automated open source code assessment tools to verify the relevance of code elements A top-notch tool automatically tracks possible vulnerabilities in open source code and spots issues on time.
• 10.
  © Сopyright, 1995-202010 Final recommendations Inventory your open source components Create policies for your development and legal teams to regulate every open source activity in the project Keep on auditing your open source code regularly to detect and troubleshoot issues on time Engage in open source communities
• 11.
  © Сopyright, 1995-202011 TETRA Not confident about the product quality and wish to scrutinize your open source components? Go for a large-scale software project assessment! The TETRA platform can help you uncover technical debt and get an in-depth analysis of code quality, as well as useful ideas for solving your burning issues. TM
• 12.
  12 Thank you! Intetics Inc. 10001Tamiami Trl N, Suite 114 Naples, Florida 34108 United States www.intetics.com intetics@intetics.com Office: +1-239-217-4907