NeuVector Vulnerability Scanner

ID: neuvector-vulnerability-scanner

Description

This is a Jenkins Plugin to do security vulnerabilities scan on registries and local images with NeuVector Scanner.

Notes

  • It supports two scan modes. The first is "Controller & Scanner" mode. The second is the standalone scanner mode. You can select the scan mode in the project configuration page. By default, it uses the "Controller & Scanner" mode.

Requirements

  • For the "Controller & Scanner" mode, you need to install the NeuVector controller and scanner in the network. To scan the local image (the image on the Jenkins machine), the "Controller & Scanner" needs to be installed on the same node where the image exists.

  • For the standalone mode, Docker must be installed on the same host with Jenkins. Also, add jenkins user to the docker group.

    sudo usermod -aG docker jenkins
    

Setup the configuration in Jenkins

  1. After installed the plugin, you will find the ‘NeuVector Vulnerability Scanner’ section in the global configuration page (Jenkins ‘Configure System’). Enter values for the "Controller & Scanner" mode which includes NeuVector Scanner source name, controller IP, port, username, and password. You may click the ‘Test Connection’ button to validate the values. It will show ‘Connection Success’ or an error message.

    The timeout minutes value will terminate the build step within the time entered. The default value of 0 means no timeout will occur.

    Enter values for the standalone scanner mode which includes NeuVector Scanner Registry URL, NeuVector Scanner Image Repository, NeuVector Scanner Registry User, NeuVector Scanner Registry Password, NeuVector License.

    Click the ‘Add Registry’ to enter values for the registry you will use in your project. If you just want to scan local images, you don’t need to add a registry here.

  2. In your project configuration page, choose the 'NeuVector Vulnerability Scanner' plugin from the drop down menu in the 'Add build step'. Firstly, check the checkbox "Scan with Standalone scanner" if you want to do the scan in the standalone scanner mode. By default, it uses "Controller & Scanner" mode to do the scan. Secondly, choose 'Local' for local image scan. To do a registry scan, you need to define the registry in the global config page and choose the registry name here. Enter the repository (image) name and tag name. You may choose Jenkins default environment variables for the repository or tag. e.g. $JOB_NAME, $BUILD_TAG, $BUILD_NUMBER. Enter the values for the number of high or medium, the vulnerability names that present to fail the build, the vulnerability names that are exempt from the scan.

    When the build finishes, a NeuVector report will be generated. The report shows the scan details and errors if any.

Changelog:

Newer versions

See GitHub releases

1.12 (Feb 18, 2021)

  • Provide cause message to the abort runtime exception
  • Show the severity numbers in the scan summary report
  • Support Customized Severity Rating Scale

1.11 (Feb 01, 2021)

  • Support Standalone scanner mode

1.10 (December 11, 2020)

  • Show the build user name as anonymous if it doesn't exist

1.9 (September 14, 2020)

  • Support to exempt CVE names from Jenkins scan

1.8.1 (March 05, 2020)

  • Update ChangeLogs

1.8 (March 04, 2020)

  • Migrate to GitHub docs

1.7 (March 03, 2020)

  • Add source name to scanner's global setting
  • Report Jenkins build user, job name and workspace.

1.6 (September 21, 2019)

  • Use secret for password.

1.5 (July 1, 2019)

  • Support layer scan.

1.4 (April 16, 2019)

  • Support multiple build steps in one Jenkins build.

1.3 (September 24, 2018)

  • Update long poll status code.

1.2 (July 20, 2018)

  • Update for no scan entity case.

1.1 (July 19, 2018)

  • Add no vulnerabilities found case.

1.0 (June 1, 2018)

  • First release.
ArchivesGet past versions
Version: 1.12
Released:
Requires Jenkins 1.625.3
Installs: 51
Labels
This plugin has no labels
Maintainers
Sun
Gavin
Song Long
Help us improve this page!
To propose a change submit a pull request to the plugin page on GitHub.
Previous Security Warnings