Re-attempting to clean the getting started files

raw-migrated-files/toc.yml

@@ -268,7 +268,6 @@ toc:
       - file: docs-content/serverless/project-settings-content.md
       - file: docs-content/serverless/security-about-rules.md
       - file: docs-content/serverless/security-add-manage-notes.md
-      - file: docs-content/serverless/security-advanced-settings.md
       - file: docs-content/serverless/security-agent-tamper-protection.md
       - file: docs-content/serverless/security-ai-assistant-esql-queries.md
       - file: docs-content/serverless/security-ai-assistant.md

solutions/security/get-started/configure-advanced-settings.md

@@ -4,34 +4,7 @@ mapped_urls:
   - https://www.elastic.co/guide/en/serverless/current/security-advanced-settings.html
 ---
 
-# Configure advanced settings
-
-% What needs to be done: Align serverless/stateful
-
-% Use migrated content from existing pages that map to this page:
-
-% - [x] ./raw-migrated-files/security-docs/security/advanced-settings.md
-% - [ ] ./raw-migrated-files/docs-content/serverless/security-advanced-settings.md
-
-% Internal links rely on the following IDs being on this page (e.g. as a heading ID, paragraph ID, etc):
-
-$$$update-sec-indices$$$
-
-$$$exclude-cold-frozen-data-rule-executions$$$
-
-$$$exclude-cold-frozen-tiers$$$
-
-$$$ip-reputation-links$$$
-
-$$$manage-alert-tags$$$
-
-$$$max-notes-alerts-events$$$
-
-$$$show-related-integrations$$$
-
-$$$update-threat-intel-indices$$$
-
-$$$visualizations-in-flyout$$$
+# Configure advanced settings [security-advanced-settings]
 
 The advanced settings determine:
 
@@ -46,15 +19,18 @@ The advanced settings determine:
 * Whether related integrations are displayed on the Rules page tables
 * The options provided in the alert tag menu
 
-To change these settings, you need `All` privileges for the **Advanced Settings** [{{kib}} feature](/deploy-manage/users-roles/cluster-or-deployment-auth/kibana-privileges.md).
+::::{important}
+- To change these settings in the {{stack}}, you need `All` privileges for the **Advanced Settings** [{{kib}} feature](/deploy-manage/users-roles/cluster-or-deployment-auth/kibana-privileges.md).
+- To change these settings in {{serverless-short}}, you need either the appropriate [predefined Security user role](/deploy-manage/users-roles/cloud-organization/user-roles.md#general-assign-user-roles) or a [custom role](/deploy-manage/users-roles/cloud-organization/user-roles.md) with `All` privileges for the **Advanced Settings** feature.
+::::
 
 ::::{warning}
 Modifying advanced settings can affect Kibana performance and cause problems that are difficult to diagnose. Setting a property value to a blank field reverts to the default behavior, which might not be compatible with other configuration settings. Deleting a custom setting removes it from Kibana permanently.
 ::::
 
 
 
-## Access advanced settings [_access_advanced_settings]
+## Access advanced settings [security-advanced-settings-access-advanced-settings]
 
 To access advanced settings, go to **Stack Management** → **Advanced Settings**, then scroll down to **Security Solution** settings.
 
@@ -68,14 +44,24 @@ To access advanced settings, go to **Stack Management** → **Advanced Settings*
 
 The `securitySolution:defaultIndex` field defines which {{es}} indices the {{security-app}} uses to collect data. By default, index patterns are used to match sets of {{es}} indices.
 
+The `securitySolution:defaultIndex` field defines which {{es}} indices the {{security-app}} uses to collect data. By default, index patterns are used to match sets of {{es}} indices:
+
+* `apm-*-transaction*`
+* `auditbeat-*`
+* `endgame-*`
+* `filebeat-*`
+* `logs-*`
+* `packetbeat-*`
+* `winlogbeat-*`
+
 ::::{note}
 Index patterns use wildcards to specify a set of indices. For example, the `filebeat-*` index pattern means all indices starting with `filebeat-` are available in the {{security-app}}.
 ::::
 
 
 All of the default index patterns match [{{beats}}](asciidocalypse://docs/beats/docs/reference/ingestion-tools/index.md) and [{{agent}}](asciidocalypse://docs/docs-content/docs/reference/ingestion-tools/fleet/index.md) indices. This means all data shipped via {{beats}} and the {{agent}} is automatically added to the {{security-app}}.
 
-You can add or remove any indices and index patterns as required. For background information on {{es}} indices, refer to [Data in: documents and indices](/manage-data/data-store/index-basics.md).
+You can add or remove any indices and index patterns as required. In {{serverless-short}}, the maximum number of items that you can include in a comma-delimited list is 50. In {{stack}, there is no limit.} For more information on {{es}} indices, refer to [Data in: documents and indices](/manage-data/data-store/index-basics.md).
 
 ::::{note}
 If you leave the `-*elastic-cloud-logs-*` index pattern selected, all Elastic cloud logs are excluded from all queries in the {{security-app}} by default. This is to avoid adding data from cloud monitoring to the app.
@@ -90,7 +76,11 @@ If you leave the `-*elastic-cloud-logs-*` index pattern selected, all Elastic cl
 
 ## Update default Elastic Security threat intelligence indices [update-threat-intel-indices]
 
-The `securitySolution:defaultThreatIndex` advanced setting specifies threat intelligence indices that {{elastic-sec}} features query for ingested threat indicators. This setting affects features that query threat intelligence indices, such as the Threat Intelligence view on the Overview page, indicator match rules, and the alert enrichment query. You can specify one or more threat intelligence indices; multiple indices must be separated by commas. By default, only the `logs-ti*` index pattern is specified. Do not remove or overwrite this index pattern, as it is used by {{agent}} integrations.
+The `securitySolution:defaultThreatIndex` advanced setting specifies threat intelligence indices that {{elastic-sec}} features query for ingested threat indicators. This setting affects features that query threat intelligence indices, such as the Threat Intelligence view on the Overview page, indicator match rules, and the alert enrichment query.
+
+
+
+You can specify one or more threat intelligence indices; multiple indices must be separated by commas. By default, only the `logs-ti*` index pattern is specified. Do not remove or overwrite this index pattern, as it is used by {{agent}} integrations.
 
 ::::{important}
 Threat intelligence indices aren’t required to be ECS-compatible for use in indicator match rules. However, we strongly recommend compatibility if you want your alerts to be enriched with relevant threat indicator information. When searching for threat indicator data, indicator match rules use the threat indicator path specified in the **Indicator prefix override** advanced setting. Visit [Configure advanced rule settings](/solutions/security/detect-and-alert/create-detection-rule.md#rule-ui-advanced-params) for more information.
@@ -111,14 +101,14 @@ Kibana transmits certain information about Elastic Security when users interact
 To learn more, refer to our [Privacy Statement](https://www.elastic.co/legal/privacy-statement).
 
 
-## Set machine learning score threshold [_set_machine_learning_score_threshold]
+## Set machine learning score threshold [security-advanced-settings-set-machine-learning-score-threshold]
 
 When security [{{ml}} jobs](/solutions/security/advanced-entity-analytics/anomaly-detection.md) are enabled, this setting determines the threshold above which anomaly scores appear in {{elastic-sec}}:
 
 * `securitySolution:defaultAnomalyScore`
 
 
-## Modify news feed settings [_modify_news_feed_settings]
+## Modify news feed settings [security-advanced-settings-modify-news-feed-settings]
 
 You can change these settings, which affect the news feed displayed on the {{elastic-sec}} **Overview** page:
 
@@ -141,7 +131,7 @@ This functionality is in technical preview and may be changed or removed in a fu
 The `securitySolution:enableVisualizationsInFlyout` setting allows you to access the event analyzer and Session View in the **Visualize** [tab](/solutions/security/detect-and-alert/view-detection-alert-details.md#expanded-visualizations-view) on the alert or event details flyout. This setting is turned off by default.
 
 
-## Change the default search interval and data refresh time [_change_the_default_search_interval_and_data_refresh_time]
+## Change the default search interval and data refresh time [security-advanced-settings-change-the-default-search-interval-and-data-refresh-time]
 
 These settings determine the default time interval and refresh rate {{elastic-sec}} pages use to display data when you open the app:
 
@@ -150,7 +140,7 @@ These settings determine the default time interval and refresh rate {{elastic-se
 
 ::::{note}
 Refer to [Date Math](asciidocalypse://docs/elasticsearch/docs/reference/elasticsearch/rest-apis/common-options.md) for information about the syntax. The UI [time filter](/explore-analyze/query-filter/filtering.md) overrides the default values.
-::::
+`::::