diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-11-23 09:09:38 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-11-23 09:09:38 +0300 |
| commit | 45205f0db533235111ac4e14032b395e76b526be (patch) | |
| tree | efc32f75692424f5b9228b9135ae916238dccf0f /doc/user/application_security/secret_detection | |
| parent | a0ebcf42d29ee1272f2ebcbbde900b4832a241a2 (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/user/application_security/secret_detection')
| -rw-r--r-- | doc/user/application_security/secret_detection/index.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/user/application_security/secret_detection/index.md b/doc/user/application_security/secret_detection/index.md index 025a37f684d..5eba0fa44ba 100644 --- a/doc/user/application_security/secret_detection/index.md +++ b/doc/user/application_security/secret_detection/index.md @@ -128,7 +128,7 @@ always take the latest Secret Detection artifact available. ### Post-processing -> [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/46390) in GitLab 13.6. +> [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/4639) in GitLab 13.6. Upon detection of a secret, GitLab supports post processing hooks. These can be used to take actions like notifying the cloud service who issued the secret. The cloud provider can confirm the credentials and take remediation actions like revoking or reissuing a new secret and notifying the creator of the secret. Post-processing workflows vary by supported cloud providers. |