diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2021-05-14 09:10:55 +0300 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2021-05-14 09:10:55 +0300 |
commit | 94a191f3d969724031efb9b15cdfd97a5af6defa (patch) | |
tree | 0dd612d29eea8ef5f694097787c9302223f69391 /doc/administration/compliance.md | |
parent | 67cc693c9a96f565da999550f4f3a4906ce43e85 (diff) |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/administration/compliance.md')
-rw-r--r-- | doc/administration/compliance.md | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/doc/administration/compliance.md b/doc/administration/compliance.md index 04369a76fb3..77174bf327f 100644 --- a/doc/administration/compliance.md +++ b/doc/administration/compliance.md @@ -27,3 +27,5 @@ relevant compliance standards. |**[Auditor users](auditor_users.md)**<br>Auditor users are users who are given read-only access to all projects, groups, and other resources on the GitLab instance.|Premium+||Instance| |**[Credentials inventory](../user/admin_area/credentials_inventory.md)**<br>With a credentials inventory, GitLab administrators can keep track of the credentials used by all of the users in their GitLab instance. |Ultimate||Instance| |**Separation of Duties using [Protected branches](../user/project/protected_branches.md#protected-branches-approval-by-code-owners) and [custom CI Configuration Paths](../ci/pipelines/settings.md#custom-cicd-configuration-path)**<br> GitLab Premium users can leverage the GitLab cross-project YAML configurations to define deployers of code and developers of code. View the [Separation of Duties Deploy Project](https://gitlab.com/guided-explorations/separation-of-duties-deploy/blob/master/README.md) and [Separation of Duties Project](https://gitlab.com/guided-explorations/separation-of-duties/blob/master/README.md) to see how to use this set up to define these roles.|Premium+|✓|Project| +|**[Compliance frameworks](../user/project/settings/index.md#compliance-frameworks)**<br>Create a custom compliance framework at the group level to describe the type of compliance requirements any child project needs to follow. |Premium+|✓|Group| +|**[Compliance pipelines](../user/project/settings/index.md#compliance-pipeline-configuration)**<br>Define a pipeline configuration to run for any projects with a given compliance framework.|Ultimate|✓|Group| |