Merge 4.9.1 into 4.10.0

CHANGELOG.md

@@ -19,23 +19,39 @@ All notable changes to the Wazuh app project will be documented in this file.
 
 - Removed agent RBAC filters from dashboard queries [#6945](https://github.com/wazuh/wazuh-dashboard-plugins/pull/6945)
 
-## Wazuh v4.9.1 - OpenSearch Dashboards 2.13.0 - Revision 00
+## Wazuh v4.9.1 - OpenSearch Dashboards 2.13.0 - Revision 01
 
 ### Added
 
 - Support for Wazuh 4.9.1
+- Add feature to filter by field in the events table rows [#6977](https://github.com/wazuh/wazuh-dashboard-plugins/pull/6991)
 
 ### Fixed
 
+- Fixed issue causing vulnerability dashboard to fail loading for read-only users [#6933](https://github.com/wazuh/wazuh-dashboard-plugins/pull/6993)
 - Fixed the temporal directory variable on the the command to deploy a new Windows agent [#6905](https://github.com/wazuh/wazuh-dashboard-plugins/pull/6905)
 - Fixed an error on the command to deploy a new macOS agent that could cause the registration password had a wrong value because a `\n` could be included [#6906](https://github.com/wazuh/wazuh-dashboard-plugins/pull/6906)
 - Fixed rendering an active response as disabled when is active [#6901](https://github.com/wazuh/wazuh-dashboard-plugins/pull/6901)
 - Fixed an error on Dev Tools when using payload properties as arrays [#6908](https://github.com/wazuh/wazuh-dashboard-plugins/pull/6908)
+- Fixed of the font size in the table used in the events tab, in the Threat hunting dashboard tab and in the Vulnerabilities inventory tab [#6987](https://github.com/wazuh/wazuh-dashboard-plugins/pull/6987)
+- Fixed missing link to Vulnerabilities detection and Office 365 in the agent menu of `Endpoints Summary` [#6983](https://github.com/wazuh/wazuh-dashboard-plugins/pull/6983)
+- Fixed missing options depending on agent operating system in the agent configuration report [#6983](https://github.com/wazuh/wazuh-dashboard-plugins/pull/6983)
+- Fixed an style that affected the Discover plugin [#6989](https://github.com/wazuh/wazuh-dashboard-plugins/pull/6989)
+- Fixed a problem updating the API host registry in the GET /api/check-stored-api [#6995](https://github.com/wazuh/wazuh-dashboard-plugins/pull/6995)
 
 ### Changed
 
+- Change the text of the query limit tooltip [#6981](https://github.com/wazuh/wazuh-dashboard-plugins/pull/6981)
 - Upgraded the `axios` dependency to `1.7.4` [#6919](https://github.com/wazuh/wazuh-dashboard-plugins/pull/6919)
 - Improved MITRE ATT&CK intelligence flyout details readability [#6954](https://github.com/wazuh/wazuh-dashboard-plugins/pull/6954)
+- Upgraded Event-tab column selector showing first the picked columns [#6984](https://github.com/wazuh/wazuh-dashboard-plugins/pull/6984)
+- Changed vulnerabilities.reference to links in Vulnerability Detection > Inventory columns [#6960](https://github.com/wazuh/wazuh-dashboard-plugins/pull/6960)
+- Upgraded the `follow-redirects` dependency to `1.15.6` [#6982](https://github.com/wazuh/wazuh-dashboard-plugins/pull/6982)
+- Changed many loading spinners in some views to loading search progress [#6956](https://github.com/wazuh/wazuh-dashboard-plugins/pull/6956)
+
+### Removed
+
+- Removed the XML autoformat function group configuration due to performance [#6999](https://github.com/wazuh/wazuh-dashboard-plugins/pull/6999)
 
 ## Wazuh v4.9.0 - OpenSearch Dashboards 2.13.0 - Revision 07
 

SECURITY.md

@@ -11,19 +11,15 @@ This policy applies to all open source projects developed, maintained, or hosted
 ## Reporting Security Vulnerabilities
 If you believe you've discovered a potential security vulnerability in one of our open source projects, we strongly encourage you to report it to us responsibly.
 
-Please submit your findings as security advisories under the "Security" tab in the relevant GitHub repository. Alternatively, you may send the details of your findings to [email protected].
+Please submit your findings as security advisories under the "Security" tab in the relevant GitHub repository. Alternatively, you may send the details of your findings to [[email protected]](mailto:[email protected]).
 
 ## Vulnerability Disclosure Policy
 Upon receiving a report of a potential vulnerability, our team will initiate an investigation. If the reported issue is confirmed as a vulnerability, we will take the following steps:
 
 1. Acknowledgment: We will acknowledge the receipt of your vulnerability report and begin our investigation.
-
 2. Validation: We will validate the issue and work on reproducing it in our environment.
-
 3. Remediation: We will work on a fix and thoroughly test it
-
 4. Release & Disclosure: After 90 days from the discovery of the vulnerability, or as soon as a fix is ready and thoroughly tested (whichever comes first), we will release a security update for the affected project. We will also publicly disclose the vulnerability by publishing a CVE (Common Vulnerabilities and Exposures) and acknowledging the discovering party.
-
 5. Exceptions: In order to preserve the security of the Wazuh community at large, we might extend the disclosure period to allow users to patch their deployments.
 
 This 90-day period allows for end-users to update their systems and minimizes the risk of widespread exploitation of the vulnerability.
@@ -37,7 +33,7 @@ We believe in giving credit where credit is due. If you report a security vulner
 We do appreciate and encourage feedback from our community, but currently we do not have a bounty program. We might start bounty programs in the future.
 
 ## Compliance with this Policy
-We consider the discovery and reporting of security vulnerabilities an important public service. We encourage responsible reporting of any vulnerabilities that may be found in our site or applications. 
+We consider the discovery and reporting of security vulnerabilities an important public service. We encourage responsible reporting of any vulnerabilities that may be found in our site or applications.
 
 Furthermore, we will not take legal action against or suspend or terminate access to the site or services of those who discover and report security vulnerabilities in accordance with this policy because of the fact.
 
@@ -46,4 +42,4 @@ We ask that all users and contributors respect this policy and the security of o
 ## Changes to this Security Policy
 This policy may be revised from time to time. Each version of the policy will be identified at the top of the page by its effective date.
 
-If you have any questions about this Security Policy, please contact us at [email protected]
+If you have any questions about this Security Policy, please contact us at [[email protected]](mailto:[email protected])

docker/osd-dev/README.md

@@ -1,12 +1,32 @@
 # Wazuh development with Wazuh Stack
 
+## Requirements
+
+- vm.max_map_count=262144
+
+  To modify the vm.max_map_count, you can run this command:
+  `sudo sysctl -w vm.max_map_count=262144`
+
+- jq
+
+  To install jq, you can run this command:
+
+  - In Debian/Ubuntu os:
+    `sudo apt-get install jq`
+  - In RedHat/CentOS:
+    `sudo yum install jq`
+  - In Arch:
+    `sudo pacman -Sy --noconfirm jq`
+  - In MAC:
+    `brew install jq`
+
 ## Usage
 
 Use always the provided script to bring up or down the development
 environment. For example:
 
 ```bash
-./dev.sh 1.2.4 1.2.0 $WZ_HOME up [saml]
+./dev.sh [-o 1.2.4] [-d 1.2.0] $WZ_HOME up [saml]
 ```
 
 The script will ask you all the required parameters to bring up the
@@ -27,7 +47,7 @@ the server using the `--no-base-path`**.
 wazuh-dashboard-plugins to use, so be sure to check out the appropriate version
 before bringing up the environment!**
 
-###  UI Credentials
+### UI Credentials
 
 The default user and password to access the UI at https://0.0.0.0:5601/ are:
 
@@ -42,26 +62,15 @@ version of the OpenSearch Stack. We will only create environments for
 the versions of OpenSearch which will be included into a Wazuh
 version.
 
-`OpenSearch` supported versions:
-- 1.2.4
-- 2.3.0
-- 2.4.0
-- 2.4.1
-
-`OpenSearch Dashboards` supported versions:
-- 1.2.0
-- 2.3.0
-- 2.4.0
-- 2.4.1
-
 We must use official `Wazuh Indexer` and `Wazuh Dashboard` images for
 testing!
 
 This environment will start a working deployment with:
-  - Imposter - a mock server.
-  - Elasticsearch-exporter - Elasticsearch metrics to Prometheus adapter.
-  - OpenSearch single-node cluster.
-  - OpenSearch Dashboards development environment.
+
+- Imposter - a mock server.
+- Elasticsearch-exporter - Elasticsearch metrics to Prometheus adapter.
+- OpenSearch single-node cluster.
+- OpenSearch Dashboards development environment.
 
 The OpenSearch Dashboards development environment includes an already
 bootstrapped Kibana, with all the node modules precompiled and ready to