Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/entur/owasp-orb
CircleCI Orb for running OWASP depenency check plugin for Maven and Gradle builds
https://github.com/entur/owasp-orb
circleci circleci-orbs gradle maven owasp owasp-dependencycheck
Last synced: about 1 month ago
JSON representation
CircleCI Orb for running OWASP depenency check plugin for Maven and Gradle builds
- Host: GitHub
- URL: https://github.com/entur/owasp-orb
- Owner: entur
- License: eupl-1.2
- Created: 2019-01-21T10:18:59.000Z (almost 6 years ago)
- Default Branch: master
- Last Pushed: 2023-12-01T14:19:12.000Z (about 1 year ago)
- Last Synced: 2023-12-01T15:31:56.647Z (about 1 year ago)
- Topics: circleci, circleci-orbs, gradle, maven, owasp, owasp-dependencycheck
- Homepage:
- Size: 41 KB
- Stars: 10
- Watchers: 25
- Forks: 0
- Open Issues: 2
-
Metadata Files:
- Readme: README.md
- Codeowners: CODEOWNERS
Awesome Lists containing this project
README
# owasp-orb
A Circle CI orb using [OWASP Dependency Check](https://jeremylong.github.io/DependencyCheck/) to check for components with known security-vulnerablities. Supported variants:
* [Gradle plugin](https://jeremylong.github.io/DependencyCheck/dependency-check-gradle/index.html)
* [Maven plugin](https://jeremylong.github.io/DependencyCheck/dependency-check-maven/index.html)
* [Command Line Tool](https://jeremylong.github.io/DependencyCheck/dependency-check-cli/index.html)
## Usage
Import the orb
```yaml
orbs:
owasp: entur/[email protected]
```
where `x` is the latest version from [the orb registry](https://circleci.com/orbs/registry/orb/entur/owasp).
### Default executor
To use the default executor, [Docker Hub credentials](https://circleci.com/docs/2.0/private-images/) must be set as the environment variables `$DOCKERHUB_LOGIN` and `$DOCKERHUB_PASSWORD`.
## Gradle
Configure a job
```yaml
workflows:
version: 2.1
build:
jobs:
- owasp/gradle_owasp_dependency_check:
executor: java_17
context: global
```
Then add [OWASP Gradle Plugin](https://github.com/jeremylong/DependencyCheck) to your gradle build:
```groovy
plugins {
id 'org.owasp.dependencycheck' version '9.0.2'
}
dependencyCheck {
analyzedTypes = ['jar'] // the default artifact types that will be analyzed.
format = 'ALL' // CI-tools usually needs XML-reports, but humans needs HTML.
failBuildOnCVSS = 7 // Specifies if the build should be failed if a CVSS score equal to or above a specified level is identified.
suppressionFiles = ["$rootDir/owasp_suppressions.xml"] // specify a list of known issues which contain false-positives
nvd {
apiKey = "${project.properties['NVD_API_KEY'] ?: System.env.NVD_API_KEY}"
}
}
```
where
* suppressions (false positives) are assumed to be in `owasp_suppressions.xml` in the root of the project.
* `NVD_API_KEY` is assumed to contain the [NVD API Key](https://nvd.nist.gov/developers/request-an-api-key) via
* `~/.gradle/gradle.properties`, or
* environment variable, or
* command line parameter
#### Details
The default OWASP plugin task is `dependencyCheckAnalyze`, for using other tasks, add a `task` parameter as so:
```yaml
workflows:
version: 2.1
build:
jobs:
- owasp/gradle_owasp_dependency_check:
executor: java_17
context: global
task: dependencyCheckAggregate
```
where task is one of [dependencyCheckAnalyze](https://jeremylong.github.io/DependencyCheck/dependency-check-gradle/configuration.html), [dependencyCheckAggregate](https://jeremylong.github.io/DependencyCheck/dependency-check-gradle/configuration-aggregate.html), [dependencyCheckUpdate](https://jeremylong.github.io/DependencyCheck/dependency-check-gradle/configuration-update.html), and [dependencyCheckPurge](https://jeremylong.github.io/DependencyCheck/dependency-check-gradle/configuration-purge.html).
Alternatively, use the `wrapped_gradle_steps` command to customize further.
## Maven
Configure a job
```yaml
workflows:
version: 2.1
build:
jobs:
- owasp/maven_owasp_dependency_check:
executor: java_17
context: global
```
Then add [OWASP Maven Plugin](https://jeremylong.github.io/DependencyCheck/dependency-check-maven/index.html) to your Maven build:
```xml
org.owasp
dependency-check-maven
10.0.4
all
7
${NVD_API_KEY}
${basedir}/owasp_suppressions.xml
check
none
```
* suppressions (false positives) are assumed to be in `owasp_suppressions.xml` in the root of the project.
* `NVD_API_KEY` is assumed to contain the [NVD API](https://nvd.nist.gov/developers/request-an-api-key) via
* `~/.m2/settings.xml`, or
* environment variable, or
* command line parameter
### Configure NVD API Key on local machine
In `~/.m2/settings.xml`, add
```
properties
YOUR KEY HERE
```
with
```
properties
```
#### Details
The default OWASP plugin task is `check`, for using other tasks, add a `task` parameter as so:
```yaml
workflows:
version: 2.1
build:
jobs:
- owasp/maven_owasp_dependency_check:
executor: java_17
task: aggregate
context: global
```
#### Maven multi-module projects
The dependency plugin currently is not able to resolve artifacts before they are built. If internal submodule dependencies cannot reached in the build, add a few `wrapped_pre_steps` to do so.
```yaml
workflows:
version: 2.1
build:
jobs:
- owasp/maven_owasp_dependency_check:
executor: java_17
context: global
wrapped_pre_steps:
- run: mvn install -Dmaven.test.skip=true
```
Alternatively, use the `wrapped_maven_steps` command to customize further.
## Command Line Tool
Configure a job
```yaml
workflows:
version: 2.1
build:
jobs:
- owasp/commandline_owasp_dependency_check:
executor: java_17
context: global
```
#### Details
The default OWASP arguments is `--scan ./`, for using other commands, add an `arguments` parameter as so:
```yaml
workflows:
version: 2.1
build:
jobs:
- owasp/commandline_owasp_dependency_check:
executor: java_17
arguments: "--scan ./ --failOnCVSS 7 --suppression ./dependency-check-suppressions.xml --nvdApiKey $NVD_API_KEY"
context: global
```
See the [arguments page](https://jeremylong.github.io/DependencyCheck/dependency-check-cli/arguments.html) for further details. Note that `--format`, `--data` and `--noupdate` arguments are already appended by this orb (updating the database is performed in an individual previous step).
Use `no_output_timeout` parameter to avoid "Too long with no output (exceeded 10m0s): context deadline exceeded" error
## Caching
The OWASP plugin checks for updates to its database every four hours, and the database is cached by the orb like so:
* Year
* Quarter (12 weeks)
* Month (4 weeks)
* Week
* Day
* 12 hours
* 4 hours
So for each working day, the first builds (in the morning) will check for updates, and last for four hours with potential cache refreshes every four clock hours (at 9, 13, 17, 21 and so on). In other words, the OWASP plugin will check for updates whenever four hours have passed, and will be able to persist those updates to CircleCI cache in maximum four hours - a compromise between time spent saving cache and time spent checking for updates.
### Data directory
Use the orb parameter `cve_data_directory` to configure non-standard data directory. Note that for Gradle builds this is necessary for plugin version <= `5.1.0`.
Configuration examples (using default directories):
#### Gradle
```
dependencyCheck {
data {
// must correspond with CircleCI-configuration
directory = System.properties['user.home'] + "/.gradle/dependency-check-data"
}
}
```
for `cve_data_directory` parameter value `~/.gradle/dependency-check-data`.
#### Maven
```xml
${user.home}/.m2/repository/org/owasp/dependency-check-data
```
for `cve_data_directory` parameter value `~/.m2/repository/org/owasp/dependency-check-data`.
## Further reading
See the [orb](/src/@orb.yml) source or [CircleCI orb registry](https://circleci.com/orbs/registry/orb/entur/owasp) for further details.