2019-12-06 16:07:54 -05:00
---
type: reference, howto
2020-05-26 14:08:20 -04:00
stage: Secure
group: Static Analysis
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers
2019-12-06 16:07:54 -05:00
---
# Security Configuration **(ULTIMATE)**
2020-02-06 10:09:11 -05:00
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/20711) in [GitLab Ultimate](https://about.gitlab.com/pricing/) 12.6.
2019-12-06 16:07:54 -05:00
2020-08-17 17:09:56 -04:00
The Security Configuration page displays the configuration state of each security feature in the
current project. The page uses the project's latest default branch [CI pipeline ](../../../ci/pipelines/index.md )
to determine each feature's configuration state. If a job with the expected security report artifact
exists in the pipeline, the feature is considered enabled.
2019-12-06 16:07:54 -05:00
2020-08-17 17:09:56 -04:00
You can only enable SAST from the Security Configuration page. Documentation links are included for
the other features. For details about configuring SAST, see [Configure SAST in the UI ](../sast/index.md#configure-sast-in-the-ui ).
2019-12-06 16:07:54 -05:00
2020-07-16 02:09:33 -04:00
NOTE: **Note:**
2020-07-16 20:09:37 -04:00
If the latest pipeline used [Auto DevOps ](../../../topics/autodevops/index.md ),
2020-08-17 17:09:56 -04:00
all security features are configured by default.
2020-08-11 11:10:08 -04:00
2020-08-17 17:09:56 -04:00
## View Security Configuration
2019-12-06 16:07:54 -05:00
2020-08-17 17:09:56 -04:00
To view a project's security configuration:
2020-07-16 11:09:38 -04:00
2020-08-17 17:09:56 -04:00
1. Go to the project's home page.
2020-08-25 23:10:11 -04:00
1. In the left sidebar, go to **Security & Compliance** > **Configuration** .
