Adapt documentation to the new side menu.

source/_themes/wazuh_doc_theme_v3/package.json

@@ -1,7 +1,7 @@
 {
   "name": "wazuh-documentation",
   "version": "3.0.0",
-  "description": "Wazuh is a free, open source and enterprise-ready security monitoring solution for threat detection, integrity monitoring, incident response and compliance.",
+  "description": "Wazuh is a free, open source and enterprise-ready security monitoring solution for threat detection, file integrity monitoring, incident response and compliance.",
   "main": "index.html",
   "watch": {
     "build": {

source/cloud-security/amazon/services/prerequisites/considerations.rst

@@ -263,30 +263,3 @@ The following is an example of a valid configuration.
     </service>
 
   </wodle>
-
-Enabling dashboard visualization  
---------------------------------
-
-You can activate the corresponding Security Information Management module on the Wazuh Dashboard. This module provides additional details and insights about events, as shown in the screenshots below.
-
-    .. thumbnail:: /images/aws/aws-dashboard.png
-       :title: Amazon AWS dashboard
-       :alt: Amazon AWS dashboard
-       :align: center
-       :width: 80%
-
-    .. thumbnail:: /images/aws/aws-events.png
-       :title: Amazon AWS events
-       :alt: Amazon AWS events
-       :align: center
-       :width: 80%
-
-To activate the **Amazon AWS** module, navigate to your Wazuh Dashboard and click on **Wazuh > Settings > Modules**. In the **Security Information Management** section, enable the **Amazon AWS** module as shown in the image below.
-
-    .. thumbnail:: /images/aws/aws-module.png
-       :title: Amazon AWS module
-       :alt: Amazon AWS module
-       :align: center
-       :width: 80%
-
-For further information, please refer to the `modules <https://documentation.wazuh.com/current/user-manual/wazuh-dashboard/settings.html#modules>`_ section.

source/cloud-security/amazon/services/supported-services/trusted-advisor.rst

@@ -145,7 +145,7 @@ Policy configuration
 Wazuh configuration
 -------------------
 
-#. Access the Wazuh configuration in **Wazuh** > **Management** > **Configuration** using the Wazuh UI or by manually editing the ``/var/ossec/etc/ossec.conf`` file in the host:
+#. Access the Wazuh configuration in **Settings** using the Wazuh UI or by manually editing the ``/var/ossec/etc/ossec.conf`` file in the host:
 
     .. thumbnail:: /images/cloud-security/aws/trusted-ui-1.png
       :align: center
@@ -184,7 +184,7 @@ Wazuh configuration
       .. include:: /_templates/common/restart_agent.rst
 
 
-The :ref:`AWS S3 module <wodle_s3>` configuration can be reviewed from **Wazuh** > **Management** > **Configuration** > **Cloud security monitoring** once added in the :ref:`Local configuration <reference_ossec_conf>`.
+The :ref:`AWS S3 module <wodle_s3>` configuration can be reviewed from **Settings** > **Cloud security monitoring** once added in the :ref:`Local configuration <reference_ossec_conf>`.
 
     .. thumbnail:: /images/cloud-security/aws/trusted-ui-3.png
       :align: center

source/cloud-security/amazon/services/troubleshooting.rst

@@ -13,7 +13,7 @@ The below information is intended to assist in troubleshooting issues.
 Checking if the module is running
 ---------------------------------
 
-When the module runs it writes its output in the ``ossec.log`` file. This log file can be found in ``WAZUH_PATH/logs/ossec.log`` or under **Wazuh** > **Management** > **Logs** if using the Wazuh UI.
+When the module runs it writes its output in the ``ossec.log`` file. This log file can be found in ``WAZUH_PATH/logs/ossec.log`` or under **App Logs** if using the Wazuh UI.
 
 It is possible to check if the module is running without issues by looking in the ``ossec.log`` file. These are the messages that are displayed in the ``ossec.log``, depending on how the module has been configured:
 

source/cloud-security/gcp/prerequisites/considerations.rst

@@ -84,30 +84,3 @@ Below there is an example of a configuration that uses more than one bucket:
 
   </gcp-bucket>
 
-
-Enabling dashboard visualization  
---------------------------------
-
-You can activate the corresponding Security Information Management module on the Wazuh Dashboard. This module provides additional details and insights about events, as shown in the screenshots below.
-
-    .. thumbnail:: /images/gcp/gcp-dashboard.png
-       :title: GCP dashboard
-       :alt: GCP dashboard
-       :align: center
-       :width: 80%
-
-    .. thumbnail:: /images/gcp/gcp-events.png
-       :title: GCP events
-       :alt: GCP events
-       :align: center
-       :width: 80%
-
-To activate the **GCP** module, navigate to your Wazuh Dashboard and click on **Wazuh > Settings > Modules**. In the **Security Information Management** section, enable the **GCP** module as shown in the image below.
-
-    .. thumbnail:: /images/gcp/gcp-module.png
-       :title: GCP module
-       :alt: GCP module
-       :align: center
-       :width: 80%
-
-For further information, please refer to the `modules <https://documentation.wazuh.com/current/user-manual/wazuh-dashboard/settings.html#modules>`_ section.

source/cloud-security/github/monitoring-github-activity.rst

@@ -138,32 +138,4 @@ If Wazuh successfully connects to GitHub, the events raised above will trigger t
         },
         "location":"github"
     }
-
-
-Enabling dashboard visualization  
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-You can activate the corresponding Security Information Management module on the Wazuh Dashboard. This module provides additional details and insights about events, as shown in the screenshots below.
-
-    .. thumbnail:: /images/github/github-dashboard.png
-       :title: GitHub dashboard
-       :alt: GitHub dashboard
-       :align: center
-       :width: 80%
-
-    .. thumbnail:: /images/github/github-events.png
-       :title: GitHub events
-       :alt: GitHub events
-       :align: center
-       :width: 80%
-
-To activate the **GitHub** module, navigate to your Wazuh Dashboard and click on **Wazuh > Settings > Modules**. In the **Security Information Management** section, enable the **GitHub** module as shown in the image below.
-
-    .. thumbnail:: /images/github/github-module.png
-       :title: GitHub module
-       :alt: GitHub module
-       :align: center
-       :width: 80%
-
-For further information, please refer to the `modules <https://documentation.wazuh.com/current/user-manual/wazuh-dashboard/settings.html#modules>`_ section.
-
+

source/cloud-security/office365/monitoring-office365-activity.rst

@@ -241,32 +241,3 @@ If Wazuh successfully connects to Office 365 API, the events raised above will t
         },
         "location":"office365"
     }
-
-
-Enabling dashboard visualization  
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-Once the configuration is complete, you can activate the corresponding Security Information Management module on the Wazuh Dashboard. This module provides additional details and insights about events, as shown in the screenshots below.
-
-    .. thumbnail:: /images/office365/office365-dashboard.png
-       :title: Office 365 dashboard
-       :alt: Office 365 dashboard
-       :align: center
-       :width: 80%
-
-    .. thumbnail:: /images/office365/office365-events.png
-       :title: Office 365 events
-       :alt: Office 365 events
-       :align: center
-       :width: 80%
-
-To activate the **Office 365** module, navigate to your Wazuh Dashboard and click on **Wazuh > Settings > Modules**. In the **Security Information Management** section, enable the **Office 365** module as shown in the image below.
-
-    .. thumbnail:: /images/office365/office365-module.png
-       :title: Office 365 module
-       :alt: Office 365 module
-       :align: center
-       :width: 80%
-
-For further information, please refer to the `modules <https://documentation.wazuh.com/current/user-manual/wazuh-dashboard/settings.html#modules>`_ section.
-

source/cloud-service/getting-started/register-agents.rst

@@ -13,7 +13,7 @@ Follow these steps to register an agent:
 
 #. Log into the Wazuh WUI.
 
-#. Click **Wazuh** and then **Agents**.
+#. Click **Endpoints Summary**.
 
 #. Click **Deploy a new agent**.
 

source/cloud-service/your-environment/manage-auth.rst

@@ -32,19 +32,19 @@ Follow these steps to create an internal user and map it to its appropriate role
 
 #. :ref:`Log into your WUI <cloud_wui_access>` as administrator.
 
-#. Click the upper-left menu icon **☰** to open the options, select **Security**, and then **Internal users** to open the internal users' page.
+#. Click the upper-left menu icon **☰** to open the options, go to **Indexer/dashboard management** > **Security**, and then **Internal users** to open the internal users' page.
 
 #. Click **Create internal user**, complete the empty fields with the requested information, and click **Create** to complete the action.
 
 #. To map the user to the appropriate role, follow these steps:
 
-   #. Go to **Security**, select **Roles** to open the page, and click the name of the role selected to open the window.
+   #. Click the upper-left menu icon **☰** to open the options, go to **Indexer/dashboard management** > **Security**, select **Roles** to open the page, and click the name of the role selected to open the window.
    #. Select the **Mapped users** tab and click **Manage mapping**.
    #. Add the user you created in the previous steps and click **Map** to confirm the action.
 
 #. To map the user with Wazuh, follow these steps:
 
-   #. Go to the Wazuh WUI, click **Wazuh** to open the menu, select **Security**, and then **Roles mapping** to open the page.
+   #. Click the upper-left menu icon **☰** to open the options, go to **Server management** > **Security**, and then **Roles mapping** to open the page.
    #. Click **Create Role mapping** and complete the empty fields with the following parameters:
 
       - **Role mapping name**: Assign a name to the role mapping.
@@ -61,13 +61,13 @@ Follow these steps to create an internal user, create a new role mapping, and gi
 
 #. :ref:`Log into your WUI <cloud_wui_access>` as administrator.
 
-#. Click the upper-left menu icon **☰** to open the options, select **Security**, and then **Internal users** to open the internal users' page.
+#. Click the upper-left menu icon **☰** to open the options, go to **Indexer/dashboard management** > **Security**, and then **Internal users** to open the internal users' page.
 
 #. Click **Create internal user**, complete the empty fields with the requested information, and click **Create** to complete the action.
 
 #. To map the user to the appropriate role, follow these steps:
 
-   #. Click the upper-left menu icon **☰** to open the options, select **Security**, and then **Roles** to open the roles page.
+   #. Click the upper-left menu icon **☰** to open the options, go to **Indexer/dashboard management** > **Security**, and then **Roles** to open the roles page.
 
    #. Search for the **all_access** role in the roles list and select it.
 
@@ -83,7 +83,7 @@ Follow these steps to create an internal user, create a new role mapping, and gi
 
 #. To map the user with Wazuh, follow these steps:
 
-   #. Go to the Wazuh WUI, click **Wazuh** to open the menu, select **Security**, and then **Roles mapping** to open the page.
+   #. Click the upper-left menu icon **☰** to open the options, go to **Server management** > **Security**, and then **Roles mapping** to open the page.
    #. Click **Create Role mapping** and complete the empty fields with the following parameters:
 
       - **Role mapping name**: Assign a name to the role mapping.
@@ -101,13 +101,13 @@ Follow these steps to create an internal user, create a new role mapping, and gi
 
 #. :ref:`Log into your WUI <cloud_wui_access>` as administrator.
 
-#. Click the upper-left menu icon **☰** to open the options, select **Security**, and then **Internal users** to open the internal users' page.
+#. Click the upper-left menu icon **☰** to open the options, go to **Indexer/dashboard management** > **Security**, and then **Internal users** to open the internal users' page.
 
 #. Click **Create internal user**, complete the empty fields with the requested information, and click **Create** to complete the action.
 
 #. To map the user to the appropriate role, follow these steps:
 
-   #. Click the upper-left menu icon **☰** to open the options, select **Security**, and then **Roles** to open the roles page.
+   #. Click the upper-left menu icon **☰** to open the options, go to **Indexer/dashboard management** > **Security**, and then **Roles** to open the roles page.
 
    #. Click **Create role**, complete the empty fields with the following parameters, and then click **Create** to complete the task. 
 
@@ -127,7 +127,7 @@ Follow these steps to create an internal user, create a new role mapping, and gi
 
 #. To map the user with Wazuh, follow these steps:
 
-   #. Go to the Wazuh WUI, click **Wazuh** to open the menu, select **Security**, and then **Roles mapping** to open the page.
+   #. Click the upper-left menu icon **☰** to open the options, go to **Server management** > **Security**, and then **Roles mapping** to open the page.
 
    #. Click **Create Role mapping** and complete the empty fields with the following parameters:
 

source/compliance/gdpr/gdpr-IV.rst

@@ -330,10 +330,10 @@ Ubuntu endpoint
 		# touch /customers/regular_data.txt
 		# echo "this is regular data" >> /customers/regular_data.txt 
 
-	You can see a level 7 alert generated in the **Integrity monitoring** section of the Wazuh dashboard to show that a file in the monitored directory was modified.
+	You can see a level 7 alert generated in the **File Integrity Monitoring** section of the Wazuh dashboard to show that a file in the monitored directory was modified.
 
 	.. thumbnail:: /images/compliance/gdpr/integrity-monitoring-level-7.png
-	   :title: Integrity monitoring level 7 alert visualization
+	   :title: File Integrity Monitoring level 7 alert visualization
 	   :align: center
 	   :width: 80%
 
@@ -347,7 +347,7 @@ Ubuntu endpoint
 	You can see a level 15 alert generated to show that a sensitive file in the monitored directory was modified.
 
 	.. thumbnail:: /images/compliance/gdpr/integrity-monitoring-level-15.png
-	   :title: Integrity monitoring level 15 alert visualization
+	   :title: File Integrity Monitoring level 15 alert visualization
 	   :align: center
 	   :width: 80%
 

source/compliance/hipaa/configuration-assessment.rst

@@ -23,10 +23,10 @@ The SCA module can help to implement the following HIPAA sections:
 Use cases: SCA scan and SSH session timeout
 -------------------------------------------
 
-- In this use case, the SCA module performs periodic scans on an Ubuntu 22.04 endpoint to ensure that it complies with security policies and hardening configurations. Additionally, the SCA module on the Wazuh dashboard displays the status of the SCA checks (passed, failed, or not applicable) and the time of the last scan for a specific endpoint, as shown below:
+- In this use case, the SCA module performs periodic scans on an Ubuntu 22.04 endpoint to ensure that it complies with security policies and hardening configurations. Additionally, the **Configuration Assessment** module on the Wazuh dashboard displays the status of the SCA checks (passed, failed, or not applicable) and the time of the last scan for a specific endpoint, as shown below:
 
   .. thumbnail:: /images/compliance/hipaa/02-configuration-assessment.png    
-    :title: The SCA module on the Wazuh dashboard displays the status of the SCA checks 
+    :title: The Configuration Assessment module on the Wazuh dashboard displays the status of the SCA checks 
     :align: center
     :width: 80%
 

source/compliance/hipaa/visualization-and-dashboard.rst

@@ -6,7 +6,7 @@
 Visualization and dashboard
 ===========================
 
-Wazuh offers a web dashboard for data visualization and analysis. The Wazuh dashboard comes with out-of-the-box modules for security events, compliance, detected vulnerable applications, file integrity monitoring data, configuration assessment results, and cloud infrastructure monitoring. It’s useful for performing forensic and historical alert analysis.
+Wazuh offers a web dashboard for data visualization and analysis. The Wazuh dashboard comes with out-of-the-box modules for threat hunting, compliance, detected vulnerable applications, file integrity monitoring data, configuration assessment results, and cloud infrastructure monitoring. It’s useful for performing forensic and historical alert analysis.
 
 The Wazuh dashboard assists in meeting the following HIPAA section:
 

source/compliance/nist/configuration-assessment.rst

@@ -29,7 +29,7 @@ This use case shows how Wazuh helps meet the **CM-6 Configuration settings** req
 
       # systemctl restart wazuh-agent
 
-#. Select the **Security configuration assessment** module on your Wazuh dashboard. SCA scans are enabled by default so you don’t require further configuration actions.
+#. Select the **Configuration Assessment** module on your Wazuh dashboard. SCA scans are enabled by default so you don’t require further configuration actions.
 
    .. thumbnail:: /images/compliance/nist/select-sca-module.png    
       :title: Select the SCA module

source/compliance/nist/file-integrity-monitoring.rst

@@ -44,11 +44,11 @@ In this scenario, the Wazuh FIM monitors the SSH configuration file ``/etc/ssh/s
 
         # sed -re 's/^(PasswordAuthentication)([[:space:]]+)no/\1\2yes/' -i.`date -I` /etc/ssh/sshd_config
 
-#. Select the **Integrity monitoring** tab from the Wazuh dashboard. Find the alert triggered by rule ID ``550``. The alert details show that the content of ``/etc/ssh/sshd_config`` has changed. They include the differences in the file checksum, the modification made, the modification time, and other information.
+#. Select the **File Integrity Monitoring** module from the Wazuh dashboard. Find the alert triggered by rule ID ``550``. The alert details show that the content of ``/etc/ssh/sshd_config`` has changed. They include the differences in the file checksum, the modification made, the modification time, and other information.
 
    .. thumbnail:: /images/compliance/nist/integrity-monitoring-tab.png    
-      :title: Integrity monitoring tab
-      :alt: Integrity monitoring tab
+      :title: File Integrity Monitoring module
+      :alt: File Integrity Monitoring module
       :align: center
       :width: 80%
 

source/compliance/nist/malware-detection.rst

@@ -56,11 +56,11 @@ The Wazuh rootcheck module is enabled by default on the Wazuh agent configuratio
 
       $ sudo systemctl restart wazuh-agent
 
-#. Navigate to the **Security events** dashboard. Search for the event with rule ID ``510``. 
+#. Navigate to the **Threat Hunting** dashboard. Search for the event with rule ID ``510``. 
 
    .. thumbnail:: /images/compliance/nist/security-events-dashboard.png    
-      :title: Security events dashboard
-      :alt: Security events dashboard
+      :title: Threat Hunting dashboard
+      :alt: Threat Hunting dashboard
       :align: center
       :width: 80%
 

source/compliance/nist/visualization-and-dashboard.rst

@@ -6,7 +6,7 @@
 Visualization and dashboard
 ===========================
 
-Wazuh offers a web dashboard for continuous data visualization and analysis. The Wazuh dashboard comes with out-of-the-box modules for: security events, regulatory compliance, detected vulnerable applications, file integrity monitoring, configuration assessment results, and cloud infrastructure monitoring. It helps perform forensic and historical alert analyses.
+Wazuh offers a web dashboard for continuous data visualization and analysis. The Wazuh dashboard comes with out-of-the-box modules for: threat hunting, regulatory compliance, detected vulnerable applications, file integrity monitoring, configuration assessment results, and cloud infrastructure monitoring. It helps perform forensic and historical alert analyses.
 
 The :doc:`Wazuh dashboard </getting-started/components/wazuh-dashboard>` assists in meeting the following NIST 800-53 controls:
 
@@ -24,7 +24,7 @@ Generate a report of successful authentications
 
 This use case shows how Wazuh helps meet the **CA-7 Continuous monitoring** NIST requirement by providing security reporting to administrators. Use the Wazuh dashboard to generate a report of all successful authentications in the last 24 hours:
 
-#. Go to the Wazuh dashboard menu and select **Discover** under **OpenSearch Dashboards**.
+#. Go to the Wazuh dashboard menu and select **Discover** under **Explore**.
 
    .. thumbnail:: /images/compliance/nist/select-discover.png    
       :title: Select Discover