diff options
Diffstat (limited to 'doc/security/responding_to_security_incidents.md')
| -rw-r--r-- | doc/security/responding_to_security_incidents.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/security/responding_to_security_incidents.md b/doc/security/responding_to_security_incidents.md index 5c00c53c5bf..0cd7170d35b 100644 --- a/doc/security/responding_to_security_incidents.md +++ b/doc/security/responding_to_security_incidents.md @@ -14,7 +14,7 @@ additional steps. These suggestions are intended to supplement existing security If you suspect that a user account or bot account has been compromised, consider taking the following steps: -- [Block the user](../user/admin_area/moderate_users.md#block-a-user) to mitigate any current risk. +- [Block the user](../administration/moderate_users.md#block-a-user) to mitigate any current risk. - [Review the audit events](../administration/audit_events.md) available to you to identify any suspicious account behavior. For example: - Suspicious sign-in events. @@ -44,8 +44,8 @@ hosts in accordance with vendor guidance. If you suspect that your GitLab instance has been compromised, consider taking the following steps: - [Review the audit events](../administration/audit_events.md) available to you for suspicious account behavior. -- [Review all users](../user/admin_area/moderate_users.md) (including the Administrative root user), and follow the steps in [Suspected compromised user account](#suspected-compromised-user-account) if necessary. -- Review the [Credentials Inventory](../user/admin_area/credentials_inventory.md), if available to you. +- [Review all users](../administration/moderate_users.md) (including the Administrative root user), and follow the steps in [Suspected compromised user account](#suspected-compromised-user-account) if necessary. +- Review the [Credentials Inventory](../administration/credentials_inventory.md), if available to you. - Change any sensitive credentials, variables, tokens, and secrets. For example, those located in instance configuration, database, CI/CD pipelines, or elsewhere. - Upgrade to the latest version of GitLab and adopt a plan to upgrade after every security patch release. |