Modern software stands on the shoulders of third-party frameworks and libraries, many of which are open source. This leads to fantastic possibilities in software composition and productivity, but also means that most projects depend on massive amounts of potentially vulnerable or malicious code.
Managing the different classes of threats from dependencies is complex, and there is no single tool to solve all problems. For most organisations it is possible to reduce the risk through awareness and sound policies and automation.
Examples of risk to consider and mitigate are:
– Dependencies with known vulnerabilities
– Depending on unmaintained projects
– Supply-chain attacks and malicious dependencies
In this tech talk we will take a look at typical threats and risks with third party components and find pragmatic approaches to managing the risk, while staying productive.
- Classes of threats to consider when using third-party dependencies in software development
- General policies to reduce third-party risk for most development projects
- The benefits of visibility and risk reduction through automation
Software developers, software project managers, software product managers, information security professionals.