diff --git a/.apigentools-info b/.apigentools-info
index a8768bc70d..479e708ef7 100644
--- a/.apigentools-info
+++ b/.apigentools-info
@@ -4,13 +4,13 @@
     "spec_versions": {
         "v1": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2024-01-26 20:57:00.588070",
-            "spec_repo_commit": "a1db94fd"
+            "regenerated": "2024-01-30 13:10:11.080986",
+            "spec_repo_commit": "ca2ada97"
         },
         "v2": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2024-01-26 20:57:00.671832",
-            "spec_repo_commit": "a1db94fd"
+            "regenerated": "2024-01-30 13:10:11.098730",
+            "spec_repo_commit": "ca2ada97"
         }
     }
 }
\ No newline at end of file
diff --git a/.generator/schemas/v2/openapi.yaml b/.generator/schemas/v2/openapi.yaml
index fccffb364a..f58a6b2872 100644
--- a/.generator/schemas/v2/openapi.yaml
+++ b/.generator/schemas/v2/openapi.yaml
@@ -17240,7 +17240,7 @@ components:
           description: 'Keyword list that will be checked during scanning in order
             to validate a match.
 
-            The number of keywords in the list must be less than or equal to 20.'
+            The number of keywords in the list must be lower or equal than 30.'
           example:
           - credit card
           - cc
diff --git a/src/datadog_api_client/v2/model/sensitive_data_scanner_included_keyword_configuration.py b/src/datadog_api_client/v2/model/sensitive_data_scanner_included_keyword_configuration.py
index 612f18feed..ecd02eba37 100644
--- a/src/datadog_api_client/v2/model/sensitive_data_scanner_included_keyword_configuration.py
+++ b/src/datadog_api_client/v2/model/sensitive_data_scanner_included_keyword_configuration.py
@@ -43,7 +43,7 @@ def __init__(self_, character_count: int, keywords: List[str], **kwargs):
         :type character_count: int
 
         :param keywords: Keyword list that will be checked during scanning in order to validate a match.
-            The number of keywords in the list must be less than or equal to 20.
+            The number of keywords in the list must be lower or equal than 30.
         :type keywords: [str]
         """
         super().__init__(kwargs)
diff --git a/tests/v2/features/sensitive_data_scanner.feature b/tests/v2/features/sensitive_data_scanner.feature
index 845632a082..57808d6657 100644
--- a/tests/v2/features/sensitive_data_scanner.feature
+++ b/tests/v2/features/sensitive_data_scanner.feature
@@ -8,14 +8,14 @@ Feature: Sensitive Data Scanner
     And a valid "appKeyAuth" key in the system
     And an instance of "SensitiveDataScanner" API
 
-  @generated @skip @team:DataDog/logs-app @team:DataDog/logs-core
+  @generated @skip @team:DataDog/logs-app @team:DataDog/sensitive-data-scanner
   Scenario: Create Scanning Group returns "Bad Request" response
     Given new "CreateScanningGroup" request
     And body with value {"data": {"attributes": {"filter": {}, "product_list": ["logs"]}, "relationships": {"configuration": {"data": {"type": "sensitive_data_scanner_configuration"}}, "rules": {"data": [{"type": "sensitive_data_scanner_rule"}]}}, "type": "sensitive_data_scanner_group"}, "meta": {"version": 0}}
     When the request is sent
     Then the response status is 400 Bad Request
 
-  @team:DataDog/logs-app @team:DataDog/logs-core
+  @team:DataDog/logs-app @team:DataDog/sensitive-data-scanner
   Scenario: Create Scanning Group returns "OK" response
     Given a valid "configuration" in the system
     And new "CreateScanningGroup" request
@@ -25,7 +25,7 @@ Feature: Sensitive Data Scanner
     And the response "data.type" is equal to "sensitive_data_scanner_group"
     And the response "data.attributes.name" is equal to "{{ unique }}"
 
-  @team:DataDog/logs-app @team:DataDog/logs-core
+  @team:DataDog/logs-app @team:DataDog/sensitive-data-scanner
   Scenario: Create Scanning Rule returns "Bad Request" response
     Given a valid "configuration" in the system
     And there is a valid "scanning_group" in the system
@@ -34,7 +34,7 @@ Feature: Sensitive Data Scanner
     When the request is sent
     Then the response status is 400 Bad Request
 
-  @team:DataDog/logs-app @team:DataDog/logs-core
+  @team:DataDog/logs-app @team:DataDog/sensitive-data-scanner
   Scenario: Create Scanning Rule returns "OK" response
     Given a valid "configuration" in the system
     And there is a valid "scanning_group" in the system
@@ -48,7 +48,7 @@ Feature: Sensitive Data Scanner
     And the response "data.attributes.included_keyword_configuration.character_count" is equal to 35
     And the response "data.attributes.included_keyword_configuration.keywords[0]" is equal to "credit card"
 
-  @generated @skip @team:DataDog/logs-app @team:DataDog/logs-core
+  @generated @skip @team:DataDog/logs-app @team:DataDog/sensitive-data-scanner
   Scenario: Delete Scanning Group returns "Bad Request" response
     Given new "DeleteScanningGroup" request
     And request contains "group_id" parameter from "REPLACE.ME"
@@ -56,7 +56,7 @@ Feature: Sensitive Data Scanner
     When the request is sent
     Then the response status is 400 Bad Request
 
-  @generated @skip @team:DataDog/logs-app @team:DataDog/logs-core
+  @generated @skip @team:DataDog/logs-app @team:DataDog/sensitive-data-scanner
   Scenario: Delete Scanning Group returns "Not Found" response
     Given new "DeleteScanningGroup" request
     And request contains "group_id" parameter from "REPLACE.ME"
@@ -64,7 +64,7 @@ Feature: Sensitive Data Scanner
     When the request is sent
     Then the response status is 404 Not Found
 
-  @team:DataDog/logs-app @team:DataDog/logs-core
+  @team:DataDog/logs-app @team:DataDog/sensitive-data-scanner
   Scenario: Delete Scanning Group returns "OK" response
     Given a valid "configuration" in the system
     And there is a valid "scanning_group" in the system
@@ -74,7 +74,7 @@ Feature: Sensitive Data Scanner
     When the request is sent
     Then the response status is 200 OK
 
-  @generated @skip @team:DataDog/logs-app @team:DataDog/logs-core
+  @generated @skip @team:DataDog/logs-app @team:DataDog/sensitive-data-scanner
   Scenario: Delete Scanning Rule returns "Bad Request" response
     Given new "DeleteScanningRule" request
     And request contains "rule_id" parameter from "REPLACE.ME"
@@ -82,7 +82,7 @@ Feature: Sensitive Data Scanner
     When the request is sent
     Then the response status is 400 Bad Request
 
-  @generated @skip @team:DataDog/logs-app @team:DataDog/logs-core
+  @generated @skip @team:DataDog/logs-app @team:DataDog/sensitive-data-scanner
   Scenario: Delete Scanning Rule returns "Not Found" response
     Given new "DeleteScanningRule" request
     And request contains "rule_id" parameter from "REPLACE.ME"
@@ -90,7 +90,7 @@ Feature: Sensitive Data Scanner
     When the request is sent
     Then the response status is 404 Not Found
 
-  @team:DataDog/logs-app @team:DataDog/logs-core
+  @team:DataDog/logs-app @team:DataDog/sensitive-data-scanner
   Scenario: Delete Scanning Rule returns "OK" response
     Given a valid "configuration" in the system
     And there is a valid "scanning_group" in the system
@@ -101,13 +101,13 @@ Feature: Sensitive Data Scanner
     When the request is sent
     Then the response status is 200 OK
 
-  @generated @skip @team:DataDog/logs-app @team:DataDog/logs-core
+  @generated @skip @team:DataDog/logs-app @team:DataDog/sensitive-data-scanner
   Scenario: List Scanning Groups returns "Bad Request" response
     Given new "ListScanningGroups" request
     When the request is sent
     Then the response status is 400 Bad Request
 
-  @team:DataDog/logs-app @team:DataDog/logs-core
+  @team:DataDog/logs-app @team:DataDog/sensitive-data-scanner
   Scenario: List Scanning Groups returns "OK" response
     Given a valid "configuration" in the system
     And there is a valid "scanning_group" in the system
@@ -116,19 +116,19 @@ Feature: Sensitive Data Scanner
     Then the response status is 200 OK
     And the response "included" has item with field "id" with value "{{ group.data.id }}"
 
-  @generated @skip @team:DataDog/logs-app @team:DataDog/logs-core
+  @generated @skip @team:DataDog/logs-app @team:DataDog/sensitive-data-scanner
   Scenario: List standard patterns returns "Bad Request" response
     Given new "ListStandardPatterns" request
     When the request is sent
     Then the response status is 400 Bad Request
 
-  @integration-only @team:DataDog/logs-app @team:DataDog/logs-core
+  @integration-only @team:DataDog/logs-app @team:DataDog/sensitive-data-scanner
   Scenario: List standard patterns returns "OK" response
     Given new "ListStandardPatterns" request
     When the request is sent
     Then the response status is 200 OK
 
-  @team:DataDog/logs-app @team:DataDog/logs-core
+  @team:DataDog/logs-app @team:DataDog/sensitive-data-scanner
   Scenario: Reorder Groups returns "Bad Request" response
     Given a valid "configuration" in the system
     And there is a valid "scanning_group" in the system
@@ -137,7 +137,7 @@ Feature: Sensitive Data Scanner
     When the request is sent
     Then the response status is 400 Bad Request
 
-  @replay-only @team:DataDog/logs-app @team:DataDog/logs-core
+  @replay-only @team:DataDog/logs-app @team:DataDog/sensitive-data-scanner
   Scenario: Reorder Groups returns "OK" response
     Given a valid "configuration" in the system
     And there is a valid "scanning_group" in the system
@@ -146,7 +146,7 @@ Feature: Sensitive Data Scanner
     When the request is sent
     Then the response status is 200 OK
 
-  @generated @skip @team:DataDog/logs-app @team:DataDog/logs-core
+  @generated @skip @team:DataDog/logs-app @team:DataDog/sensitive-data-scanner
   Scenario: Update Scanning Group returns "Bad Request" response
     Given new "UpdateScanningGroup" request
     And request contains "group_id" parameter from "REPLACE.ME"
@@ -154,7 +154,7 @@ Feature: Sensitive Data Scanner
     When the request is sent
     Then the response status is 400 Bad Request
 
-  @generated @skip @team:DataDog/logs-app @team:DataDog/logs-core
+  @generated @skip @team:DataDog/logs-app @team:DataDog/sensitive-data-scanner
   Scenario: Update Scanning Group returns "Not Found" response
     Given new "UpdateScanningGroup" request
     And request contains "group_id" parameter from "REPLACE.ME"
@@ -162,7 +162,7 @@ Feature: Sensitive Data Scanner
     When the request is sent
     Then the response status is 404 Not Found
 
-  @team:DataDog/logs-app @team:DataDog/logs-core
+  @team:DataDog/logs-app @team:DataDog/sensitive-data-scanner
   Scenario: Update Scanning Group returns "OK" response
     Given a valid "configuration" in the system
     And there is a valid "scanning_group" in the system
@@ -172,7 +172,7 @@ Feature: Sensitive Data Scanner
     When the request is sent
     Then the response status is 200 OK
 
-  @team:DataDog/logs-app @team:DataDog/logs-core
+  @team:DataDog/logs-app @team:DataDog/sensitive-data-scanner
   Scenario: Update Scanning Rule returns "Bad Request" response
     Given a valid "configuration" in the system
     And there is a valid "scanning_group" in the system
@@ -183,7 +183,7 @@ Feature: Sensitive Data Scanner
     When the request is sent
     Then the response status is 400 Bad Request
 
-  @generated @skip @team:DataDog/logs-app @team:DataDog/logs-core
+  @generated @skip @team:DataDog/logs-app @team:DataDog/sensitive-data-scanner
   Scenario: Update Scanning Rule returns "Not Found" response
     Given new "UpdateScanningRule" request
     And request contains "rule_id" parameter from "REPLACE.ME"
@@ -191,7 +191,7 @@ Feature: Sensitive Data Scanner
     When the request is sent
     Then the response status is 404 Not Found
 
-  @team:DataDog/logs-app @team:DataDog/logs-core
+  @team:DataDog/logs-app @team:DataDog/sensitive-data-scanner
   Scenario: Update Scanning Rule returns "OK" response
     Given a valid "configuration" in the system
     And there is a valid "scanning_group" in the system