防护思路
点击放大

This repository packages a small SOC-style monitoring en built around Wazuh, Prometheus, Grafana, Alertmanager, Blackbox Exporter, and an internal service index page. It is structured for local deployment first, with the root stack handling monitoring and alert delivery while the bundled wazuh-docker-stack/ directory provides the Wazuh platform and recovery assets.
wazuh-docker-stack/: Wazuh deployment assets, Docker Compose stacks, and recovery automationThe root monitoring stack expects the external Docker single-node_wazuh_logs to exist, which is provided by the single-node Wazuh deployment.
1. Copy .en to .env and adjust for your en.
2. Create required local-only secrets under secrets/.
3. Generate gateway credentials with scripts/windows/In.ps1.
4. Review targets/ping_servers.yml and update monitored hosts.
5. Start the Wazuh single-node stack from wazuh-docker-stack/single-node/.
6. Start the monitoring stack from the repository root with docker compose up -d.
docker-compose.yml: root monitoring servicesprometheus.yml: scrape jobs and alerting targetsblackbox.yml: Blackbox Exporter probe modulesalert.rules.yml: stack health and ICMP probe alertsalertmanager.yml: notification routinggrafana/: pro datasource and monitoring dashboardstargets/ping_servers.yml: file-based ICMP target intargets/sensor_http_endpoints.yml: Pi-hole and mitmproxy HTTP probe intargets/sensor_tcp_endpoints.yml: mitmproxy TCP probe intargets/sensor_dns_endpoints.yml: Pi-hole DNS probe indocs/runbooks/phase1-rollout.md: staged rollout and rollback notesdocs/runbooks/wazuh-single-node-rollout.md: guarded Wazuh single-node rollout pathdocs/runbooks/sensor-.md: canonical Ubuntu sensor deployment pathdocs/runbooks/secret-vault.md: encrypted local secret export, import, and rekey workflowdocs/runbooks/bare-metal-rebuild-drill.md: staged clean-host rebuild rehearsal from the recovery bundle and secret vaultdocs/runbooks/ubuntu-lightweight-soc.md: low-resource Ubuntu SOC profile with Suricata, Cowrie, Wazuh ingestion, and Grafanadocs/reference/repository-layout.md: folder map for source-of-truth files recovery artifactsdocs/operator-handbook/README.md: installation, troubleshooting, tools usage, access in, and threat monitoring guidesdocs/pdf-handbook/README.md: offline PDF export set in one folderscripts/windows/Inion.ps1: mo secrets into gitignored secret filesscripts/windows/Inlout.ps1: rollout helperscripts/windows/Inout.ps1: Wazuh single-node rollout helperscripts/windows/In.ps1: create or rotate local HTTPS gateway credentialsscripts/windows/In.ps1: encrypt local secret files into one vault filescripts/windows/In.ps1: restore local secret files from the encrypted vaultscripts/windows/In.ps1: rotate the encrypted vault passphrasescripts/windows/Inll.ps1: stage a clean-host rebuild drill from the recovery bundle and secret vault, including staged sensor bootstrap and archiscripts/windows/In.ps1: Windows entrypoint for the canonical sensor bootstrapscripts/windows/Inport.ps1: local-only credential export generatorscripts/windows/Incher.ps1: local-only launcher for the public index, private credentials, and PDFsscripts/windows/Inose.ps1: local secret-aware wrapper for Wazuh single-node compose commands.github/workflows/ci-smoke-checks.yml: repo smoke for compose rendering, config checks, gateway , and one Blackbox probescripts/python/monitoring_ser.py: internal browser page for service health, links, and PDF docsPhase 1 standardizes the Ubuntu sensor on one declared blueprint instead of multiple inline-generated installers.
wazuh-docker-stack/single-node/reco/blueprints/sensor-vm/scripts/windows/In.ps1scripts/linux/bootstrap_sensor_vm.shThe older Ubuntu install scripts under scripts/linux/ and scripts/windows/ remain in the repo only as compatibility wrappers that delegate to the canonical bootstrap.
The canonical sensor path now also defaults Pi-hole and mitmproxy to pinned digests through the blueprint and Windows wrapper.
This repository is prepared for public Git hosting:
.env, dashboard credentials, and certificate material remain untrackedlocal/secret-vault/Before deploying, create or supply these local-only inputs yourself:
.envsecrets/bre.txtsecrets/gateway_admin_username.txtsecrets/gateway_admin_password.txtsecrets/gateway_admin_password_hash.txtsecrets/grafana_admin_username.txtsecrets/grafana_admin_password.txtsecrets/.txtsecrets/.txtsecrets/pihole_web_password.txtwazuh-docker-stack/secrets/indexer_password.txtwazuh-docker-stack/secrets/api_password.txtwazuh-docker-stack/secrets/dashboard_password.txtThe generated PDF handbook li docs/pdf-handbook/ and is served by the monitoring service index on .
Use scripts/windows/In.ps1 to generate or rotate the gateway credential files locally.
Use scripts/windows/In.ps1 to keep an encrypted backup of the local secret state.
Use scripts/windows/Inll.ps1 to rehearse a clean monitoring-host rebuild and staged sensor recovery before you need a real recovery.
wazuh-docker-stack/single-node/ is the source of truth for the li stack.wazuh-docker-stack/single-node/reco/blueprints/sensor-vm/ is the only tracked clean-build blueprint.wazuh-docker-stack/single-node/reco/backups/ is the timestamped recovery history, not a second source tree.projects/ubuntu-lightweight-soc/ is the dedicated 4 GB Ubuntu SOC lab profile.local/, logs/, and archives/ hold machine-local or generated operational artifacts.开发语言:PowerShell
Star 数:1
该项目属于防护思路方向的开源资源,代码结构清晰,适合安全研究人员学习参考。项目围绕Wazuh-based security monitoring lab with Docker and defensive engineering workflows.展开,提供了可运行的实现,对理解相关安全机制、工具原理与攻防技术具有较高的研究价值。
从技术实现角度看,此类项目的核心在于对底层原理的深入理解与工程化落地。开发者在研究过程中可以结合官方文档与社区讨论,梳理项目的初始化流程、核心模块职责与数据流转,逐步掌握其中的技术细节与设计思路。
1. 下载源码压缩包,解压到本地环境。
2. 根据项目类型准备对应的运行环境与依赖。
3. 按照 README 中的步骤完成配置与部署。
4. 在隔离的测试环境中运行验证,避免影响生产系统。
本资源来源于开源社区,仅供安全研究、技术学习与合法授权范围内的攻防演练使用,请勿用于任何非法或侵害他人权益的用途。使用本项目产生的一切后果由使用者自行承担。
| 资源标题 | wazuh-docker-stack-2 - Wazuh-based security monitoring lab with Docker an |
| 所属分类 | 防护思路 |
| 发布作者 | admin |
| 发布时间 | 2026-10-06 00:25:08 |
| 下载权限 | 免费下载 |
| 附件数量 | 2 个下载链接 |
| 浏览次数 | 372 |
| 讨论数量 | 0 |
| 主题状态 | 正常讨论中 |