diff --git a/source/user-manual/manager/wazuh-manager.rst b/source/user-manual/manager/wazuh-manager.rst index 0ba149705a..fa3fa6528c 100644 --- a/source/user-manual/manager/wazuh-manager.rst +++ b/source/user-manual/manager/wazuh-manager.rst @@ -206,7 +206,7 @@ Decoding is the process of analyzing structured or unstructured data, such as lo hostname: '192.168.1.1' program_name: 'sshd' -- **Decoding**: In this phase, the Wazuh analysis engine applies a decoder that matches the log. Decoders extract fields such as user names, IP addresses, error codes, URLs, and any other relevant information contained in the logs. The decoders below match the sample log. These decoders are in the ``/var/ossec/rulesets/decoders/0310-ssh_decoders.xml`` file on the Wazuh server: +- **Decoding**: In this phase, the Wazuh analysis engine applies a decoder that matches the log. Decoders extract fields such as user names, IP addresses, error codes, URLs, and any other relevant information contained in the logs. The decoders below match the sample log. These decoders are in the ``/var/ossec/ruleset/decoders/0310-ssh_decoders.xml`` file on the Wazuh server: .. code-block:: console @@ -276,4 +276,4 @@ Where: By default, the Wazuh server generates alerts for any rule with a level above 2. In this scenario, the log triggers an alert because the rule level is 3 and this will be visible on the Wazuh dashboard. -You can create custom decoders and rules to analyze logs not supported by default. To learn how to create custom rules and decoders, refer to :doc:`custom rules ` and :doc:`custom decoders ` documentation. \ No newline at end of file +You can create custom decoders and rules to analyze logs not supported by default. To learn how to create custom rules and decoders, refer to :doc:`custom rules ` and :doc:`custom decoders ` documentation.