Wazuh架构与Docker Compose部署
Wazuh 4.9模块化部署指南,在Docker容器中分配复杂字母数字凭据并配置安全端口路由。
0阅读
本指南详细说明在单节点 Docker 环境(single-node)中部署 Wazuh 4.9 的标准技术流程。本模块涵盖资源规划、主机环境准备、docker-compose.yml 文件结构以及网络安全路由架构。
为避免 Docker 引擎在容器初始化时发生解析错误(例如在 YAML 文件中错误解释特殊字符 $ 或 *),并严格遵守 Wazuh 的安全策略,已为核心服务定义了一组高熵字母数字凭据矩阵:
| 组件/服务 | 标识/用户 | 虚拟示例密码 | 集成说明 |
|---|---|---|---|
| Wazuh接口(索引器) | 管理员 | zR9mK2vX5pW8qN3tY6cR4vB1 | 主Web管理访问账户。 |
| 内部Wazuh API | wazuh-wui | mP5nT8qB2vK9wR3xY6cS4dB9. | 必须以点号 . 结尾,以符合符号策略要求。 |
| 通信服务 | kibanaserver | yQ3wV8xR9pK2mN6tT5sR4vC1 | 用于节点间内部通信的账户。 |
2. 主机环境供应 (Ubuntu)
Sección titulada «2. Aprovisionamiento del Entorno en el Host (Ubuntu)»完整部署将整合在主机目录下:/opt/wazuh-stack/single-node。
Wazuh 需要 SSL/TLS 证书来对其三个主要容器(Indexer、Manager 和 Dashboard)之间的通信进行端到端加密。请登录主机控制台,并克隆经过认证的精确版本(v4.9.0):
# 1. Crear el directorio y clonar el repositorio oficial de desplieguesudo mkdir -p /opt/wazuh-stacksudo chown -R $USER:$USER /opt/wazuh-stackgit clone https://github.com/wazuh/wazuh-docker.git -b v4.9.0 /opt/wazuh-stack
# 2. Posicionarse en el directorio del nodo únicocd /opt/wazuh-stack/single-node初始化临时生成容器以自动配置公钥基础设施(PKI)和服务数字签名:
sudo docker compose -f generate-indexer-certs.yml run --rm generator3. 生产环境Docker Compose文件
Sección titulada «3. Archivo Docker Compose de Producción»该文件包含服务的最终声明,优化的内核内存限制和环境的初始静态凭据。
文件路径:/opt/wazuh-stack/single-node/docker-compose.yml
# Wazuh App Copyright (C) 2017, Wazuh Inc. (License GPLv2)services: wazuh.manager: image: wazuh/wazuh-manager:4.9.0 hostname: wazuh.manager restart: always ports: - "1514:1514" - "1515:1515" - "514:514/udp" - "55000:55000" ulimits: memlock: soft: -1 hard: -1 nofile: soft: 655360 hard: 655360 environment: - INDEXER_URL=https://wazuh.indexer:9200 - INDEXER_USERNAME=admin - INDEXER_PASSWORD=zR9mK2vX5pW8qN3tY6cR4vB1 - FILEBEAT_SSL_VERIFICATION_MODE=full - SSL_CERTIFICATE_AUTHORITIES=/etc/ssl/root-ca.pem - SSL_CERTIFICATE=/etc/ssl/filebeat.pem - SSL_KEY=/etc/ssl/filebeat.key - API_USERNAME=wazuh-wui - API_PASSWORD=mP5nT8qB2vK9wR3xY6cS4dB9. - TZ=Europe/Madrid volumes: - wazuh_api_configuration:/var/ossec/api/configuration - wazuh_etc:/var/ossec/etc - wazuh_logs:/var/ossec/logs - wazuh_queue:/var/ossec/queue - wazuh_var_multigroups:/var/ossec/var/multigroups - wazuh_integrations:/var/ossec/integrations - wazuh_active_response:/var/ossec/active-response/bin - wazuh_agentless:/var/ossec/agentless - wazuh_wodles:/var/ossec/wodles - filebeat_etc:/etc/filebeat - filebeat_var:/var/lib/filebeat - ./config/wazuh_indexer_ssl_certs/root-ca-manager.pem:/etc/ssl/root-ca.pem - ./config/wazuh_indexer_ssl_certs/wazuh.manager.pem:/etc/ssl/filebeat.pem - ./config/wazuh_indexer_ssl_certs/wazuh.manager-key.pem:/etc/ssl/filebeat.key - ./config/wazuh_cluster/wazuh_manager.conf:/wazuh-config-mount/etc/ossec.conf
wazuh.indexer: image: wazuh/wazuh-indexer:4.9.0 hostname: wazuh.indexer restart: always ports: - "9200:9200" environment: - "OPENSEARCH_JAVA_OPTS=-Xms1g -Xmx1g" - TZ=Europe/Madrid ulimits: memlock: soft: -1 hard: -1 nofile: soft: 65536 hard: 65536 volumes: - wazuh-indexer-data:/var/lib/wazuh-indexer - ./config/wazuh_indexer_ssl_certs/root-ca.pem:/usr/share/wazuh-indexer/certs/root-ca.pem - ./config/wazuh_indexer_ssl_certs/wazuh.indexer-key.pem:/usr/share/wazuh-indexer/certs/wazuh.indexer.key - ./config/wazuh_indexer_ssl_certs/wazuh.indexer.pem:/usr/share/wazuh-indexer/certs/wazuh.indexer.pem - ./config/wazuh_indexer_ssl_certs/admin.pem:/usr/share/wazuh-indexer/certs/admin.pem - ./config/wazuh_indexer_ssl_certs/admin-key.pem:/usr/share/wazuh-indexer/certs/admin-key.pem - ./config/wazuh_indexer/wazuh.indexer.yml:/usr/share/wazuh-indexer/opensearch.yml - ./config/wazuh_indexer/internal_users.yml:/usr/share/wazuh-indexer/opensearch-security/internal_users.yml
wazuh.dashboard: image: wazuh/wazuh-dashboard:4.9.0 hostname: wazuh.dashboard restart: always ports: - "443:5601" environment: - INDEXER_USERNAME=admin - INDEXER_PASSWORD=zR9mK2vX5pW8qN3tY6cR4vB1 - WAZUH_API_URL=https://wazuh.manager - DASHBOARD_USERNAME=kibanaserver - DASHBOARD_PASSWORD=yQ3wV8xR9pK2mN6tT5sR4vC1 - API_USERNAME=wazuh-wui - API_PASSWORD=mP5nT8qB2vK9wR3xY6cS4dB9. - TZ=Europe/Madrid volumes: - ./config/wazuh_indexer_ssl_certs/wazuh.dashboard.pem:/usr/share/wazuh-dashboard/certs/wazuh-dashboard.pem - ./config/wazuh_indexer_ssl_certs/wazuh.dashboard-key.pem:/usr/share/wazuh-dashboard/certs/wazuh-dashboard-key.pem - ./config/wazuh_indexer_ssl_certs/root-ca.pem:/usr/share/wazuh-dashboard/certs/root-ca.pem - ./config/wazuh_dashboard/opensearch_dashboards.yml:/usr/share/wazuh-dashboard/config/opensearch_dashboards.yml - ./config/wazuh_dashboard/wazuh.yml:/usr/share/wazuh-dashboard/data/wazuh/config/wazuh.yml - wazuh-dashboard-config:/usr/share/wazuh-dashboard/data/wazuh/config - wazuh-dashboard-custom:/usr/share/wazuh-dashboard/plugins/wazuh/public/assets/custom depends_on: - wazuh.indexer links: - wazuh.indexer:wazuh.indexer - wazuh.manager:wazuh.manager
networks: default: name: wazuh_local
volumes: wazuh_api_configuration: wazuh_etc: wazuh_logs: wazuh_queue: wazuh_var_multigroups: wazuh_integrations: wazuh_active_response: wazuh_agentless: wazuh_wodles: filebeat_etc: filebeat_var: wazuh-indexer-data: wazuh-dashboard-config: wazuh-dashboard-custom:为了允许蓝队分析人员正确配置外围过滤规则(如pfSense防火墙或主机策略),详细说明了映射端口的技术功能:
A. 容器:wazuh.manager(分析大脑)
Sección titulada «A. Contenedor: wazuh.manager (Cerebro de Análisis)»1514(TCP/UDP) - 代理:关键通信端口。远程收集代理通过此端口实时发送解密后的日志和元数据。1515(TCP) - Authd:代理注册服务端口。仅用于在配对新节点时生成并传输对称加密密钥。514(UDP) - Syslog:可选服务,用于收集不支持原生代理的网络设备日志(如路由器、pfSense 防火墙和交换机)。55000(TCP) - REST API:Manager 控制接口。Dashboard 调用该接口处理内部管理查询。
B. 容器:wazuh.indexer(存储)
Sección titulada «B. Contenedor: wazuh.indexer (Almacenamiento)»9200(TCP) - OpenSearch API:索引数据库读写端口。Filebeat 将告警写入此处,Dashboard 从该端口读取数据并在图表中展示。
C. 容器:wazuh.dashboard(Web 控制台)
Sección titulada «C. Contenedor: wazuh.dashboard (Consola Web)»443 ➔ 5601(TCP) - HTTPS 门户:内部服务使用端口5601,但在 Docker 中映射到主机的标准端口 443 (HTTPS),以便从浏览器直接、简洁地访问,无需指定非常规端口。
配置好 docker-compose.yml 文件后,在后台启动基础设施:
sudo docker compose up -d安全警告
尽管容器在Docker引擎中正确初始化,但在生成并注入以下文档中详细说明的加密哈希值之前,该套件将无法正常运行或保持安全。

