From b3f4558a102c55d4d145f33e31369baec0114384 Mon Sep 17 00:00:00 2001
From: Harjeet Sharma <hsharma@gitlab.com>
Date: Thu, 18 Jan 2024 07:21:56 +0000
Subject: [PATCH] Fixes to bug in misconfigured project/group settings tier

---
 doc/security/responding_to_security_incidents.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/security/responding_to_security_incidents.md b/doc/security/responding_to_security_incidents.md
index 6a7ff884449d..10d8176fe1b7 100644
--- a/doc/security/responding_to_security_incidents.md
+++ b/doc/security/responding_to_security_incidents.md
@@ -147,7 +147,7 @@ If you suspect that your GitLab instance has been compromised, you should:
 
 Review [system access audit events](../administration/audit_event_streaming/audit_event_types.md#system-access) to determine any changes related to system settings, user permissions and user login events.
 
-### Misconfigured project or group settings **(ULTIMATE PREMIUM)**
+### Misconfigured project or group settings **(PREMIUM ALL)**
 
 Security incidents can occur as a result of improperly configured project or group settings, potentially leading to unauthorized access to sensitive or proprietary data. These incidents may include but are not limited to:
 
-- 
GitLab