Security Configuration

Version history

The Security Configuration page displays what security scans are available, links to documentation and also simple enablement tools for the current project.

To view a project’s security configuration, go to the project’s home page, then in the left sidebar go to Security & Compliance > Configuration.

For each security control the page displays:

  • Its name, description and a documentation link.
  • Whether or not it is available.
  • A configuration button or a link to its configuration guide.

Security testing

You can configure the following security controls:

  • Auto DevOps
    • Click Enable Auto DevOps on the alert to enable it for the current project. For more details, see Auto DevOps.
  • SAST
  • DAST
    • Click Enable DAST to use DAST for the current Project. To manage the available DAST profiles used for on-demand scans Click Manage Scans. For more details, see DAST on-demand scans.
  • Dependency Scanning
  • Container Scanning
  • Cluster Image Scanning
  • Secret Detection
  • API Fuzzing
    • Click Enable API Fuzzing to use API Fuzzing for the current Project. For more details, see API Fuzzing.
  • Coverage Fuzzing

Status

Version history

The status of each security control is determined by the project’s latest default branch CI pipeline. If a job with the expected security report artifact exists in the pipeline, the feature’s status is enabled.

If the latest pipeline used Auto DevOps, all security features are configured by default.

Click View history to see the .gitlab-ci.yml file’s history.

Compliance

You can configure the following security controls:

  • License Compliance