Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
71e59870
Commit
71e59870
authored
Oct 26, 2021
by
Russell Dickenson
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Improve security report validation topic
parent
45da3d6d
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
27 additions
and
32 deletions
+27
-32
doc/user/application_security/index.md
doc/user/application_security/index.md
+27
-32
No files found.
doc/user/application_security/index.md
View file @
71e59870
...
...
@@ -279,44 +279,39 @@ If you don't want scans running in your normal DevOps process you can use on-dem
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/321918) in GitLab 13.11.
> - Schema validation message [added](https://gitlab.com/gitlab-org/gitlab/-/issues/321730) in GitLab 14.0.
You can optionally enable validation of the security report artifacts based on the
[
report schemas
](
https://gitlab.com/gitlab-org/security-products/security-report-schemas/-/tree/master/dist
)
.
If you enable validation, GitLab validates the report artifacts before ingesting the vulnerabilities.
This prevents ingestion of broken vulnerability data into the database.
You can enforce validation of the security report artifacts before ingesting the vulnerabilities.
This prevents ingestion of broken vulnerability data into the database. GitLab validates the
artifacts based on the
[
report schemas
](
https://gitlab.com/gitlab-org/security-products/security-report-schemas/-/tree/master/dist
)
.
In GitLab 14.0 and later,
the pipeline's
**Security**
tab lists any report artifac
ts
that failed validation. Security report validation must first be enabled
.
In GitLab 14.0 and later,
when artifact validation is enabled, the pipeline's
**Security**
tab lis
ts
any report artifacts that failed validation
.
### Enable security report validation
To enable report artifacts validation, set the
`VALIDATE_SCHEMA`
environment variable to
`"true"`
for the jobs in the
`.gitlab-ci.yml`
file.
To enable report artifacts validation, set the
`VALIDATE_SCHEMA`
environment variable to
`"true"`
for the desired jobs in the
`.gitlab-ci.yml`
file.
For example, t
he configuration below enables
validation for only the
`sast`
job:
For example, t
o enable
validation for only the
`sast`
job:
```
yaml
include
:
-
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
stages
:
-
security-scan
dependency_scanning
:
stage
:
security-scan
license_scanning
:
stage
:
security-scan
sast
:
stage
:
security-scan
variables
:
VALIDATE_SCHEMA
:
"
true"
.secret-analyzer
:
stage
:
security-scan
```
```
yaml
include
:
-
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
stages
:
-
security-scan
dependency_scanning
:
stage
:
security-scan
license_scanning
:
stage
:
security-scan
sast
:
stage
:
security-scan
variables
:
VALIDATE_SCHEMA
:
"
true"
.secret-analyzer
:
stage
:
security-scan
```
## Interacting with findings and vulnerabilities
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment