Fortnight #5 - Merge 4.9.0 into master

.github/ISSUE_TEMPLATE/compatibility_request.md

@@ -0,0 +1,23 @@
+---
+name: Compatibility request
+about: Suggest supporting a new version of OpenSearch
+title: 'Compatibility with OpenSearch (version)'
+labels: compatibility, level/task, type/research
+assignees: ''
+
+---
+
+## Description
+We need to ensure the compatibility with the next version of OpenSearch vX.X.
+This update is still being discussed, but we need to be aware of potential issues.
+
+For that, we need to:
+
+- [ ] Review opensearch's release notes. 
+- [ ] Identify improvements and potential impact.
+- [ ] Create new development branch.
+- [ ] Develop a testing environment to verify our components would work under this new build.
+
+
+## Issues
+-  _List here the detected issues_

ecs/vulnerability-detector/event-generator/event_generator.py

@@ -173,6 +173,9 @@ def generate_random_wazuh():
         'cluster': {
             'name': f'wazuh-cluster-{random.randint(0,10)}',
             'node': f'wazuh-cluster-node-{random.randint(0,10)}'
+        },
+        'manager': {
+            'name': f'wazuh-manager-{random.randint(0,10)}'
         }
     }
     return wazuh

ecs/vulnerability-detector/fields/custom/wazuh.yml

@@ -13,4 +13,9 @@
       type: keyword
       level: custom
       description: >
-        Wazuh cluster node name.
+        Wazuh cluster node name.
+    - name: manager.name
+      type: keyword
+      level: custom
+      description: >
+        Wazuh manager name. Used by dashboards to filter results on single node deployments.

integrations/.gitignore

@@ -0,0 +1,6 @@
+elastic
+opensearch
+splunk
+common
+config
+docker/certs

integrations/README.md

@@ -0,0 +1,37 @@
+## Wazuh indexer integrations
+
+This folder contains integrations with third-party XDR, SIEM and cybersecurity software. 
+The goal is to transport Wazuh's analysis to the platform that suits your needs.
+
+### Amazon Security Lake
+
+Amazon Security Lake automatically centralizes security data from AWS environments, SaaS providers, 
+on premises, and cloud sources into a purpose-built data lake stored in your account. With Security Lake, 
+you can get a more complete understanding of your security data across your entire organization. You can 
+also improve the protection of your workloads, applications, and data. Security Lake has adopted the 
+Open Cybersecurity Schema Framework (OCSF), an open standard. With OCSF support, the service normalizes 
+and combines security data from AWS and a broad range of enterprise security data sources.
+
+##### Usage
+
+A demo of the integration can be started using the content of this folder and Docker.
+
+```console
+docker compose -f ./docker/amazon-security-lake.yml up -d
+```
+
+This docker compose project will bring a *wazuh-indexer* node, a *wazuh-dashboard* node, 
+a *logstash* node and our event generator. On the one hand, the event generator will push events 
+constantly to the indexer. On the other hand, logstash will constantly query for new data and
+deliver it to the integration Python program, also present in that node. Finally, the integration 
+module will prepare and send the data to the Amazon Security Lake's S3 bucket. 
+<!-- TODO continue with S3 credentials setup -->
+
+For production usage, follow the instructions in our documentation page about this matter.
+(_when-its-done_)
+
+As a last note, we would like to point out that we also use this Docker environment for development.
+
+### Other integrations
+
+TBD

integrations/amazon-security-lake/.dockerignore

@@ -0,0 +1,180 @@
+wazuh-event.ocsf.json
+*.parquet
+Dockerfile
+
+# Created by https://www.toptal.com/developers/gitignore/api/python
+# Edit at https://www.toptal.com/developers/gitignore?templates=python
+
+### Python ###
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#pdm.lock
+#   pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
+#   in version control.
+#   https://pdm.fming.dev/#use-with-ide
+.pdm.toml
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#  and can be added to the global gitignore or merged into this file.  For a more nuclear
+#  option (not recommended) you can uncomment the following to ignore the entire idea folder.
+#.idea/
+
+### Python Patch ###
+# Poetry local configuration file - https://python-poetry.org/docs/configuration/#local-configuration
+poetry.toml
+
+# ruff
+.ruff_cache/
+
+# LSP config files
+pyrightconfig.json
+
+# End of https://www.toptal.com/developers/gitignore/api/python