Explore section cleanup (#506)

Cleans up 'align serverless/stateful' pages in the Solutions and use
cases > Security > Explore section.
Removes serverless raw migrated files.

Previews:

- [Hosts
page](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/506/solutions/security/explore/hosts-page)
- [Network
page](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/506/solutions/security/explore/network-page)
- [Configure network map
data](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/506/solutions/security/explore/configure-network-map-data)
- [Users
page](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/506/solutions/security/explore/users-page)

Author: natasha-moore-elastic

raw-migrated-files/docs-content/serverless/ingest-aws-securityhub-data.md

@@ -13,4 +13,4 @@ In order to enrich your {{elastic-sec}} workflows with third-party cloud securit
 
 After you’ve completed these steps, AWS Security Hub data will appear on the **Misconfigurations** tab of the [**Findings**](../../../solutions/security/cloud/findings-page.md) page.
 
-Any available findings data will also appear in the entity details flyouts for related [alerts](../../../solutions/security/detect-and-alert/view-detection-alert-details.md#insights-section). If alerts are present for a user or host that has findings data from AWS Security Hub, the findings will appear on the [users](../../../solutions/security/explore/users-page.md#security-users-page-user-details-flyout), and [hosts](../../../solutions/security/explore/hosts-page.md#security-hosts-overview-host-details-flyout) flyouts.
+Any available findings data will also appear in the entity details flyouts for related [alerts](../../../solutions/security/detect-and-alert/view-detection-alert-details.md#insights-section). If alerts are present for a user or host that has findings data from AWS Security Hub, the findings will appear on the [users](/solutions/security/explore/users-page.md#user-details-flyout), and [hosts](/solutions/security/explore/hosts-page.md#host-details-flyout) flyouts.

raw-migrated-files/docs-content/serverless/ingest-third-party-cloud-security-data.md

@@ -14,7 +14,7 @@ You can ingest third-party cloud security alerts into {{elastic-sec}} to view th
 
 ## Ingest third-party security posture and vulnerability data [_ingest_third_party_security_posture_and_vulnerability_data] 
 
-You can ingest third-party data into {{elastic-sec}} to review and investigate it alongside data collected by {{elastic-sec}}'s native cloud security integrations. Once ingested, cloud security posture and vulnerability data appears on the [Findings](../../../solutions/security/cloud/findings-page.md) page and in the entity details flyouts for [alerts](../../../solutions/security/detect-and-alert/view-detection-alert-details.md#insights-section), [users](../../../solutions/security/explore/users-page.md#security-users-page-user-details-flyout), and [hosts](../../../solutions/security/explore/hosts-page.md#security-hosts-overview-host-details-flyout) flyouts.
+You can ingest third-party data into {{elastic-sec}} to review and investigate it alongside data collected by {{elastic-sec}}'s native cloud security integrations. Once ingested, cloud security posture and vulnerability data appears on the [Findings](../../../solutions/security/cloud/findings-page.md) page and in the entity details flyouts for [alerts](../../../solutions/security/detect-and-alert/view-detection-alert-details.md#insights-section), [users](/solutions/security/explore/users-page.md#user-details-flyout), and [hosts](/solutions/security/explore/hosts-page.md#host-details-flyout) flyouts.
 
 * Learn to [ingest cloud security posture data from AWS Security Hub](../../../solutions/security/cloud/ingest-aws-security-hub-data.md).
 * Learn to [ingest cloud security posture and vulnerability data from Wiz](../../../solutions/security/cloud/ingest-wiz-data.md).

raw-migrated-files/docs-content/serverless/ingest-wiz-data.md

@@ -21,4 +21,4 @@ After you’ve completed these steps, Wiz data will appear on the **[**Misconfig
 :alt: Wiz data on the Findings page
 :::
 
-Any available findings data will also appear in the entity details flyouts for related [alerts](../../../solutions/security/detect-and-alert/view-detection-alert-details.md#insights-section). If alerts are present for a user or host that has findings data from Wiz, the findings will appear on the [users](../../../solutions/security/explore/users-page.md#security-users-page-user-details-flyout), and [hosts](../../../solutions/security/explore/hosts-page.md#security-hosts-overview-host-details-flyout) flyouts.
+Any available findings data will also appear in the entity details flyouts for related [alerts](../../../solutions/security/detect-and-alert/view-detection-alert-details.md#insights-section). If alerts are present for a user or host that has findings data from Wiz, the findings will appear on the [users](/solutions/security/explore/users-page.md#user-details-flyout), and [hosts](/solutions/security/explore/hosts-page.md#host-details-flyout) flyouts.

raw-migrated-files/docs-content/serverless/security-alerts-manage.md

@@ -22,7 +22,7 @@ The Alerts page offers various ways for you to organize and triage detection ale
     ![View details button](../../../images/serverless--detections-view-alert-details.png "")
 
 * View the rule that created an alert. Click a name in the **Rule** column to open the rule’s details.
-* View the details of the host and user associated with the alert. In the Alerts table, click a host name to open the [host details flyout](../../../solutions/security/explore/hosts-page.md#security-hosts-overview-host-details-flyout), or a user name to open the [user details flyout](../../../solutions/security/explore/users-page.md#security-users-page-user-details-flyout).
+* View the details of the host and user associated with the alert. In the Alerts table, click a host name to open the [host details flyout](/solutions/security/explore/hosts-page.md#host-details-flyout), or a user name to open the [user details flyout](/solutions/security/explore/users-page.md#user-details-flyout).
 * Filter for a specific rule in the KQL bar (for example, `kibana.alert.rule.name :"SSH (Secure Shell) from the Internet"`). KQL autocomplete is available for `.alerts-security.alerts-*` indices.
 * Use the date and time filter to define a specific time range. By default, this filter is set to search the last 24 hours.
 * Use the drop-down filter controls to filter alerts by up to four fields. By default, you can filter alerts by **Status**, **Severity***, ***User**, and **Host**, and you can [edit the controls](../../../solutions/security/detect-and-alert/manage-detection-alerts.md#drop-down-filter-controls) to use other fields.