From 59d96dbbed5584782343478fc8f72fbd8c2d6ec7 Mon Sep 17 00:00:00 2001
From: natasha-moore-elastic
 <137783811+natasha-moore-elastic@users.noreply.github.com>
Date: Thu, 12 Dec 2024 16:53:29 +0000
Subject: [PATCH] [DOCS] Adds conceptual content to API docs (#202305)

## Summary

Resolves https://github.com/elastic/security-docs-internal/issues/49.

In order to retire asciidoc API docs, we first need to move over any
relevant content from those docs to the API reference site. This PR adds
the relevant conceptual information from:

-
https://www.elastic.co/guide/en/security/master/exceptions-api-overview.html
-
https://www.elastic.co/guide/en/security/master/lists-api-overview.html
- https://www.elastic.co/guide/en/security/master/rule-api-overview.html

### Previews:
Bump previews expire after 30min, so I'm providing screenshots below:

Detections preview:

![detections_preview](https://github.com/user-attachments/assets/c47b9d85-b5d0-4a32-8668-dc1ae2215681)

Exceptions preview:

![exceptions_preview](https://github.com/user-attachments/assets/b3fe9139-2162-4c56-bba9-751dffa11cb4)

Lists preview:

![lists_preview](https://github.com/user-attachments/assets/1c714f17-825d-45c7-8112-cc3d25c51047)

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
(cherry picked from commit cebcf01d35b84308e1ca9eabed694864a9e39ed9)

# Conflicts:
#	oas_docs/output/kibana.serverless.yaml
#	packages/kbn-securitysolution-lists-common/docs/openapi/ess/security_solution_lists_api_2023_10_31.bundled.schema.yaml
#	packages/kbn-securitysolution-lists-common/docs/openapi/serverless/security_solution_lists_api_2023_10_31.bundled.schema.yaml
---
 oas_docs/output/kibana.yaml                   | 68 ++++++++++++++++-
 ...eptions_api_2023_10_31.bundled.schema.yaml | 54 ++++++++++++-
 ...eptions_api_2023_10_31.bundled.schema.yaml | 54 ++++++++++++-
 .../scripts/openapi_bundle.js                 | 32 +-------
 .../exceptions_ess.info.yaml                  | 26 +++++++
 .../exceptions_serverless.info.yaml           | 26 +++++++
 ...n_lists_api_2023_10_31.bundled.schema.yaml | 75 ++++++++++++++++++-
 ...n_lists_api_2023_10_31.bundled.schema.yaml | 75 ++++++++++++++++++-
 .../scripts/openapi_bundle.js                 | 30 +-------
 .../openapi_bundle_info/lists_ess.info.yaml   | 49 ++++++++++++
 .../lists_serverless.info.yaml                | 49 ++++++++++++
 ...ections_api_2023_10_31.bundled.schema.yaml | 28 +++++--
 ...ections_api_2023_10_31.bundled.schema.yaml | 28 +++++--
 .../scripts/openapi/bundle_detections.js      | 38 ++--------
 .../detections_ess.info.yaml                  | 14 ++++
 .../detections_serverless.info.yaml           | 14 ++++
 16 files changed, 545 insertions(+), 115 deletions(-)
 create mode 100644 packages/kbn-securitysolution-exceptions-common/scripts/openapi_bundle_info/exceptions_ess.info.yaml
 create mode 100644 packages/kbn-securitysolution-exceptions-common/scripts/openapi_bundle_info/exceptions_serverless.info.yaml
 create mode 100644 packages/kbn-securitysolution-lists-common/scripts/openapi_bundle_info/lists_ess.info.yaml
 create mode 100644 packages/kbn-securitysolution-lists-common/scripts/openapi_bundle_info/lists_serverless.info.yaml
 create mode 100644 x-pack/plugins/security_solution/scripts/openapi/bundle_detections_info/detections_ess.info.yaml
 create mode 100644 x-pack/plugins/security_solution/scripts/openapi/bundle_detections_info/detections_serverless.info.yaml

diff --git a/oas_docs/output/kibana.yaml b/oas_docs/output/kibana.yaml
index 98dd14d116985..a78e7066126df 100644
--- a/oas_docs/output/kibana.yaml
+++ b/oas_docs/output/kibana.yaml
@@ -120,7 +120,12 @@ tags:
   - description: Manage and interact with Security Assistant resources.
     name: Security AI Assistant API
     x-displayName: Security AI assistant
-  - description: You can create rules that automatically turn events and external alerts sent to Elastic Security into detection alerts. These alerts are displayed on the Detections page.
+  - description: |
+      Use the detections APIs to create and manage detection rules. Detection rules search events and external alerts sent to Elastic Security and generate detection alerts from any hits. Alerts are displayed on the **Alerts** page and can be assigned and triaged, using the alert status to mark them as open, closed, or acknowledged.
+      > warn
+      > If the API key used for authorization has different privileges than the key that created or most recently updated a rule, the rule behavior might change.
+
+      > If the API key that created a rule is deleted, or the user that created the rule becomes inactive, the rule will stop running.
     name: Security Detections API
     x-displayName: Security detections
   - description: Endpoint Exceptions API allows you to manage detection rule endpoint exceptions to prevent a rule from generating an alert from incoming events even when the rule's other criteria are met.
@@ -132,10 +137,67 @@ tags:
   - description: ''
     name: Security Entity Analytics API
     x-displayName: Security entity analytics
-  - description: Exceptions API allows you to manage detection rule exceptions to prevent a rule from generating an alert from incoming events even when the rule's other criteria are met.
+  - description: |
+      Exceptions are associated with detection and endpoint rules, and are used to prevent a rule from generating an alert from incoming events, even when the rule's other criteria are met. They can help reduce the number of false positives and prevent trusted processes and network activity from generating unnecessary alerts.
+
+      Exceptions are made up of:
+
+      * **Exception containers**: A container for related exceptions. Generally, a single exception container contains all the exception items relevant for a subset of rules. For example, a container can be used to group together network-related exceptions that are relevant for a large number of network rules. The container can then be associated with all the relevant rules.
+      * **Exception items**: The query (fields, values, and logic) used to prevent rules from generating alerts. When an exception item's query evaluates to `true`, the rule does not generate an alert.
+
+      For detection rules, you can also use lists to define rule exceptions. A list holds multiple values of the same Elasticsearch data type, such as IP addresses. These values are used to determine when an exception prevents an alert from being generated.
+      > info
+      > You cannot use lists with endpoint rule exceptions.
+
+      > info
+      > Only exception containers can be associated with rules. You cannot directly associate an exception item or a list container with a rule. To use list exceptions, create an exception item that references the relevant list container.
+
+      ## Exceptions requirements
+
+      Before you can start working with exceptions that use value lists, you must create the `.lists` and `.items` data streams for the relevant Kibana space. To do this, use the [Create list data streams](../operation/operation-createlistindex) endpoint. Once these data streams are created, your role needs privileges to manage rules. For a complete list of requirements, refer to [Enable and access detections](https://www.elastic.co/guide/en/security/current/detections-permissions-section.html#enable-detections-ui).
     name: Security Exceptions API
     x-displayName: Security exceptions
-  - description: Lists API allows you to manage lists of keywords, IPs or IP ranges items.
+  - description: |
+      Lists can be used with detection rule exceptions to define values that prevent a rule from generating alerts.
+
+      Lists are made up of:
+
+      * **List containers**: A container for values of the same Elasticsearch data type. The following data types can be used:
+          * `boolean`
+          * `byte`
+          * `date`
+          * `date_nanos`
+          * `date_range`
+          * `double`
+          * `double_range`
+          * `float`
+          * `float_range`
+          * `half_float`
+          * `integer`
+          * `integer_range`
+          * `ip`
+          * `ip_range`
+          * `keyword`
+          * `long`
+          * `long_range`
+          * `short`
+          * `text`
+      * **List items**: The values used to determine whether the exception prevents an alert from being generated.
+
+      All list items in the same list container must be of the same data type, and each item defines a single value. For example, an IP list container named `internal-ip-addresses-southport` contains five items, where each item defines one internal IP address:
+      1. `192.168.1.1`
+      2. `192.168.1.3`
+      3. `192.168.1.18`
+      4. `192.168.1.12`
+      5. `192.168.1.7`
+
+      To use these IP addresses as values for defining rule exceptions, use the Security exceptions API to [create an exception list item](../operation/operation-createexceptionlistitem) that references the `internal-ip-addresses-southport` list.
+      > info
+      > Lists cannot be added directly to rules, nor do they define the operators used to determine when exceptions are applied (`is in list`, `is not in list`). Use an exception item to define the operator and associate it with an [exception container](../operation/operation-createexceptionlist). You can then add the exception container to a rule's `exceptions_list` object.
+
+      ## Lists requirements
+
+      Before you can start using lists, you must create the `.lists` and `.items` data streams for the relevant Kibana space. To do this, use the [Create list data streams](../operation/operation-createlistindex) endpoint. Once these data streams are created, your role needs privileges to manage rules. Refer to [Enable and access detections](https://www.elastic.co/guide/en/security/current/detections-permissions-section.html#enable-detections-ui) for a complete list of requirements.
     name: Security Lists API
     x-displayName: Security lists
   - description: Run live queries, manage packs and saved queries.
diff --git a/packages/kbn-securitysolution-exceptions-common/docs/openapi/ess/security_solution_exceptions_api_2023_10_31.bundled.schema.yaml b/packages/kbn-securitysolution-exceptions-common/docs/openapi/ess/security_solution_exceptions_api_2023_10_31.bundled.schema.yaml
index ac08ffe99ef3a..270c977c377a2 100644
--- a/packages/kbn-securitysolution-exceptions-common/docs/openapi/ess/security_solution_exceptions_api_2023_10_31.bundled.schema.yaml
+++ b/packages/kbn-securitysolution-exceptions-common/docs/openapi/ess/security_solution_exceptions_api_2023_10_31.bundled.schema.yaml
@@ -1853,9 +1853,55 @@ components:
 security:
   - BasicAuth: []
 tags:
-  - description: >-
-      Exceptions API allows you to manage detection rule exceptions to prevent a
-      rule from generating an alert from incoming events even when the rule's
-      other criteria are met.
+  - description: >
+      Exceptions are associated with detection and endpoint rules, and are used
+      to prevent a rule from generating an alert from incoming events, even when
+      the rule's other criteria are met. They can help reduce the number of
+      false positives and prevent trusted processes and network activity from
+      generating unnecessary alerts.
+
+
+      Exceptions are made up of:
+
+
+      * **Exception containers**: A container for related exceptions. Generally,
+      a single exception container contains all the exception items relevant for
+      a subset of rules. For example, a container can be used to group together
+      network-related exceptions that are relevant for a large number of network
+      rules. The container can then be associated with all the relevant rules.
+
+      * **Exception items**: The query (fields, values, and logic) used to
+      prevent rules from generating alerts. When an exception item's query
+      evaluates to `true`, the rule does not generate an alert.
+
+
+      For detection rules, you can also use lists to define rule exceptions. A
+      list holds multiple values of the same Elasticsearch data type, such as IP
+      addresses. These values are used to determine when an exception prevents
+      an alert from being generated.
+
+      > info
+
+      > You cannot use lists with endpoint rule exceptions.
+
+
+      > info
+
+      > Only exception containers can be associated with rules. You cannot
+      directly associate an exception item or a list container with a rule. To
+      use list exceptions, create an exception item that references the relevant
+      list container.
+
+
+      ## Exceptions requirements
+
+
+      Before you can start working with exceptions that use value lists, you
+      must create the `.lists` and `.items` data streams for the relevant Kibana
+      space. To do this, use the [Create list data
+      streams](../operation/operation-createlistindex) endpoint. Once these data
+      streams are created, your role needs privileges to manage rules. For a
+      complete list of requirements, refer to [Enable and access
+      detections](https://www.elastic.co/guide/en/security/current/detections-permissions-section.html#enable-detections-ui).
     name: Security Exceptions API
     x-displayName: Security exceptions
diff --git a/packages/kbn-securitysolution-exceptions-common/docs/openapi/serverless/security_solution_exceptions_api_2023_10_31.bundled.schema.yaml b/packages/kbn-securitysolution-exceptions-common/docs/openapi/serverless/security_solution_exceptions_api_2023_10_31.bundled.schema.yaml
index 3ec5d97ca8eec..ec250e4643ed0 100644
--- a/packages/kbn-securitysolution-exceptions-common/docs/openapi/serverless/security_solution_exceptions_api_2023_10_31.bundled.schema.yaml
+++ b/packages/kbn-securitysolution-exceptions-common/docs/openapi/serverless/security_solution_exceptions_api_2023_10_31.bundled.schema.yaml
@@ -1853,9 +1853,55 @@ components:
 security:
   - BasicAuth: []
 tags:
-  - description: >-
-      Exceptions API allows you to manage detection rule exceptions to prevent a
-      rule from generating an alert from incoming events even when the rule's
-      other criteria are met.
+  - description: >
+      Exceptions are associated with detection and endpoint rules, and are used
+      to prevent a rule from generating an alert from incoming events, even when
+      the rule's other criteria are met. They can help reduce the number of
+      false positives and prevent trusted processes and network activity from
+      generating unnecessary alerts.
+
+
+      Exceptions are made up of:
+
+
+      * **Exception containers**: A container for related exceptions. Generally,
+      a single exception container contains all the exception items relevant for
+      a subset of rules. For example, a container can be used to group together
+      network-related exceptions that are relevant for a large number of network
+      rules. The container can then be associated with all the relevant rules.
+
+      * **Exception items**: The query (fields, values, and logic) used to
+      prevent rules from generating alerts. When an exception item's query
+      evaluates to `true`, the rule does not generate an alert.
+
+
+      For detection rules, you can also use lists to define rule exceptions. A
+      list holds multiple values of the same Elasticsearch data type, such as IP
+      addresses. These values are used to determine when an exception prevents
+      an alert from being generated.
+
+      > info
+
+      > You cannot use lists with endpoint rule exceptions.
+
+
+      > info
+
+      > Only exception containers can be associated with rules. You cannot
+      directly associate an exception item or a list container with a rule. To
+      use list exceptions, create an exception item that references the relevant
+      list container.
+
+
+      ## Exceptions requirements
+
+
+      Before you can start working with exceptions that use value lists, you
+      must create the `.lists` and `.items` data streams for the relevant Kibana
+      space. To do this, use the [Create list data
+      streams](../operation/operation-createlistindex) endpoint. Once these data
+      streams are created, your role needs privileges to manage rules. For a
+      complete list of requirements, refer to [Enable and access
+      detections](https://www.elastic.co/guide/en/serverless/current/security-detections-requirements.html#enable-detections-ui).
     name: Security Exceptions API
     x-displayName: Security exceptions
diff --git a/packages/kbn-securitysolution-exceptions-common/scripts/openapi_bundle.js b/packages/kbn-securitysolution-exceptions-common/scripts/openapi_bundle.js
index 83c84d91daaf5..70299e56eac2e 100644
--- a/packages/kbn-securitysolution-exceptions-common/scripts/openapi_bundle.js
+++ b/packages/kbn-securitysolution-exceptions-common/scripts/openapi_bundle.js
@@ -22,21 +22,7 @@ const ROOT = resolve(__dirname, '..');
     ),
     options: {
       includeLabels: ['serverless'],
-      prototypeDocument: {
-        info: {
-          title: 'Security Exceptions API (Elastic Cloud Serverless)',
-          description:
-            "Exceptions API allows you to manage detection rule exceptions to prevent a rule from generating an alert from incoming events even when the rule's other criteria are met.",
-        },
-        tags: [
-          {
-            name: 'Security Exceptions API',
-            'x-displayName': 'Security exceptions',
-            description:
-              "Exceptions API allows you to manage detection rule exceptions to prevent a rule from generating an alert from incoming events even when the rule's other criteria are met.",
-          },
-        ],
-      },
+      prototypeDocument: join(ROOT, 'scripts/openapi_bundle_info/exceptions_serverless.info.yaml'),
     },
   });
 
@@ -48,21 +34,7 @@ const ROOT = resolve(__dirname, '..');
     ),
     options: {
       includeLabels: ['ess'],
-      prototypeDocument: {
-        info: {
-          title: 'Security Exceptions API (Elastic Cloud and self-hosted)',
-          description:
-            "Exceptions API allows you to manage detection rule exceptions to prevent a rule from generating an alert from incoming events even when the rule's other criteria are met.",
-        },
-        tags: [
-          {
-            name: 'Security Exceptions API',
-            'x-displayName': 'Security exceptions',
-            description:
-              "Exceptions API allows you to manage detection rule exceptions to prevent a rule from generating an alert from incoming events even when the rule's other criteria are met.",
-          },
-        ],
-      },
+      prototypeDocument: join(ROOT, 'scripts/openapi_bundle_info/exceptions_ess.info.yaml'),
     },
   });
 })();
diff --git a/packages/kbn-securitysolution-exceptions-common/scripts/openapi_bundle_info/exceptions_ess.info.yaml b/packages/kbn-securitysolution-exceptions-common/scripts/openapi_bundle_info/exceptions_ess.info.yaml
new file mode 100644
index 0000000000000..855870c444c7c
--- /dev/null
+++ b/packages/kbn-securitysolution-exceptions-common/scripts/openapi_bundle_info/exceptions_ess.info.yaml
@@ -0,0 +1,26 @@
+openapi: 3.0.3
+info:
+  title: "Security Exceptions API (Elastic Cloud and self-hosted)"
+  description: "Exceptions API allows you to manage detection rule exceptions to prevent a rule from generating an alert from incoming events even when the rule's other criteria are met."
+
+tags:
+  - name: "Security Exceptions API"
+    x-displayName: "Security exceptions"
+    description: |
+      Exceptions are associated with detection and endpoint rules, and are used to prevent a rule from generating an alert from incoming events, even when the rule's other criteria are met. They can help reduce the number of false positives and prevent trusted processes and network activity from generating unnecessary alerts.
+
+      Exceptions are made up of:
+
+      * **Exception containers**: A container for related exceptions. Generally, a single exception container contains all the exception items relevant for a subset of rules. For example, a container can be used to group together network-related exceptions that are relevant for a large number of network rules. The container can then be associated with all the relevant rules.
+      * **Exception items**: The query (fields, values, and logic) used to prevent rules from generating alerts. When an exception item's query evaluates to `true`, the rule does not generate an alert.
+
+      For detection rules, you can also use lists to define rule exceptions. A list holds multiple values of the same Elasticsearch data type, such as IP addresses. These values are used to determine when an exception prevents an alert from being generated.
+      > info
+      > You cannot use lists with endpoint rule exceptions.
+
+      > info
+      > Only exception containers can be associated with rules. You cannot directly associate an exception item or a list container with a rule. To use list exceptions, create an exception item that references the relevant list container.
+
+      ## Exceptions requirements
+
+      Before you can start working with exceptions that use value lists, you must create the `.lists` and `.items` data streams for the relevant Kibana space. To do this, use the [Create list data streams](../operation/operation-createlistindex) endpoint. Once these data streams are created, your role needs privileges to manage rules. For a complete list of requirements, refer to [Enable and access detections](https://www.elastic.co/guide/en/security/current/detections-permissions-section.html#enable-detections-ui).
diff --git a/packages/kbn-securitysolution-exceptions-common/scripts/openapi_bundle_info/exceptions_serverless.info.yaml b/packages/kbn-securitysolution-exceptions-common/scripts/openapi_bundle_info/exceptions_serverless.info.yaml
new file mode 100644
index 0000000000000..a8894d997be98
--- /dev/null
+++ b/packages/kbn-securitysolution-exceptions-common/scripts/openapi_bundle_info/exceptions_serverless.info.yaml
@@ -0,0 +1,26 @@
+openapi: 3.0.3
+info:
+  title: "Security Exceptions API (Elastic Cloud Serverless)"
+  description: "Exceptions API allows you to manage detection rule exceptions to prevent a rule from generating an alert from incoming events even when the rule's other criteria are met."
+
+tags:
+  - name: "Security Exceptions API"
+    x-displayName: "Security exceptions"
+    description: |
+      Exceptions are associated with detection and endpoint rules, and are used to prevent a rule from generating an alert from incoming events, even when the rule's other criteria are met. They can help reduce the number of false positives and prevent trusted processes and network activity from generating unnecessary alerts.
+
+      Exceptions are made up of:
+
+      * **Exception containers**: A container for related exceptions. Generally, a single exception container contains all the exception items relevant for a subset of rules. For example, a container can be used to group together network-related exceptions that are relevant for a large number of network rules. The container can then be associated with all the relevant rules.
+      * **Exception items**: The query (fields, values, and logic) used to prevent rules from generating alerts. When an exception item's query evaluates to `true`, the rule does not generate an alert.
+
+      For detection rules, you can also use lists to define rule exceptions. A list holds multiple values of the same Elasticsearch data type, such as IP addresses. These values are used to determine when an exception prevents an alert from being generated.
+      > info
+      > You cannot use lists with endpoint rule exceptions.
+
+      > info
+      > Only exception containers can be associated with rules. You cannot directly associate an exception item or a list container with a rule. To use list exceptions, create an exception item that references the relevant list container.
+
+      ## Exceptions requirements
+
+      Before you can start working with exceptions that use value lists, you must create the `.lists` and `.items` data streams for the relevant Kibana space. To do this, use the [Create list data streams](../operation/operation-createlistindex) endpoint. Once these data streams are created, your role needs privileges to manage rules. For a complete list of requirements, refer to [Enable and access detections](https://www.elastic.co/guide/en/serverless/current/security-detections-requirements.html#enable-detections-ui).
diff --git a/packages/kbn-securitysolution-lists-common/docs/openapi/ess/security_solution_lists_api_2023_10_31.bundled.schema.yaml b/packages/kbn-securitysolution-lists-common/docs/openapi/ess/security_solution_lists_api_2023_10_31.bundled.schema.yaml
index 708aacdd51e7c..28495aa3ddb35 100644
--- a/packages/kbn-securitysolution-lists-common/docs/openapi/ess/security_solution_lists_api_2023_10_31.bundled.schema.yaml
+++ b/packages/kbn-securitysolution-lists-common/docs/openapi/ess/security_solution_lists_api_2023_10_31.bundled.schema.yaml
@@ -1521,6 +1521,79 @@ components:
 security:
   - BasicAuth: []
 tags:
-  - description: 'Lists API allows you to manage lists of keywords, IPs or IP ranges items.'
+  - description: >
+      Lists can be used with detection rule exceptions to define values that
+      prevent a rule from generating alerts.
+
+
+      Lists are made up of:
+
+
+      * **List containers**: A container for values of the same Elasticsearch
+      data type. The following data types can be used:
+          * `boolean`
+          * `byte`
+          * `date`
+          * `date_nanos`
+          * `date_range`
+          * `double`
+          * `double_range`
+          * `float`
+          * `float_range`
+          * `half_float`
+          * `integer`
+          * `integer_range`
+          * `ip`
+          * `ip_range`
+          * `keyword`
+          * `long`
+          * `long_range`
+          * `short`
+          * `text`
+      * **List items**: The values used to determine whether the exception
+      prevents an alert from being generated.
+
+
+      All list items in the same list container must be of the same data type,
+      and each item defines a single value. For example, an IP list container
+      named `internal-ip-addresses-southport` contains five items, where each
+      item defines one internal IP address:
+
+      1. `192.168.1.1`
+
+      2. `192.168.1.3`
+
+      3. `192.168.1.18`
+
+      4. `192.168.1.12`
+
+      5. `192.168.1.7`
+
+
+      To use these IP addresses as values for defining rule exceptions, use the
+      Security exceptions API to [create an exception list
+      item](../operation/operation-createexceptionlistitem) that references the
+      `internal-ip-addresses-southport` list.
+
+      > info
+
+      > Lists cannot be added directly to rules, nor do they define the
+      operators used to determine when exceptions are applied (`is in list`, `is
+      not in list`). Use an exception item to define the operator and associate
+      it with an [exception
+      container](../operation/operation-createexceptionlist). You can then add
+      the exception container to a rule's `exceptions_list` object.
+
+
+      ## Lists requirements
+
+
+      Before you can start using lists, you must create the `.lists` and
+      `.items` data streams for the relevant Kibana space. To do this, use the
+      [Create list data streams](../operation/operation-createlistindex)
+      endpoint. Once these data streams are created, your role needs privileges
+      to manage rules. Refer to [Enable and access
+      detections](https://www.elastic.co/guide/en/security/current/detections-permissions-section.html#enable-detections-ui)
+      for a complete list of requirements.
     name: Security Lists API
     x-displayName: Security lists
diff --git a/packages/kbn-securitysolution-lists-common/docs/openapi/serverless/security_solution_lists_api_2023_10_31.bundled.schema.yaml b/packages/kbn-securitysolution-lists-common/docs/openapi/serverless/security_solution_lists_api_2023_10_31.bundled.schema.yaml
index 8f1374241e4c2..cb76238bc48dc 100644
--- a/packages/kbn-securitysolution-lists-common/docs/openapi/serverless/security_solution_lists_api_2023_10_31.bundled.schema.yaml
+++ b/packages/kbn-securitysolution-lists-common/docs/openapi/serverless/security_solution_lists_api_2023_10_31.bundled.schema.yaml
@@ -1521,6 +1521,79 @@ components:
 security:
   - BasicAuth: []
 tags:
-  - description: 'Lists API allows you to manage lists of keywords, IPs or IP ranges items.'
+  - description: >
+      Lists can be used with detection rule exceptions to define values that
+      prevent a rule from generating alerts.
+
+
+      Lists are made up of:
+
+
+      * **List containers**: A container for values of the same Elasticsearch
+      data type. The following data types can be used:
+          * `boolean`
+          * `byte`
+          * `date`
+          * `date_nanos`
+          * `date_range`
+          * `double`
+          * `double_range`
+          * `float`
+          * `float_range`
+          * `half_float`
+          * `integer`
+          * `integer_range`
+          * `ip`
+          * `ip_range`
+          * `keyword`
+          * `long`
+          * `long_range`
+          * `short`
+          * `text`
+      * **List items**: The values used to determine whether the exception
+      prevents an alert from being generated.
+
+
+      All list items in the same list container must be of the same data type,
+      and each item defines a single value. For example, an IP list container
+      named `internal-ip-addresses-southport` contains five items, where each
+      item defines one internal IP address:
+
+      1. `192.168.1.1`
+
+      2. `192.168.1.3`
+
+      3. `192.168.1.18`
+
+      4. `192.168.1.12`
+
+      5. `192.168.1.7`
+
+
+      To use these IP addresses as values for defining rule exceptions, use the
+      Security exceptions API to [create an exception list
+      item](../operation/operation-createexceptionlistitem) that references the
+      `internal-ip-addresses-southport` list.
+
+      > info
+
+      > Lists cannot be added directly to rules, nor do they define the
+      operators used to determine when exceptions are applied (`is in list`, `is
+      not in list`). Use an exception item to define the operator and associate
+      it with an [exception
+      container](../operation/operation-createexceptionlist). You can then add
+      the exception container to a rule's `exceptions_list` object.
+
+
+      ## Lists requirements
+
+
+      Before you can start using lists, you must create the `.lists` and
+      `.items` data streams for the relevant Kibana space. To do this, use the
+      [Create list data streams](../operation/operation-createlistindex)
+      endpoint. Once these data streams are created, your role needs privileges
+      to manage rules. Refer to [Enable and access
+      detections](https://www.elastic.co/guide/en/serverless/current/security-detections-requirements.html#enable-detections-ui)
+      for a complete list of requirements.
     name: Security Lists API
     x-displayName: Security lists
diff --git a/packages/kbn-securitysolution-lists-common/scripts/openapi_bundle.js b/packages/kbn-securitysolution-lists-common/scripts/openapi_bundle.js
index b8ea2ea2e8377..7a61724759178 100644
--- a/packages/kbn-securitysolution-lists-common/scripts/openapi_bundle.js
+++ b/packages/kbn-securitysolution-lists-common/scripts/openapi_bundle.js
@@ -22,20 +22,7 @@ const ROOT = resolve(__dirname, '..');
     ),
     options: {
       includeLabels: ['serverless'],
-      prototypeDocument: {
-        info: {
-          title: 'Security Lists API (Elastic Cloud Serverless)',
-          description: 'Lists API allows you to manage lists of keywords, IPs or IP ranges items.',
-        },
-        tags: [
-          {
-            name: 'Security Lists API',
-            'x-displayName': 'Security lists',
-            description:
-              'Lists API allows you to manage lists of keywords, IPs or IP ranges items.',
-          },
-        ],
-      },
+      prototypeDocument: join(ROOT, 'scripts/openapi_bundle_info/lists_serverless.info.yaml'),
     },
   });
 
@@ -47,20 +34,7 @@ const ROOT = resolve(__dirname, '..');
     ),
     options: {
       includeLabels: ['ess'],
-      prototypeDocument: {
-        info: {
-          title: 'Security Lists API (Elastic Cloud and self-hosted)',
-          description: 'Lists API allows you to manage lists of keywords, IPs or IP ranges items.',
-        },
-        tags: [
-          {
-            name: 'Security Lists API',
-            'x-displayName': 'Security lists',
-            description:
-              'Lists API allows you to manage lists of keywords, IPs or IP ranges items.',
-          },
-        ],
-      },
+      prototypeDocument: join(ROOT, 'scripts/openapi_bundle_info/lists_ess.info.yaml'),
     },
   });
 })();
diff --git a/packages/kbn-securitysolution-lists-common/scripts/openapi_bundle_info/lists_ess.info.yaml b/packages/kbn-securitysolution-lists-common/scripts/openapi_bundle_info/lists_ess.info.yaml
new file mode 100644
index 0000000000000..f2f528c8d7ba7
--- /dev/null
+++ b/packages/kbn-securitysolution-lists-common/scripts/openapi_bundle_info/lists_ess.info.yaml
@@ -0,0 +1,49 @@
+openapi: 3.0.3
+info:
+  title: "Security Lists API (Elastic Cloud and self-hosted)"
+  description: "Lists API allows you to manage lists of keywords, IPs or IP ranges items."
+
+tags:
+  - name: "Security Lists API"
+    x-displayName: "Security lists"
+    description: |
+      Lists can be used with detection rule exceptions to define values that prevent a rule from generating alerts.
+
+      Lists are made up of:
+
+      * **List containers**: A container for values of the same Elasticsearch data type. The following data types can be used:
+          * `boolean`
+          * `byte`
+          * `date`
+          * `date_nanos`
+          * `date_range`
+          * `double`
+          * `double_range`
+          * `float`
+          * `float_range`
+          * `half_float`
+          * `integer`
+          * `integer_range`
+          * `ip`
+          * `ip_range`
+          * `keyword`
+          * `long`
+          * `long_range`
+          * `short`
+          * `text`
+      * **List items**: The values used to determine whether the exception prevents an alert from being generated.
+
+      All list items in the same list container must be of the same data type, and each item defines a single value. For example, an IP list container named `internal-ip-addresses-southport` contains five items, where each item defines one internal IP address:
+      1. `192.168.1.1`
+      2. `192.168.1.3`
+      3. `192.168.1.18`
+      4. `192.168.1.12`
+      5. `192.168.1.7`
+
+      To use these IP addresses as values for defining rule exceptions, use the Security exceptions API to [create an exception list item](../operation/operation-createexceptionlistitem) that references the `internal-ip-addresses-southport` list.
+      > info
+      > Lists cannot be added directly to rules, nor do they define the operators used to determine when exceptions are applied (`is in list`, `is not in list`). Use an exception item to define the operator and associate it with an [exception container](../operation/operation-createexceptionlist). You can then add the exception container to a rule's `exceptions_list` object.
+
+      ## Lists requirements
+
+      Before you can start using lists, you must create the `.lists` and `.items` data streams for the relevant Kibana space. To do this, use the [Create list data streams](../operation/operation-createlistindex) endpoint. Once these data streams are created, your role needs privileges to manage rules. Refer to [Enable and access detections](https://www.elastic.co/guide/en/security/current/detections-permissions-section.html#enable-detections-ui) for a complete list of requirements.
diff --git a/packages/kbn-securitysolution-lists-common/scripts/openapi_bundle_info/lists_serverless.info.yaml b/packages/kbn-securitysolution-lists-common/scripts/openapi_bundle_info/lists_serverless.info.yaml
new file mode 100644
index 0000000000000..8f3245db29a99
--- /dev/null
+++ b/packages/kbn-securitysolution-lists-common/scripts/openapi_bundle_info/lists_serverless.info.yaml
@@ -0,0 +1,49 @@
+openapi: 3.0.3
+info:
+  title: "Security Lists API (Elastic Cloud Serverless)"
+  description: "Lists API allows you to manage lists of keywords, IPs or IP ranges items."
+
+tags:
+  - name: "Security Lists API"
+    x-displayName: "Security lists"
+    description: |
+      Lists can be used with detection rule exceptions to define values that prevent a rule from generating alerts.
+
+      Lists are made up of:
+
+      * **List containers**: A container for values of the same Elasticsearch data type. The following data types can be used:
+          * `boolean`
+          * `byte`
+          * `date`
+          * `date_nanos`
+          * `date_range`
+          * `double`
+          * `double_range`
+          * `float`
+          * `float_range`
+          * `half_float`
+          * `integer`
+          * `integer_range`
+          * `ip`
+          * `ip_range`
+          * `keyword`
+          * `long`
+          * `long_range`
+          * `short`
+          * `text`
+      * **List items**: The values used to determine whether the exception prevents an alert from being generated.
+
+      All list items in the same list container must be of the same data type, and each item defines a single value. For example, an IP list container named `internal-ip-addresses-southport` contains five items, where each item defines one internal IP address:
+      1. `192.168.1.1`
+      2. `192.168.1.3`
+      3. `192.168.1.18`
+      4. `192.168.1.12`
+      5. `192.168.1.7`
+
+      To use these IP addresses as values for defining rule exceptions, use the Security exceptions API to [create an exception list item](../operation/operation-createexceptionlistitem) that references the `internal-ip-addresses-southport` list.
+      > info
+      > Lists cannot be added directly to rules, nor do they define the operators used to determine when exceptions are applied (`is in list`, `is not in list`). Use an exception item to define the operator and associate it with an [exception container](../operation/operation-createexceptionlist). You can then add the exception container to a rule's `exceptions_list` object.
+
+      ## Lists requirements
+
+      Before you can start using lists, you must create the `.lists` and `.items` data streams for the relevant Kibana space. To do this, use the [Create list data streams](../operation/operation-createlistindex) endpoint. Once these data streams are created, your role needs privileges to manage rules. Refer to [Enable and access detections](https://www.elastic.co/guide/en/serverless/current/security-detections-requirements.html#enable-detections-ui) for a complete list of requirements.
diff --git a/x-pack/plugins/security_solution/docs/openapi/ess/security_solution_detections_api_2023_10_31.bundled.schema.yaml b/x-pack/plugins/security_solution/docs/openapi/ess/security_solution_detections_api_2023_10_31.bundled.schema.yaml
index e3b49871fa5a1..875471fb4ec15 100644
--- a/x-pack/plugins/security_solution/docs/openapi/ess/security_solution_detections_api_2023_10_31.bundled.schema.yaml
+++ b/x-pack/plugins/security_solution/docs/openapi/ess/security_solution_detections_api_2023_10_31.bundled.schema.yaml
@@ -1,9 +1,11 @@
 openapi: 3.0.3
 info:
   description: >-
-    You can create rules that automatically turn events and external alerts sent
-    to Elastic Security into detection alerts. These alerts are displayed on the
-    Detections page.
+    Use the detections APIs to create and manage detection rules. Detection
+    rules search events and external alerts sent to Elastic Security and
+    generate detection alerts from any hits. Alerts are displayed on the
+    **Alerts** page and can be assigned and triaged, using the alert status to
+    mark them as open, closed, or acknowledged.
   title: Security Detections API (Elastic Cloud and self-hosted)
   version: '2023-10-31'
 servers:
@@ -7104,9 +7106,21 @@ components:
 security:
   - BasicAuth: []
 tags:
-  - description: >-
-      You can create rules that automatically turn events and external alerts
-      sent to Elastic Security into detection alerts. These alerts are displayed
-      on the Detections page.
+  - description: >
+      Use the detections APIs to create and manage detection rules. Detection
+      rules search events and external alerts sent to Elastic Security and
+      generate detection alerts from any hits. Alerts are displayed on the
+      **Alerts** page and can be assigned and triaged, using the alert status to
+      mark them as open, closed, or acknowledged.
+
+      > warn
+
+      > If the API key used for authorization has different privileges than the
+      key that created or most recently updated a rule, the rule behavior might
+      change.
+
+
+      > If the API key that created a rule is deleted, or the user that created
+      the rule becomes inactive, the rule will stop running.
     name: Security Detections API
     x-displayName: Security detections
diff --git a/x-pack/plugins/security_solution/docs/openapi/serverless/security_solution_detections_api_2023_10_31.bundled.schema.yaml b/x-pack/plugins/security_solution/docs/openapi/serverless/security_solution_detections_api_2023_10_31.bundled.schema.yaml
index 9384496c41b35..83f59786a9b96 100644
--- a/x-pack/plugins/security_solution/docs/openapi/serverless/security_solution_detections_api_2023_10_31.bundled.schema.yaml
+++ b/x-pack/plugins/security_solution/docs/openapi/serverless/security_solution_detections_api_2023_10_31.bundled.schema.yaml
@@ -1,9 +1,11 @@
 openapi: 3.0.3
 info:
   description: >-
-    You can create rules that automatically turn events and external alerts sent
-    to Elastic Security into detection alerts. These alerts are displayed on the
-    Detections page.
+    Use the detections APIs to create and manage detection rules. Detection
+    rules search events and external alerts sent to Elastic Security and
+    generate detection alerts from any hits. Alerts are displayed on the
+    **Alerts** page and can be assigned and triaged, using the alert status to
+    mark them as open, closed, or acknowledged.
   title: Security Detections API (Elastic Cloud Serverless)
   version: '2023-10-31'
 servers:
@@ -6250,9 +6252,21 @@ components:
 security:
   - BasicAuth: []
 tags:
-  - description: >-
-      You can create rules that automatically turn events and external alerts
-      sent to Elastic Security into detection alerts. These alerts are displayed
-      on the Detections page.
+  - description: >
+      Use the detections APIs to create and manage detection rules. Detection
+      rules search events and external alerts sent to Elastic Security and
+      generate detection alerts from any hits. Alerts are displayed on the
+      **Alerts** page and can be assigned and triaged, using the alert status to
+      mark them as open, closed, or acknowledged.
+
+      > warn
+
+      > If the API key used for authorization has different privileges than the
+      key that created or most recently updated a rule, the rule behavior might
+      change.
+
+
+      > If the API key that created a rule is deleted, or the user that created
+      the rule becomes inactive, the rule will stop running.
     name: Security Detections API
     x-displayName: Security detections
diff --git a/x-pack/plugins/security_solution/scripts/openapi/bundle_detections.js b/x-pack/plugins/security_solution/scripts/openapi/bundle_detections.js
index 2c0e36f3db8ee..7bfd659927ec3 100644
--- a/x-pack/plugins/security_solution/scripts/openapi/bundle_detections.js
+++ b/x-pack/plugins/security_solution/scripts/openapi/bundle_detections.js
@@ -20,21 +20,10 @@ const ROOT = resolve(__dirname, '../..');
     ),
     options: {
       includeLabels: ['serverless'],
-      prototypeDocument: {
-        info: {
-          title: 'Security Detections API (Elastic Cloud Serverless)',
-          description:
-            'You can create rules that automatically turn events and external alerts sent to Elastic Security into detection alerts. These alerts are displayed on the Detections page.',
-        },
-        tags: [
-          {
-            name: 'Security Detections API',
-            'x-displayName': 'Security detections',
-            description:
-              'You can create rules that automatically turn events and external alerts sent to Elastic Security into detection alerts. These alerts are displayed on the Detections page.',
-          },
-        ],
-      },
+      prototypeDocument: join(
+        ROOT,
+        'scripts/openapi/bundle_detections_info/detections_serverless.info.yaml'
+      ),
     },
   });
 
@@ -46,21 +35,10 @@ const ROOT = resolve(__dirname, '../..');
     ),
     options: {
       includeLabels: ['ess'],
-      prototypeDocument: {
-        info: {
-          title: 'Security Detections API (Elastic Cloud and self-hosted)',
-          description:
-            'You can create rules that automatically turn events and external alerts sent to Elastic Security into detection alerts. These alerts are displayed on the Detections page.',
-        },
-        tags: [
-          {
-            name: 'Security Detections API',
-            'x-displayName': 'Security detections',
-            description:
-              'You can create rules that automatically turn events and external alerts sent to Elastic Security into detection alerts. These alerts are displayed on the Detections page.',
-          },
-        ],
-      },
+      prototypeDocument: join(
+        ROOT,
+        'scripts/openapi/bundle_detections_info/detections_ess.info.yaml'
+      ),
     },
   });
 })();
diff --git a/x-pack/plugins/security_solution/scripts/openapi/bundle_detections_info/detections_ess.info.yaml b/x-pack/plugins/security_solution/scripts/openapi/bundle_detections_info/detections_ess.info.yaml
new file mode 100644
index 0000000000000..bb3f8830dc35a
--- /dev/null
+++ b/x-pack/plugins/security_solution/scripts/openapi/bundle_detections_info/detections_ess.info.yaml
@@ -0,0 +1,14 @@
+openapi: 3.0.3
+info:
+  title: "Security Detections API (Elastic Cloud and self-hosted)"
+  description: "Use the detections APIs to create and manage detection rules. Detection rules search events and external alerts sent to Elastic Security and generate detection alerts from any hits. Alerts are displayed on the **Alerts** page and can be assigned and triaged, using the alert status to mark them as open, closed, or acknowledged."
+
+tags:
+  - name: "Security Detections API"
+    x-displayName: "Security detections"
+    description: |
+      Use the detections APIs to create and manage detection rules. Detection rules search events and external alerts sent to Elastic Security and generate detection alerts from any hits. Alerts are displayed on the **Alerts** page and can be assigned and triaged, using the alert status to mark them as open, closed, or acknowledged.
+      > warn
+      > If the API key used for authorization has different privileges than the key that created or most recently updated a rule, the rule behavior might change.
+
+      > If the API key that created a rule is deleted, or the user that created the rule becomes inactive, the rule will stop running.
\ No newline at end of file
diff --git a/x-pack/plugins/security_solution/scripts/openapi/bundle_detections_info/detections_serverless.info.yaml b/x-pack/plugins/security_solution/scripts/openapi/bundle_detections_info/detections_serverless.info.yaml
new file mode 100644
index 0000000000000..a90f669b4ed28
--- /dev/null
+++ b/x-pack/plugins/security_solution/scripts/openapi/bundle_detections_info/detections_serverless.info.yaml
@@ -0,0 +1,14 @@
+openapi: 3.0.3
+info:
+  title: "Security Detections API (Elastic Cloud Serverless)"
+  description: "Use the detections APIs to create and manage detection rules. Detection rules search events and external alerts sent to Elastic Security and generate detection alerts from any hits. Alerts are displayed on the **Alerts** page and can be assigned and triaged, using the alert status to mark them as open, closed, or acknowledged."
+
+tags:
+  - name: "Security Detections API"
+    x-displayName: "Security detections"
+    description: |
+      Use the detections APIs to create and manage detection rules. Detection rules search events and external alerts sent to Elastic Security and generate detection alerts from any hits. Alerts are displayed on the **Alerts** page and can be assigned and triaged, using the alert status to mark them as open, closed, or acknowledged.
+      > warn
+      > If the API key used for authorization has different privileges than the key that created or most recently updated a rule, the rule behavior might change.
+
+      > If the API key that created a rule is deleted, or the user that created the rule becomes inactive, the rule will stop running.
\ No newline at end of file