diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2023-12-07 03:08:33 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2023-12-07 03:08:33 +0300 |
| commit | c9a3dc1c2464a92a8f2a5c2f4f30883aa9f976f1 (patch) | |
| tree | a56df6907c26f0aa59f2c6e211e0cc7aea61e026 /doc/security/responding_to_security_incidents.md | |
| parent | aa74b7b4c5f326e82fcd6bb681296dce435ea024 (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/security/responding_to_security_incidents.md')
| -rw-r--r-- | doc/security/responding_to_security_incidents.md | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/doc/security/responding_to_security_incidents.md b/doc/security/responding_to_security_incidents.md index e49903cc5a9..f99a1879b7a 100644 --- a/doc/security/responding_to_security_incidents.md +++ b/doc/security/responding_to_security_incidents.md @@ -9,6 +9,10 @@ info: To determine the technical writer assigned to the Stage/Group associated w When a security incident occurs, you should follow the processes defined by your organization. However, you might consider some additional steps. These suggestions are intended to supplement existing security incident response processes within your organization. +Administrators can choose to +[provide public security contact information](../administration/settings/security_contact_information.md) +to support receiving reports of security issues from security researchers. + ## Suspected compromised user account If you suspect that a user account or bot account has been compromised, consider taking the following steps: |