Commit 48c4712c authored by rossfuhrman's avatar rossfuhrman

Update SAST CI template refs to include Security

The refences to the SAST CI vendored templates should include the full
path (Security/)
parent 5130c9c7
......@@ -68,7 +68,7 @@ microservice_a:
trigger:
include:
- local: path/to/microservice_a.yml
- template: SAST.gitlab-ci.yml
- template: Security/SAST.gitlab-ci.yml
```
NOTE: **Note:**
......@@ -82,7 +82,7 @@ microservice_a:
trigger:
include:
- local: path/to/microservice_a.yml
- template: SAST.gitlab-ci.yml
- template: Security/SAST.gitlab-ci.yml
strategy: depend
```
......
......@@ -22,10 +22,10 @@ Testing (SAST), and Secret Detection by adding the following to your `.gitlab-ci
```yaml
include:
- template: Dependency-Scanning.gitlab-ci.yml
- template: License-Scanning.gitlab-ci.yml
- template: SAST.gitlab-ci.yml
- template: Secret-Detection.gitlab-ci.yml
- template: Security/Dependency-Scanning.gitlab-ci.yml
- template: Security/License-Scanning.gitlab-ci.yml
- template: Security/SAST.gitlab-ci.yml
- template: Security/Secret-Detection.gitlab-ci.yml
```
To add Dynamic Application Security Testing (DAST) scanning, add the following to your
......@@ -33,7 +33,7 @@ To add Dynamic Application Security Testing (DAST) scanning, add the following t
```yaml
include:
- template: DAST.gitlab-ci.yml
- template: Security/DAST.gitlab-ci.yml
variables:
DAST_WEBSITE: https://staging.example.com
......@@ -449,7 +449,7 @@ To fix this issue, you can either:
```yaml
include:
template: SAST.gitlab-ci.yml
template: Security/SAST.gitlab-ci.yml
spotbugs-sast:
stage: unit-tests
......@@ -490,7 +490,7 @@ would look similar to:
```yaml
include:
- template: SAST.gitlab-ci.yml
- template: Security/SAST.gitlab-ci.yml
# Ensure that the scanning is only executed on master or merge requests
spotbugs-sast:
......@@ -505,7 +505,7 @@ would be written as follows:
```yaml
include:
- template: SAST.gitlab-ci.yml
- template: Security/SAST.gitlab-ci.yml
# Ensure that the scanning is only executed on master or merge requests
spotbugs-sast:
......@@ -519,7 +519,7 @@ it would look similar to:
```yaml
include:
- template: SAST.gitlab-ci.yml
- template: Security/SAST.gitlab-ci.yml
# Ensure that the scanning is not executed on tags
spotbugs-sast:
......@@ -531,7 +531,7 @@ To transition to the new `rules` syntax, the override would be rewritten as:
```yaml
include:
- template: SAST.gitlab-ci.yml
- template: Security/SAST.gitlab-ci.yml
# Ensure that the scanning is not executed on tags
spotbugs-sast:
......
......@@ -53,7 +53,7 @@ In `.gitlab-ci.yml` define:
```yaml
include:
- template: SAST.gitlab-ci.yml
- template: Security/SAST.gitlab-ci.yml
variables:
SECURE_ANALYZERS_PREFIX: my-docker-registry/gl-images
......@@ -70,7 +70,7 @@ In `.gitlab-ci.yml` define:
```yaml
include:
- template: SAST.gitlab-ci.yml
- template: Security/SAST.gitlab-ci.yml
variables:
SAST_DEFAULT_ANALYZERS: "bandit,flawfinder"
......@@ -86,7 +86,7 @@ default analyzers. In `.gitlab-ci.yml` define:
```yaml
include:
- template: SAST.gitlab-ci.yml
- template: Security/SAST.gitlab-ci.yml
variables:
SAST_DEFAULT_ANALYZERS: ""
......
......@@ -169,7 +169,7 @@ set the `SAST_GOSEC_LEVEL` variable to `2`:
```yaml
include:
- template: SAST.gitlab-ci.yml
- template: Security/SAST.gitlab-ci.yml
variables:
SAST_GOSEC_LEVEL: 2
......@@ -191,7 +191,7 @@ inclusion and specify any additional keys under it. For example, this enables `F
```yaml
include:
- template: SAST.gitlab-ci.yml
- template: Security/SAST.gitlab-ci.yml
spotbugs-sast:
variables:
......@@ -222,7 +222,7 @@ Kubesec analyzer. In `.gitlab-ci.yml`, define:
```yaml
include:
- template: SAST.gitlab-ci.yml
- template: Security/SAST.gitlab-ci.yml
variables:
SCAN_KUBERNETES_MANIFESTS: "true"
......@@ -248,7 +248,7 @@ stages:
- test
include:
- template: SAST.gitlab-ci.yml
- template: Security/SAST.gitlab-ci.yml
build:
stage: build
......@@ -525,7 +525,7 @@ Add the following configuration to your `.gitlab-ci.yml` file. You must replace
```yaml
include:
- template: SAST.gitlab-ci.yml
- template: Security/SAST.gitlab-ci.yml
variables:
SECURE_ANALYZERS_PREFIX: "localhost:5000/analyzers"
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment