2020-01-01 13:55:28 +05:30
---
type: reference, howto
2020-06-23 00:09:42 +05:30
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
2020-01-01 13:55:28 +05:30
---
# Security Configuration **(ULTIMATE)**
2020-03-13 15:44:24 +05:30
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/20711) in [GitLab Ultimate](https://about.gitlab.com/pricing/) 12.6.
2020-01-01 13:55:28 +05:30
2020-10-24 23:57:45 +05:30
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.
2020-01-01 13:55:28 +05:30
2020-10-24 23:57:45 +05:30
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 ).
2020-01-01 13:55:28 +05:30
2020-07-28 23:09:34 +05:30
NOTE: **Note:**
If the latest pipeline used [Auto DevOps ](../../../topics/autodevops/index.md ),
2020-10-24 23:57:45 +05:30
all security features are configured by default.
2020-01-01 13:55:28 +05:30
2020-10-24 23:57:45 +05:30
## View Security Configuration
2020-01-01 13:55:28 +05:30
2020-10-24 23:57:45 +05:30
To view a project's security configuration:
2020-07-28 23:09:34 +05:30
2020-10-24 23:57:45 +05:30
1. Go to the project's home page.
1. In the left sidebar, go to **Security & Configuration** > **Configuration** .
