Any security warnings are also [shown in the merge request widget](../../user/project/merge_requests/sast.md).
Any security warnings are also [shown in the merge request widget](../../user/project/merge_requests/sast.md).
### Auto SAST
### Auto SAST for Docker images
> Introduced in [GitLab Enterprise Edition Ultimate][ee] 10.3.
> Introduced in [GitLab Enterprise Edition Ultimate][ee] 10.4.
Static Application Security Testing (SAST) uses the
Vulnerability Static Analysis for Containers. It uses the
[gl-sast Docker image](https://gitlab.com/gitlab-org/gl-sast) to run static
[clair](https://github.com/coreos/clair) to run static
analysis on the current code and checks for potential security issues. Once the
analysis on the current Docker image and checks for potential security issues. Once the
report is created, it's uploaded as an artifact which you can later download and
report is created, it's uploaded as an artifact which you can later download and
check out.
check out.
Any security warnings are also [shown in the merge request widget](https://docs.gitlab.com/ee/user/project/merge_requests/sast.html).
Any security warnings are also [shown in the merge request widget](../../user/project/merge_requests/sast.md).
### Auto Browser Performance Testing
### Auto Browser Performance Testing
...
@@ -233,7 +234,8 @@ Auto Browser Performance Testing utilizes the [Sitespeed.io container](https://h
...
@@ -233,7 +234,8 @@ Auto Browser Performance Testing utilizes the [Sitespeed.io container](https://h
/direction
/direction
```
```
In GitLab Enterprise Edition Premium, performance differences between the source and target branches are [shown in the merge request widget](https://docs.gitlab.com/ee/user/project/merge_requests/browser_performance_testing.html).
In GitLab Enterprise Edition Premium, performance differences between the source
and target branches are [shown in the merge request widget](../../user/project/merge_requests/browser_performance_testing.md).