You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@taverna.apache.org by "Albert Baker (JIRA)" <ji...@apache.org> on 2018/08/05 05:01:00 UTC
[jira] [Created] (TAVERNA-1052) Please add OWASP Dependency Check
to the build (pom.xml)
Albert Baker created TAVERNA-1052:
-------------------------------------
Summary: Please add OWASP Dependency Check to the build (pom.xml)
Key: TAVERNA-1052
URL: https://issues.apache.org/jira/browse/TAVERNA-1052
Project: Apache Taverna
Issue Type: New Feature
Components: Taverna Common Activities, Taverna Engine, Taverna Server, Taverna Workbench
Environment: All development, build, test, environments.
Reporter: Albert Baker
Fix For: workbench 3.1.0, common activities 2.2.0, engine 3.2.0, server 3.2.0
Please add OWASP Dependency Check to the build (pom.xml). OWASP DC makes an outbound REST call to MITRE Common Vulnerabilities & Exposures (CVE) to perform a lookup for each dependant .jar to list any/all known vulnerabilities for each jar. This step is needed because a manual MITRE CVE lookup/check on the main component does not include checking for vulnerabilities in components or in dependant libraries.
OWASP Dependency check : https://www.owasp.org/index.php/OWASP_Dependency_Check has plug-ins for most Java build/make types (ant, maven, ivy, gradle).
Also, add the appropriate command to the nightly build to generate a report of all known vulnerabilities in any/all third party libraries/dependencies that get pulled in. example : mvn -Powasp -Dtest=false -DfailIfNoTests=false clean aggregate
Generating this report nightly/weekly will help inform the project's development team if any dependant libraries have a reported known vulnerailities. Project teams that keep up with removing vulnerabilities on a weekly basis will help protect businesses that rely on these open source componets.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)