Skip to content

Commit

Permalink
Rebase and review comments.
Browse files Browse the repository at this point in the history
  • Loading branch information
GabrielEValenzuela committed Feb 29, 2024
1 parent da5744c commit 69a067a
Show file tree
Hide file tree
Showing 3 changed files with 23 additions and 3 deletions.
20 changes: 20 additions & 0 deletions source/installation-guide/wazuh-server/step-by-step.rst
Original file line number Diff line number Diff line change
Expand Up @@ -77,6 +77,26 @@ Installing the Wazuh manager
.. note:: The default step-by-step installation credentials are ``admin``:``admin``

#. Configure indexer connection

Edit ``/var/ossec/etc/ossec.conf`` to configure the indexer connection. Set your host indexer IP address and port. You can skip this step if you are not going to use the vulnerability detection capability. For example:

.. code-block:: console
<indexer>
<enabled>yes</enabled>
<hosts>
<host>https://0.0.0.0:9200</host> <!-- Replace with your indexer IP address and PORT -->
</hosts>
<ssl>
<certificate_authorities>
<ca>/etc/filebeat/certs/root-ca.pem</ca>
</certificate_authorities>
<certificate>/etc/filebeat/certs/filebeat.pem</certificate>
<key>/etc/filebeat/certs/filebeat-key.pem</key>
</ssl>
</indexer>
#. Enable and start the Wazuh manager service.

.. include:: /_templates/installations/wazuh/common/enable_wazuh_manager_service.rst
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@ Configuration

The Vulnerability Detection module is enabled by default. You can perform the following steps on the Wazuh server to ensure that the Wazuh Vulnerability Detection module is enabled.

#. Open the ``/var/ossec/etc/ossec.conf`` file on the Wazuh server. Check the Vulnerability Detection module is enabled:
#. Open the ``/var/ossec/etc/ossec.conf`` file on the Wazuh server. Check the Vulnerability Detection module is enabled, if you are going to use the indexer capability, check the IP and PORT of your indexer.

.. code-block:: xml
:emphasize-lines: 2
Expand Down
4 changes: 2 additions & 2 deletions source/upgrade-guide/upgrading-central-components.rst
Original file line number Diff line number Diff line change
Expand Up @@ -176,8 +176,8 @@ When upgrading a multi-node Wazuh manager cluster, run the upgrade in every node
If the ``/var/ossec/etc/ossec.conf`` configuration file was modified, it will not be replaced by the upgrade. You will therefore have to add the settings of the new capabilities manually. More information can be found in :doc:`/user-manual/index`.


.. warning::
Upgrading from Wazuh 4.7.x or lower with the vulnerability detector enabled requires additional steps, related with the indexer connection. For more information, check the :doc:`/user-manual/reference/ossec-conf/indexer` section.
.. note::
Upgrading from Wazuh version 4.7.x or earlier, with the Vulnerability Detector feature enabled, necessitates additional steps pertaining to the indexer connection. These procedures align with those required for a fresh installation of Wazuh. For comprehensive guidance, please consult the "Installing the Wazuh Manager" section within our Installation Guide. Detailed instructions can be accessed at: :doc:`/installation-guide/wazuh-server/step-by-step`.

#. Download the Wazuh module for Filebeat:

Expand Down

0 comments on commit 69a067a

Please sign in to comment.