Skip to main content

Command Palette

Search for a command to run...

Exploring OWASP Dependency Check in Jenkins: A Step-by-Step Guide

Updated
3 min read
Exploring OWASP Dependency Check in Jenkins: A Step-by-Step Guide
K

"Hello, I'm Kiran Pawar, a passionate Cloud and Devops Engineer with a strong background in cloud automation, configuration, and deployment. My journey in the world of technology has been a thrilling adventure, where I've had the privilege to work with cutting-edge tools and practices.

🚀 As a DevOps Engineer:

I specialize in automating, configuring, and deploying instances in cloud environments and data centers. My expertise extends to DevOps, GitOps, CI/CD pipeline management, HashiCorp Terraform, and containerization. I'm proficient in AWS and Linux/Unix administration, ensuring robust infrastructure and application performance.

🔧 My Tech Stack:

Front-end skills: HTML, CSS, SCSS, Tailwind CSS, Bootstrap, React, Material-UI, JavaScript DevOps toolbox: GIT, OWASP,Nexus,Trivy, Github, Gitlab, Terraform, Ansible, Docker, Kubernetes, Helm, Jenkins, Prometheus, Grafana, Argo CD, AWS EKS.

🌐 My Cloud Expertise:

I have hands-on experience managing AWS services, including EC2, S3, EBS, VPC, ELB, RDS, IAM, Route53, and more.

🔒 Networking and Security:

My skills include managing networking concepts such as TCP/IP protocols, security policies, and subnet interfacing. I have a strong understanding of infrastructure and networking, covering topics like firewalls, IP addressing, DNS, and more.

💡 What Sets Me Apart:

I bring a positive attitude, a strong work ethic, and a collaborative spirit to every project. I'm a self-starter, a fast learner, and an effective team player with strong interpersonal skills. In addition to my DevOps skills, I've developed shell scripts (Bash) for automating tasks and have proficiency in Python scripting. My ability to communicate and manage projects, along with a track record of resolving client issues, adds value to every team I work with. If you're looking for a DevOps engineer who is also well-versed in front-end technologies, feel free to connect with me. Let's explore new possibilities and create exceptional technical solutions together!"

Overview

OWASP Dependency Check is a crucial tool in the realm of software composition analysis, aiding in the identification of project dependencies with known vulnerabilities. This guide provides step-by-step instructions on setting up OWASP Dependency Check in Jenkins for efficient vulnerability detection.

Installation

  1. Open Jenkins and navigate to the Jenkins home page.

  2. Click on "Manage Jenkins" in the left-hand sidebar.

  3. Select "Manage Plugins" from the options.

  4. In the "Available" tab, search for "OWASP Dependency-Check Plugin" in the filter box.

  5. Check the checkbox next to the plugin and click on the "Install without restart" button.

  6. Once the installation is complete, go back to the Jenkins home page.

Setting up OWASP Dependency Check in Jenkins

  1. Click on "New Item" in the left-hand sidebar to create a new Jenkins job.

  2. Enter a name for your job and select the type of job you want to create (e.g., Freestyle project or Pipeline).

  3. Configure the job as per your requirements (e.g., source code management, build triggers, etc.).

  4. Scroll down to the "Build" section and click on the "Add build step" dropdown.

  5. Select "Invoke OWASP Dependency-Check" from the dropdown.

  6. Configure the plugin settings according to your needs, specifying the path to your project, any additional arguments, and choosing the appropriate OWASP Dependency-Check installation.

  7. Save the job configuration.

  8. Before running the job, ensure you've set up the desired OWASP Dependency-Check installation in Jenkins (Go to "Manage Jenkins" > "Global Tool Configuration").

Installation Options for OWASP Dependency Check

Option 1: Downloading the Standalone JAR

  • Go to the OWASP Dependency Check releases page.

  • Download the latest version of the standalone JAR file (dependency-check.jar).

  • Ensure you have Java 8 or higher installed on your system.

  • Run the tool using the following command:

      java -jar dependency-check.jar --project <project-name> --scan <path-to-project>
    

Option 2: Using Package Managers

Maven

  • Add the following plugin to your pom.xml file:

      <build>
        <plugins>
          <plugin>
            <groupId>org.owasp</groupId>
            <artifactId>dependency-check-maven</artifactId>
            <version>INSERT_VERSION_HERE</version>
            <executions>
              <execution>
                <goals>
                  <goal>check</goal>
                </goals>
              </execution>
            </executions>
          </plugin>
        </plugins>
      </build>
    
  • Run mvn dependency-check:check to analyze your project.

Usage

Once installed, run OWASP Dependency Check against your project to identify vulnerabilities:

For the standalone JAR:

java -jar dependency-check.jar --project <project-name> --scan <path-to-project>

For Maven:

mvn dependency-check:check

Make sure to replace <project-name> with your project's name and <path-to-project> with the project's directory.

Configuration

OWASP Dependency Check offers various configuration options. Refer to the Configuration Guide for detailed information.

Reporting

OWASP Dependency Check generates comprehensive reports about identified vulnerabilities. Reports can be found at:

  • For the standalone JAR: <path-to-project>/target/dependency-check-report.html

  • For Maven: <path-to-project>/target/dependency-check-report.html

  • For Gradle: <path-to-project>/build/reports/dependency-check-report.html

Open the HTML report in your web browser to view vulnerability details.

Resources

Jenkins Pipeline Integration

pipeline {
    agent any

    tools {
        jdk 'jdk11'
        maven 'maven3'
    }

    environment {
        SCANNER_HOME = tool 'sonar-scanner'
    }

    stages {
        // ... Previous stages ...

        stage('OWASP Dependency Check') {
            steps {
                dependencyCheck additionalArguments: '--scan target/', odcInstallation: 'owasp'
            }
        }

        stage('Publish OWASP Dependency Check Report') {
            steps {
                publishHTML(target: [
                    allowMissing: false,
                    alwaysLinkToLastBuild: true,
                    keepAll: true,
                    reportDir: 'target',
                    reportFiles: 'dependency-check-report.html',
                    reportName: 'OWASP Dependency Check Report'
                ])
            }
        }

        // ... Subsequent stages ...
    }
}

Feel free to customize the pipeline according to your specific project structure and needs.

A

"Great guide! I appreciated how you walked through setting up OWASP Dependency‑Check in Jenkins from plugin installation to configuring build steps and publishing reports making it approachable even if you’re new to CI/CD security tooling. The step‑by‑step format is clear and actionable, and the insights into integrating vulnerability scanning into pipelines add solid value.

I also recently read a related implementation guide on blog https://mobisoftinfotech.com/resources/blog/ai-development/develop-use-mcp-server-ai-agents-maven-guide -which dives into using a java dependency scanner while setting up agent‑driven systems with MCP Server."

A

I came upon your blog on exploring OWASP Dependency-Check in Jenkins—great guide! The step-by-step setup and integration into Jenkins pipelines are super helpful for anyone looking to add vulnerability scanning to their CI/CD workflows. I especially appreciate the different installation options you covered, including Maven, and the clear breakdown of configuring and generating reports.

While looking further into it, I found a related resource on integrating OWASP Dependency-Check with SonarQube for early-stage vulnerability management in DevSecOps: https://mobisoftinfotech.com/resources/blog/devsecops-mitigating-vulnerabilities-sonarqube-owasp . It emphasizes how these tools work together to improve secure coding practices.

Since you’ve covered Jenkins integration, I’d love to hear your thoughts on how OWASP Dependency-Check fits into the broader DevSecOps landscape in 2025. Do you think it’s becoming an essential part of automated security checks for modern development pipelines?

J

Earning through cryptocurrency is genuine, If you are new to crypto trading and you don't know how to earn from it or your an old investor who have been losing try to earn from cryptocurrency, here is an opportunity for you to earn through cryptocurrency trading visit Adelynn Richardson fx on lnstagram/Facebook for a safe and secure investment

More from this blog

Kiran Pawar's Blog

122 posts