add wip

Author: florent-leborgne

deploy-manage/security/data-security.md

@@ -1 +1,5 @@
-# Data security
+# Secure your data
+
+:::{warning}
+**This page is a work in progress.** 
+:::

deploy-manage/security/install-stack-demo-secure.md

@@ -11,7 +11,7 @@ For traffic to be encrypted between {{es}} cluster nodes and between {{kib}} and
 * [Prerequisites and assumptions](secure-your-cluster-deployment.md#install-stack-demo-secure-prereqs)
 * [Step 1: Generate a new self-signed CA certificate](secure-your-cluster-deployment.md#install-stack-demo-secure-ca)
 * [Step 2: Generate a new certificate for the transport layer](secure-your-cluster-deployment.md#install-stack-demo-secure-transport)
-* [Step 3: Generate new certificate(s) for the HTTP layer](../../raw-migrated-files/stack-docs/deploy-manage/security/secure-your-cluster-deployment.md#install-stack-demo-secure-http)
+* [Step 3: Generate new certificate(s) for the HTTP layer](secure-your-cluster-deployment.md#install-stack-demo-secure-http)
 * [Step 4: Configure security on additional {{es}} nodes](secure-your-cluster-deployment.md#install-stack-demo-secure-second-node)
 * [Step 5: Generate server-side and client-side certificates for {{kib}}](secure-your-cluster-deployment.md#install-stack-demo-secure-kib-es)
 * [Step 6: Install {{fleet}} with SSL certificates configured](secure-your-cluster-deployment.md#install-stack-demo-secure-fleet)
@@ -23,7 +23,7 @@ It should take between one and two hours to complete these steps.
 
 ## Prerequisites and assumptions [install-stack-demo-secure-prereqs]
 
-Before starting, you’ll need to have set up an on-premises {{es}} cluster with {{kib}}, following the steps in [Tutorial 1: Installing a self-managed {{stack}}](../deploy/self-managed/installing-elasticsearch.md).
+Before starting, you’ll need to have set up an on-premises {{es}} cluster with {{kib}}, following the steps in [Tutorial 1: Installing a self-managed {{stack}}](/deploy/self-managed/installing-elasticsearch.md).
 
 The examples in this guide use RPM packages to install the {{stack}} components on hosts running Red Hat Enterprise Linux 8. The steps for other install methods and operating systems are similar, and can be found in the documentation linked from each section.
 
@@ -874,7 +874,7 @@ View your system metrics data:
 2. In the query field, search for `Metrics System`.
 3. Select the `[Metrics System] Host overview` link. The {{kib}} Dashboard opens with visualizations of host metrics including CPU usage, memory usage, running processes, and more.
 
-    :::{image} ../../../images/elastic-stack-install-stack-metrics-dashboard.png
+    :::{image} /images/elastic-stack-install-stack-metrics-dashboard.png
     :alt: The System metrics host overview showing CPU usage, memory usage, and other visualizations
     :::
 

deploy-manage/security/secure-clients-integrations.md

@@ -5,6 +5,11 @@ mapped_pages:
 
 # Secure clients and integrations [security-clients-integrations]
 
+:::{warning}
+**This page is a work in progress.** 
+:::
+
+
 You will need to update the configuration for several [clients](httprest-clients-security.md) to work with a secured {{es}} cluster.
 
 The {{es}} {{security-features}} enable you to secure your {{es}} cluster. But {{es}} itself is only one product within the {{stack}}. It is often the case that other products in the {{stack}} are connected to the cluster and therefore need to be secured as well, or at least communicate with the cluster in a secured way:

deploy-manage/security/secure-hosting-environment.md

@@ -6,6 +6,10 @@ applies_to:
 
 # Secure your hosting environment
 
+:::{warning}
+**This page is a work in progress.** 
+:::
+
 Whether you're running Elastic on {{ecloud}}, through an {{ece}} or {{eck}} orchestrator, or self-managed on your own premises, it is critical that you secure the layer responsible for deploying and hosting your Elastic products.
 
 This section covers security measures specific to:

deploy-manage/security/secure-your-eck-installation.md

@@ -7,7 +7,10 @@ applies_to:
 
 # Secure your {{eck}} installation [eck-securing-considerations]
 
-**This page is a work in progress.**
+:::{warning}
+**This page is a work in progress.** 
+:::
+
 
 ## TLS certificate management
 

deploy-manage/security/secure-your-elastic-cloud-enterprise-installation.md

@@ -9,7 +9,10 @@ mapped_pages:
 
 # Secure your Elastic Cloud Enterprise installation [ece-securing-considerations]
 
-**This page is a work in progress.**
+:::{warning}
+**This page is a work in progress.** 
+:::
+
 
 When securing your {{ece}} installation, consider the following:
 

deploy-manage/security/secure-your-elastic-cloud-organization.md

@@ -8,7 +8,10 @@ applies_to:
 
 # Secure your Elastic Cloud organization [ec-securing-considerations]
 
-**This page is a work in progress.**
+:::{warning}
+**This page is a work in progress.** 
+:::
+
 
 ## TLS certificate management
 

deploy-manage/security/secure-your-personal-account.md

@@ -6,4 +6,6 @@ applies_to:
 
 # Secure your personal account
 
-**This page is a work in progress.**
+:::{warning}
+**This page is a work in progress.** 
+:::

deploy-manage/security/traffic-filtering.md

@@ -7,6 +7,11 @@ mapped_urls:
 
 # Secure network access
 
+:::{warning}
+**This page is a work in progress.** 
+:::
+
+
 Never expose {{es}} to unwanted internet traffic. Using an application to sanitize requests to {{es}} still poses risks, such as a malicious user writing [`_search`](https://www.elastic.co/docs/api/doc/elasticsearch/group/endpoint-search) requests that could overwhelm an {{es}} cluster and bring it down. Depending on your environment, consider the following:
 
 - **IP traffic filtering**: Restrict access based on IP addresses or CIDR ranges.

deploy-manage/users-roles.md

@@ -21,7 +21,7 @@ The methods that you use to authenticate users and control access depends on the
 Preventing unauthorized access is only one element of a complete security strategy. To secure your Elastic environment, you can also do the following:
 
 * Restrict the nodes and clients that can connect to the cluster using [traffic filters](/deploy-manage/security/traffic-filtering.md). 
-* Take steps to maintain your data integrity and confidentiality by [encrypting HTTP and inter-node communications](/deploy-manage/security/secure-endpoints.md), as well as [encrypting your data at rest](/deploy-manage/security/encrypt-deployment.md).
+* Take steps to maintain your data integrity and confidentiality by [encrypting HTTP and inter-node communications](/deploy-manage/security/secure-cluster-communications.md), as well as [encrypting your data at rest](/deploy-manage/security/encrypt-deployment.md).
 * Maintain an [audit trail](/deploy-manage/monitor/logging-configuration/security-event-audit-logging.md) for security-related events.
 * Control access to dashboards and other saved objects in your UI using [{{kib}} spaces](/deploy-manage/manage-spaces.md). 
 * Connect your cluster to a [remote cluster](/deploy-manage/remote-clusters.md) to enable cross-cluster replication and search.