34 lines
3.3 KiB
YAML
34 lines
3.3 KiB
YAML
|
- title: "Secure scanning CI/CD templates will use new job `rules`" # (required) Clearly explain the change, or planned change. For example, "The `confidential` field for a `Note` is deprecated" or "CI/CD job names will be limited to 250 characters."
|
||
|
|
announcement_milestone: "15.9" # (required) The milestone when this feature was first announced as deprecated.
|
||
|
|
removal_milestone: "16.0" # (required) The milestone when this feature is planned to be removed
|
||
|
|
breaking_change: true # (required) Change to false if this is not a breaking change.
|
||
|
|
reporter: connorgilbert # (required) GitLab username of the person reporting the change
|
||
|
|
stage: secure # (required) String value of the stage that the feature was created in. e.g., Growth
|
||
|
|
issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/391822 # (required) Link to the deprecation issue in GitLab
|
||
|
|
body: | # (required) Do not modify this line, instead modify the lines below.
|
||
|
|
GitLab-managed CI/CD templates for security scanning will be updated in the GitLab 16.0 release.
|
||
|
|
The updates will include improvements already released in the Latest versions of the CI/CD templates.
|
||
|
|
We released these changes in the Latest template versions because they have the potential to disrupt customized CI/CD pipeline configurations.
|
||
|
|
|
||
|
|
In all updated templates, we're:
|
||
|
|
|
||
|
|
- Adding support for running scans in merge request (MR) pipelines.
|
||
|
|
- Updating the definition of variables like `SAST_DISABLED` and `DEPENDENCY_SCANNING_DISABLED` to disable scanning only if the value is `"true"`. Previously, even if the value were `"false"`, scanning would be disabled.
|
||
|
|
|
||
|
|
The following templates will be updated:
|
||
|
|
|
||
|
|
- API Fuzzing: [`API-Fuzzing.gitlab-ci.yml`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Security/API-Fuzzing.gitlab-ci.yml)
|
||
|
|
- Container Scanning: [`Container-Scanning.gitlab-ci.yml`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Jobs/Container-Scanning.gitlab-ci.yml)
|
||
|
|
- Coverage-Guided Fuzzing: [`Coverage-Fuzzing.gitlab-ci.yml`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Security/Coverage-Fuzzing.gitlab-ci.yml)
|
||
|
|
- DAST: [`DAST.gitlab-ci.yml`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Security/DAST.gitlab-ci.yml)
|
||
|
|
- DAST API: [`DAST-API.gitlab-ci.yml`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Security/DAST-API.gitlab-ci.yml)
|
||
|
|
- Dependency Scanning: [`Dependency-Scanning.gitlab-ci.yml`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Jobs/Dependency-Scanning.gitlab-ci.yml)
|
||
|
|
- IaC Scanning: [`SAST-IaC.gitlab-ci.yml`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Jobs/SAST-IaC.gitlab-ci.yml)
|
||
|
|
- SAST: [`SAST.gitlab-ci.yml`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Jobs/SAST.gitlab-ci.yml)
|
||
|
|
- Secret Detection: [`Secret-Detection.gitlab-ci.yml`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Jobs/Secret-Detction.gitlab-ci.yml)
|
||
|
|
|
||
|
|
We recommend that you test your pipelines before the 16.0 release if you use one of the templates listed above and you do any of the following:
|
||
|
|
|
||
|
|
1. You override `rules` for your security scanning jobs.
|
||
|
|
1. You use the `_DISABLED` variables but set a value other than `"true"`.
|